Website Migration SEO Checklist (2026)

Organic search drives 53.3% of all website traffic, making it the single largest source of visitors for most businesses (BrightEdge, 2019). Yet nine out of ten site migrations fail to improve SEO performance, according to data shared by migration specialists at Search Engine Journal. The problem isn't that migrations are inherently destructive. It's that most teams skip the planning steps that preserve ranking signals.

Whether you're switching from WordPress to a headless CMS, moving to a new domain, or redesigning with a new URL structure, this 15-step checklist covers what to do before, during, and after launch. Every step maps to a specific SEO risk that, left unaddressed, can cost months of organic traffic. If you're also planning a full website redesign, pair this checklist with that broader planning guide.

Why Are Website Migrations SEO Danger Zones?

Organic search accounts for 53.3% of all website traffic (BrightEdge, 2019), and a botched migration can wipe out months or years of ranking progress overnight. The average website lifespan is just 2 years and 7 months (Orbit Media, 2024), meaning most businesses will face at least one migration during their site's lifetime. Understanding why migrations are risky is the first step toward avoiding the pitfalls.

When a website migrates, Google has to recrawl, re-index, and reassess every page. That process takes time. During the gap, rankings fluctuate. If redirect maps are incomplete, pages return 404 errors and accumulated link equity evaporates. Ahrefs found that 66.5% of links on the web are broken (Ahrefs, 2024) — and poorly planned migrations accelerate that decay.

Types of Website Migrations

Not all migrations carry equal risk. Here are the most common types, ranked from lower to higher SEO impact:

• Hosting change — Moving servers with the same domain and URLs. Lowest risk if DNS propagation is handled cleanly.
• HTTP to HTTPS — Protocol change. Low risk with proper 301 redirects and updated canonical tags.
• CMS switch — Changing platforms (WordPress to Next.js, Squarespace to Webflow). Medium risk because URL patterns and page templates often change.
• URL restructure — Changing URL paths without changing domains. High risk because every internal and external link needs redirecting.
• Redesign with URL changes — Combining visual overhaul with structural changes. High risk due to simultaneous content, template, and URL shifts.
• Domain change — Moving to an entirely new domain name. Highest risk. Google must transfer all trust signals to a new entity.

The golden rule: change as few variables as possible at once. If you're switching CMS platforms, keep URLs identical. If you must change URLs, keep the domain. Bundling a domain change with a CMS switch and URL restructure is the migration scenario most likely to produce lasting traffic loss.

How Do You Prepare for a Website Migration? (Steps 1–5)

A study of 892 website migrations found the average SEO recovery time was 523 days, and 17% of sites never recovered at all (Search Engine Journal, 2023). The difference between fast recovery and permanent damage almost always comes down to pre-migration preparation. These five steps create the safety net that protects your rankings during the transition.

Step 1 — Crawl and Benchmark Your Current Site

Before changing anything, document what you have. Run a full crawl with Screaming Frog, Sitebulb, or Ahrefs Site Audit. Export every URL, its status code, title tag, meta description, canonical tag, internal links, and page depth. This becomes your baseline for the entire migration.

Record your current metrics in Google Search Console: total indexed pages, average position, total clicks, and impressions by page. Screenshot your top 20 landing pages by organic traffic. You'll compare against these numbers daily after launch.

• Export full URL list with status codes, titles, and canonicals
• Document current indexed page count in Google Search Console
• Screenshot top 20 organic landing pages (traffic + rankings)
• Record Core Web Vitals baseline scores
• Save a copy of robots.txt and XML sitemap

Step 2 — Identify Your Highest-Value Pages

Not all pages carry equal weight. Sort your pages by three criteria: organic traffic, number of backlinks, and conversion rate. Pages ranking in positions 1–10 for target keywords need the most careful handling. A page with 50 referring domains that generates 200 visits per month is far more valuable than a thin page with zero links.

Use Ahrefs, SEMrush, or Moz to export your backlink profile by landing page. Cross-reference with Google Analytics to identify which pages drive revenue. These high-value pages get 1-to-1 redirects to equivalent new URLs — never to the homepage. For a deeper analysis methodology, see our guide to measuring website ROI.

Step 3 — Build a Complete Redirect Map

The redirect map is the single most important document in any migration. Google's Gary Illyes confirmed that 301 redirects transfer 90–99% of link equity to the destination URL. Without redirects, that equity is lost completely. Map every old URL to its corresponding new URL in a spreadsheet with columns for old URL, new URL, status code, and notes.

For sites with hundreds or thousands of pages, use pattern-based redirects where URL structures follow consistent rules (e.g., /blog/post-name to /articles/post-name). But always verify the patterns with spot checks. A regex error in a bulk redirect rule can send thousands of pages to the wrong destination.

• Map every old URL to its most relevant new URL (1-to-1 when possible)
• Use 301 redirects for permanent moves (not 302 temporary redirects)
• Avoid redirect chains — old URL should point directly to final URL
• Test redirects on staging before deploying to production
• Include URLs from deleted pages — redirect them to the closest topical match

