Site Migration SEO Checklist: Domain Changes, Redesigns & URL Moves

Site migration is one of the riskiest operations in technical SEO: changing domains, redesigning, restructuring URLs—one mistake can evaporate years of accumulated rankings and traffic overnight. But with thorough preparation and rigorous process, migrations can be completed smoothly. This article ties together the entire Technical SEO section, giving you a complete migration checklist from prep to wrap-up—and serves as the finale of this section.

Migration Types#

"Site migration" is a broad term—different types carry different risks and priorities. First, identify which type you're doing (often multiple combined):

Pre-Migration: Preparation#

Migration success is 80% preparation. Before taking action, complete these steps:

1. Full crawl of existing site: Use tools like Screaming Frog to crawl all URLs, status codes, titles, meta descriptions, and canonicals—save as a baseline snapshot.
2. Identify important pages: Combine GSC and analytics data to list high-value pages that drive traffic and rankings—prioritize protecting them.
3. Export backlink data: Use backlink tools to export links pointing to your site; identify which pages are link targets—after migration, these URLs must have destinations.
4. Record baseline metrics: Document pre-migration traffic, rankings, index count, Core Web Vitals—your reference for post-migration comparison.
5. Prepare staging environment: Build the new site in staging, protecting it with noindex or access control to prevent indexing (see Crawling & Indexing).

Core: URL Mapping & 301s#

This is the heart of the entire migration. Every old URL must have a clear destination, pointed via 301 permanent redirect one-to-one to the new URL.

Old URL                          New URL                         Type
/old-blog/seo-tips             /articles/seo-tips             301
/products/shoes.php?id=5       /shop/shoes/running            301
/about-us.html                /about                         301
/discontinued-product         /shop/category                 301  (no exact match→related page)

Key mapping principles:

• One-to-one, use 301: Permanent migration requires 301 (not 302) to transfer signals to the new URL—see HTTP Status & Redirects.
• Map to most relevant page: When no exact match exists, redirect to the most relevant page (such as a related category)—don't redirect everything to homepage—that's treated as a soft 404.
• Avoid redirect chains: Old URL should reach the final new URL in one hop—no A→B→C.
• Really no equivalent content: If content is permanently deleted with no replacement, let it return 404/410—don't force a redirect.
• Cover backlink targets: All old URLs with external links must be in your mapping table to preserve equity.

Migration Day#

Choose a low-traffic period and have a rollback plan ready. At launch, verify each item:

1. Deploy 301 redirects: Enable all redirects per your mapping table.
2. Remove staging protections: Delete staging-phase noindex and robots blocks—ensure new site is crawlable and indexable.
3. Update canonicals: All pages' canonical should point to the new URL itself.
4. Update internal links: Internal links should point directly to new URLs, not rely on redirect hops.
5. Update and submit new sitemap: New sitemap should contain only new URLs—submit to GSC.
6. Update robots.txt: Verify nothing is incorrectly blocked; Sitemap URL points to new domain.
7. Check hreflang: For multilingual sites, update hreflang to new URLs.
8. GSC Change of Address: For domain changes, use the Change of Address tool in GSC once both old and new properties are verified.
9. Update third-party: Analytics tools, ads, CDN, API callbacks, social profiles pointing to new domain.

# Verify old URL 301s to new URL in one hop
$ curl -IL https://old-domain.com/old-page
HTTP/2 301
location: https://new-domain.com/new-page
HTTP/2 200

# Verify new page returns 200, canonical points to self, no noindex

Post-Migration: Monitoring & Fixes#

Launch isn't the end—it's the start of monitoring. For weeks to months post-launch, watch closely:

• Crawling & indexing: In GSC, observe new URL indexing progress and old URL drop-off; watch for anomalies like "Crawled - Not Indexed" or "Redirect Error".
• 404 spikes: If Coverage Report shows many 404s, your mapping has gaps—add corresponding 301s immediately.
• Redirect issues: Hunt down redirect chains, loops, and misplaced 302s.
• Rankings & traffic: Compare against pre-migration baseline—minor fluctuation is normal; sustained significant decline means investigate immediately.
• Crawl stats: Monitor Googlebot crawl volume and error rates—confirm server stability.
• Core Web Vitals: Ensure new site performance meets thresholds—optimize if needed (see Site Speed).

Keep Redirects Long-Term#

A critical afterthought often overlooked: 301 redirects must be kept long-term—don't remove them after migration completes.

• Google needs time to transfer signals and fully update its index—removing redirects too soon aborts this process.
• External links pointing to old URLs will persist for a long time—once redirects are removed, these links turn into 404s, wasting their equity.
• Recommendation: Keep redirects for at least one year. For domain changes, retain ownership of the old domain and maintain redirects as long as possible—keep them if you can.

Complete Migration Checklist#

Pre-Migration

• Full crawl of old site, save URL/status/meta baseline
• Inventory high-value pages and keywords
• Export backlink data, mark backlink target URLs
• Record traffic, rankings, index count, CWV baseline
• Build protected staging environment (noindex/auth)
• Create complete old→new URL mapping table

Migration Day

• Choose low-traffic window, prepare rollback plan
• Deploy all 301s (one-to-one, no chains, no loops)
• Remove staging noindex / robots blocks
• Canonical, internal links point to new URLs
• Submit new sitemap, update robots.txt
• Update hreflang (for multilingual sites)
• GSC verify new property + use Change of Address
• Update analytics/ads/CDN/third-party configs
• Spot-check redirects and new page status codes

Post-Migration

• Monitor indexing progress and crawl errors
• Fix 404 spikes, complete missing mappings
• Hunt redirect chains/loops and incorrect 302s
• Track rankings and traffic against baseline
• Monitor CWV and server stability
• Keep 301s long-term (minimum one year)

This Site & Migration#

Frequently Asked Questions#

Do rankings always drop after a site migration?

Properly executed migrations typically only see short-term, minor fluctuations that recover within weeks to months—there should be no long-term loss. Google needs time to recrawl, process redirects, and transfer signals, so temporary ranking and traffic fluctuations during this period are normal. What causes permanent loss are errors: missing or incorrect redirect types, omitted URL mappings, major content changes, forgetting to migrate backlinks, etc. Thorough preparation, complete mapping, and diligent monitoring minimize risk.

How long should I keep redirects from the old domain?

At least one year, longer if possible (many recommend permanent or multi-year retention). Google takes time to transfer signals and update its index, and external links pointing to old URLs may persist long-term. Removing 301 redirects too early turns these old links into 404s, losing their equity. When feasible, maintain ownership of the old domain and keep redirects active indefinitely.

Should I migrate the entire site at once or in stages?

Depends on site size and migration type. Pure domain changes (URL paths unchanged) typically can be done all at once since mapping is straightforward. But when multiple changes are involved—major URL restructuring, content reorganization, platform change—risks compound; staging the migration is recommended. Complete one type of change, verify stability, then proceed to the next, making it easier to isolate problems if something goes wrong. Regardless of approach, operate during low-traffic periods and have a rollback plan ready.

What should I do in Search Console during a migration?

For domain changes, use Search Console's Change of Address tool to notify Google, provided both old and new domains are verified in GSC. Also verify the new site property, submit the new sitemap, and check the Coverage report and crawl stats. Post-migration, continuously monitor index status, crawl errors, 404s and redirect issues, fixing promptly. GSC is the most critical monitoring tool during migrations.