SEO Checklist for Website Migration: 22 Steps (2026)

Every SEO who has run more than a couple of migrations has the same story: a client or team assumes the new site just needs to go live, and three weeks later organic traffic is down 40% with no one quite sure why. It is almost never one catastrophic mistake. It is usually five small ones, a missed redirect segment, a robots.txt rule copied from staging, a sitemap still pointing at old URLs, that compound into a real ranking loss.

This is built to be the most complete, practical SEO checklist for website migration you will find, structured around the three points in a migration where things actually break: before you touch anything, the moment the new site goes live, and the weeks after launch when Google is still deciding how much to trust the new URLs. It also covers what most website migration checklists skip entirely: real redirect code you can copy, platform-specific notes for WordPress and Wix, a free downloadable checklist and redirect map template, and what a migration means for how AI systems like ChatGPT, Perplexity, and Google’s AI Overviews see your site, not just classic search rankings.

What Counts as a Website Migration (And Why the Type Changes Your Risk)

Not every migration puts the same amount of ranking equity at stake, and treating a simple redesign with the same paranoia as a domain change wastes time you could spend elsewhere. The type of migration you are running should set the scope of your checklist.

Why Website Migrations Actually Lose Rankings

Google does not penalize migrations. What causes the visible traffic drop is almost always one of a small set of preventable technical errors, understanding them upfront makes the rest of this checklist make sense rather than feeling like an arbitrary list of tasks.

• Missing or incomplete redirects. Every unredirected old URL becomes a 404, and every incoming link and bit of ranking history pointing at it goes nowhere.
• Noindex tags left on from staging. The single most common launch-day failure: a staging environment’s noindex meta tag or robots.txt disallow rule ships to production untouched.
• Redirect chains and loops. Old URL to intermediate URL to final URL wastes crawl budget and can silently drop link equity at each hop.
• Metadata that never migrated. Titles and descriptions reverting to CMS defaults instead of the tuned versions that were ranking.
• A new site architecture that orphans previously well-linked pages. A page that ranked partly because of strong internal linking can lose that support if the new navigation and related-content links do not carry it forward.

Pre-Migration SEO Checklist (Steps 1 to 9)

This is the phase that determines whether the rest of the migration goes smoothly, and it is also the phase teams under deadline pressure are most tempted to shortcut. Do not.

1. Benchmark Everything You Are About to Change

Export and save, outside the CMS you are migrating away from, your current organic traffic by landing page, your ranking keyword list, your indexed page count from Search Console, and your backlink profile. Pull at least 16 months of Search Console performance data (queries, pages, clicks, impressions, CTR, and average position), since Search Console only keeps 16 months and you lose the old property’s history the moment you stop checking it. A free rank tracking tool set up before launch gives you a clean daily baseline to compare against. Without this baseline, judging whether the migration hurt rankings becomes a guess instead of a measurement.

2. Crawl and Inventory the Current Site

Run a full crawl (Screaming Frog, Sitebulb, or a similar tool) of the live site before migration and export every indexable URL, its title, meta description, canonical tag, and internal link count. Merge that list with URLs from your XML sitemaps, Search Console’s Pages report, GA4 landing pages, and your backlink tool, because a crawler only finds pages that are linked internally. This combined list becomes the source for your redirect map in the next step, missing this means guessing at URLs from memory, which is how pages get silently dropped.

3. Build a Complete Redirect Map

Map every URL from your inventory to its closest-matching URL on the new site, 1:1 where possible. Closest matching means actual topical equivalence, not just a convenient catch-all redirect to the homepage, redirecting everything to the homepage is treated by Google as close to not redirecting at all and forfeits the ranking value those pages built up. Pages with no real equivalent should return a 410 Gone (or a 404) instead of a misleading redirect. You can download our free redirect map template (CSV) with columns for old URL, new URL, redirect type, priority, clicks, and referring domains.

4. Set Up a Staging Environment That Mirrors Production

Password-protect it, block it from search engines with both a site-wide noindex and a robots.txt disallow, and use it to validate every item in the launch-day checklist below before the real cutover. Preview links from tunnels and temporary domains leak into Google more often than people expect, our guide on keeping temporary tunnel URLs out of Google’s index shows how to lock them down. Set a calendar reminder to remove both blocks the moment the site actually goes live, this exact step is where most launch-day noindex disasters originate.

