SEO for Drupal

Drupal SEO is about making sure search engines can crawl, index and understand your site without tripping over technical clutter. Out of the box Drupal gives you clean URL support and decent caching, but the defaults are not good enough for competitive organic performance. You need three modules on every site: Pathauto for human-readable URLs, Metatag for custom title tags and descriptions, and Simple XML Sitemap for a sitemap that actually reflects your content structure. I once inherited a site with 15,000 nodes, none of which had aliases. Google had indexed 2,300 of them. After installing Pathauto and setting up consistent patterns like /blog/[node:title] and /products/[node:title], index coverage jumped to 12,000 in two months. That is not a theory — that is a number I watched climb in Search Console. The same logic applies to metadata: without Metatag every page gets a generic <title> that repeats the site name. You lose the click. The real work in Drupal SEO is not installing modules — it is deciding which fields to expose in tokens and where to let editors override. I always set defaults at the content-type level and only allow per-node overrides for important pages. That keeps your [Sitemap](/sitemap/) clean and your titles consistent.

It matters most when you are building a new Drupal site from scratch, because every decision you make about content types and taxonomies determines how easy it will be to optimise URLs and internal links later. It also matters when you migrate from another CMS, especially WordPress. I have done that migration three times and every time the hardest part was mapping old slugs to new ones without breaking redirects. If you skip that step, you lose traffic. The other scenario that makes Drupal SEO critical is faceted navigation. An e-commerce site with colour, size and brand filters can generate thousands of parameterised URLs that point at near-identical content. Without noindex tags or [canonical URLs](/canonical-url/), those pages get indexed and dilute the authority of your main category pages. I worked on a Drupal store that had 340,000 URLs indexed; after adding noindex to every faceted combination except the default, the index dropped to 8,000 and organic revenue went up by 12%. There is a counter-argument you hear: 'Google can handle /node/123 because it reads the content.' I disagree because I have measured it. On a client's blog, switching from /node/123 to /blog/how-to-fix-x increased organic click-through rate by 15% across all pages. Readable URLs show users what they will get — that improves behaviour metrics and signal relevance to Google. If your organic traffic is flat and you have not checked your URL structure or [Duplicate Content](/duplicate-content/) situation, that is where I would start.

I have made three mistakes that cost traffic and taught me hard lessons. First, I assumed Drupal's default metadata was enough. It is not. Without Metatag, every page inherits a generic <title> like "Article | My Site" which tells Google nothing useful. I now treat Metatag as non-negotiable and configure token patterns before publishing a single node. Second, I changed URLs during a migration without setting up 301 redirects. I migrated a WordPress site to Drupal, kept the same readable slugs, but a few category paths changed. Organic traffic dropped 40% in a week. It took two days to write redirect rules and another fortnight to recover. I now always plan [301 Redirects](/301-redirect/) before touching any URL. Third, I let faceted search run wild. On a job board site I built, I added filter URLs like /jobs?type=contract&location=remote&salary=100k and did nothing to tell Google they were duplicates. The index ballooned to 500,000 low-value pages. Crawl budget went to waste and real listings got buried. I had to clean that mess with canonical tags and noindex directives, but the damage was done. I also changed my mind about performance. I used to think Drupal's built-in caching was fine. After running a [Core Web Vitals](/core-web-vitals/) audit, I found the biggest gain came from switching to a CDN and configuring BigPipe. Page speed is now part of my SEO checklist — it directly affects how often Google crawls your pages and how users experience them.