Moving your website feels a lot like moving house. The difference is that Google keeps your old address on file, and every customer who searches still gets sent there.
A migration changes the URLs, server or platform your rankings are attached to it. Done carelessly, an SEO website migration can wipe out organic traffic overnight, and the leads go with it.
So which steps does your move need, and in what order? This checklist covers your migration type, what to do before, during and after launch, and how to diagnose a drop. We migrated our own agency website and ran this process on client moves, so it reflects what breaks in practice.
What Is an SEO Website Migration?
An SEO website migration is any significant change to a site’s domain, URLs, platform, hosting or structure that can affect how search engines crawl, index and rank it. The SEO work is protecting the signals tied to the old setup so they transfer cleanly to the new one.
The risk comes from how rankings work: Google ranks specific URLs, their content and the links pointing at them, not your business. Change those without a plan and Google sees a brand-new site.
If you are keeping your domain and changing only the design, our website redesign SEO checklist covers that project in detail. This guide covers every other kind of move.
Which Type of Migration Are You Doing?
Each migration type carries a different risk. Find yours below.
| Migration type | What changes | SEO risk | Change of Address tool? | Steps that matter most |
|---|---|---|---|---|
| Domain change or rebrand | Every URL’s domain | High | Yes, for each domain variant | Redirect map, Change of Address, backlink outreach |
| HTTP to HTTPS | Protocol | Low to medium | No, Google detects it | Sitewide 301s, canonicals, mixed content |
| CMS or platform switch | URL patterns, templates, code | High | No | Redirect map, metadata and schema carry-over |
| Hosting or server move | IP address, server, speed | Low | No | DNS timing, uptime, Core Web Vitals |
| URL structure change | Paths within the same domain | Medium to high | No | Redirect map, internal links |
| Site merge | Two sites become one | High | Yes, if a domain retires | Content mapping, consolidation, redirects |
The Change of Address column follows Google’s Search Console documentation, which limits the tool to domain and subdomain moves.
The most useful rule in Google’s site move guidance is to change one thing at a time. A new domain and a new CMS in the same weekend leaves you guessing which caused a drop. If a platform switch is on the table, our WordPress vs Shopify comparison helps with that decision first.
Pre-Migration Checklist: 4 to 8 Weeks Before Launch
Most migration damage is decided before launch day. These four groups of tasks are where it gets prevented.
Benchmark the Site You Have
- Export every URL. Combine a full crawl, your XML sitemap, Search Console pages and GA4 landing pages. Crawlers miss orphaned pages that still earn links.
- Flag your high-value pages. Sort by organic clicks, conversions and inbound links. These get the most careful redirects.
- Export Search Console data. Save query and page performance, and record rankings for your priority keywords.
- Record Core Web Vitals and speed for each key template.
- Note current conversion rates so you can tell later if tracking broke.
Benchmarks taken now settle the “did we lose traffic?” argument later. If the Search Console is not set up yet, start with our Search Console setup guide.
Build the Redirect Map
- Map every old URL to its closest new equivalent, one to one.
- Use server-side 301 or 308 redirects. Google confirms that permanent redirects do not cause a loss in PageRank.
- Point every redirect straight to the final URL. Google recommends keeping chains to three hops or fewer; one is better.
- Never bulk-redirect old pages to the homepage. Where a page has no equivalent and no value, let it return a 404 or 410.
- Plan to keep redirects for at least a year, which is Google’s guidance, and longer if visitors still arrive through them.
The redirect map is the most important document in the whole project. Our redesign checklist walks through how we build that spreadsheet.
Prepare the New Site in Staging
- Password-protect staging and block indexing so Google never sees a half-built copy.
- Carry over titles, meta descriptions, H1s, canonicals, alt text and schema. A new CMS will happily generate defaults that erase years of optimization.
- Rebuild internal links to point at final URLs, not at redirects.
- Test Core Web Vitals on staging against Google’s “good” thresholds: LCP within 2.5 seconds, INP under 200 milliseconds and CLS under 0.1.
- Generate the new XML sitemap, split into multiple files if it passes 50,000 URLs or 50MB.
Our technical SEO audit checklist doubles as a staging QA list.
Line Up Domain, DNS and Accounts
- Verify the new property in Search Console before launch, for any domain or protocol change.
- Lower your DNS TTL a couple of days early so a server or domain switch spreads quickly.
- Check server capacity. Google crawls a moved site more heavily than usual, and a slow server during that window hurts.
- List every place your URLs live: Google Ads, Meta ads, email templates, Google Business Profile, social bios and directories.
- Pick a low-traffic launch day with your developer available, not a Friday afternoon.
Launch Day: The Migration Sequence
Run these steps in order:
- Take a complete backup of the old site.
- Deploy the new site and the full redirect file together, not hours apart.
- Remove the staging password and noindex, and confirm robots.txt is not blocking the site.
- Hand-test your top 50 old URLs. Each should land on its mapped page through a single 301.
- Confirm GA4, conversion tags and call tracking fire on the new templates.
- Submit the new XML sitemap in Search Console.
- For domain moves only, submit a Change of Address request for every verified variant of the old domain (www, non-www and subdomains). Google forwards signals for 180 days.
- Update your Google Business Profile URL and every paid-ad destination URL.
Post-Migration Checklist: The First 90 Days
First 72 Hours
- Crawl the live site for 404s, redirect chains, broken internal links and stray noindex tags.
- Check Search Console page indexing and crawl stats daily.
- Submit a test form, make a test call and run a test purchase to confirm conversions are still recorded.
- Fix any old URL that returns a 404 by adding its redirect the same day.
Weeks 1 to 4
- Compare clicks and rankings page by page against your benchmarks. A sitewide total can hide one key page losing half its traffic.
- Watch both sitemaps. Google’s guidance is that indexed pages in the old URL list should fall toward zero while the new sitemap’s indexed count rises.
- Ask the sites behind your most valuable backlinks to update their links.
- Update your URL in directories and social profiles.
Months 2 to 3
- Re-run the full crawl and Core Web Vitals check.
- Review the queries that lost position and the pages behind them.
- Only now start content rewrites or new sections, so any ranking movement has one cause.
- Leave your redirects in place. Cleaning them up after a few months undoes the work.
When we migrated our own site, the crawl after launch caught a template-level internal-link error across more than a dozen of our posts, something a redirect map alone would never have flagged. We also moved the structure first and rewrote content in scheduled passes afterwards. Organic clicks returned to our pre-migration baseline in [FILL: number of weeks, from Search Console].
Traffic Dropped After Migration? How to Diagnose It
| Symptom | Likely cause | Fix |
|---|---|---|
| Whole site disappearing from Google | Noindex or robots.txt block left over from staging | Remove the block and request indexing for key pages |
| Specific pages lost rankings | Missing or wrong redirect, or content cut during the rebuild | Correct the redirect and restore the content |
| Spike in 404 errors | Old URLs left out of the redirect map | Add 301s to the closest equivalent pages |
| Rankings steady, conversions down | Tracking tags missing on the new templates | Reinstall and test GA4 and conversion tags |
| Slow, gradual decline | Weaker internal linking or slower pages | Rebuild internal links and fix Core Web Vitals |
| Old URLs still indexed weeks later | Redirect chains, or the old sitemap removed too early | Flatten chains and keep both sitemaps submitted for now |
| Symptom | Likely cause | Fix |
|---|---|---|
| Whole site disappearing from Google | Noindex or robots.txt block left over from staging | Remove the block and request indexing for key pages |
| Specific pages lost rankings | Missing or wrong redirect, or content cut during the rebuild | Correct the redirect and restore the content |
| Spike in 404 errors | Old URLs left out of the redirect map | Add 301s to the closest equivalent pages |
| Rankings steady, conversions down | Tracking tags missing on the new templates | Reinstall and test GA4 and conversion tags |
| Slow, gradual decline | Weaker internal linking or slower pages | Rebuild internal links and fix Core Web Vitals |
| Old URLs still indexed weeks later | Redirect chains, or the old sitemap removed too early | Flatten chains and keep both sitemaps submitted for now |
A drop that keeps falling after a month almost always means a step on this checklist was missed.
How Long Does SEO Recovery Take After a Migration?
There is no fixed timeline. Google says new URLs can take a few weeks or more to appear on medium-sized sites, longer on large ones. In our experience, HTTPS and hosting moves settle fastest, while domain changes and site merges take the longest because every URL and every backlink has to be reprocessed.
Clean one-hop redirects, unchanged content, a submitted sitemap and a Change of Address request (for domain moves) speed recovery up. Changing domain, platform and content together slows it down. Be wary of anyone promising a precise recovery date.
The Bottom Line
Migrations rarely fail because of bad luck. They fail because a step got skipped: a redirect nobody mapped, a noindex tag nobody removed, a tracking code nobody tested. Benchmark the site you have, map every URL, launch in a deliberate sequence, and watch your data closely for 90 days. Do that, and Google follows you to your new address with your rankings intact.
Planning a move? Book a free pre-migration SEO audit. We will crawl your site, flag the pages carrying your rankings and show you what your redirect map needs before launch. Our Technical SEO work runs month to month, with no contract.
Frequently Asked Questions
Expect a temporary wobble while Google recrawls. A lasting loss usually traces to missing redirects, removed content or a leftover noindex tag.
Google recommends at least one year, and longer if people still reach your site through them.
No. The tool is only for new domains or subdomains. Google detects HTTP to HTTPS moves on its own.
Avoid it if you can. Changing one thing at a time tells you exactly which change caused any drop.
No. Redirect each page to its closest equivalent, and return a 404 or 410 where none exists.
Leaving the staging noindex tag or robots.txt block in place, which tells Google to drop the new site.
Rarely, as long as your URLs stay the same and the new server is fast and stable. Watch Core Web Vitals and uptime closely for the first few weeks.
