Your Drupal site is a content framework, not a WordPress blog — and it needs SEO built for how Drupal actually renders, deploys, and gets crawled by Google and AI engines.
We’re a Drupal-focused SEO team. We do the work Drupal’s editor leaves in your hands — Views crawl control, Metatag token architecture, configuration deployment safety, migration protection, headless coordination, and AI search readiness. Everything on this page is what we do, how we do it, and what it costs — no inflated claims, no ranking guarantees.
Founder & Drupal SEO Lead, WLM Agency
Leads WLM’s Drupal SEO practice. Seven years in search across SEO, GEO, AEO, ASO and Local SEO, with an operational focus on Drupal. Attended DrupalCon Vienna 2025 and Chicago 2026. Documentation-first — every audit finding ships with the affected URL, the evidence, the fix, and the acceptance criteria.
Drupal SEO isn’t one task. It’s a discipline applied across the parts of the platform that decide what Google and AI engines actually receive — the content model, the URL layer, the rendered output, the deployment pipeline, and the search-facing configuration. Everything below is delivered in-house on Drupal projects. Nothing is subcontracted. Nothing is aspirational.
A complete audit built on a rendered-output crawl — the way Googlebot and AI crawlers actually see your site — not an admin-panel walkthrough. We check resolved Metatag tokens, rendered Twig output, canonical tags as they appear in the HTML, Views pagination behaviour, taxonomy term-page indexability, and media-entity URL exposure. Findings ship as developer-ready tickets: severity, affected URLs, evidence, recommended fix, acceptance criteria.
Pathauto pattern architecture with collision prevention. Redirect module governance with chain and loop detection. Canonical consolidation across language and domain variants. Simple XML Sitemap configuration with entity-type inclusion rules. Metatag token configuration at the entity-type level — with empty-field handling so meta descriptions never render blank. Heading hierarchy verified against rendered Twig, not assumed from the admin.
Schema.org Metatag configuration for JSON-LD output, mapped per entity bundle. Schema.org Blueprints for content-model-first structured data. Every schema type validated against rendered HTML with Google’s Rich Results Test — not assumed correct from admin configuration. Structured data is also the single biggest lever for getting cited by AI engines, which we cover below.
Keyword and content strategy mapped to Drupal’s entity model — content types, bundles, fields, taxonomy vocabularies, Views-driven landing pages — instead of a flat list of pages. Every content type gets a deliberate SEO purpose. Every taxonomy vocabulary gets a decision: promoted into an indexable landing page, used for navigation only, or noindexed.
The most common source of Drupal crawl waste, and the least understood outside the specialist community. We audit every View for exposed-filter parameter URLs, paginated crawl surfaces, sort-order duplicate pages, and Ajax-refresh behaviour. Every taxonomy vocabulary reviewed for whether its term pages deserve to be indexable — or are quietly cannibalizing your real landing pages. Often the highest-impact work on a project.
Drupal’s native translation system is one of the best in any CMS — but translated aliases drift, hreflang points to the wrong page after alias changes, untranslated fallback content confuses Google, and multilingual sitemaps miss language variants. We configure language-specific Metatag tokens and validate hreflang across every language pair against rendered output.
What almost nobody outside the Drupal community talks about — and where quiet catastrophes happen. Every Drupal deployment moves configuration between environments. If robots.txt, canonical base URLs, noindex settings, or Metatag defaults get exported from staging, they silently overwrite production — and your SEO resets on a release nobody flagged as risky. We set up Config Split rules that isolate environment-specific SEO settings, build post-deployment QA checklists, and add regression testing so a routine deploy never quietly de-indexes your site. This is the work we’re known for.
Reports, audits and deliverables carry your loaDrupal 7 → Drupal 11 migrations. Drupal 9 or 10 → Drupal 11 upgrades. Domain moves. Headless transitions. Platform replatforming. Every indexable URL inventoried. Every redirect mapped one-to-one — never bulk-redirected to the homepage. Search Console and server logs monitored for ninety days after launch, with a documented recovery protocol if regressions appear.go, not ours. Your client never sees WLM.
When Drupal serves content through JSON:API or GraphQL and a framework like Next.js renders the site, SEO responsibility splits across two systems — and things fall through the seam. Metadata generation, canonical tags, sitemap URLs, structured data, and JavaScript-free internal-link crawlability all move to the front end. We define ownership boundaries and ensure parity between what Drupal stores and what Google — and AI crawlers — actually receive.
AI engines — ChatGPT, Perplexity, Google AI Overviews, Gemini — cite only a handful of sources per answer, and they read the raw HTML your server returns, not JavaScript-rendered content. Drupal has a real structural advantage here: server-side rendering by default, clean semantic HTML, and JSON-LD via Schema.org Metatag. We build on that with extractable content structure, entity consistency, valid structured data, and — where it fits — Drupal’s LLM-optimized content tooling (the Markdownify module and the AI LLM Optimized Content recipe) to expose clean, token-efficient versions of your pages for AI systems. The goal: get your Drupal content cited in generative answers, not just ranked in blue links.
These are the failure patterns we find on almost every Drupal site built without SEO oversight. Each one is specific to how Drupal works. If your current agency can’t explain these, they’re doing WordPress SEO on a Drupal site.
Every exposed filter on a View — department, category, date, format — creates a unique parameter URL. Google crawls every permutation. We’ve seen a 4,000-page site generate 11,000+ indexable URLs this way. We audit every View and control which parameter surfaces are crawlable.
A staging robots.txt or a noindex setting exported to production during a routine deploy can de-index your site overnight — and nobody notices until traffic drops. Config Split rules and post-deploy QA stop this. This is the single most damaging Drupal-specific SEO failure, and the least discussed.
Metatag uses tokens to pull metadata from fields. When a field is empty, a poorly-configured token renders a blank meta description — silently, across hundreds of pages. We configure fallback chains so metadata always resolves to something useful.
Drupal makes taxonomy term pages indexable by default. Those auto-generated, thin term pages often rank instead of the program or product pages they should be supporting — splitting your ranking signals. We decide, per vocabulary, what earns indexation.
Change a Pathauto pattern mid-life and every internal link built on the old alias now points at a 301. Hundreds or thousands of unnecessary redirect hops, diluting crawl efficiency. We audit internal links against current aliases and fix at the source.
When a Next.js or React front end renders your Drupal content, critical metadata, canonicals, and structured data often never make it into the server-rendered HTML. Google struggles; AI crawlers — which don’t execute JavaScript at all — see an empty shell and can’t cite you. We enforce parity between what Drupal stores and what actually renders server-side.
Drupal’s translation system is excellent — until translated aliases are updated without maintaining Multilingual Associations. Then hreflang tags point to 404s or the wrong language variant, and Google serves the wrong page to the wrong country. We validate hreflang across every language pair against rendered output.
Drupal exposes media entities at /media/[id] URLs. Left unmanaged, that’s hundreds or thousands of thin, orphaned pages in the index, wasting crawl budget on files instead of content. We noindex or block them deliberately.
Drupal sites aren’t comparable. A 50-page brochure site and a 15,000-page multilingual multisite are different projects, and pricing that pretends otherwise won’t survive contact with your actual site. Start with the free audit — it tells us both exactly what your site needs.
A complete technical and content audit of your Drupal site, using the same rendered-output methodology we run on paid engagements — free, because we’d rather show you the work than describe it.
Ongoing Drupal SEO for sites on Drupal 10 or 11 that need continuous technical optimization, content work, deployment QA, and steady authority building.
Technical work every month
Content & AI search
For projects that don’t fit a standard retainer: migrations, complex upgrades, multisite, headless, or ongoing white-label delivery for agencies.
Prices are transparent starting points. Actual scope is confirmed after the free audit or a discovery call — because pricing that survives contact with your Drupal site is more useful than pricing that looks clean on a page.
Drupal SEO isn’t one task. It’s a discipline applied across the parts of the platform that decide what Google and AI engines actually receive — the content model, the URL layer, the rendered output, the deployment pipeline, and the search-facing configuration. Everything below is delivered in-house on Drupal projects. Nothing is subcontracted. Nothing is aspirational.
A complete audit built on a rendered-output crawl — the way Googlebot and AI crawlers actually see your site — not an admin-panel walkthrough. We check resolved Metatag tokens, rendered Twig output, canonical tags as they appear in the HTML, Views pagination behaviour, taxonomy term-page indexability, and media-entity URL exposure. Findings ship as developer-ready tickets: severity, affected URLs, evidence, recommended fix, acceptance criteria.
Pathauto pattern architecture with collision prevention. Redirect module governance with chain and loop detection. Canonical consolidation across language and domain variants. Simple XML Sitemap configuration with entity-type inclusion rules. Metatag token configuration at the entity-type level — with empty-field handling so meta descriptions never render blank. Heading hierarchy verified against rendered Twig, not assumed from the admin.
Schema.org Metatag configuration for JSON-LD output, mapped per entity bundle. Schema.org Blueprints for content-model-first structured data. Every schema type validated against rendered HTML with Google’s Rich Results Test — not assumed correct from admin configuration. Structured data is also the single biggest lever for getting cited by AI engines, which we cover below.
Keyword and content strategy mapped to Drupal’s entity model — content types, bundles, fields, taxonomy vocabularies, Views-driven landing pages — instead of a flat list of pages. Every content type gets a deliberate SEO purpose. Every taxonomy vocabulary gets a decision: promoted into an indexable landing page, used for navigation only, or noindexed.
The most common source of Drupal crawl waste, and the least understood outside the specialist community. We audit every View for exposed-filter parameter URLs, paginated crawl surfaces, sort-order duplicate pages, and Ajax-refresh behaviour. Every taxonomy vocabulary reviewed for whether its term pages deserve to be indexable — or are quietly cannibalizing your real landing pages. Often the highest-impact work on a project.
Drupal’s native translation system is one of the best in any CMS — but translated aliases drift, hreflang points to the wrong page after alias changes, untranslated fallback content confuses Google, and multilingual sitemaps miss language variants. We configure language-specific Metatag tokens and validate hreflang across every language pair against rendered output.
What almost nobody outside the Drupal community talks about — and where quiet catastrophes happen. Every Drupal deployment moves configuration between environments. If robots.txt, canonical base URLs, noindex settings, or Metatag defaults get exported from staging, they silently overwrite production — and your SEO resets on a release nobody flagged as risky. We set up Config Split rules that isolate environment-specific SEO settings, build post-deployment QA checklists, and add regression testing so a routine deploy never quietly de-indexes your site. This is the work we’re known for.
Reports, audits and deliverables carry your loaDrupal 7 → Drupal 11 migrations. Drupal 9 or 10 → Drupal 11 upgrades. Domain moves. Headless transitions. Platform replatforming. Every indexable URL inventoried. Every redirect mapped one-to-one — never bulk-redirected to the homepage. Search Console and server logs monitored for ninety days after launch, with a documented recovery protocol if regressions appear.go, not ours. Your client never sees WLM.
When Drupal serves content through JSON:API or GraphQL and a framework like Next.js renders the site, SEO responsibility splits across two systems — and things fall through the seam. Metadata generation, canonical tags, sitemap URLs, structured data, and JavaScript-free internal-link crawlability all move to the front end. We define ownership boundaries and ensure parity between what Drupal stores and what Google — and AI crawlers — actually receive.
AI engines — ChatGPT, Perplexity, Google AI Overviews, Gemini — cite only a handful of sources per answer, and they read the raw HTML your server returns, not JavaScript-rendered content. Drupal has a real structural advantage here: server-side rendering by default, clean semantic HTML, and JSON-LD via Schema.org Metatag. We build on that with extractable content structure, entity consistency, valid structured data, and — where it fits — Drupal’s LLM-optimized content tooling (the Markdownify module and the AI LLM Optimized Content recipe) to expose clean, token-efficient versions of your pages for AI systems. The goal: get your Drupal content cited in generative answers, not just ranked in blue links.
What we did: A six-month engagement in three phases: technical cleanup prioritized by impact, then content-model restructuring for the vocabularies we promoted into real landing pages, then ongoing optimization and deployment QA. We consolidated the indexable surface from 11,400 to 3,800. Rebuilt twelve taxonomy vocabularies as proper landing pages with curated Views displays and unique content. Fixed 2,200 redirect chains in one coordinated deployment. Rebuilt Multilingual Associations across all three languages and revalidated hreflang against rendered output. Implemented Config Split to isolate environment-specific SEO settings, and added a fifteen-item SEO QA checklist to the release process. Implemented Schema.org Metatag for EducationalOrganization, Course, Event, and Article types — which also made the department pages far more extractable for Google AI Overviews, increasingly where prospective students start their research.
Indexed URL bloat
Organic dept traffic
Inquiry submissions
Ranking loss
Results reflect a real engagement over approximately eight months. The numbers are accurate for this project. We don’t guarantee the same outcomes elsewhere — search depends on your market, competition, content, and starting point. What we guarantee is the methodology.
Want the full breakdown? The complete case study — the technical audit findings, the exact Config Split structure we built, the URL restructuring plan, and the month-by-month recovery curve — is available on request. We share it after a short conversation to confirm you’re a fit (we don’t send full engagement details to competitors).
SEO work on Drupal isn’t one fixed thing. The release you’re running decides what needs to happen next, what breaks if you wait, and how urgent the timeline is. Here’s where your site sits in the platform’s support lifecycle right now — and what each position means for search.
Current
The healthiest place to be. Roughly half the database queries per request compared to 11.3, and new default robots.txt rules that block search-parameter URLs — closing a crawl-waste problem that generated infinite indexable combinations on faceted Drupal search pages for years. If you’re here, the work is optimization, not rescue.
EOL Dec 9, 2026
Not a distant deadline — it’s months away. Every Drupal 10 site needs a planned upgrade to Drupal 11 before that date, with compatibility remediation, template changes, and SEO regression testing so rankings survive the jump. Drupal 12 ships the same week (December 2026), but the right target is Drupal 11.5 LTS first, not a direct leap to 12.
Unsupported Nov 2023
Sites still on Drupal 9 are running unsupported software and quietly accumulating both security and SEO debt. The pragmatic move is a single planned project landing on Drupal 11.
Ended Jan 5, 2025
A move from D7 to D11 is not an upgrade — it’s a full migration. Content model, module ecosystem, theme layer, and URLs are all different. This is where most agencies quietly lose rankings. It’s also where we do our most careful work: every indexable URL inventoried, every redirect mapped one-to-one, ninety days of post-launch monitoring.
Ships Dec 2026
Arrives alongside Drupal 11.5 LTS. The pragmatic path for most teams: land on 11.5 LTS first, then evaluate Drupal 12 adoption over the following year. We build to what’s stable, not what’s aspirational.
These are the failure patterns we find on almost every Drupal site built without SEO oversight. Each one is specific to how Drupal works. If your current agency can’t explain these, they’re doing WordPress SEO on a Drupal site.
How it works
You own the client relationship, set the price, and keep the margin. We deliver through your project channel, work under your brand on every audit, ticket, and report, and never contact your client directly. NDA and non-solicitation on every engagement.
Where our depth complements yours
If your team is strong on Drupal development but generalist on SEO, we cover the layer where Drupal-specific SEO problems live: Views exposed-filter crawl traps, taxonomy cannibalization, Metatag empty-field handling, Config Split deployment safety, headless coordination, migration SEO with one-to-one redirect mapping, and AI search readiness.
Delivered under your brand as a paid client deliverable
Full SEO protection during version transitions
Monthly Drupal SEO as if from your in-house team
Specialist backup in busy periods without hiring
Yes — in some ways Drupal is stronger for SEO than any competing CMS. Its content model gives granular control over how content is structured, classified, and rendered. Core modules — Metatag, Pathauto, Redirect, Simple XML Sitemap, Schema.org Metatag — provide enterprise-grade SEO infrastructure. Drupal 11.4 even added default robots.txt rules that block crawlable search-parameter URLs. The platform isn’t the limitation. Configuration, content architecture, and deployment discipline decide whether a Drupal site ranks or slowly loses ground.
This is what we call GEO — Generative Engine Optimization — and Drupal is well-positioned for it. AI engines read the raw HTML your server returns, not JavaScript-rendered content, and Drupal renders server-side by default. We build on that with valid JSON-LD structured data, extractable content structure, entity consistency, and Drupal’s LLM-optimized content tooling where it fits. AI engines cite only a handful of sources per answer — the work is making your content the one they can parse and trust.
Both, depending on your team. If you have Drupal developers, we deliver implementation-ready tickets — severity, affected URLs, evidence, the fix, acceptance criteria — so your devs execute without ambiguity. If you need us to implement, we configure Metatag, Pathauto, Redirect, Simple XML Sitemap, Schema.org Metatag, Config Split, and other SEO-adjacent modules directly. Custom module development and deep Twig template work is scoped separately and coordinated with your dev team.
For an audit: a read-only crawl of the live site plus, ideally, admin or appropriate access to review configuration, and access to Google Search Console and Analytics. For implementation: a role-appropriate Drupal account (we work within your permissions, not shared logins), plus Search Console and Analytics. For headless projects, access to the front-end repository or a staging environment. We work through your access system and never need shared credentials.
No. The Standard plan is month-to-month with no cancellation fee. The free audit has no commitment attached. Longer terms only apply where you want them — enterprise, migration, or white-label engagements where a defined term helps both sides plan.
The standard stack on almost every project: Metatag (metadata with token defaults), Pathauto (clean URL aliases), Redirect (301 management), Simple XML Sitemap (entity- and Views-aware sitemaps), Schema.org Metatag (JSON-LD structured data), and Config Split (environment-specific configuration isolation). For content-model-first structured data, Schema.org Blueprints. For AI search, the Markdownify module and AI LLM Optimized Content recipe where they fit. Modules provide controls — strategy, configuration, and QA decide whether they produce good SEO.
That’s exactly what migration SEO is for. A D7→D11 move is a full migration — content model mapping, module replacement, theme rebuild, URL preservation. Every indexable URL is inventoried before we start. Every redirect mapped one-to-one — never bulk-redirected to the homepage. Every canonical, heading, schema output, and Metatag token validated against a pre-migration baseline. Search Console, server logs, rankings, and traffic monitored for 90 days post-launch, with a documented recovery protocol. Anyone who guarantees zero ranking loss on a D7 migration is either inexperienced or overpromising — but the methodology gives you the best possible chance.
Yes. Headless Drupal creates specific challenges: metadata must be generated by the front-end framework from Drupal’s API, canonicals must point to the front-end domain, sitemaps must reflect rendered URLs, internal links must be crawlable without JavaScript, and structured data must render server-side. This last point matters doubly for AI search — AI crawlers don’t execute JavaScript, so client-side-only content is invisible to them. We define ownership boundaries between Drupal and the front end and enforce parity between what Drupal stores and what Google and AI engines receive.
It depends on your starting point. On a site with existing rankings but technical problems — Views crawl waste, misconfigured Metatag, taxonomy cannibalization — cleanup often produces measurable improvement within four to eight weeks as Google recrawls the consolidated URL surface. On a new or thin site needing content and authority, meaningful movement typically takes four to six months and compounds beyond that. On a migration, the immediate goal is preserving rankings at launch. We report on leading indicators — crawl behaviour, indexed-URL trends, keyword coverage — monthly, so you see progress before final rankings catch up.
No — and any Drupal SEO agency that does should be a red flag. Google’s own quality-rater guidelines flag ranking guarantees as a low-trust signal. Search results depend on your market, competition, starting authority, and Google’s ongoing changes. What we guarantee is the methodology: every service on this page delivered the same disciplined way every time. We’d rather earn your continued business with real results than lock you into a promise we can’t control.
Send us your Drupal site and we’ll show you the Views crawl traps eating your crawl budget, the taxonomy pages cannibalizing your real landing pages, the Metatag tokens rendering blank descriptions, the config deployment risks that quietly reset your SEO, and the gaps keeping you out of AI Overviews. You get a prioritized findings roadmap with developer-ready tickets — yours to act on with or without us.
