SEO Migration Checklist: What to Check Before, During, and After a Site Move

Overview

If you need a working SEO migration checklist, start with one principle: migrations fail when teams treat SEO as a post-launch cleanup task. The safest approach is to plan the move in three phases: before launch, during launch, and after launch. That keeps technical SEO, on page SEO, and measurement aligned while the site changes underneath them.

This article covers website migration SEO for the most common scenarios:

• domain changes
• site redesigns with URL changes
• CMS or platform migrations
• HTTPS, subdomain, or folder moves
• consolidations that merge sections or remove content

The core goal is simple: preserve the pages, signals, and pathways that already earn visibility. That means keeping high-value URLs reachable, mapping redirects carefully, retaining important metadata, maintaining internal linking patterns, and checking crawlability the moment the new site goes live.

Before doing anything else, define the migration type. Different moves create different risks:

• Redesign with same URLs: lower redirect risk, higher risk of template, content, and internal linking changes.
• Domain migration: highest risk to indexing, redirects, backlinks, and canonical signals.
• Platform migration: often changes templates, code output, structured data, page speed, and crawl directives.
• Content consolidation: risk of removing pages that still rank, attract links, or support topic coverage.

If your migration includes more than one of these changes at the same time, complexity rises quickly. A redesign plus domain move plus taxonomy cleanup is not one change; it is several layered changes, and each one needs its own checks.

For supporting technical reviews, it helps to pair this checklist with a broader technical SEO checklist, a robots.txt guide, and XML sitemap best practices.

Checklist by scenario

Use the relevant checklist below based on what kind of move you are planning. In mixed migrations, combine them rather than choosing only one.

Universal pre-migration checklist

• Crawl the current site. Export all indexable URLs, status codes, titles, meta descriptions, canonicals, headers, internal links, and image references.
• Pull baseline performance data. Record top landing pages, rankings, clicks, impressions, conversions, backlink targets, and pages with strong referral traffic.
• Identify high-priority URLs. Flag pages that drive organic traffic, revenue, leads, links, branded visibility, or local intent.
• Create a redirect map. Every old URL should have a clear destination, especially for pages that rank or have backlinks. This is the heart of redirect mapping SEO.
• Document current metadata. Save title tags, meta descriptions, canonical tags, structured data patterns, and indexation rules.
• Review internal linking. Note hub pages, navigation elements, breadcrumbs, footer links, and contextual links that support topic clusters. If needed, review your internal linking strategy.
• Check content parity. Make sure valuable copy, FAQs, headings, and entities are not removed unintentionally during redesign.
• Prepare XML sitemaps. Have fresh sitemap files ready for the new environment.
• Review robots directives. Make sure staging blocks do not carry into production.
• Set a rollback plan. Define what would trigger a pause or reversal if serious technical issues appear after launch.

Domain migration checklist

A domain move needs careful signal transfer. Use this domain migration checklist when changing from one domain to another.

• Map every important old URL to its most relevant new URL, not just the homepage.
• Use permanent redirects where appropriate and avoid redirect chains.
• Update canonical tags so they point to the new domain, not the old one.
• Update internal links, image URLs, hreflang references, and structured data references to the new domain.
• Verify the new domain in your measurement and webmaster tools before launch.
• Retain equivalent content and intent on key pages where possible.
• Update branded citations, directory listings, and owned profiles if the public-facing domain changes.
• Keep the old domain active long enough to support redirects and recovery monitoring.

Site redesign SEO checklist

In a redesign, rankings often drop not because the site looks new, but because templates and content patterns change at scale. For site redesign SEO, check the following:

• Compare old and new page templates for heading structure, body copy length, internal link modules, and crawlable navigation.
• Confirm that important content is still rendered in accessible HTML and not hidden behind non-indexable interactions.
• Check title tag and H1 logic on category, product, service, location, and article pages.
• Make sure faceted navigation does not create uncontrolled duplicate URLs.
• Review pagination, filters, breadcrumbs, and search result pages for indexation risks.
• Test Core Web Vitals and general performance on the most important template types. See Core Web Vitals benchmarks by page type for a practical reference point.

CMS or platform migration checklist

Platform changes introduce hidden SEO differences even when URLs stay the same.

• Compare how the old and new systems handle canonicals, redirects, sitemaps, schema, pagination, and image optimization.
• Check whether the new platform changes trailing slash behavior, lowercase handling, parameter URLs, or default taxonomy pages.
• Review server-side rendering or client-side rendering changes that might affect crawlability.
• Test whether noindex, canonical, and meta robots rules can be edited reliably.
• Confirm that templates do not auto-generate thin archive pages or duplicate tags.
• Validate that analytics, tag management, and event tracking still work after launch.

Launch day checklist

• Remove all staging noindex directives and password protections from the live site.
• Confirm that robots.txt on production is correct and does not block important sections.
• Test a sample of redirects manually, especially top landing pages and linked pages.
• Spot-check canonical tags on major templates.
• Verify that XML sitemaps are live, updated, and contain preferred canonical URLs.
• Check that navigation, breadcrumbs, and footer links point to final URLs.
• Run a crawl of the live site to catch broken links, redirect loops, orphan pages, and noindex mistakes.
• Inspect page rendering on desktop and mobile for hidden content or JavaScript issues.
• Submit important sitemap files and request inspection of key pages in webmaster tools.

Post-launch checklist