5. Export Your Top Backlinks for Outreach

Use Ahrefs, Semrush, or Search Console’s Links report to export every referring domain and the exact URLs they link to. Sort by authority and traffic, then flag the top 20 to 50 links. Redirects pass most of their value, but a direct link to the final URL is always stronger than one that has to hop through a 301, and this list drives your outreach in step 20.

6. Check Content Parity and JavaScript Rendering on Staging

Compare old and new versions of your top pages side by side: body copy, headings, images and alt text, internal links, and structured data should all carry over unless you removed them on purpose. If the new site is a JavaScript framework or headless build, check that the main content appears in the rendered HTML using Search Console’s URL Inspection tool, and read Google’s JavaScript SEO basics before you commit to client-side rendering. Many AI crawlers do not render JavaScript at all, so server-side rendering is the safer default.

7. Plan Canonicals, Hreflang, and Pagination for the New URLs

Every new URL should carry a self-referencing canonical that points at its final HTTPS version, never at the old domain or a staging host. If you run multiple languages or regions, rebuild your hreflang tags so every alternate points to a live new URL and returns the reciprocal link, Google’s localized versions guide covers the exact rules. Paginated category and blog archive URLs also need to be in the redirect map, they are often forgotten because nobody thinks of them as real pages.

8. Re-Validate Metadata and Schema on Staging

Crawl staging and compare titles, meta descriptions, H1s, and canonicals against your step 2 export, so tuned metadata does not quietly reset to CMS defaults. Run your key templates through the Rich Results Test while they are still on staging, the schema section below covers what to check in detail.

9. Pick a Low-Traffic Launch Window and Annotate It

Launch during your quietest traffic period (commonly a weekend night, and never right before a sales peak) so you have time to catch problems before most visitors arrive. Add an annotation for the launch date in GA4 and your rank tracker, it makes every before-and-after comparison in the post-migration phase far easier to read.

The Redirect Mapping Process, With Real Code

Most migration checklists tell you to set up 301 redirects without showing what that actually looks like. Here is the real implementation for the two most common server setups.

Apache (.htaccess), single-URL redirect:

Redirect 301 /old-page-url/ https://www.example.com/new-page-url/

Apache (.htaccess), pattern-based redirect for a moved directory:

RewriteEngine On
RewriteRule ^old-category/(.*)$ /new-category/$1 [R=301,L]

Nginx, single-URL redirect:

location = /old-page-url/ {
    return 301 https://www.example.com/new-page-url/;
}

Apache (.htaccess), page removed with no equivalent (410 Gone):

Redirect gone /discontinued-product/

Check any redirect from the command line:

curl -sIL https://old-site.com/old-page-url/ | grep -iE "^HTTP|^location"

You should see exactly one 301 followed by a 200. Two or more 301 lines means a redirect chain you need to flatten.

• Always use 301, not 302, for a permanent migration. A 302 tells search engines the move is temporary, so they keep the old URL indexed and do not transfer ranking signals the way a 301 does.
• Avoid redirect chains. If page A redirects to B, and B is also being redirected to C, point A directly at C. Each extra hop adds latency and risks losing link equity along the way.
• Preserve query parameters used for tracking (UTM codes especially) unless you have a specific reason to strip them, losing them breaks attribution in analytics for anyone who bookmarked or shared a tagged URL.
• Never mass-redirect everything to the homepage. It is faster to set up, but it discards the topical relevance that made each page rank in the first place.

Google’s own documentation on redirects and Google Search confirms that permanent server-side redirects are the strongest signal that a page has moved, and its site move guide is worth reading in full before any domain change.

Launch Day SEO Checklist (Steps 10 to 16)

Work through these steps in order on launch day. Each one takes minutes, and skipping any of them is behind most sudden post-launch traffic losses.

10. Remove Every Noindex Tag and Staging Robots.txt Block

Do this the moment the new site is live, not later. Check the robots meta tag on a few templates, the X-Robots-Tag HTTP header, and the live robots.txt file. In WordPress, also confirm “Discourage search engines from indexing this site” is unticked under Settings, Reading. This is the single highest-frequency launch-day mistake.

11. Activate the Full Redirect Map and Spot-Check a Sample

Push the redirect map live, then test a representative sample: the homepage, a few category pages, your top 20 traffic pages, and a handful of deep pages. Run the full old URL list through a crawler in list mode afterwards to confirm every row returns a single 301 to a 200 page.

