Site Migration SEO: The Checklist That Prevents Traffic Loss

Site migrations are where organic traffic goes to die. According to Ahrefs’ 2024 analysis of 100+ domain migrations, 72% of sites lost at least 10% of their organic traffic post-migration, and 34% never recovered to pre-migration levels. The reason isn’t that migrations are inherently destructive. It’s that teams treat SEO as an afterthought instead of a migration requirement.

“We’ve managed migrations for brands doing ₹50 crore to ₹500 crore in annual revenue. The ones that lose traffic always have the same thing in common: SEO wasn’t in the room when the migration was planned. By the time someone thinks about redirects, the new site is already live,” says Hardik Shah, Founder of ScaleGrowth.Digital.

This checklist covers every SEO task before, during, and after a site migration, whether you’re changing domains, moving to a new CMS, redesigning your URL structure, or switching from HTTP to HTTPS.

What Counts as a “Site Migration” in SEO Terms?

The term “site migration” covers more scenarios than most people realize. Each type carries different risk levels:

The rule is simple: the more URLs that change, the higher the risk. A protocol change with identical URLs is relatively safe. A domain change with URL restructuring and CMS migration simultaneously is three migrations stacked on top of each other. Don’t do that unless you absolutely have to.

What Should You Do 4 to 6 Weeks Before Migration?

Pre-migration work determines 80% of your outcome. Skip this phase and no amount of post-launch fixing will compensate.

Crawl your existing site completely. Use Screaming Frog (or Sitebulb, or your preferred crawler) to capture every URL, its status code, title tag, meta description, canonical tag, H1, internal links, and response time. Export this to a spreadsheet. This is your baseline. If you don’t have this data before migration, you can’t verify anything after.

Export all rankings data. Pull your current keyword rankings from Google Search Console (Performance report, full date range), Semrush, or Ahrefs. You need to know exactly which URLs rank for which keywords before you change anything. Export organic landing pages from Google Analytics 4 with sessions, conversions, and revenue for the past 12 months.

Build your redirect map. This is the single most important migration document. It maps every old URL to its new URL equivalent. Every. Single. One.

For sites with 500+ pages, this takes days, not hours. Budget the time. Automated redirect mapping tools exist (Screaming Frog has a compare feature, Semrush has migration tools), but they need human review. An algorithm matching old URLs to new ones by slug similarity will get 70% right and miss critical edge cases.

Identify your VIP pages. Your top 100 pages by organic traffic, your top 50 pages by backlinks, and your top 30 pages by conversions. These pages get individual attention during and after migration. If a VIP page loses its rankings, you need to know immediately, not 6 weeks later when someone notices traffic dropped.

Benchmark Core Web Vitals. Run a Lighthouse audit or use the CrUX (Chrome User Experience Report) data from PageSpeed Insights for your top 50 pages. If your new site is slower than your old site, you’ll compound migration losses with performance losses. The new site should be at least as fast, ideally faster.

What’s the Technical Pre-Migration Checklist?

These are the items your development team needs to verify on the staging environment before launch:

Redirect implementation. Every row in your redirect map should be testable on staging. Use a tool like httpstatus.io or a custom script to verify each redirect returns a 301 (not 302, not 307) and points to the correct destination. Redirect chains must be zero. Every redirect should go directly from old URL to final new URL in a single hop.

Robots.txt on the new site. Staging environments almost always have a disallow-all robots.txt. If that goes live, Google can’t crawl your new site. I’ve seen this happen to a major Indian e-commerce brand in 2023. Their staging robots.txt went live and it took 11 days for someone to notice. They lost an estimated ₹2 crore in organic revenue during that window.

XML sitemap generation. Your new sitemap should contain only new URLs. It should not contain old URLs, redirected URLs, or non-indexable pages. Submit it to GSC within hours of launch.

Canonical tags on every page. Each page on the new site should have a self-referencing canonical pointing to its own new URL. Watch for canonical tags that still point to old-site URLs: this is a common CMS configuration bug during migrations.

Internal links updated. Your new site’s internal links should point to new URLs directly, not rely on redirects. If your navigation, footer, sidebar, and in-content links all point to old URLs that then redirect, you’re creating unnecessary redirect load and losing a small amount of link equity on every internal link.

Structured data migrated. If your old site had schema markup (Product, FAQ, LocalBusiness, Organization, Article), verify it exists on the corresponding new pages. Schema doesn’t transfer automatically in most CMS migrations.

Meta tags migrated. Custom title tags and meta descriptions from your old site need to appear on their new-URL equivalents. If your CMS auto-generates these, you’ll lose the custom titles you’ve optimized over years.

What Should Happen on Launch Day?

