⭐ Beginner — No coding experience needed
Site Migration: The Beginner's Guide to Moving Without Losing Traffic
Learn how to plan and execute a site migration so you keep your Google rankings, your backlinks, and your traffic. The exact sequence to follow before, during and after launch.
What you will learn in this guide
- When site migrations actually make sense
- The 4 things that must happen before launch day
- How to build a complete 301 redirect map
- What to expect in the post-launch traffic dip
- How to track recovery and know when to worry
1 When migrations actually make sense
Migrations are risky. Even perfect migrations usually lose 10-20% of traffic temporarily, and many lose much more. Only migrate when you have to:
- Rebranding (legal name change, acquisition)
- Moving to HTTPS (still common on legacy sites)
- Consolidating multiple domains into one
- Changing CMS or platform (WordPress → Shopify, etc.)
- Changing URL structure to fix a long-standing problem
Don't migrate for cosmetic reasonsIf your only motivation is "the new domain looks nicer", don't. The 6-month traffic recovery often costs more than the perceived benefit.
2 The pre-launch checklist
- 1Crawl your current site fullyUse the site crawler to get a list of every URL that currently returns 200. This is your "old URL" baseline.
- 2Build a complete 301 mapEvery old URL needs a target on the new site. Use a spreadsheet. Each row: Old URL → New URL. Pages that are gone need a decision: 301 to a parent, 410 Gone, or noindex.
- 3Test redirects on stagingSet up your new site on a staging URL with the 301 rules applied. Crawl it; confirm every old URL redirects correctly with a single 301.
- 4Submit both sitemaps to Search ConsoleOld and new domains both in Search Console before launch. The old sitemap helps Google discover redirects faster.
3 Launch day
- 1Deploy in a low-traffic windowTuesday or Wednesday morning is safer than Friday afternoon. Less impact if something breaks.
- 2Verify 301s with a fresh crawlWithin 1 hour of launch, crawl the new domain. Every important old URL should redirect cleanly.
- 3Submit the new sitemapIn Search Console, add the new sitemap. In the old property, use the "Change of address" tool.
- 4Monitor server errorsWatch logs for 24 hours. Spikes in 500s or 404s indicate issues that need urgent fixing.
4 Post-launch tracking
Track recovery against this expected timeline:
| Week | Expected traffic | When to worry |
|---|---|---|
| Week 0 | -20% to -30% vs baseline | Normal |
| Week 1 | -25% to -35% | Normal (worst week usually) |
| Week 2 | -15% to -25% | Recovering |
| Week 4 | -5% to -15% | On track |
| Week 8 | -5% to +5% | Should be near baseline |
| Week 12 | Back to baseline | If still down 15%+, investigation needed |
The migration audit tooltracks day-by-day recovery against this curve. If you fall significantly below, it identifies the most likely cause: 301 chains, indexation lag, schema regression, or content quality drift.