Prompt
I'm building a site migration from Drupal to headless and want to avoid SEO issues
Latest observation
A Drupal → headless migration can be very SEO-safe if you treat it like a URL/content preservation project, not just a CMS swap. Here’s a practical checklist to avoid the common traps.
1) Keep URL structure the same if you can
Best case: preserve existing URLs exactly.
If URLs must change, map every old URL to one new destination with 301 redirects. Avoid:
- redirect chains
- redirect loops
- mass redirects to the homepage
- 302s for permanent moves
2) Inventory everything before migration
Create a crawl of the current site and export:
- all indexable URLs
- title tags, meta descriptions
- H1s, canonicals
- structured data
- internal links
- status codes
- XML sitemaps
- top traffic pages from analytics
- pages with backlinks from Search Console / Ahrefs / Majestic
This gives you a “do not lose” list.
3) Match content, not just page names
When moving to headless, ensure each page still has:
- equivalent text content
- same intent/topic
- same schema/structured data where relevant
- same media alt text and captions
- same internal linking context
If a page is thinned out too much, rankings can drop even with redirects.
4) Preserve metadata and canonical tags
Make sure your new front end outputs:
- unique
<title>tags - meta descriptions
- canonical tags
- robots meta tags
- hreflang if you use it
- Open Graph/Twitter tags if needed
Common issue: headless front ends render pages without proper SEO tags or use one generic template.
5) Use server-side rendering or pre-rendering
If the new site is JS-heavy, search engines may still crawl it, but SEO risk is higher.
Prefer:
- SSR
- SSG
- hybrid rendering
Avoid relying on client-side rendering for critical indexable content and metadata.
6) Maintain internal links
Update internal links so they point directly to the final destination URLs, not old Drupal URLs that then redirect.
Also preserve:
- breadcrumbs
- related content links
- navigation links
- footer links
This helps crawling and preserves link equity.
7) Redirect old URLs carefully
Build a redirect map for:
- old node URLs
- taxonomy pages
- author pages
- media/file URLs
- paginated views
- legacy paths
- trailing slash / no-slash variants
- uppercase/lowercase variants if relevant
Test with a crawler that:
- all old URLs resolve to 301
- all redirected URLs land on the intended page
- final destination returns 200
8) Keep XML sitemaps accurate
Generate fresh sitemaps for the new site:
- only canonical, indexable URLs
- no redirected or 404 URLs
- split large sitemaps if needed
- include lastmod if reliable
Submit them in Google Search Console and Bing Webmaster Tools.
9) Control robots.txt and indexing rules
Double-check you’re not accidentally blocking:
- CSS/JS assets needed for rendering
- important sections of the site
- the whole site in staging leftover settings
Also ensure no accidental noindex remains from staging or preview environments.
10) Handle staging safely
Staging should be blocked from indexing via:
- authentication, or
- IP restriction, or
noindexplus robots blocking if appropriate
But be careful: if you use robots.txt to block crawling entirely, search engines can’t see a noindex tag. For staging, authentication is usually best.
11) Preserve structured data
If the current Drupal site has schema markup, keep or improve it:
- Article
- Organization
- BreadcrumbList
- Product
- FAQ
- Event
- LocalBusiness
Validate with Google’s Rich Results Test and Schema Markup Validator.
12) Watch for pagination/filter URL issues
Drupal sites often have:
- faceted navigation
- parameterized URLs
- filtered listings
- sort orders
Decide what should be indexable and what should be canonicalized or blocked. Otherwise, you can create duplicate-content bloat.
13) Track backlinks and priority pages
Don’t let high-value pages disappear. Prioritize:
- pages with backlinks
- pages with high organic traffic
- conversion pages
- evergreen content
If a page is removed, redirect it to the closest relevant page, not just a category page.
14) Validate before launch
Run a pre-launch QA:
- crawl staging with auth access
- compare old vs new URL inventory
- compare titles/H1s/meta/canonicals
- validate structured data
- check response codes
- confirm redirects
- verify mobile rendering and page speed
15) Monitor closely after launch
For 2–8 weeks after launch:
- monitor crawl errors in Search Console
- check index coverage
- look for sudden drops in impressions/clicks
- inspect top landing pages
- monitor server logs for bot behavior
- fix broken redirects quickly
16) Common migration mistakes to avoid
- changing too many URLs at once without redirects
- shipping a JS app with missing metadata
- forgetting canonical tags
- launching with staging
noindex - leaving old internal links in place
- redirecting everything to the homepage
- not migrating image URLs/media
- losing taxonomy page content
- removing thin but ranking pages too aggressively
Practical migration workflow
- Crawl old site and export all URLs and metadata
- Define new information architecture
- Map old URL → new URL
- Rebuild templates with SEO fields
- Implement SSR/SSG as needed
- Test on staging with authenticated crawl
- Launch redirects and sitemaps
- Submit in Search Console
- Monitor logs, rankings, and errors
If you want, I can give you:
- a Drupal-to-headless SEO migration checklist
- a redirect mapping spreadsheet template
- or a pre-launch QA test plan for your team.