Website Migration SEO Checklist: Redirects, Testing, and Recovery Steps

Overview

The goal of site migration SEO is simple: preserve as much existing search equity as possible while moving the site to a new setup. In practice, that means keeping valuable URLs accessible, mapping old pages to the right new destinations, retaining important content signals, and monitoring post-launch behavior closely enough to catch issues before they become long-term ranking losses.

A migration is not only a domain change. It can include a full website redesign SEO project, a CMS replacement, a move from HTTP to HTTPS, a subdomain shift, a navigation overhaul, or a major cleanup of outdated pages. Each of these changes can affect crawling, indexing, internal linking, canonicals, structured data, and backlink value.

The safest approach is to treat migration as three separate phases:

• Before launch: benchmark the current site, export important data, map redirects, and test the staging environment.
• During launch: implement redirects, remove noindex rules from production, verify analytics and search console properties, and test key templates.
• After launch: monitor indexation, crawl errors, rankings, and traffic by page group; then fix issues in order of impact.

If you need a broader technical review before moving anything, it helps to pair this checklist with a full technical SEO checklist. For larger websites with many low-value URLs, migration planning should also include crawl budget optimization so search engines spend time on the pages that matter.

Use the checklist below as an operations document rather than a one-time read. The exact tools may change, but the workflow remains useful across most migration types.

Checklist by scenario

This section breaks the process into common migration types so you can adapt the checklist to the scale of change.

1. Full domain migration SEO checklist

Use this when the site moves from one domain to another and the content is mostly staying intact.

• Export all indexable URLs from the current site using your crawler, XML sitemaps, CMS export, and analytics landing page data.
• Export top-performing organic landing pages, top linked pages, and pages that drive conversions.
• Back up title tags, meta descriptions, canonicals, headers, structured data, and image alt text where possible.
• Create a one-to-one redirect map from every meaningful old URL to the most relevant new URL.
• Keep redirects at the page level, not just the homepage. A homepage catch-all wastes relevance and link equity.
• Preserve high-value content during the move. If content changes at the same time as the domain, diagnosing ranking drops becomes harder.
• Verify both old and new domains in your search monitoring platforms.
• Update canonical tags to point to the new domain, not the old one.
• Update XML sitemaps so they list only final, indexable new URLs.
• Check robots.txt on the new domain and make sure critical areas are not blocked accidentally.
• Update internal links, navigation, hreflang references, structured data URLs, and image paths.
• Maintain control of the old domain so redirects remain active long enough for search engines and users to follow them.

2. Website redesign SEO checklist

Use this when branding, templates, navigation, and page layouts change, even if the domain stays the same.

• Benchmark current performance by page type: blog posts, product pages, service pages, category pages, location pages, and support content.
• Identify the pages that rank for valuable non-brand queries and mark them as protected assets during redesign.
• Compare old and new navigation to make sure important pages do not lose internal links.
• Review heading structure, body copy, and template changes so core topic relevance stays intact.
• Check that new design elements do not hide key content behind tabs, scripts, or interaction patterns that reduce crawlability.
• Retain or improve page titles and meta descriptions where they already support good performance.
• Test page speed, mobile usability, and Core Web Vitals-related issues before launch.
• Make sure pagination, faceted navigation, filter URLs, and search pages are handled intentionally.
• Review image sizes, lazy loading behavior, and JavaScript dependencies that could affect rendering.
• Rebuild internal linking pathways if layout changes remove contextual links from major pages. For a deeper process, see these internal linking best practices.

3. CMS migration checklist

Use this when moving from one content platform to another, such as from a legacy CMS to a modern framework.

• Audit URL patterns before the move. Many CMS changes create unnecessary URL changes.
• Keep existing slugs where possible to reduce redirect volume.
• Test how the new CMS handles canonicals, redirects, XML sitemaps, schema markup, pagination, and noindex settings.
• Check whether the new platform changes trailing slashes, capitalization, parameter handling, or category paths.
• Confirm that editable SEO fields migrate correctly, including title tags, meta descriptions, and open graph data if relevant.
• Test templates for blog posts, taxonomy pages, author pages, product pages, and archives.
• Check that staging restrictions are removed from production at launch.
• Review server responses for deleted, redirected, canonicalized, and indexable pages.

4. URL structure or information architecture migration

Use this when category names, folder structures, or content hubs are being reorganized.

• Do not change URLs purely for aesthetics if rankings are stable and there is no business reason.
• Map every old URL to the closest matching new destination.
• Avoid redirect chains by pointing all old URLs directly to final URLs.
• Update breadcrumbs, HTML sitemaps, related content modules, and in-content links.
• Recheck canonical tags after the restructure. They often still point to old paths.
• Watch for orphan pages created when navigation changes remove crawl paths.
• Review category and hub pages carefully, as they often drive internal authority across the site.

5. Practical pre-launch master checklist

• Crawl the live site and export all key URLs.
• Build a redirect mapping sheet with old URL, new URL, status, priority, and owner.
• Label top pages by traffic, conversions, backlinks, and strategic importance.
• Prepare benchmark reports for organic traffic, rankings, indexed pages, and crawl errors.
• Audit backlinks pointing to pages likely to change. This is a good time to review a backlink audit checklist so high-value linked pages are protected.
• Test staging with a crawler and manually review key templates.
• Confirm analytics, tag manager, event tracking, and form tracking plans.
• Validate robots rules and confirm that search engines will be allowed to crawl production.
• Review XML sitemap generation rules.
• Prepare a rollback or hotfix process in case a severe launch issue appears.

6. Launch-day SEO redirects checklist

