SEO Migration Guide: Changing Domains Without Losing Rankings

The migration that lost 80% of traffic

A colleague moved a client from exampleold.com to examplenew.com last year. They set up 301 redirects, submitted the change of address in Search Console, and waited. Three months later, traffic was down 80%.

What went wrong: they redirected the homepage and top 10 pages but missed 847 internal pages. Those 847 pages had zero redirects. Google hit dead ends, dropped them from the index, and never recovered.

Domain migrations are brutal. But if you do it right, you can keep 95%+ of your traffic. Here's how.

Preparation phase (4-6 weeks before)

Crawl your entire existing site. Use Screaming Frog or Sitebulb. Export every single URL — pages, images, PDFs, everything. You need the complete URL list for your redirect map.

Identify your top pages by traffic. Export the last 12 months of data from Google Analytics and Search Console. Rank pages by organic traffic. These are the pages you absolutely cannot mess up.

Fix existing issues first. If your current site has broken links, slow pages, or indexing problems, fix them before the migration. You don't want to carry problems to the new domain. Our technical SEO checklist covers every issue you should fix before a migration.

Build the redirect map. This is the most important step. Every URL from the old site needs a 301 redirect to the most relevant URL on the new site. Not just the homepage — everything. Group similar pages together if needed, but avoid redirect chains.

Migration day

Set up the new site first. Get the new domain fully functional with all content, design, and functionality working before you touch the old domain. Test everything on a staging URL or dev domain.

Implement 301 redirects. Use server-level redirects (via .htaccess or nginx config) rather than plugin-based redirects. Server-level redirects are faster and more reliable. For a deep dive into when to use 301 vs 302 redirects and how status codes affect SEO, see our HTTP status codes guide.

Update internal links. Every internal link on your new site should point to the new domain, not redirect. Search and replace all old domain references in your database.

Update external references. Change your Google Search Console property, Google Analytics property, Google My Business listing, social media profiles, and any directory listings to the new domain.

Submit change of address. In Google Search Console, use the Change of Address tool under Settings. This tells Google the site has permanently moved.

Post-migration monitoring (8 weeks critical)

Week 1: Monitor Search Console for crawl errors and spikes in 404s. Every 404 is a missed redirect. Fix them immediately. Check the Index Coverage report daily.

Week 2-4: Traffic will fluctuate. This is normal. Don't panic. Watch for pages dropping out of the index — re-submit them via URL Inspection Tool.

Week 4-8: Monitor rankings for your top 50 keywords. If a specific page cluster dropped, check its redirect. I've found cases where a category page missed its redirect and the entire subfolder lost traffic.

Month 3-6: Traffic should stabilize near pre-migration levels. If it's still down 20%+, something went wrong. Re-crawl, check redirect chains, and verify all content transferred correctly.

Common migration killers

- Redirecting to the homepage instead of the specific page

- Using 302 redirects instead of 301

- Forgetting to migrate XML sitemaps

- Not updating robots.txt

- Leaving old domain SSL certificate expired (creates security warnings)

- Changing URL structure AND domain at the same time

Don't combine a domain migration with a site redesign. Do them separately, 3-6 months apart. Too many variables at once means you won't know what broke.

Related Articles

- Technical SEO Checklist 2026: Crawl, Index, Render, Rank

- HTTP Status Codes for SEO: 301, 302, 404, 410 Explained