Step 4 — Lock Down Your Staging Environment

Your staging site must be invisible to search engines. Add a noindex, nofollow meta tag to every page and block all crawlers via robots.txt. If Google indexes your staging site, you'll have duplicate content competing with your live site — and potentially lose rankings before the migration even starts.

Password-protect the staging environment as an extra layer. Use HTTP authentication or IP allowlisting so only your team can access it. Before launching, create a checklist item to remove the noindex tag and update robots.txt. This is one of the most commonly missed steps — teams launch with noindex still active and wonder why Google isn't indexing the new site.

Step 5 — Preserve On-Page SEO Elements

During platform changes, on-page SEO elements often get lost in translation. Export your current title tags, meta descriptions, H1 headings, image alt text, and structured data markup before migration. Verify that the new site reproduces these elements exactly.

Pay special attention to internal link structures. If your current site has contextual internal links within blog posts and service pages, those links need to point to the new URLs after migration. A technical SEO audit before launch catches these gaps before they affect rankings.

• Export and compare title tags, meta descriptions, and H1s (old vs. new)
• Verify structured data markup is present on the new site
• Check that internal links point to new URLs, not old ones
• Preserve image alt text and file names where possible
• Confirm canonical tags point to the correct new URLs

What Should You Do on Migration Day? (Steps 6–10)

A site that doubled its load speed during migration saw its crawl rate jump from 150,000 to 600,000 URLs per day (Google). Migration day is when preparation meets execution. The five steps below must happen in sequence, and most should be completed within a single maintenance window.

Step 6 — Deploy Redirects Before Launch

Redirects should be live before the new site goes public. If there's any gap between launch and redirect deployment, users and search engines will encounter 404 errors. Configure redirects at the server level (Nginx, Apache, or edge functions) rather than relying on client-side JavaScript redirects, which search engines may not follow.

Test a sample of at least 50 redirects manually after deployment. Use a tool like Screaming Frog in list mode — paste in your old URLs and verify each one returns a 301 to the correct destination. Pay extra attention to URLs with query parameters, trailing slashes, and case sensitivity.

Step 7 — Submit Updated Sitemap to Google Search Console

Upload your new XML sitemap to Google Search Console immediately after launch. The sitemap should contain only live, indexable URLs on the new site. Remove any old URLs that now redirect. If you're changing domains, add and verify the new domain in Search Console and use the Change of Address tool.

Submit the old sitemap as well — this helps Google discover redirects faster. For large sites, consider submitting a dedicated redirect sitemap containing just the old URLs. Google will crawl them, follow the 301s, and update its index more quickly.

Step 8 — Verify Robots.txt and Canonical Tags

This is where the staging environment mistake bites hard. Confirm that your production robots.txt allows crawling and that the staging noindex tags are removed. Use Google's URL Inspection tool to verify that Googlebot can access and render your key pages.

Check canonical tags on every page template. Self-referencing canonicals are the standard — each page should point to its own URL. Watch for canonicals still referencing old URLs or staging domains. A single misconfigured canonical can deindex a page from Google's results.

Step 9 — Test Core Web Vitals on the New Site

Core Web Vitals are a confirmed Google ranking factor, and migrations often change performance characteristics dramatically. Run PageSpeed Insights on your top 10 landing pages immediately after launch. Compare LCP, INP, and CLS scores against your pre-migration baseline. Our Core Web Vitals guide covers the specific thresholds and fix strategies.

If your new platform loads faster, that's a migration bonus. Google crawls faster sites more aggressively, which accelerates re-indexing. But if performance has regressed — larger JavaScript bundles, unoptimized images, missing lazy loading — fix those issues on day one. Slow sites during migration slow down the entire recovery process.

Step 10 — Preserve Structured Data and Schema Markup

Structured data powers rich results in Google — review stars, FAQ dropdowns, breadcrumbs, and product information. If your old site had schema markup generating rich snippets, verify that the new site includes equivalent markup. Use Google's Rich Results Test on a sample of pages from each template type.

Losing rich results during migration means losing click-through rate even if your ranking position stays the same. A listing with review stars gets significantly more clicks than a plain blue link. Treat structured data as a first-class citizen during migration, not an afterthought.

How Do You Monitor SEO After a Migration? (Steps 11–15)

A study of 892 website migrations found that the average recovery time is 523 days, and 17% of sites never fully recovered their pre-migration traffic (Search Engine Journal, 2023). Post-migration monitoring is what separates the 83% that recover from the 17% that don't. Catching issues in the first 48 hours prevents small problems from becoming permanent damage.

Step 11 — Monitor Indexing Daily for 30 Days

Open Google Search Console every day for the first 30 days after migration. Check the Index Coverage report for spikes in "Excluded" or "Error" pages. A sudden jump in "Not found (404)" errors means your redirect map has gaps. A spike in "Crawled — currently not indexed" may indicate quality signals that weren't carried over.

