The Site Migration Checklist That Prevents Traffic Loss

Site migrations are the highest-risk project in SEO. Redesigns, replatforming, domain changes, and HTTPS moves all touch URLs, content, and infrastructure at once — and any one mistake can erase years of organic equity overnight. The good news: nearly every migration disaster is preventable with disciplined preparation. Here's the checklist.

First, define what's actually changing

"Migration" covers very different projects, each with its own risk profile:

• Domain change (old.com → new.com) — highest risk; every URL changes.
• Protocol change (HTTP → HTTPS) — lower risk if redirects are clean.
• URL structure change — high risk; requires a full redirect map.
• Replatforming (new CMS/e-commerce engine) — high risk; templates and URLs both change.
• Redesign (same URLs, new templates) — medium risk; content and internal linking shift.

Know your type before you plan. The more that changes at once, the more that can break.

Pre-launch: build your safety net

1. Benchmark everything. Before touching anything, record current state: organic traffic by page, rankings for key terms, indexed URL count, top landing pages, and conversions. Capture a Domain Overview at /tools/domain-overview and export your Search Console data via /search-console. You cannot measure success without a baseline.

2. Crawl the current site. Run a Full Site Audit at /full-site-audit to get a complete inventory of live, indexable URLs. This is the master list every old URL must be accounted for.

3. Build the redirect map. Every old URL maps to its closest new equivalent. Rules:

• Use 301 (permanent) redirects, never 302.
• Redirect to the most relevant page, not a blanket redirect to the homepage (which search engines treat as a soft 404).
• Map one hop only — old URL straight to final new URL, no chains.
• Prioritize by traffic and backlinks: your top 20% of pages carry most of the equity.

4. Preserve on-page equity. Keep titles, headings, body content, and internal links as intact as possible. The more content changes simultaneously with URLs, the harder it is to isolate what went wrong.

5. Prepare technical files. Ready the new robots.txt (/tools/robots-generator), XML sitemaps, and server rules. Generate redirect and canonicalization rules with the .htaccess Generator at /tools/htaccess-generator.

6. Stage and test. On staging, confirm the redirect map works, structured data (/tools/schema-generator) is intact, and the robots.txt does not block the live site. This staging-file mistake ships to production constantly.

Launch day: execute in order

1. Deploy the new site with all redirects live from the first minute.
2. Swap robots.txt — verify it allows crawling and isn't the staging "Disallow: /" file.
3. Submit new sitemaps in Search Console via /search-console.
4. Verify redirects with the HTTP Status Checker at /tools/http-status — spot-check that top URLs return a single 301 to the correct 200 destination.
5. Run a Broken Link Checker pass at /tools/broken-link-checker to catch internal links still pointing at old URLs.
6. If changing domains, use the Change of Address tool in Search Console and keep both properties verified.

Post-launch: monitor relentlessly

The first two weeks decide everything. Some ranking fluctuation is normal; a sustained collapse is not.

Week 1:

• Watch crawl activity in your logs via /tools/log-analyzer — crawlers should be discovering new URLs and hitting your redirects.
• Check Search Console for a spike in 404s or crawl errors and fix redirect gaps immediately.
• Confirm new URLs are getting indexed and old ones dropping out.

Weeks 2–4:

• Compare traffic and rankings against your pre-launch benchmark.
• Re-run the Full Site Audit at /full-site-audit to catch new technical issues.
• Reclaim backlinks: contact high-value linking sites to update URLs (redirects pass most equity, but direct links are stronger).

Ongoing:

• Keep 301 redirects in place for at least a year — ideally permanently. Removing them too soon re-breaks every old link.
• Monitor the Domain Overview at /tools/domain-overview to confirm authority and visibility recover.

The most common migration killers

• Redirecting everything to the homepage instead of relevant pages.
• Redirect chains and loops.
• Shipping the staging robots.txt that blocks the whole site.
• Forgetting to redirect image and PDF URLs.
• Removing redirects too early.
• Changing content and URLs and design all at once, making diagnosis impossible.

The bottom line

A clean migration is boring — and boring is the goal. Benchmark before you touch anything, map every URL to a single 301, test on staging, launch with redirects live, and monitor obsessively for a month. Do that and you'll carry your rankings across intact instead of rebuilding them from scratch.