Website Migration SEO Checklist: A Step-by-Step Guide

A website migration can improve your website’s design, performance, technology, or content structure. But when important URLs change, even a well-built website can experience broken links, indexing problems, and drops in organic traffic.

The problem is rarely the redesign alone. Issues often arise when old URLs are not mapped correctly, new pages cannot be crawled, canonical tags point to the wrong addresses, or important content disappears during the transition.

A website migration SEO checklist gives your team a clear process for protecting existing search visibility while moving to the new website. It helps you document the current site, prepare the replacement, test the launch, and investigate issues afterward.

This guide covers the main SEO tasks before, during, and after a migration, whether you are changing domains, moving to a new CMS, or restructuring your URLs.

What Counts as a Website Migration?

A website migration is a significant change to a website’s domain, platform, infrastructure, URL structure, or architecture that can affect how search engines access and understand its pages.

Common examples include:

Moving from one domain to another.
Switching from HTTP to HTTPS.
Moving a website to a different content management system.
Reorganizing URL folders or category structures.
Rebuilding a website with different page templates.
Moving hosting while retaining the same URLs.

The type of migration matters because the technical requirements differ. A hosting change that keeps every URL unchanged does not need the same redirect plan as a domain migration. Google provides separate guidance for site moves that change URLs and hosting changes that keep URLs the same.

Phase 1: Prepare Before Launch

1. Crawl the Existing Website

Before making changes, crawl the current website and save the results. A crawler can provide a record of URLs, response codes, page titles, meta descriptions, canonical tags, internal links, and indexability signals.

This crawl becomes your baseline. After launch, you can compare the new website against it to identify unexpected differences.

Do not rely only on the XML sitemap. It may not include every URL that receives organic traffic, has external backlinks, or remains accessible through internal links.

Include important images, downloadable files, and other resources if their addresses will also change.

2. Record Search and Business Performance

Use Google Search Console and your analytics platform to record how the existing website performs.

Capture:

Organic clicks and impressions.
Important landing pages and queries.
Organic conversions, leads, or sales.
Indexed pages and known technical issues.
Pages that attract valuable external backlinks.
High-performing content and important business pages.

Choose a comparison period that reflects your normal traffic patterns. Seasonal businesses should compare similar periods rather than relying on a short window.

This information helps you investigate changes after launch without confusing normal fluctuations with migration problems.

3. Identify URLs That Need Special Attention

Not every page has equal value. Prioritize URLs that attract organic visits, generate leads, support sales, or receive useful external links.

For each existing URL, decide whether it should:

Remain unchanged.
Move to a new URL.
Be merged into a relevant replacement page.
Be retired because no suitable replacement exists.

Do not remove a page solely because it has little recent traffic. It may still satisfy a useful search intent or receive valuable referral visits.

4. Prepare a Redirect Map

If URLs are changing, create a document that maps each old address to its intended destination. A redirect map allows the SEO and development teams to agree on the plan before implementation.

For example:

Old URL	New URL	Planned action
/old-seo-guide/	/seo-guide/	Permanent redirect
/blog/technical-seo/	/resources/technical-seo/	Permanent redirect
/retired-service/	No relevant replacement	Review retirement response

Redirects should take users to a page that genuinely replaces the original content. Sending every discontinued URL to the homepage can create a poor user experience and may not preserve the intended relationship between the pages.

Use our guide to building a reliable URL redirect map for the detailed mapping process.

5. Review the Staging Website

Before launch, inspect the new website in its staging environment.

Check page content, navigation, metadata, canonical tags, mobile layouts, images, forms, and internal links. Confirm that staging-only protections, such as a noindex directive, will not accidentally remain on the production website.

Also review robots.txt and verify that pages intended for search indexing will be accessible after launch.

Test templates as well as individual pages. A single faulty template can affect an entire category of content.

Phase 2: Launch-Day SEO Checks

6. Test Redirects and Status Codes

When URLs change, implement server-side permanent redirects where possible. Google recommends permanent redirects such as HTTP 301 and 308 for site moves.

Test the planned rules and confirm that old URLs reach the intended final destinations. Check for redirect loops, irrelevant destinations, and chains that pass through unnecessary intermediate URLs.

For example, a cleaner redirect is:

/old-page/ → /new-page/

rather than:

/old-page/ → /temporary-page/ → /new-page/

Keep a record of failed tests so the development team can correct and retest them.

7. Check Canonical Tags and Indexability

Review the production site’s canonical tags, robots directives, and response codes.

Important pages should not be unintentionally blocked by robots.txt or marked noindex. Canonical tags should reflect the intended preferred URLs, rather than pointing back to the old domain or a staging address.

If the migration changes domains or subdomains, verify the relevant properties in Google Search Console and review whether Google’s Change of Address process applies.

8. Update Internal Links and the XML Sitemap

Update internal links to point directly to the new URLs. Review navigation, breadcrumbs, contextual links, category pages, and other important site elements.

Generate a new XML sitemap containing the canonical URLs that you want search engines to discover. Submit it through Search Console and monitor the reported status.

A sitemap helps search engines discover URLs, but submission does not guarantee that every page will be indexed. The pages still need to be accessible and suitable for indexing.

9. Test Important Website Functions

A technically accessible website can still fail users if important features break during the migration.

Test the main user journeys on mobile and desktop, including:

Contact and lead-generation forms.
Checkout and payment processes, if applicable.
Account registration and login.
Navigation and calls to action.
Analytics and conversion events.
Images, downloadable files, and essential resources.

Verify that analytics records activity on the production website and that important conversions are still measured correctly.

Phase 3: Audit and Monitor After Launch

10. Crawl the New Website

Crawl the live website after launch and compare it with the original crawl.

Look for missing pages, unexpected status codes, broken internal links, incorrect redirects, missing metadata, and changes to canonical or indexability signals.

Prioritize issues affecting high-value pages first. A broken page that previously generated qualified leads deserves more immediate attention than a minor issue on a rarely visited page.

11. Monitor Search Console and Organic Traffic

Review Search Console regularly for indexing issues, sitemap processing, clicks, impressions, and the performance of important landing pages.

Investigate patterns rather than reacting to a single day’s data. A sitewide decline may require a different investigation from a problem affecting only one category or template.

Google notes that search visibility can fluctuate during a site move while its systems discover and process the new URLs. The timeline varies with site size, server performance, and other technical factors. A temporary change does not automatically mean the migration has failed.

12. Keep Redirects Active

Do not remove redirects immediately after launch. Google advises keeping site-move redirects for as long as possible, generally at least one year. Keeping them longer may also help users who continue to visit old bookmarks or follow external links.

Where practical, update important external links that still point to old addresses. Retain the redirect map as a reference for future audits and maintenance.