An SEO site migration is one of the highest-risk operations in search engine optimisation. When an SEO site migration is handled correctly, Google processes the change smoothly and rankings remain stable. When it is handled poorly — missing redirects, canonical errors, robots.txt mistakes — organic traffic can drop 30%, 50%, or more almost overnight. And the painful part is that most SEO site migration ranking drops are entirely preventable with the right preparation.
Whether you are changing your domain name, switching CMS platforms, restructuring URL paths, or moving from HTTP to HTTPS, the same core website migration SEO principles apply. This checklist walks through the complete process: what to do before the migration, what to get right on launch day, and what to monitor in the weeks after to catch and fix problems before they compound.
What Types of Website Migration Carry SEO Risk?
Not every website change is a migration in the SEO sense. Updating content on existing pages or changing your design without changing URLs carries minimal migration risk. The changes that create real SEO site migration danger are those that alter how pages are addressed:
Domain changes — moving from olddomain.com to newdomain.com — require all your content, rankings, and link equity to transfer to a new address that Google has never seen before. URL structure changes — restructuring /category/subcategory/product into /products/product-name — change where every affected page lives, breaking all internal and external links if redirects are not implemented. Platform migrations — moving from WordPress to Shopify, or from a custom CMS to a new one — often change both URL structure and technical implementation simultaneously. Each of these website migration scenarios requires careful redirect mapping and post-launch verification to preserve the SEO value built up over time.
Phase 1: Pre-Migration SEO Preparation
Pre-migration preparation is where SEO site migrations succeed or fail. Most businesses rush to implementation without the foundational work, creating problems they spend weeks diagnosing post-launch.
Run a Full Pre-Migration SEO Audit
Before changing anything, conduct a comprehensive pre-migration SEO audit of the current site. This produces the baseline data you need to compare against after migration to identify any performance issues immediately. The audit should capture every indexed URL and its current keyword rankings, organic traffic per page over the past 12 months, inbound links for each URL, Core Web Vitals scores, and the current technical health status across the site. Export all of this before touching anything — this data is your migration benchmark and your recovery diagnostic tool if something goes wrong.
Build Your Redirect Map Before Launch
The redirect map is the most critical SEO site migration deliverable. For every existing URL that will change, document exactly where it should redirect to. Every product page, category page, blog post, and location page. Missing redirects in your website migration mean old URLs return 404 errors, losing all the ranking signals and external link equity those pages accumulated. This is the most common cause of severe SEO site migration traffic drops — not technical failures, but incomplete redirect coverage.
Every redirect should point directly to the most semantically equivalent new URL — never to the homepage. Redirecting everything to the homepage tells Google that those pages no longer exist with their previous content, and the ranking signals do not transfer. A page about “termite control in Phoenix” that redirects to the homepage loses its termite-related ranking signals entirely.
Validate the Staging Environment Before Launch
Before the new site goes live, validate the staging environment thoroughly. Confirm that staging is blocked from Google via robots.txt — you do not want new URLs indexed before you are ready. Test every redirect in the redirect map. Check that canonical tags on the new site point to the new domain, not the old one. Confirm that all page templates render correctly and that no on-page elements — title tags, meta descriptions, headings, structured data — have been lost in the CMS migration process.
The specific considerations for a CMS migration — particularly how different platforms handle metadata, schema, and URL generation — add extra complexity at this stage. A WordPress to Shopify migration, for example, requires careful attention to how each platform generates canonical URLs and handles pagination, because the defaults differ significantly.
Phase 2: Migration Day SEO Checklist
Timing and Launch Sequencing
Schedule your SEO site migration for your lowest-traffic period — midweek overnight works well for most businesses. This minimises user impact if something goes wrong and keeps your development team available during business hours if issues arise. Never migrate around major campaigns, peak sales periods, or important business events where organic search performance matters most.
Implement All 301 Redirects at Launch
All 301 redirects from your website migration redirect map should go live simultaneously with the new site, not after it. Server-level redirects — configured in .htaccess for Apache or nginx configuration — are more reliable than JavaScript-based redirects and are more efficiently followed by Googlebot. Every redirect in your website migration should be a single-hop 301 pointing directly to the final destination URL. Chains — where redirect A points to redirect B before the final URL — dilute the SEO signal transfer and can cause Googlebot to stop following the chain.
Remove Staging Restrictions Correctly
When the new site launches, confirm that the staging robots.txt blocking rule has been removed or replaced with the correct production robots.txt. This is a commonly missed SEO site migration step that leaves the site technically live but completely uncrawlable by Google — traffic disappears not from ranking drops but from complete inaccessibility.
Notify Google Through Search Console
For domain migrations, use Google Search Console’s Change of Address tool to notify Google explicitly that your domain has moved. Submit the new XML sitemap reflecting the new URL structure. Use the URL Inspection tool to request indexing of your highest-priority new pages — this prompts Googlebot to crawl them sooner than waiting for the next regular crawl cycle.
Phase 3: Post-Migration SEO Monitoring
The first four weeks after an SEO site migration require close daily monitoring. Some ranking fluctuation is normal during any website migration as Google processes the redirect signals and updates its index. Drops of 10 to 20 percent in the first two weeks are common and typically recover. Drops beyond 30 percent, or drops that do not begin recovering by week three, indicate specific problems that need to be found and fixed.
Monitor Crawl Errors Daily
Check the Coverage report in Google Search Console daily for the first two weeks post-migration. Spikes in 404 errors indicate redirect gaps — URLs not covered by your redirect map that are now returning not found. Address missing redirects immediately before the ranking signals on those URLs decay further.
Verify Canonical Tags Across Page Types
Spot-check canonical tags across different page types on the new site. The canonical must reference the new domain, not the old one. A site that migrated to a new domain but left canonical tags pointing to the old domain tells Google to treat the old domain as authoritative — effectively undoing the SEO migration from a ranking signal perspective. This error is more common than it should be, particularly in CMS migrations where the canonical URL is generated dynamically from a stored setting.
Update Your Sitemap After Migration
Your XML sitemap should be updated to reflect the new URL structure. Updating your sitemap to remove old redirected URLs and any noindexed pages ensures Googlebot’s crawl allocation focuses on the new live pages rather than wasting time on redirecting URLs that should not be in the sitemap.
SEO Site Migration Recovery Timeline
A well-executed website migration with comprehensive redirect coverage typically sees ranking stabilisation within four to eight weeks. The compounding benefit of careful pre-migration preparation is that recovery is fast because there are no gaps to find and fix retroactively. Full traffic recovery to pre-migration levels generally takes two to three months as Google completes re-indexing the new URL structure.
SEO site migrations that missed redirect coverage, had canonical errors, or launched with technical implementation problems recover slowly — sometimes taking six months or longer to return to pre-migration organic performance levels. The investment in thorough preparation before migration day consistently separates the migrations that recover in weeks from those that become months-long ranking rescue projects.