Launch day is not the day to discover problems. It’s the day to verify that everything you prepared works correctly.

Verify redirects are live. Test your top 100 URLs manually or with a script. Every one should return a 301 pointing to the correct new URL. If even 5 of your top 100 are wrong, stop and fix them before proceeding.

Update Google Search Console. If you’ve changed domains, use the Change of Address tool in GSC. Add and verify the new domain as a property. Submit your new sitemap. If you’ve changed URL structure without changing domains, submit the updated sitemap and request indexing for your VIP pages.

Monitor server logs. Watch your server logs for the first 24 hours. Look for Googlebot activity, 404 errors, 5xx errors, and redirect patterns. High 404 rates from Googlebot mean your redirect map has gaps.

Update Google Analytics. Verify your GA4 tracking fires correctly on the new site. Check that goals, events, and e-commerce tracking work. A migration that drops analytics tracking means you’re flying blind during the most critical period.

Notify Google. Beyond GSC, update your Google Business Profile if your URL has changed. Update links in Google Ads campaigns. Update any structured data that references your domain (Organization schema, sameAs properties).

What Should You Monitor in the First 30 Days After Migration?

The first 30 days determine whether your migration succeeds or fails. Check these metrics daily for the first two weeks, then weekly through day 30.

Expect a temporary dip. Even perfectly executed migrations see a 5 to 15% traffic drop in the first 2 to 4 weeks. Google needs time to recrawl, reprocess redirects, and reassess rankings. The key difference between a successful migration and a failed one is whether traffic recovers by week 6 to 8.

How Do You Handle Pages That Don’t Have a 1-to-1 Redirect Match?

Not every old page has a direct equivalent on the new site. Maybe you consolidated five thin pages into one comprehensive guide. Maybe you discontinued a product line. Maybe you restructured your blog categories entirely.

The hierarchy of redirect targets:

Best: 1-to-1 match. Old page redirects to the exact equivalent new page. User gets what they expected.

Good: Redirect to the nearest parent or category. If /products/widget-blue no longer exists but /products/widgets does, redirect there. The user lands in the right neighborhood.

Acceptable: Redirect to a relevant hub page. If an entire product category was removed, redirect those URLs to your main products page or a relevant alternative category.

Bad: Redirect everything to the homepage. This is called a “soft 404” in Google’s eyes. Google will eventually treat mass redirects to the homepage as 404s anyway, and you lose whatever link equity those old pages had. Only use homepage redirects as a last resort for pages with zero traffic and zero backlinks.

Worst: Let them 404 without any redirect. If a page has backlinks or traffic, a 404 is the most destructive option. You lose the traffic immediately, and the link equity evaporates over time as linking sites get 404 responses.

What Are the Most Common Migration Mistakes?

After managing or auditing dozens of migrations, here’s my list of the mistakes I see most often. Some of them are obvious. Most of them still happen.

302 redirects instead of 301s. A 302 tells Google the redirect is temporary. Google may keep the old URL indexed and ignore the new one. For permanent migrations, always use 301 (or 308 for modern HTTP). Check every redirect; don’t assume your dev team knows the difference.

Forgetting about parameter URLs. Your old site might have URLs like /products?category=shoes&sort=price. If these had traffic or backlinks, they need redirects too. Crawl your old site with URL parameters enabled in Screaming Frog to catch these.

No backlink outreach post-migration. Your top 50 backlinks by authority should be contacted after migration to update their links to your new URLs. Yes, your redirects will pass equity in the short term. But redirects decay over time, and direct links are always stronger than redirected ones. This is tedious work. It matters.

Changing content during migration. A migration should change URLs and templates. It should not simultaneously change page content, add new pages, or remove existing content. When you change everything at once and traffic drops, you can’t diagnose whether the problem is redirects, content, performance, or something else. Separate the variables.

Not keeping old redirects long enough. Redirects from a migration should stay in place for a minimum of 12 months. Ideally, keep them permanently. Google can take months to fully process a large redirect map, and external sites may reference your old URLs for years. Removing redirects after 3 months because “it’s been long enough” is a common cause of delayed traffic loss.

“The best site migration is the one your users don’t notice. If your URLs change but your content, performance, and findability stay the same, you’ve done it right. That takes preparation, not luck,” says Hardik Shah, Founder of ScaleGrowth.Digital.

What Tools Do You Need for a Migration?

A site migration isn’t a project you hand off to developers alone. It requires SEO, content, development, and analytics working together with a shared checklist and clear ownership. The checklist above isn’t exhaustive for every edge case, but it covers the 90% of issues that cause 90% of migration failures.

Planning a migration? Reach out before you start, not after traffic drops.