When Search Engine Journal tracked 892 domain migrations in third-party tools, the new domain took 523 days on average to reach the old domain's estimated organic traffic, and 17% had not got there after 1,000 days (Search Engine Journal, January 2025). Most of the damage in a migration is done before launch day, in a spreadsheet nobody finished.
This guide covers the three pieces of work that decide whether a redesign or replatform keeps its rankings: the redirect map, a rehearsal on staging, and a 30-day watch. The rules come from Google's site move documentation.
Why migrations lose rankings, and how much
Domain moves are slow to recover. Dan Taylor's Search Engine Journal study found the 2023 sample of 171 migrations took 229 days on average, with 42% never recovering; the 2025 sample of 892 took 523 days. These are crowd-sourced, third-party traffic estimates, so treat them as a warning, not a forecast. Our CMS Migration Statistics 2026 post puts them next to switching rates and costs.
Unchanged URLs are the cheapest insurance. A 2013 Practical Ecommerce case report by Jill Kocher Brown describes three redesigns. The one that kept its main URLs saw no noticeable change. The one that changed every URL with a full 301 plan lost about 25% for six weeks, then finished 19% up. The one that skipped redirects was down 42% after 12 days. Three old anecdotes, but the order matches Google's guidance.
Most losses trace back to a short list of mistakes. Google's troubleshooting section names them: noindex or robots.txt blocks left over from staging, redirects pointing to the wrong or non-existent URLs, crawl errors, servers that cannot take the extra crawling, and sitemaps still listing old URLs. All of them can be caught before launch.
Decide what is changing, one thing at a time
Google advises changing one thing at a time: move the domain, then change the layout, not both on one night. Most projects still bundle a platform change and a redesign, so be clear which of these you are doing, because each needs different steps.
| What changes | Redirect map needed | Change of Address tool | Main risk |
|---|---|---|---|
| Hosting only, same URLs | No | No | DNS cutover and server errors |
| Design only, same URLs | No, unless pages are removed | No | Lost internal links, changed titles and copy |
| Platform or CMS, same URLs | Only for URLs the new CMS cannot reproduce | No | URL patterns the new CMS forces on you |
| URL structure, same domain | Yes, every changed URL | No | Incomplete map, chains, homepage dumping |
| Domain or subdomain | Yes, every URL | Yes, for every verified variant | Long recovery, signals split across domains |
| HTTP to HTTPS, or www to non-www | Yes, usually a pattern rule | No | Mixed canonicals |
Source: Google Search Central, Site moves with URL changes and Changing your web hosting; Google Search Console Help, Change of Address tool, read 2026-10-21
For a hosting-only move, Google suggests lowering DNS TTL to a few hours at least a week ahead. For WordPress to Webflow specifically, our WordPress to Webflow Migration checklist covers the permalink patterns; this guide is the platform-neutral version.
The redirect map: build it before anyone designs a template
The redirect map is a spreadsheet with one row per old URL and a column for where it goes. It is the document that decides the outcome.
Collect every old URL, from more than one place. Google lists sitemaps, server logs or analytics, the Search Console Links report and the CMS's own page list; Screaming Frog adds a full crawl and backlink tools. No single source is complete: crawls miss orphan pages and analytics misses pages with links but no visits. Google also asks you to include images, videos and downloads such as PDFs.
Save the live crawl as a baseline. Screaming Frog's migration guide makes this step one: a complete crawl of the current site to compare staging against and to test old URLs after launch. Crawl again just before launch if content changes often.
Rank the rows by value. URLs with clicks, conversions or referring domains get a hand-checked destination. Long tails can use pattern rules.
Map to the closest equivalent, not the nearest page. Google says redirecting many old URLs to one irrelevant page, such as the homepage, can be treated as a soft 404. Merged pages can all point to the merged page. Content that is gone should return 404 or 410; Google treats all 4xx codes except 429 the same and drops the URL from the index.
| Column | What goes in it | Why |
|---|---|---|
| Old URL | Full path, with protocol and host | The thing you are testing after launch |
| Source | Crawl, sitemap, logs, GSC, backlinks | Shows coverage gaps |
| Clicks, 12 months | From Search Console | Sets the priority |
| Referring domains | From a backlink tool | Pages with links need exact mapping |
| New URL | Final destination, never an intermediate | Avoids chains |
| Rule type | One-to-one, pattern, 410 | Pattern rules need extra testing |
| Owner and status | Who checked it, pass or fail | Makes the rehearsal auditable |
Source: Google Search Central, Site moves with URL changes; Screaming Frog, How to use the SEO Spider in a site migration
Pick the right status code. Google recommends server-side 301 or 308 redirects. It treats a 302 or 307 as a weak signal, so the old URL may stay in results, and JavaScript redirects are a last resort.
The rehearsal: launch the site on staging first
A rehearsal runs the launch against staging so you fix what breaks while nobody can see it. On a four-week build, we would put it at the start of the final week.
Crawl staging and compare it with the live crawl. Screaming Frog's crawl comparison maps live URLs to staging URLs, even across hostnames, and its change detection flags changed titles, meta descriptions, word counts and internal links. A migration is the worst time to rewrite every title tag.
Check internal links against the map. Google asks for internal links to point at new URLs directly, not through your own redirects.
Test every redirect in the map. Crawl the old URL list in list mode with redirects followed. Each row should show one hop, a 301 or 308, a final 200 and an indexable destination, with no loops. Screaming Frog also says to check final addresses by hand, because a redirect to an unrelated page will likely be ignored by Google.
Prepare the switches you will flip. Google suggests preparing the production robots.txt and the list of noindex rules to remove before launch day. Prepare the new XML sitemap too: one file holds up to 50,000 URLs or 50MB uncompressed.
Check canonicals and verification. Every new URL needs a self-referencing canonical. If Search Console is verified by an HTML file or meta tag, the new site must carry it.
Launch day, in order
- Freeze content changes on the old site and take a final crawl.
- Remove staging blocks: production robots.txt live, noindex rules removed.
- Turn on redirects and publish the new site.
- Spot-check the most valuable old URLs with the URL Inspection live test, then rerun the full list.
- Submit the new sitemap and keep the old one, so you can watch its indexed count fall.
- For a domain change, submit the Change of Address for each old property.
- Update links you control: social profiles, ad campaigns and partner pages that send visits.
For domain moves, Dan Taylor suggests from experience putting the new URLs live 24 to 48 hours before the redirects; that is one consultant's view, not Google's.
The 30-day watch
Google says a move is complete only when Googlebot has visited every old and new URL at least once. A fixed schedule stops the team panicking on day two or missing a broken template until day 40.
| When | Check | Where | What good looks like |
|---|---|---|---|
| Launch hour | Live visitors and form events | Analytics real-time report | Sessions and conversions arriving on new URLs |
| Day 1 | Full redirect list rerun | Crawler in list mode | One hop, 301 or 308, final 200, indexable |
| Day 1 | Robots.txt, noindex, canonicals | Crawl of the new site | Every page meant to rank reads as indexable |
| Days 1 to 7 | Server errors and 404s | Server logs, Page indexing report | No spike in 5xx or Not found on new URLs |
| Days 3 to 14 | Sitemap indexed counts | Search Console Sitemaps | Old sitemap falling, new sitemap rising |
| Weekly | Clicks and impressions by page | Search Console Performance, weekly view | Top pages recovering towards baseline |
| Days 14 to 30 | Top 50 old URLs | URL Inspection | Google-selected canonical is the new URL |
| Day 30 | Backlinks to old URLs | Backlink tool, outreach list | Highest-value links updated at the source |
Source: Google Search Central, Site moves with URL changes; Google Search Console Help, Page indexing report and URL Inspection tool; Google Analytics Help, Realtime report
Real-time data is for the first hour only. Google Analytics' Realtime report covers the last 30 minutes with limited attribution. Use it to confirm tracking survived, not to judge traffic.
Ignore redirect warnings on the old sitemap. Google says they are normal.
Validate fixes in small batches. Validation in the Page indexing report typically takes up to about two weeks; a sitemap of only your key pages validates faster. URL Inspection has a daily limit per property, so spend it on high-value pages.
Use the weekly view. The Performance report can smooth data by week, removing weekend dips.
Know when to escalate. If a page that ranked well shows no impressions after two weeks, check the redirect, the destination's indexability, its canonical, and whether its content changed. We would check content with the crawl comparison, not from memory.
What this means for your migration
A migration keeps its rankings when the redirect map is finished before design sign-off, the launch is rehearsed on staging and somebody owns the 30-day watch. The hard part is getting marketing, design and development to agree on the map early.
At Octo we build marketing sites in Webflow on a four-week process, and over twelve months we delivered more than 20 Webflow sites as a white-label partner, the largest with a CMS of over 1,200 items. On a redesign or replatform, we would treat the redirect map as a week-one deliverable rather than a launch task. If you are planning a move, our marketing websites service page explains how we scope it.