12. Crawl the Live Site and Update Internal Links

Crawl the new site to confirm titles, meta descriptions, canonical tags, and heading structure came across correctly and were not reset to CMS defaults. Then update internal links, navigation, and footer links so they point straight to the final URLs instead of relying on redirects, internal links that hop through a 301 waste crawl budget and dilute the signal.

13. Submit the New XML Sitemap and Inspect Key URLs

Generate a fresh XML sitemap containing only your new, live, 200-status URLs with self-referencing canonicals, then submit it in Google Search Console. Use the URL Inspection tool to request indexing for your most important pages. Our guide on how to get URLs indexed by Google faster covers the remaining options for speeding up recrawling.

14. Use Change of Address in Search Console and Site Move in Bing

If the domain changed, use Search Console’s Change of Address tool on the old property to tell Google explicitly where the site moved, it only works once the 301 redirects are live. Bing Webmaster Tools has its own Site Move tool, and Bing data also feeds several AI assistants, so do both. This is a distinct step from redirects and easy to forget.

15. Verify GA4 and All Tracking Codes

Confirm GA4, Google Tag Manager, conversion pixels, and call tracking are firing on the new site before you consider the launch complete. A broken tracking snippet means you fly blind during the most important monitoring window.

16. Confirm SSL, CDN, DNS, and Core Web Vitals

Check that SSL is valid on every hostname with no mixed-content warnings, that DNS has fully propagated, and that your CDN is not caching old redirects or error pages. Run your key templates through PageSpeed Insights, a slower server or heavier theme can cost rankings even when every redirect is perfect. If the move also involved a new host, our SEO checklist for web hosting covers the server-side checks.

Post-Migration SEO Checklist (Steps 17 to 22)

Migration SEO does not end at launch, most of the actual recovery and stabilization work happens in the weeks after, and the checklist changes as you move further from launch day.

17. Monitor the Page Indexing Report Daily for Two Weeks

Watch Search Console’s Pages (Page indexing) report and the Crawl Stats report every day for the first two weeks. You want to see new URLs moving into “Indexed” and old URLs moving into “Page with redirect”. A sudden jump in “Not found (404)” or “Excluded by noindex” is your early warning.

18. Compare Traffic and Rankings Against Your Benchmark Weekly

Compare clicks, impressions, and rankings for your top pages against the step 1 baseline every week, using the GA4 annotation as the dividing line. Look at page groups (blog, categories, products) rather than sitewide totals, a single broken section is easy to hide inside an overall number.

19. Fix Redirect Chains, Loops, and Gaps With Crawls and Server Logs

Re-crawl the old URL list weekly and fix any chains, loops, or 404s. If you have access to server log files, filter for Googlebot hits on old URLs and on 404s, they show exactly which redirects Google is still requesting and which ones are missing.

20. Ask Your Top Referring Sites to Update Their Links

Take the backlink list from step 5 and contact the sites behind your most valuable links, asking them to point at the new URL. Also update links you control directly: social profiles, Google Business Profile, directory listings, email signatures, and paid ad destinations.

21. Re-Check AI Crawler Access and Entity Consistency

Confirm robots.txt still allows GPTBot, ClaudeBot, PerplexityBot, and Google-Extended, and that your Organization schema, sameAs links, and brand description match what they were before. An entity SEO audit after launch catches mismatches that would otherwise confuse AI systems about who you are.

22. Keep Redirects for at Least a Year and Renew the Old Domain

Google’s site move guidance is to keep redirects for as long as possible, and generally for at least one year. In practice, keep them permanently and keep renewing the old domain, if it expires, every backlink still pointing at it breaks, and someone else can buy it. If traffic has not stabilized by day 60, escalate to a full technical audit.

Use this timeline to judge whether recovery is on track:

How to Diagnose a Post-Migration Traffic Drop

A traffic dip after migration is common enough that you should not panic at the first sign of one, but you also should not assume it will fix itself. Work through this order.

