SEO Migration Checklist: Protect Search Visibility During a Website Move

Written by

in

Migration planning · A practical guide

A website migration can improve design, performance or technology, but it can also quietly remove the search equity built into old URLs, internal links and useful content. This checklist helps teams protect the important paths before, during and after a launch.

The key principle: a migration is not complete when the new site looks right. It is complete when the important pages, search signals and customer journeys have been mapped, moved and checked in the live environment.

What counts as an SEO migration?

An SEO migration includes more than moving to a new domain. It may involve a redesign, CMS change, URL restructure, HTTPS change, international expansion, subdomain move or a major overhaul of content and navigation. If search engines or customers will see meaningfully different URLs, templates or page relationships, SEO needs to be part of the launch plan.

BEFORE LAUNCHInventory pages, set priorities, map redirects and capture baseline data.
AT LAUNCHValidate the live site, redirects, technical controls and important journeys.
AFTER LAUNCHMonitor crawling, indexation, rankings, errors and real visitor actions.

Migration checklist at a glance

AreaWhat to checkWhy it matters
URL inventoryList current URLs, traffic, links, conversions and priority pages.Protects the paths that carry meaningful visibility or customer value.
Redirect mappingMap each important old URL to the closest relevant new destination.Preserves a logical path for users, links and search engines.
Technical controlsCheck robots rules, noindex tags, canonicals, sitemaps and analytics.Prevents launch settings from accidentally blocking the new site.
Internal linksUpdate navigation, contextual links, XML sitemap and key conversion paths.Helps people and crawlers discover the new structure quickly.
Post-launch reviewMonitor response codes, crawl reports, indexation and user actions.Catches issues before they create prolonged visibility loss.

Before launch: map what needs protecting

Start with an inventory, not assumptions. Export important URLs from analytics, search performance data, site crawls and your CMS. Highlight pages that earn organic visits, links, enquiries or play a key role in the customer journey. A low-traffic page can still be important if it supports a service, location or conversion path.

Then create a redirect map. Every valuable old URL should have one clear best-match destination. Do not redirect a large set of unrelated pages to the homepage. That creates a poor experience and makes it harder for search systems to understand what moved.

At launch: test the real experience

Staging environments are useful, but live testing matters. Check the final HTTPS version, canonical URLs, robots directives, key templates and redirects after deployment. Use the Redirect & HTTP Status Checker for individual URL paths, and the Robots & Sitemap Checker to review core crawl signals.

Also test the pages a customer relies on: service pages, contact journeys, forms, location details and important resources. A successful redirect cannot rescue a broken enquiry path.

After launch: monitor, then improve

Some normal variation is expected after a major move. The aim is to distinguish temporary reprocessing from real problems. Monitor crawl errors, redirect chains, indexation, traffic to priority pages and search performance trends. Fix systematic issues first, such as a template-level noindex tag or a redirect rule affecting multiple URLs.

Post-launch checks

  • Confirm important old URLs return a single, relevant permanent redirect.
  • Check priority new URLs return a successful status and are internally linked.
  • Review canonicals, sitemaps and robots rules on the live domain.
  • Submit or refresh the sitemap in the relevant search console property.
  • Track rankings, organic visits and conversions by priority page—not only site-wide totals.
  • Keep the redirect map available for future troubleshooting.

Common migration mistakes to avoid

The biggest risks are often avoidable: removing useful content without mapping it, launching staging directives on production, changing too many variables at once, and treating redirects as a task to finish after launch. Bring SEO into the project at the planning stage so page purpose, user journeys and technical implementation stay connected.

Planning a redesign, replatform or URL move?

Explore our SEO Migration Services and Technical SEO support before launch, so the site you build can keep the visibility you have earned.

Talk to Dive in SEO →

Comments

Leave a Reply

Your email address will not be published. Required fields are marked *