• Deploy redirect rules and test a sample from every page type.
• Spot-check priority URLs manually, including top landing pages and high-link pages.
• Confirm 301 status for permanent moves, not temporary redirects unless there is a clear reason.
• Check canonical tags on live pages.
• Check robots.txt and meta robots on production. For a refresher, use this robots.txt and meta robots guide.
• Submit updated XML sitemaps in your search console tools.
• Validate analytics and conversions on at least one full user journey.
• Run a quick crawl of the live site to identify broken links, redirect loops, and non-indexable templates.

7. Post-launch recovery checklist

• Monitor organic traffic daily at the page-group level, not only sitewide.
• Track rankings for priority keywords and compare by URL.
• Review crawl errors, excluded pages, soft 404s, and redirect issues.
• Check whether important pages dropped out of the index.
• Compare internal link counts on priority pages before and after launch.
• Review server logs if available to confirm search bots are reaching important sections.
• Re-crawl the site after each major fix rather than waiting for a full review cycle.
• Reach out to important referring sites and update links where practical if the most linked URLs changed. This is especially useful when valuable digital PR or directory links point to retired pages.

What to double-check

Even well-managed migrations can fail because a few quiet issues were missed. These are the areas worth checking twice.

Redirect logic

The redirect map is the center of most migration projects. Review not just whether redirects exist, but whether they point to the best destination. A redirect from an old service page to a generic category page is better than a 404, but it may still weaken relevance. Your first choice is usually the closest content equivalent. Also test for chains, loops, mixed protocol redirects, and rules that behave differently with parameters, uppercase URLs, or trailing slashes.

Indexation controls

Many migrations inherit noindex tags, blocked directories, password protection, or staging restrictions. Double-check the live environment for accidental indexation controls. This matters most on templates, because one bad setting can affect thousands of pages at once.

Canonical tags

Canonicals should support your final URL structure. Common migration errors include canonicals still referencing old URLs, self-referential canonicals missing on new pages, or templates canonically pointing many pages to one parent page.

Internal linking and navigation

Large traffic losses sometimes come less from redirects and more from weaker internal linking. Compare menus, breadcrumbs, related links, footer links, and in-body links before and after launch. Important pages should still be easy to reach within a few clicks.

Template parity

Review one live example of every important template. A homepage may look fine while product pages, blog posts, or location pages have missing titles, duplicate H1s, broken schema, or blocked assets.

XML sitemaps and crawl paths

Only include final, indexable URLs in XML sitemaps. Remove redirected, canonicalized, noindex, and error pages. Sitemaps are not a substitute for internal linking, but they help search engines discover your intended URL set faster during a migration.

Backlink destinations

Identify pages with the strongest external links and verify their redirects carefully. If your site has earned mentions through broken link building, digital PR, or directory listings, those legacy URLs can carry meaningful value. For local businesses, review important citations and directory profiles and update destination URLs where needed using guidance like this article on best business directories for SEO.

Measurement setup

Do not wait until rankings move to discover that analytics broke. Check pageview tracking, conversion events, form submissions, ecommerce tracking if relevant, and campaign parameters. Migration without clean measurement leaves the team guessing.

Common mistakes

The biggest migration problems are usually avoidable. These are the patterns that cause the most cleanup work.

• Combining too many changes at once: moving domains, changing CMS, rewriting content, and restructuring URLs in one release makes troubleshooting much harder.
• Redirecting everything to the homepage: this creates a poor user experience and weakens topical continuity.
• Launching without a benchmark: if you do not know which pages drove traffic and conversions before launch, you cannot prioritize recovery intelligently.
• Ignoring internal links: external backlinks matter, but internal authority flow often changes more than teams expect during redesigns.
• Letting staging controls leak into production: blocked crawling or noindex tags can suppress an otherwise successful migration.
• Keeping outdated sitemaps live: old sitemaps can continue surfacing retired URLs and confuse the clean-up process.
• Failing to protect linked pages: pages with strong backlink profiles should be mapped carefully and checked manually. If you need a workflow for reviewing external link value, see how to analyze competitor backlinks and adapt the same discipline to your own site.
• Trusting visual QA alone: a page that looks correct can still return the wrong status code, carry a broken canonical, or be omitted from internal linking modules.
• Ending monitoring too early: some migration issues appear after bots reprocess more of the site, not only in the first few days.

If your team uses multiple crawlers or audit platforms, it can help to compare them before a migration so you know which reports to trust for redirects, canonicals, and template errors. This overview of SEO audit tools compared can help structure that decision.

When to revisit

This checklist works best as a living document. Revisit it before any change that affects URLs, templates, crawl rules, internal linking, or tracking. In practice, that usually means:

• Before a redesign or rebrand
• Before moving to a new CMS or headless setup
• Before consolidating subdomains, folders, or duplicated content sections
• Before changing navigation, taxonomy, or URL naming conventions
• Before seasonal planning cycles when teams queue infrastructure and content changes together
• Whenever your SEO tools, crawling workflow, or analytics setup changes

A useful habit is to keep a migration packet ready in advance. That packet can include a redirect template, benchmark dashboard, launch QA sheet, page-priority list, and contact list for engineering, SEO, analytics, and content owners. The more standardized this packet becomes, the less likely the team is to miss critical details under deadline pressure.

For your next migration, take these action steps:

1. List the exact type of migration: domain, redesign, CMS, URL structure, or a combination.
2. Export your top pages by traffic, conversions, and backlinks.
3. Create and review the redirect map before development is complete.
4. Crawl staging and compare it against the current live site.
5. Prepare launch-day checks for redirects, robots rules, canonicals, sitemaps, and analytics.
6. Schedule post-launch reviews for day one, week one, week two, and month one.

That rhythm turns migration from a one-off scramble into a repeatable technical SEO process. When the next redesign, platform move, or domain change arrives, you will not be starting from scratch.