SEO Migration Checklist
A migration is where a site earns or loses a decade of link equity in a single afternoon, and the difference is almost always the redirect map. This checklist covers the fifteen checks that matter, from the inventory and the mapping through to the launch-day checks, the rollback plan, and what recovery actually looks like.
A site migration is the highest-risk project in SEO. Move a domain, platform, or URL structure badly and you lose rankings, traffic, and years of accumulated link equity. This SEO migration checklist covers the golden 301 map, staging lockdown, launch sequence, and post-launch monitoring. Follow these 15 steps to turn a risky migration into a routine one.
A Site Migration Is a Data Transfer
Google does not automatically understand your new domain. It understands redirects, sitemaps, and metadata. The entire job is transferring signals from old URLs to new ones, page by page, with nothing lost to 404s, chains, or noindex mistakes. Every top page redirecting to the homepage is a small disaster; every old URL mapped to its closest new equivalent is a clean transfer.
The failures cluster in predictable places: staging environments leaked to crawlers, metadata dropped by the new platform, internal links still pointing at old URLs, and robots.txt blocking the wrong paths. Each one is preventable with a pre-launch checklist and a post-launch audit.
Moz's own website migration guide makes the point from the other side. It notes that Google's documentation on site moves is thin and understates how often migrations cost traffic and revenue. The two checkpoints that matter most in a website migration SEO project are the redirect map and the first 48 hours after go-live.
Plan the migration like a launch, because that is what it is. Pick a low-traffic window, prepare a rollback plan, and treat the first 48 hours after launch as the highest-attention period of the project. This page is part of the complete technical SEO checklist.
Sources
- Site moves and migrations: plan the redirect strategy, keep redirects for at least a year, move all URLs at once on small and medium sites, Google Search Central.
- Change of Address: Google links the old and new sites for 180 days, then treats them as unrelated, Search Console Help.
- A study of 892 domain migrations found average traffic recovery took 523 days, and 17 percent never returned to baseline after 1,000 days, Search Engine Journal, Dan Taylor, 2025.
- A study of 1,052 domain migrations found a median recovery of 304 days, with 22.8 percent recovered by day 90 and 59.5 percent by day 365, SALT.agency, Dan Taylor, 2026.
- Normal post-migration volatility is a 10 to 20 percent dip that recovers within two to six weeks, while a migration hangover starts at a 30 to 50 percent drop, Search Engine Journal, Sophie Brannon, 2026.
- The Website Migration Guide: SEO Strategy, Process, and Checklist, Moz, Modestos Siotos, 2018.
Migration Types and Risk
The SEO Migration Plan: Before, During, and After Go-Live
Three phases, one rule: nothing transfers itself.
SEO for a site migration comes down to which URLs carry your traffic and where each of them lands. An SEO migration plan runs in three phases. Before go-live you capture a baseline, build the golden 301 map, and lock down staging. On launch day you switch DNS and verify every redirect, robots.txt, and canonical. After launch you submit the Change of Address, monitor 404s daily, and track recovery week by week.
Before: 4-6 Weeks Out
Preparation decides the outcome.
- Crawl the live site and export the Search Console URL inventory as your baseline
- Build the golden 301 map covering every old URL to its closest new equivalent
- Inventory titles, meta descriptions, headings, and schema for parity on the new build
- Lock staging behind authentication with a robots noindex
- Dry-run the redirect rules on staging and lower DNS TTL in advance
During: Launch Day
The highest-attention 48 hours.
- Switch DNS, then confirm the new site answers with 200s
- Sample old URLs and verify every one returns a single-hop 301, never a chain
- Check robots.txt is crawlable and blocks nothing it should not
- Remove the staging noindex and confirm canonical tags point to final URLs
- Publish the new XML sitemap and keep the old server live
After: First 8 Weeks
Monitoring turns a dip into a recovery.
- Submit the Change of Address tool for whole-domain moves
- Monitor 404s and redirect gaps daily in week 1, then weekly
- Check index coverage in Search Console every week
- Compare traffic against the baseline and expect the normal U-curve dip
- Keep old-domain redirects alive for 6-12 months minimum
The 15-Step SEO Site Migration Checklist
From baseline crawl to post-launch recovery monitoring.
| # | Check | Who Does It | Tool | Difficulty |
|---|---|---|---|---|
| 1 | Record a pre-migration baseline crawl | You | Screaming Frog | Easy |
| 2 | Build the golden 301 redirect map | You | Spreadsheet | Hard |
| 3 | Lock down staging with authentication | Developer | Auth / robots | Medium |
| 4 | Keep URLs stable where possible | You | URL planning | Medium |
| 5 | Preserve titles, meta descriptions, and H1s | You | CMS | Medium |
| 6 | Match status codes, avoid soft 404s | Developer | Server / crawl | Medium |
| 7 | Update internal links to new URLs | Developer | CMS / find-replace | Medium |
| 8 | Update canonicals, hreflang, and sitemaps | Developer | CMS | Medium |
| 9 | Launch in a low-traffic window | You | Analytics | Easy |
| 10 | Check robots.txt and noindex after launch | Developer | Test | Easy |
| 11 | Submit the Change of Address for domain moves | You | GSC | Easy |
| 12 | Verify old and new properties in Search Console | You | GSC | Easy |
| 13 | Monitor crawls, indexation, and 404s post-launch | You | GSC / logs | Medium |
| 14 | Track the U-curve and recovery timeline | You | Analytics | Easy |
| 15 | Keep the old site alive with redirects | You | DNS / server | Medium |
Every Migration Check Explained
How to execute each phase of the migration safely.
1 Record a Pre-Migration Baseline Crawl
Before touching anything, crawl the entire site and export every URL, status code, title, and meta description. Record traffic and rankings per page. This baseline is the ground truth you compare against after launch to know exactly what was lost, gained, or missing.
2 Build the Golden 301 Redirect Map
Create a one-to-one mapping of every old URL to its closest new equivalent. Redirect the homepage to the homepage, category to category, product to product. Every old URL with links or traffic needs a destination. Top pages dumped on the homepage leak most of their equity. Avoid redirect chains and loops.
3 Lock Down Staging With Authentication
A staging site indexed by Google is a classic migration disaster: duplicate content, split signals, and diluted rankings. Protect staging with HTTP authentication and a robots.txt disallow, and verify with the URL Inspection tool that Google cannot see it. The staging site must never be publicly crawlable.
4 Keep URLs Stable Where Possible
The best redirect is no redirect. If the platform allows it, preserve existing URL slugs during migration. Every URL you keep unchanged is link equity that never has to travel. Change URLs only when the platform forces it or the new structure is genuinely better.
5 Preserve Titles, Meta Descriptions, and H1s
New platforms frequently drop or truncate metadata. Export the old titles, meta descriptions, and H1s and import them into the new site. Missing metadata means lost CTR and weaker relevance signals. Do not let a template default overwrite years of optimized copy.
6 Match Status Codes, Avoid Soft 404s
Every migrated page must return a real status: 200 for live pages, 301 for redirected pages, and 404 or 410 for genuinely removed content. Soft 404s, pages returning 200 with no content, confuse crawlers and waste crawl budget. Validate the status code matrix after launch.
7 Update Internal Links to New URLs
Internal links still pointing at old URLs force crawlers through redirects on every hop. Find and replace old internal links with new ones sitewide. This preserves internal link equity and keeps the crawl path clean. Redirects for legacy external links stay, but your own navigation should be direct.
8 Update Canonicals, Hreflang, and Sitemaps
Every canonical tag, hreflang annotation, and sitemap entry must reference the new URLs. An old canonical on a new page points Google back to a redirected URL and undermines the transfer. Regenerate the XML sitemap from the new site and submit it fresh.
9 Launch in a Low-Traffic Window
Migrate during the quietest hours for your audience, typically overnight or a weekend for most businesses. A low-traffic launch window limits the number of users hitting errors during the highest-risk period and gives you hours of crawl data before peak traffic.
10 Check Robots.txt and Noindex After Launch
The new platform often ships a restrictive robots.txt or accidentally inherits noindex rules from staging. Test the live site with the URL Inspection tool immediately after launch. A sitewide noindex left in place is a silent killer that looks like a normal migration dip for weeks.
11 Submit the Change of Address for Domain Moves
For whole-domain moves, use Search Console's Change of Address tool. It tells Google the old domain has permanently moved to the new one and only works with verified properties on both domains plus 301 redirects in place. It cannot be undone, so submit it only after the redirects are verified live.
12 Verify Old and New Properties in Search Console
Keep both old and new Search Console properties verified for months. The old property shows redirect traffic and legacy 404s; the new property shows the indexation build. Comparing the two tells you whether signals are transferring or stalling.
13 Monitor Crawls, Indexation, and 404s Post-Launch
Watch the new property for crawl activity, indexed pages, and 404 reports. A spike in 404s means a redirect gap. Check server logs to confirm Googlebot is following redirects and not hitting chains. Fix gaps daily during the first two weeks.
14 Track the Recovery Timeline
Expect the dip and do not panic. A normal post-migration dip is 10 to 20 percent and stabilizes within two to six weeks, according to practitioner reporting in Search Engine Journal. A drop of 30 percent or more with fresh 404s and a falling indexed count is a different problem, and it needs a redirect and indexation audit rather than patience.
15 Keep the Old Site Alive With Redirects
Maintain the old domain with 301 redirects for at least a year. Google's own site move guidance says at least one year, and suggests indefinitely for users, because bookmarks, external links, and direct traffic all depend on it. Letting the old domain lapse or serve dead content destroys residual equity you did not need to lose.
What to Expect After an SEO Site Migration
Two clocks run at once, and they disagree with each other.
Indexing and traffic recovery are different processes on different timelines. Google states that a small to medium site can take a few weeks for most pages to move to the new URLs. Traffic takes much longer, because Google has to recrawl every old URL, process the redirect, and reassign the links pointing at it. Measured recovery data puts the median domain migration at 304 days.
| Recovery window | Share of migrations | Cumulative recovered |
|---|---|---|
| 0 to 30 days | 5 percent | 5.1 percent |
| 31 to 90 days | 18 percent | 22.8 percent by day 90 |
| 91 to 180 days | 13 percent | 35.4 percent by day 180 |
| 181 to 365 days | 24 percent | 59.5 percent by day 365 |
| 1 to 2 years | 24 percent | 83.5 percent by day 730 |
| 2 years and beyond | 16 percent | 86.1 percent by day 1,095 |
The figures cover domain migrations specifically, where the whole site moves to a new domain. Same-domain site migrations, where only the URL structure changes, tend to recover faster, because the research attributes the longest recoveries to authority gaps between the old and new domain, and a same-domain move has no such gap to close.
The data comes from 1,052 domain migrations measured by SALT.agency in 2026, where recovery means the new domain's monthly organic traffic matched the old domain's pre-migration baseline. The same researcher's earlier study of 892 migrations put the average at 523 days and found 17 percent had not returned to baseline after 1,000 days. The two studies use different samples and different windows, so treat the range as the honest answer rather than a single number.
What matters for your launch is the shape of the curve, not the total. A 10 to 20 percent dip that stabilizes inside six weeks with no new 404s is normal volatility. A 30 percent or larger drop alongside a falling indexed count means something is broken, and the fix is a redirect and indexation audit, not more waiting.
Read the curve weekly, not daily. Google reprocesses a migration in waves, so a single bad day tells you nothing. Export the baseline, compare the same week against the same week before the migration, and look at the trend line over four weeks before you change anything.
How to Build the Golden 301 Redirect Map
The one artifact every later migration question comes back to.
The redirect map is a spreadsheet with one row per old URL and exactly one destination. Building it from a single crawl is the most common mistake, because a crawl only finds URLs that are linked. Orphan pages, old campaign URLs, and files that earned backlinks all carry value a crawler will never discover on its own.
Six sources for the URL list
- A full crawl of the live site
- Every URL in your XML sitemaps
- Search Console pages with clicks or impressions
- Analytics landing pages with sessions
- URLs with external backlinks
- Your existing redirect rules
Four mapping rules
- One to one wherever a matching page exists
- Merged pages redirect to the merged page
- Retired pages go to the nearest real category, or return 404 or 410
- Never redirect in bulk to the homepage
Five spreadsheet columns
- Old URL
- New URL
- Expected status code
- Reason for the decision
- Source of traffic or links
| Old URL | New URL | Status | Decision rule |
|---|---|---|---|
| /blog/site-migration-seo/ | /blog/website-migration-seo/ | 301 | Closest equivalent, one to one |
| /old-product-category/ | /collections/all/ | 301 | Merged into one consolidated page |
| /sale-2019/ | no destination | 410 | Retired with no replacement, so it is removed rather than redirected |
| /index.php?p=142 | /blog/example-post/ | 301 | Parameter duplicate of an existing page |
| /old-blog/post-1/ | /blog/post-1/ | 301 | Path change only, same page and same topic |
Google's guidance is explicit on the last rule. Redirecting many old URLs to one destination, such as a homepage, can be treated as a soft 404, which means Google discards the redirect signal instead of transferring it.
Special Cases That Break Most Migrations
The standard checklist does not cover these, and they cause most failures.
| Case | What breaks | What to do instead |
|---|---|---|
| HTTP to HTTPS | A duplicate host serving both protocols splits signals | 301 the HTTP host to HTTPS in one hop. Skip Change of Address, Google handles it |
| www to non-www | Two live hosts competing for the same pages | Pick one canonical host, 301 the other, and align canonicals, sitemaps, and internal links |
| Subdomain to subdirectory | The new path looks like a fresh site with no history | 301 every subdomain URL and keep the old subdomain live and redirecting |
| Merging two sites into one | Duplicate pages compete inside the destination site | Map each old site's pages to its best home, and keep every old domain registered and redirecting |
| Moving to a client-rendered framework | Content that only appears in the browser is invisible to crawlers and AI crawlers | Confirm the main content sits in the server-rendered HTML before launch |
| Changing platform and URLs together | Two variables change at once and nobody can tell which caused the drop | Move the URLs first or freeze the URL structure, so one change can be diagnosed |
| Ecommerce catalog with filter URLs | Faceted URLs multiply into thousands of thin pages | Map only the canonical category and product URLs, and let filter combinations return 404 |
Google's Change of Address tool does not apply to every move. It is for domain and subdomain moves only. HTTP to HTTPS, www to non-www, and path changes within the same domain are handled by canonical tagging and redirects alone, and submitting them through the tool is at best unnecessary.
For a domain move, submit Change of Address for every verified variant of the old domain, including subdomains and both www forms, even the ones you no longer use.
Launch Day Hour by Hour
The order below catches the failures in the sequence they would otherwise surprise you.
| When | Action | How you verify it |
|---|---|---|
| 24 hours before | Lower DNS TTL to a few minutes so the switch propagates fast | DNS panel shows the new TTL |
| 24 hours before | Issue the TLS certificate on the new host | Certificate validates on the new hostname |
| 24 hours before | Freeze publishing and write the rollback command down | Rollback command saved in the runbook |
| T0, switch | Switch DNS, keep the old server running | New host answers with 200 |
| T0 plus 15 minutes | Remove the staging block: auth, noindex, robots disallow | URL Inspection shows the page as crawlable |
| T0 plus 30 minutes | Purge the server cache and the CDN, then test redirects | Scripted test returns one hop and a final 200 |
| T0 plus 45 minutes | Run the whole old URL list against the live site | Every row resolves to its intended destination in one hop |
| T0 plus 60 minutes | Check canonicals, hreflang, robots.txt, and the new sitemap | Canonicals self-reference, sitemap loads and lists new URLs only |
| T0 plus 90 minutes | Verify analytics and forms, and test a message from a phone | Test conversion recorded, message arrives in the inbox |
| T0 plus 2 hours | Submit the new sitemap and file Change of Address for domain moves | Search Console confirms both submissions |
Two of these steps catch mistakes that hide for weeks. Purging the cache before testing redirects is the one that fools teams most often: a cached 200 makes every check pass while every visitor still sees the old site. And leaving the staging noindex in place looks exactly like a normal migration dip for weeks, so check it in the first hour, not the first month.
If you changed DNS, confirm the mail records were left untouched and that email still arrives. A migration that silently breaks contact forms costs more in lost leads than it costs in lost rankings.
The Rollback Plan
The step that turns a failed migration into a delay.
A rollback plan that you never use costs an afternoon of preparation. A rollback plan that you need and do not have costs the business. Write it before cutover, not after the first alarm, and store it somewhere the person on call can reach without asking anyone.
- Define the trigger in advance, for example the indexed count falling below half the baseline or a redirect map error rate above a set threshold.
- Keep the old server, the old DNS records, and a pre-migration database backup for at least 30 days after launch.
- Write the exact rollback command, not the intention to roll back, and confirm the person on call has the credentials to run it.
- Do not cancel old hosting on cutover day. Old hosting is the rollback.
- Keep the old domain renewed and paid for at least a year so nobody buys it and points it somewhere else.
Friday evening launches with nobody on call over the weekend are how a small fault becomes a large one. Launch when your developer is available for the following days.
SEO Migration Mistakes That Cost Rankings
The failures behind most post-migration traffic drops.
Redirecting everything to the homepage
Dumping every old URL on the homepage leaks most link equity and breaks user intent. Google's guidance warns this can be read as a soft 404. Map each URL to its closest equivalent.
Leaking the staging site
A crawlable staging environment creates duplicate content and splits signals. Lock it down with auth and robots.txt, then verify with the URL Inspection tool.
Sitewide noindex after launch
Inherited noindex rules from staging look like a normal dip for weeks while the whole site stays out of the index. Check it in the first hour.
Redirect chains and loops
Googlebot can follow up to 10 hops, and Google advises redirecting straight to the final destination instead. Chains add latency for users and lose signal at every step.
Dropped metadata
New platforms truncate titles and descriptions. Without an import, CTR and relevance signals disappear with them. Export before you rebuild.
Letting the old domain die
Lapsing the old domain breaks legacy links and direct traffic. Keep it alive with 301s for at least a year, and keep paying for it.
Changing everything at once
New URLs, new content, new design, and a new domain in one launch leaves no way to diagnose the drop. Move one variable at a time.
Forgetting to purge the cache
A cached 200 makes every redirect test pass while every visitor still sees the old site. Purge the server and the CDN, then test.
Backlink Reclamation After Launch
The step most teams skip, and one of the reasons recovery takes a year.
A 301 redirect tells Google to transfer a link. It does not update the page that carries the link, so every referring domain keeps pointing at a URL that now redirects. Google has to recrawl that page, read the redirect, and reassign the signal. That crawl is the reason recovery takes months rather than days.
Asking the linking sites to update their URLs directly removes the recrawl from the critical path. It is a short email to a small list, and the effect on recovery time is disproportionate to the effort.
- Export your top linking pages from a backlink tool and sort by the number of links each page sends.
- Work down the list, starting with the pages that hold the most links to your most valuable URLs.
- Send one email per site, naming the old URL and the new URL so the editor does not have to look anything up.
- Update your own internal links and your own profiles first, because those are the links you control outright.
- Log the responses. A reclaimed link is worth more than a redirect, and it is measurable.
Google's own site move guidance makes the same point, recommending you update your links and any high-volume links from other websites to point at the new URLs, and to keep redirects in place for the long term regardless.
Migration Tools and What They Cost
Audit redirects, crawls, and indexation through the transition.
| Tool | Use it for | Cost |
|---|---|---|
| Screaming Frog | Crawling both sites and exporting the URL list that becomes your 301 map | Free to 500 URLs |
| Google Search Console | Change of Address, URL Inspection, index coverage, and 404 reports | Free |
| Google Analytics | The pre-migration baseline and the recovery curve you compare it against | Free |
| Redirect checker | Validating every redirect chain and status code from the map | Free |
| Server log analyser | Confirming Googlebot follows the redirects and is not hitting errors or chains | Free to low cost |
| Backlink tool | Building the reclamation list of pages that still point at old URLs | Paid, subscription |
| Site crawler suite | Continuous post-launch audits for indexation gaps and metadata loss | Paid, subscription |
Screaming Frog
Crawls old and new sites, exports the URL list for your 301 map, and finds redirect chains and soft 404s.
Free (500 URLs)Google Search Console
Change of Address, URL Inspection, crawl reports, and 404 coverage across old and new properties.
FreeRedirect checkers
Validate every redirect chain and status code from the map before and after launch.
FreeServer log analyzers
Confirm Googlebot is following redirects to the new URLs and not hitting errors or chains.
FreeAnalytics
Track the recovery curve, compare pre- and post-migration traffic, and spot lost landing pages.
FreeSite crawler suites
Continuous post-launch audits for indexation gaps, metadata loss, and internal link errors.
PaidRelated Technical SEO Checklists
Keep exploring the technical SEO series. Every checklist follows the same structure.
Redirects and Status Codes
The 301 and 410 decisions that make or break a migration.
Indexing and Canonicalization
Getting the new site indexed after Google has processed the redirects.
Site Architecture
Plan the new URL structure and internal linking before you move.
Crawl Budget and Log Analysis
Use logs to confirm Googlebot is following the golden map.
Ecommerce Faceted Navigation
Extra care when migrating a catalog with filter URL structures.
Full Technical SEO Audit
Audit before and after launch to confirm nothing was dropped.
Get Help With Your Site Migration
A migration needs two roles: a developer who owns the server and an SEO who owns the map. Clienvora writes the redirect map, the launch runbook, and the post-launch monitoring plan, then works with your developer to verify every hop and every status code before and after go-live. Start with a free audit of your current URL inventory.
We reply within 24 hours with the redirect risks we can see from your current URL structure.
Site Migration FAQs
Direct answers on redirects, recovery, and risk.
Longer than most teams plan for. Google's own documentation says a small to medium site takes a few weeks for most pages to move, and that redirects should be kept for at least a year. Independent measurements of over a thousand migrations put the median recovery at around 300 days, with a fifth of sites taking more than a year. Plan for months, not weeks.
Export every URL from the old site with its traffic, links, and rankings, then decide for each one where it goes. Every URL that had a link or an impression needs a destination, and the default of sending everything to the homepage is what destroys the equity. One old URL, one new URL, one 301, and no chains.
No. Every URL change adds a layer of risk to an event that already carries plenty. Keep the existing paths if you can, and if the platform makes that impossible, change as few as possible and redirect every one of them. A migration with no URL changes is the version where the SEO outcome is predictable.
That the old URLs redirect in one hop to the right new URLs, that the new pages return 200, that the canonical points at themselves, that the sitemap lists only the new URLs, and that the analytics are recording. Then submit the sitemap and watch the coverage report for a week. The first day is for finding the obvious breakages.
Roll back to the previous version, which is why you take a full backup and a database snapshot before you start rather than after. A rolled-back migration costs a day. A half-migrated site with 4,000 broken redirects costs a quarter. The rollback plan is not a precaution, it is the cheapest thing on this list.