1. Check the timing first. Does the drop line up precisely with the launch date, or with a known, unrelated Google algorithm update that happened to land the same week? These require completely different fixes.
2. Crawl the live site for 404s. A spike in 404 errors in Search Console’s Coverage report almost always means a gap in the redirect map, not a ranking penalty.
3. Check for an accidental noindex or robots.txt block. This single issue explains a large share of cases where rankings vanish overnight after launch.
4. Compare indexed page count before and after. A sharp drop in indexed pages points to a crawling or indexing block; a roughly stable count with lower rankings points more toward a ranking-signal issue, like lost internal linking structure.
5. Give genuine technical fixes 2-4 weeks to show results before concluding they did not work, Google needs to recrawl and reprocess the corrected signals, this is not instantaneous.

Schema Markup and Structured Data During a Migration

Structured data frequently gets rebuilt from scratch during a platform migration, and a broken or missing schema implementation on launch day is easy to miss because it does not throw a visible error to a normal site visitor.

• Re-validate every schema type that was live on the old site, Organization, Article, FAQ, Review, LocalBusiness, on the new site using Google’s Rich Results Test before and after launch.
• Confirm the WebSite and Organization schema’s url and @id values point to the new domain if it changed, stale @id references pointing at the old domain silently break the entity graph connecting your schema blocks together.
• Rebuild BreadcrumbList schema to match the new URL structure exactly, a breadcrumb schema that still reflects the old site hierarchy actively misleads search engines about your new site structure.

Example: WebPage Schema Confirming a Migrated URL (JSON-LD)

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "WebPage",
  "@id": "https://www.example.com/new-page-url/#webpage",
  "url": "https://www.example.com/new-page-url/",
  "name": "Page Title Here",
  "isPartOf": {
    "@id": "https://www.example.com/#website"
  },
  "datePublished": "2024-03-10",
  "dateModified": "2026-09-04"
}
</script>

Validate the updated markup with Google’s Rich Results Test immediately after launch, not days later, since a broken @id reference is invisible to visitors but very visible to search engines. If you are rebuilding schema from scratch on the new platform, our schema markup setup guide walks through the exact JSON-LD to use.

What a Migration Means for AI Search Visibility, Not Just Google Rankings

Classic SEO migration checklists were written before AI crawlers and AI Overviews became a meaningful share of how people find content, and most of them have not caught up. A domain or URL change affects how ChatGPT, Perplexity, and Google’s AI systems recognize your business as the same entity, not just how classic search ranks your pages.

• Check your robots.txt for AI crawler access (GPTBot, ClaudeBot, PerplexityBot, Google-Extended) on the new site immediately, a robots.txt copied over from a locked-down staging environment can accidentally block them.
• Update sameAs links and cross-platform mentions if the domain changed, an AI system trying to confirm your business is the same entity it saw before relies heavily on these consistent cross-references.
• Keep your Organization schema’s name, logo, and description identical across the transition, a migration that quietly rewrites your business description breaks entity continuity right when you need it most.

We cover this in far more depth, including the full crawler-access and entity-consistency checklist, in our guide to AI search visibility strategy, worth reading before a migration, not just after. If you are also rethinking your broader search strategy alongside the migration, our GEO vs AEO vs SEO comparison explains how these disciplines fit together.

Common Website Migration Mistakes That Tank Rankings

• Redirecting everything to the homepage instead of building a real 1:1 redirect map, the fastest way to forfeit the ranking equity every individual page had built up.
• Shipping staging’s noindex tag or robots.txt block to production and not catching it until traffic has already visibly collapsed.
• Changing URL structure and domain in the same launch as a full redesign, stacking three high-risk changes at once makes it nearly impossible to isolate what caused any specific problem afterward.
• Skipping the pre-migration crawl and relying on memory or an old sitemap for the list of URLs that need redirects, this is how entire page categories get silently dropped.
• Declaring victory after 48 hours and moving on, real migration recovery is a 30-90 day process, not a launch-night checklist.
• Forgetting internal linking, a new site architecture that does not carry forward the internal links that supported key pages removes a ranking signal even when the redirect itself works fine.

Platform-Specific Notes: WordPress, Wix, and Other Site Builders

The core checklist above applies no matter what you are migrating to or from, but the actual mechanics of setting up redirects and clearing caches differ enough by platform to call out separately.

SEO Checklist for Website Migration on WordPress

WordPress gives you the most direct control over redirects and metadata of any platform on this list, which makes it forgiving if you use the right tools.

