SEO Migration Checklist
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 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.
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
- A study of 892 migrations found average traffic recovery took 523 days, Search Engine Journal migration study.
- 50%+ traffic loss is common and 17% of sites never fully recover, Search Engine Journal migration study.
Migration Types and Risk
The 15 Migration Checks
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 |
Deep Dive: Every 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 U-Curve and Recovery Timeline
Expect the dip and do not panic. A 10-25% traffic decline after launch is normal, with recovery typically beginning within 2-8 months as Google re-crawls and re-ranks the new URLs. Track weekly. If traffic keeps sliding past the expected window, audit for redirect and indexation problems.
15 Keep the Old Site Alive With Redirects
Maintain the old domain with 301 redirects for at least 6-12 months, ideally indefinitely. Old bookmarks, external links, and direct traffic all depend on it. Letting the old domain lapse or serve dead content destroys residual equity you do not need to lose.
Migration Launch Sequence
The ordered steps from go-live to recovery.
| Phase | Timing | Key action |
|---|---|---|
| Pre-launch | Weeks before | Baseline crawl, golden 301 map, staging lockdown |
| Launch day | Day of | Switch DNS, verify live, test status codes |
| 48 hours | Days 1-2 | Fix redirect gaps, check robots and noindex |
| Two weeks | Days 3-14 | Submit Change of Address, regenerate sitemaps |
| Recovery | Months 1-8 | Track U-curve, monitor indexation weekly |
Common Migration Mistakes
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. 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.
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.
Redirect chains and loops
Redirects that bounce through multiple hops lose equity and eventually stop resolving. Test every chain length.
Dropped metadata
New platforms truncate titles and descriptions. Without an import, CTR and relevance signals disappear with them.
Letting the old domain die
Lapsing the old domain breaks legacy links and direct traffic. Keep it alive with 301s for at least 6-12 months.
Migration Tools
Audit redirects, crawls, and indexation through the transition.
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 U-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 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.
Planning a Migration?
Get professional migration support from Clienvora. Our expert team builds your golden 301 map, locks down staging, and monitors recovery so your rankings survive the move.
Free consultation. Get a personalized technical SEO audit for your website today. Or download the full checklist PDF.
Migration Frequently Asked Questions
Direct answers on redirects, recovery, and risk.
A major site change such as a new domain, platform, or URL structure that requires careful SEO planning to preserve rankings, traffic, and link equity.
Expect a U-curve: a 10-25% dip after launch, with recovery typically starting within 2-8 months. Large sites or migrations with redirect errors can take longer.
A complete old to new URL redirect map covering every page. One-to-one where possible, no chains or loops, passing link equity from every old URL to its closest new equivalent.
Yes, keep it alive with 301s for at least 6-12 months, ideally indefinitely, to preserve direct traffic and legacy links.
A Search Console feature for whole-domain moves that tells Google the old domain moved to the new one. Requires verified properties on both and 301s live.
Usually a redirect gap, dropped metadata, a sitewide noindex, a leaked staging site, or simply the normal U-curve dip. A post-launch audit identifies the cause.