• Monitor crawl errors, indexation changes, and coverage reports daily in the first period after launch.
• Track ranking movement for core keyword groups, not just single terms. If needed, revisit your keyword clustering approach.
• Compare organic landing pages before and after migration to identify missing or weakened URLs.
• Check server logs or crawl activity data if available to confirm search engines are reaching redirected and priority URLs.
• Review pages losing clicks or impressions and compare old versus new title tags, copy, links, and canonical rules.
• Reclaim broken backlinks by fixing redirects or updating destination targets.
• Audit internal links again after launch because template bugs often appear only on the live site.

What to double-check

The most damaging migration errors are usually not exotic. They are basic issues that were assumed to be fine. These are the areas worth checking twice.

1. Redirect relevance, not just redirect existence

A redirect map is only useful if old pages resolve to the most relevant new destination. Sending many retired URLs to the homepage may keep the page from returning an error, but it often loses topical relevance and user value. Strong backlink building and rankings are tied to specific pages, not just domains. Preserve that specificity where possible.

2. Canonical consistency

Canonicals should support the new URL structure, not contradict it. Double-check that canonical tags do not still reference old paths, staging environments, non-preferred parameters, or HTTP versions. Mixed canonical signals can slow down recovery after a migration.

3. Indexation controls

Look for accidental noindex tags, blocked folders, or robots rules copied from staging. This is one of the simplest ways to suppress large parts of a migrated site. Review the live directives manually and with a crawl. If your team relies on multiple environments, create a standard pre-launch signoff for robots rules.

4. Internal linking patterns

Pages that keep their URLs can still lose performance if internal authority shifts. Compare the old and new site on:

• main navigation presence
• breadcrumb paths
• footer links
• related content modules
• links from high-authority legacy pages

A page that loses its internal support may slip even if everything else looks intact. For deeper tuning, the on-page SEO checklist and internal linking strategy guide are useful follow-ups.

5. Content parity on key pages

Design teams often shorten copy for cleaner layouts. Sometimes that is harmless. Sometimes it removes the exact supporting details that helped the page rank. On pages with established visibility, compare old and new versions directly: title tag, H1, subheads, primary copy blocks, FAQs, media, structured data, and linked resources.

6. Measurement continuity

You cannot manage what you did not benchmark. Before launch, save a list of top pages and their baseline traffic, conversions, and queries. After launch, compare page by page. Use a structured review process similar to an SEO audit checklist so the migration review does not become a loose collection of screenshots and assumptions.

7. Performance by template

Migrations often change image handling, script loading, fonts, and layout shift patterns. Test important template types separately: homepage, category pages, articles, service pages, product pages, and location pages. Slowdowns may not be sitewide; they may be concentrated in the page types that matter most for organic traffic growth.

Common mistakes

If you want to reduce migration risk fast, avoid these recurring errors.

• Launching without a full redirect map. Partial redirects are one of the fastest ways to lose rankings and referral traffic.
• Changing too many variables at once. Domain, design, IA, copy, and templates all changing together make diagnosis difficult.
• Deleting pages because traffic looks small. Some low-traffic pages support long-tail visibility, internal linking, or backlinks.
• Ignoring backlinks during consolidation. A page with few visits may still have valuable external links that need preserving.
• Using blanket homepage redirects. This weakens relevance and creates poor user experience.
• Leaving staging directives on production. A single noindex rule or blocked directory can damage large sections of the site.
• Not testing live rendering. What developers see in a controlled environment may differ from the production crawl experience.
• Forgetting non-HTML assets. PDFs, images, media files, and downloadable resources can attract links and search demand too.
• Breaking internal links during URL changes. Redirects can patch some issues, but direct internal links should be updated.
• Stopping monitoring too early. Some migration issues appear only after search engines recrawl deeper sections.

Another common mistake is treating migration recovery as passive. If a key section declines, compare the old and new versions directly. Look at search intent alignment, internal links, title tags, content depth, and URL targeting. A migration can expose content problems that already existed but were hidden by older authority signals. In those cases, a quick SERP analysis guide review can help determine whether the new page still matches what search results reward.

When to revisit

This checklist is most useful when it becomes part of your operating routine, not just a one-time launch document. Revisit it in these moments:

• Before seasonal planning cycles. If traffic peaks matter to your business, avoid launching major changes without enough recovery time.
• When workflows or tools change. New CMS plugins, deployment processes, or analytics setups can alter migration risk.
• Before any template rollout. Even partial design changes can affect internal linking, metadata, and performance.
• Before content consolidation projects. Pruning and merging pages should use the same redirect and parity checks as full migrations.
• When changing domains, subdomains, protocols, or primary folders. Structural changes deserve a formal migration plan.
• After launch at set intervals. Check daily at first, then weekly, then monthly until traffic and indexing stabilize.

To make this practical, keep a reusable migration pack with these assets:

• a crawl export of the current site
• a redirect mapping sheet
• a list of top organic landing pages
• a list of pages with backlinks and referral traffic
• a template QA checklist
• a launch day signoff list for robots, canonicals, sitemaps, and analytics
• a 30-day post-launch monitoring tracker

If you are planning a move soon, the simplest action is this: start the redirect map and baseline export before any design or development work is finalized. That one habit makes the rest of website migration SEO far easier to manage. Then review crawlability, internal links, XML sitemaps, and performance as soon as the new site is live. A careful migration is rarely about one heroic fix; it is about many small checks completed at the right time.