Use the URL Inspection tool to manually request indexing for your 20 most important pages. This doesn't guarantee immediate indexing, but it tells Google to prioritize those URLs in the next crawl cycle. For larger sites, submit your sitemap via the Sitemaps report and monitor the coverage stats.

Step 12 — Track Rankings and Traffic Against Baseline

Compare weekly traffic numbers against the baseline you captured in Step 1. Some dip in the first two weeks is normal — Google is recrawling and reassessing. But a traffic drop exceeding 30% after week two signals a problem with redirects, indexing, or content changes that needs immediate investigation.

Track keyword rankings for your top 50 terms daily during the first month. Use a rank tracker like Ahrefs, SEMrush, or SE Ranking. If specific pages dropped out of the top 10, check whether the redirect is working, the canonical is correct, and the new page content matches the old page's search intent.

Step 13 — Audit for Broken Links and Crawl Errors

Run a full site crawl one week after migration. Ahrefs found that 42.5% of websites have broken links (Ahrefs, 2024), and migrations create new ones when internal links reference old URL paths that weren't updated. Fix broken internal links directly — don't rely on redirects for internal navigation.

Check server logs for 404 errors that crawlers are hitting. These logs reveal broken URLs that your crawl tool might miss — especially URLs generated by JavaScript, linked from external sites, or indexed from the old site. Building a strong internal link structure post-migration is just as important as the redirects. See our link building guide for external link recovery strategies.

Step 14 — Update External Backlinks Where Possible

Redirects pass 90–99% of link equity, but a direct link passes 100%. After migration, reach out to sites linking to your most valuable pages and ask them to update the URL. Prioritize links from high-authority domains, guest posts you wrote, partner sites, and directory listings. Even updating 20–30 of your strongest backlinks can measurably accelerate recovery.

Don't forget your own properties. Update links on your Google Business Profile, social media bios, email signatures, paid ad landing pages, and any third-party tools that link back to your site. These are the easiest links to fix because you control them directly.

Step 15 — Keep Old Domain and Redirects Active for 12+ Months

Don't remove redirects after a few months. Google recommends keeping redirects in place for at least one year after migration. Some SEO professionals keep them indefinitely, especially for domain changes. Backlinks from external sites will continue pointing to old URLs for years — redirects ensure that equity still flows to your new pages.

If you changed domains, maintain ownership and hosting of the old domain. Let the old domain's SSL certificate stay active and keep DNS records pointing to a server that handles redirects. The annual cost of maintaining a domain and minimal hosting is far less than the SEO value those redirects protect.

What Should You Do If You Already Lost Traffic After a Migration?

TransferWise (now Wise) experienced a 60% organic traffic drop after their domain migration from transferwise.com to wise.com. But with disciplined redirect management and content optimization, they recovered and eventually grew organic traffic by 500% above pre-migration levels (Search Engine Land, 2024). Recovery is possible. But it requires diagnosing the specific cause of the drop first.

Start with a triage approach. Which pages lost the most traffic? For each one, check: Does the redirect work? Is the new page indexed? Does the canonical tag point to itself? Has the content changed significantly? Often the answer is a combination — the redirect works but the new page removed key content or changed the page's topic.

Recovery Checklist for Post-Migration Traffic Loss

1. Audit redirects — Run your old URL list through Screaming Frog. Every old URL should return a 301 to the correct new page.
2. Check indexing status — In Google Search Console, verify your new pages are indexed. Use URL Inspection to request indexing for dropped pages.
3. Compare content — If you changed page content during migration, compare old and new versions. Significant content removal can cause ranking drops.
4. Verify canonicals — Ensure no pages accidentally canonical to old URLs, staging URLs, or incorrect new URLs.
5. Fix broken internal links — Crawl the new site and repair any internal links still pointing to old URLs (which now redirect instead of linking directly).
6. Restore lost structured data — Check whether rich results disappeared in Search Console. Re-add schema markup if it was lost in migration.
7. Monitor and wait — After fixing issues, give Google 4–6 weeks to recrawl and reassess. Resist the urge to make additional changes during this window.

Website Migration SEO Checklist (Summary Table)

Use this condensed checklist as a quick-reference during your migration. Each step links to the detailed section above. Print this page or save it as a bookmark — you'll reference it multiple times throughout the process.

Frequently Asked Questions

Protect Your Rankings — Don't Wing Your Migration

Website migrations don't have to be traffic disasters. The sites that recover quickly — or even grow after migration — follow a structured, documented process. Crawl before you build. Map every redirect. Monitor daily after launch. These aren't optional steps; they're the difference between a 30-day recovery and a 523-day one.

Bookmark this checklist and work through it step by step for your next migration. If you're planning a redesign alongside your migration, our website redesign checklist covers the design and UX side, and our local SEO guide helps you maintain local visibility through the transition. The work you put in before launch determines whether migration day is routine or catastrophic.