Drupal SEO

Drupal SEO is not about writing better content — it is about configuring the platform to expose your content properly. Think of Drupal as a warehouse with brilliant inventory but no signs. The modules are your signage team. Without them, search engines wander. I start with five modules every time: Metag for metadata control, Pathauto for clean URL aliases, Redirect for avoiding 404s during site changes, Simple XML Sitemap for crawl coverage, and Schema.org Metag for structured data. That stack covers 80% of what a search engine needs. Last month I helped a client who had been running an unconfigured Drupal 9 site for two years. Their product pages generated system URLs like /node/342 and their page titles were all "Home — Site Name". After installing those modules and applying templates, indexed pages jumped from 43 to 211 within six weeks. The mistake people make is treating Drupal like WordPress, where a plugin does everything. Drupal gives you a powerful but empty toolbox. You have to set the patterns. For example, with Pathauto you define that a blog post gets /blog/[node:title] and a product gets /products/[node:field_sku]. That single decision saves you from manually editing every URL. The library analogy holds: without Pathauto, every book gets a random shelf number; with it, every book goes to the right aisle. And do not assume that Drupal core handles meta tags — it does not. The module Metag is non-negotiable. I also configure the sitemap module to include only published content, and I check the robots.txt to ensure the staging environment is disallowed. This is not a set-and-forget job. Every new content type or view you create needs a metadata template. The few hours you spend upfront save months of retrofitting later.

Drupal SEO matters most in three scenarios I see repeatedly. First, at launch. If you launch a new Drupal site without SEO configuration, you gamble the first six months of organic visibility. I worked on a launch last year where the team ignored metadata templates until week two. Their pages were not indexed for three months because Google could not identify what each page was about. By the time we added templates and a sitemap, the competition had already settled on those keywords. Second, during migration. Moving from WordPress to Drupal (or from an older Drupal version) destroys rankings if you do not map old URLs to new ones. I have seen sites lose 60% of organic traffic because they forgot to configure the Redirect module. The standard rule is to create a CSV of 301 redirects for every moved URL and import them before the DNS switch. That is not optional. Third, when you scale content. A friend runs a Drupal site with 15,000 articles. Without Pathauto and Metag templates, each article would need manual metadata — impossible. With a correctly configured template, every new article gets an optimised title tag and URL automatically. I also consider performance as a ranking factor. Drupal can be slow out of the box. I have tested a default Drupal installation on shared hosting and got a Lighthouse performance score of 24. After enabling BigPipe, internal page cache, and compressing images, the same page scored 78. That matters because [Core Web Vitals](/core-web-vitals/) directly affect rankings for competitive head terms. A counter-argument: for a five-page brochure site, you could skip most of this. But I would still install the basic modules because they cost nothing and prevent technical debt when the site grows. The decision rule is simple: if your site has more than ten content types, or you plan to add content weekly, invest in Drupal SEO now.

I wasted two months on my first Drupal project because I thought installing a module equated to finishing the job. I installed Pathauto but never set the templates — so all URLs stayed as /node/123. I assumed the module would guess the pattern. It does not. You have to go to /admin/config/search/path/patterns and define the rule for each content type. I also believed that Drupal's default meta description would be good enough. It is not — it takes the first 160 characters of the body text, which often cuts off mid-sentence. The Metag module lets you write a fallback pattern using token replacement, but you have to do it. Another mistake: ignoring structured data validation. I added Schema.org Metag module and assumed the markup was correct. When I ran the data through Google's Rich Results Test, half of my pages had missing required properties. For example, for an event content type I defined a schema:Event but omitted startDate. Now I test every new content type with the Rich Results Test before publishing. The biggest miss was performance. I spent weeks on metadata and URLs but served uncompressed images from the default image style. A single 2MB hero image undid all that work by increasing load time by 4 seconds. I now use a module that compresses on upload and serve images via a [CDN](/technical-seo/) if the budget allows. I also overlooked [canonical tags](/canonical-tag/). Drupal can generate multiple URLs for the same node (e.g., /node/1 and /article/my-article). Without a canonical tag, Google splits ranking signals. The Metag module includes a canonical tag token, but it is not enabled by default. I had to manually add it to the global metadata template. Finally, I used to think Drupal SEO was a one-time setup. It is not. Every new custom content type, every view, every exposed filter page needs metadata and URL rules. I now schedule a quarterly [SEO audit](/seo-audits/) specifically for Drupal configuration to catch missing templates and broken redirects.