• Use a dedicated WordPress redirect plugin like Redirection or RankMath’s built-in redirection manager to bulk-import your redirect map from a CSV instead of hand-editing .htaccess for hundreds of URLs.
• If you are moving hosts rather than changing content structure, a migration plugin like All-in-One WP Migration or Duplicator handles the file and database transfer, but it does not replace the redirect map, plan for both separately.
• Watch for caching plugins serving stale pages after launch, purge LiteSpeed Cache, WP Rocket, or whatever caching layer you run immediately after the redirects go live.
• Regenerate your XML sitemap through RankMath or Yoast after the migration completes, rather than assuming it updates automatically the instant URLs change.

If your migration is specifically a hosting move rather than a URL or platform change, our dedicated WordPress host migration guide covers the file-transfer and DNS side step by step.

SEO Checklist for Website Migration on Wix

Wix migrations carry a different risk profile because you have less low-level control than WordPress gives you.

• Use Wix’s built-in 301 redirect manager under SEO Tools, it supports bulk CSV import on most plans, confirm your specific plan’s redirect limit before committing to a full migration.
• Re-verify site ownership in Google Search Console after a domain change, Wix’s verification method can require re-doing this step even when the underlying content did not change.
• Check Wix’s automatic sitemap (usually at /sitemap.xml) reflects the new URLs before resubmitting it in Search Console, Wix regenerates this automatically but not always instantly.
• Confirm mobile URLs match desktop URLs, Wix has historically had separate mobile optimization settings that can drift out of sync during a redesign.

SEO Checklist for Website Migration on Shopify, Webflow, and Squarespace

• Shopify forces fixed URL prefixes like /products/, /collections/, and /pages/, so almost every URL changes when you move to it. Bulk import your redirect map under Online Store, Navigation, URL Redirects.
• Webflow handles 301s under Site Settings, Publishing, and supports wildcard patterns for whole folders. Publish to the staging webflow.io domain first and keep it noindexed.
• Squarespace uses a URL Mappings box under Developer Tools, one rule per line in the format /old-url -> /new-url 301. Check plan limits before a large migration.

Free Website Migration SEO Checklist Template (Download)

Use this as your final pass before, during, and after launch. Every item matches a numbered step above, so your team can jump back to the full explanation.

Free downloads: 22-step website migration SEO checklist (CSV) and redirect map template (CSV). Both open in Google Sheets or Excel, add owners and due dates, then export to PDF if your team prefers a printed version.

Before migration (steps 1 to 9)

1. Benchmark traffic, rankings, indexed pages, and 16 months of Search Console data
2. Crawl and inventory every indexable URL on the current site
3. Build a complete 1:1 redirect map, with 410s for removed pages
4. Set up a password-protected, noindexed staging environment
5. Export top backlinks and referring domains for outreach
6. Check content parity and JavaScript rendering on staging
7. Plan canonicals, hreflang, and pagination for the new URLs
8. Re-validate metadata and schema markup on staging
9. Pick a low-traffic launch window and add a GA4 annotation

Launch day (steps 10 to 16)

10. Remove every noindex tag and staging robots.txt block
11. Activate the full redirect map and spot-check a sample
12. Crawl the live site and update internal links to final URLs
13. Submit the new XML sitemap and inspect key URLs
14. Use Change of Address in Search Console and Site Move in Bing
15. Verify GA4 and all tracking codes
16. Confirm SSL, CDN, DNS, and Core Web Vitals

Post-migration, 30 to 90 days (steps 17 to 22)

17. Monitor the Page indexing report daily for two weeks
18. Compare traffic and rankings against the benchmark weekly
19. Fix redirect chains, loops, and gaps using crawls and server logs
20. Ask top referring sites to update their links
21. Re-check AI crawler access and entity consistency
22. Keep redirects for at least 1 year and renew the old domain

Frequently Asked Questions

Final Verdict

A website migration is not inherently risky to your SEO, an unplanned one is. Every traffic-loss story in this article traces back to a small number of preventable causes: an incomplete redirect map, a noindex tag that should have been removed, metadata that never got carried over, or a team that stopped watching after the first 48 hours instead of the first 90 days.

If you are about to migrate, the highest-value place to spend your limited prep time is the redirect map and the staging QA pass, that single combination prevents the majority of the failures covered here. If you already migrated and traffic dropped, work through the diagnosis section in order rather than guessing, the cause is almost always findable, and almost always fixable. Start with the downloadable 22-step checklist, assign an owner to every row, and keep it open until day 90.