The Complete Drupal SEO Guide

Most of what you already do for search still works. What changed is that ranking is no longer the whole job: a search engine or an assistant now decides whether your page is worth quoting before a reader ever sees it. This guide separates the work that still earns a return from the AI-specific deliverables agencies are currently charging for.

Search and AI visibility for enterprise Drupal teams

Search stopped being a list of ten links. Ranking a page and earning a click still matters, but that job now sits inside a larger one: being the source a search engine or an AI assistant reaches for when it answers a question. This edition of the guide covers both, and separates what actually changed from what is being sold as change.

What is inside

Eight chapters, each opening with a direct answer.

1. How search visibility actually works now. The five surfaces a Drupal site can appear in, why indexing is the gate for all of them, and how retrieval-augmented generation and query fan-out change the way you plan content.
    
2. What on-page work still moves the needle. Eight things: clean URLs, titles that earn the click, accurate meta descriptions, descriptive alt text, genuine topical coverage, parseable structure, Core Web Vitals inside threshold, and a deliberate internal link graph. None of them are new. All of them are still where the return is.
    
3. Where to start. Three inventories: what you already rank for, what your buyers actually ask, and where AI assistants send those buyers instead of you.
    
4. How to plan and write content that gets cited. Page types and their jobs, the pillar-and-spoke model under query fan-out, and a content brief template built around a point of view and sourced evidence rather than density and word count.
    
5. How to earn authority off-page. Original research, open-source contribution, named-expert placements, conference presence, and digital PR. Why volume link acquisition is a liability with no upside.
    
6. How to be visible in AI answers. What is genuinely different (crawler access, extractability, verifiable evidence, and measurement) and the long list of AI-specific deliverables agencies are currently charging for that Google says it does not use.
    
7. What Drupal gives you that other platforms make you build. Structured content modelling, granular editorial governance, multilingual in core, and full control of the output HTML. Plus the eight modules worth deploying, and where Varbase fits.
    
8. How to measure and govern this over time. Four instruments, one monthly cadence, one quarterly audit, one named owner.

What you will be able to do

By the end of the guide, you will be able to:

• Diagnose whether your visibility problem is an indexing, ranking, or retrieval problem, and fix the right one.
   
• Audit crawler access across robots.txt and your CDN, and make a deliberate decision per AI provider instead of inheriting a blanket 2023 block.
   
• Run keyword research in two layers: the queries people type into Google, and the prompts they type into an assistant.
   
• Build a standing prompt set of twenty to forty buyer-relevant prompts and measure your AI citations monthly.
   
• Write a content brief that specifies a point of view and a named source for every statistic.
   
• Structure pages so any single section can be lifted and still make sense, which is what decides whether you get quoted.
   
• Get Core Web Vitals inside threshold on field data, not lab scores, including the INP problems that JavaScript-heavy pages hide.
   
• Deploy the right Drupal SEO module stack, and know when to prefer core over contrib over custom.
   
• Set up a measurement dashboard that reads impressions and clicks together, because impressions up with clicks down is now normal.

Who it is for

Marketing and technology leaders responsible for an enterprise Drupal platform:

• The VP of Marketing, who owns the digital experience and needs to know whether AI visibility is a new budget line or the same work.
   
• The CTO or CIO, who owns the risk, including the December 2026 Drupal 10 end-of-life.
   
• Architects and developers, who implement it.

It assumes a supported Drupal version and a site with real content, not a blank install.

One thing to check first: Drupal 10 reaches end of life on 9 December 2026, and Drupal 12 is scheduled for the week of 7 December 2026. If your platform is on an unsupported branch, the SEO work in this guide is the second priority. The upgrade is the first.

Why Vardot wrote this

We are a Drupal partner, so read the platform chapter knowing where it comes from. Everything in the guide is a claim we would defend in a technical evaluation rather than in a brochure.

• More than 200 enterprise Drupal platforms delivered, for organisations including UNHCR, UNICEF, BCG, and Georgetown University
   
• Drupal Diamond Certified Partner
   
• Top 20 Drupal contributor worldwide, with more than 6,000 contribution credits
   
• Gold Sponsor of the Drupal AI Initiative
   
• 4.9 out of 5 on Clutch across 58+ verified reviews

Those are public records anyone can check, which is what makes them useful. "A leading Drupal agency" is not checkable, and reads as noise to a system trying to assemble a factual answer.

Where to go next

Download the guide, then start with an audit: a structured review of security, performance, SEO, accessibility, and AI readiness that produces a prioritised list of what to fix and in what order.