Drupal sites that search engines understand page by page
We configure the modules Drupal needs for SEO, clean up duplicate node paths and protect rankings through version upgrades.
In plain English.
Drupal core does very little SEO on its own. Good results depend on a set of contributed modules: Metatag for titles and descriptions, Pathauto for readable URL aliases, Redirect for 301s and duplicate path handling, Simple XML Sitemap for sitemaps, and Schema.org Metatag for structured data. Each needs configuring for every content type.
Common Drupal problems include content reachable at both /node/123 and its alias, taxonomy term pages holding a single item, Views with exposed filters creating endless parameter URLs, and multilingual sites where translations are missing hreflang. Large public sector and membership sites also tend to carry years of old content nobody has reviewed.
Version changes are the other risk. Drupal 7 reached end of life in January 2025, and moving to Drupal 10 or 11 is effectively a rebuild. URL aliases, redirects and metadata have to be migrated deliberately or rankings suffer. We plan that mapping and test it before launch.
It suits you if.
- Your site runs on Drupal 9, 10 or 11
- You are still on Drupal 7 and planning an upgrade
- Search Console shows /node/ URLs being indexed
- You run a multilingual Drupal site
- Your team edits content but nobody owns the SEO settings
What we do.
Metatag configuration
Default patterns for titles, descriptions and Open Graph tags per content type, with per-page overrides for editors.
Pathauto and Redirect
Readable URL patterns, automatic redirects when titles change and enforced canonical paths so /node/ URLs redirect to their aliases.
Sitemaps and indexing
Simple XML Sitemap set up per content type and language, with thin taxonomy and utility pages left out.
Views and faceted search
Exposed filters and Search API facets are handled with noindex, canonical tags or robots rules to stop parameter sprawl.
Multilingual SEO
hreflang through the core translation modules and the Hreflang module, with translated aliases checked for each language.
Upgrade migration mapping
Every Drupal 7 alias and redirect is mapped to its new URL, tested on staging and monitored after launch.
How it runs.
- 01
Audit modules and config
We review installed modules, content types, Views and the live crawl alongside Search Console.
- 02
Agree a plan with your team
Drupal sites often have internal developers or a support supplier. We agree who makes each change and how it is deployed.
- 03
Configure and test
Modules are installed or configured on a development environment, exported as configuration and tested.
- 04
Deploy and monitor
Changes go live through your usual deployment, then indexing, redirects and coverage are watched in Search Console.
Questions people ask.
How much does Drupal SEO cost?
Drupal work is quoted per project. Configuration on a current Drupal site is a contained job, while SEO planning for a Drupal 7 upgrade is larger, as it covers every URL on the old site and the testing that goes with it.
We are still on Drupal 7. What should we do?
Plan the move now. Drupal 7 no longer gets community security updates, so an upgrade or replatform is due. Whichever route you take, the SEO risk sits in URL changes, and a full redirect map protects the rankings you have built.
Do you work with our existing Drupal developers?
Yes. We can write specifications for your developers or support supplier and review their work, or make configuration changes ourselves if you prefer. Changes are exported as configuration so they stay in your codebase.
Which environments will you work on?
We work on a development or staging copy with an administrator or site builder account, plus Search Console access and ideally your code repository. Live changes go through your normal release process, never straight onto production.
Your next chapter starts with a conversation.
Nottingham & Derby / UK-wideLet’s build
what’s next.
15 minutes with Garreth.
A real conversation about your business.