A website migration can improve usability and infrastructure, but an unmanaged domain or URL change can also interrupt rankings, organic traffic, and valuable backlinks. This technical SEO migration checklist gives you a repeatable process for planning URL changes, mapping redirects, checking crawl signals, preserving internal and external links, validating the launch, and monitoring performance after release.
Overview
A migration is any change that can alter how search engines access, understand, or rank a site. Common examples include moving to a new domain, changing URL structures, replatforming an ecommerce store, merging websites, redesigning templates, switching hosting environments, or removing and consolidating content.
The safest approach is to treat migration as a controlled project rather than a single launch-day task. Create a complete inventory of important URLs, define the destination for each one, test the new environment, and establish a baseline before changes go live. The goal is not simply to make every old URL redirect. It is to preserve the strongest possible relationship between old pages, new pages, internal links, search signals, and referring backlinks.
Assign one person responsibility for the SEO checklist, even when developers, content owners, analytics specialists, and marketing teams share implementation work. Keep a dated copy of the URL inventory, redirect rules, test results, analytics annotations, and post-launch findings so the process can be repeated or audited later.
What to track
1. Build the URL and backlink inventory
Export current URLs from your XML sitemap, analytics platform, server logs, crawl tool, and Search Console property. Include HTML pages, important PDFs, image or video landing pages, pagination where relevant, and URLs that receive organic visits or external links. A page with few visits may still matter if it has strong referring domains or supports an important internal linking path.
For each URL, record its current status, indexability, canonical target, organic clicks, impressions, conversions where available, and backlinks. A competitor backlink analysis workflow can help identify which pages and topics attract links that should not be overlooked during consolidation. Prioritize URLs that have strong traffic, useful content, high-value conversions, or authoritative referring links.
2. Complete a redirect-mapping worksheet
Use one row per old URL and include at least these columns:
- Old URL
- New URL
- Migration action: redirect, retain, consolidate, or remove
- Redirect status and destination
- Primary topic or page type
- Organic traffic and backlink notes
- Test result and owner
Map each old page to the closest relevant new page. Avoid sending many unrelated URLs to the homepage simply because it is convenient. If content is genuinely discontinued, document the decision and assess whether a useful replacement exists. A redirect should help users and crawlers reach an equivalent or clearly related destination.
3. Check technical signals before launch
Review canonical tags, robots meta directives, hreflang implementation if used, pagination, structured data, navigation links, and indexability on the new site. Confirm that the staging environment is blocked from indexing in a way that will not accidentally remain in production. At the same time, do not block the live site with a robots.txt rule that prevents search engines from discovering redirects or newly published pages.
Generate a clean XML sitemap containing the preferred, indexable URLs on the new site. Check that links in navigation, breadcrumbs, related-content modules, and important body copy point directly to current URLs rather than relying on redirect chains. A sound internal linking strategy helps search engines and users discover priority pages after the change.
4. Protect external link equity
Redirects are only part of backlink preservation. Update links you control, including social profiles, partner pages, directory listings, digital PR placements, documentation, and campaign landing pages. For important referring domains, contact the publisher when a direct link update is practical. Use a backlink recovery workflow to find links that already point to obsolete, broken, or redirected URLs, then prioritize corrections by relevance and value.
Do not assume that a migration is an opportunity to recreate every old link through aggressive outreach. Preserve legitimate editorial relationships, review important citations, and keep outreach focused on accurate destinations. When the new site has materially better resources, a white hat link building campaign can support discovery over time, but it should not replace careful technical migration work.
Cadence and checkpoints
Before development is complete
- Confirm the scope: domain, protocol, subdomain, templates, URL structure, or content changes.
- Export the current URL, traffic, indexation, and backlink baseline.
- Approve the redirect map and identify pages with no clear destination.
- Record analytics and Search Console properties that must be retained, updated, or added.
- Agree on a rollback plan and the person authorized to use it.
During staging and user acceptance testing
- Crawl representative page types, including category, product, article, landing, and error pages.
- Test canonical tags, internal links, XML sitemaps, robots directives, status codes, and structured data.
- Check that staging controls are active and that production templates will not inherit noindex or disallow rules.
- Test redirect rules for trailing slashes, uppercase variants, parameters, old folders, protocol changes, and common typo patterns where relevant.
- Verify analytics, consent handling, conversion tracking, and Search Console ownership.
On launch day
Take a final backup and record the launch time. Deploy redirects, publish the new XML sitemap, remove temporary staging restrictions, and check a sample of high-value old URLs immediately. Test both browser behavior and server responses. Confirm that the homepage, priority landing pages, login or checkout paths, navigation, canonicals, and robots.txt behave as intended.
After launch
Annotate the migration in analytics and maintain a daily log of organic clicks, impressions, indexed pages, crawl errors, redirect errors, server response issues, and conversions. Crawl old URLs and new URLs separately so you can distinguish missing redirects from problems on the destination site. Review server logs when available; log analysis can reveal whether search bots are repeatedly requesting obsolete paths or wasting crawl activity.
Use the Google Search Console SEO workflow to compare the pre-launch baseline with post-launch queries, pages, coverage signals, and reported errors. A migration should be evaluated across several checkpoints rather than judged from one day of traffic.
How to interpret changes
A short-term fluctuation does not automatically indicate failure. Separate changes caused by the migration from normal seasonality, campaign activity, tracking problems, server outages, or simultaneous content changes. Compare like-for-like date ranges and segment by device, country, directory, template, query type, and landing page.
Traffic loss concentrated on old URLs usually points to incomplete redirects, poor destination matching, or pages that were removed without an equivalent. Impressions falling while pages remain accessible may indicate canonical, indexability, content, or relevance changes. Clicks falling while impressions remain stable can suggest title, snippet, ranking-position, or intent mismatches. A rise in crawl errors, redirect chains, 5xx responses, or blocked resources deserves technical investigation before making broad content changes.
Review backlinks separately. A decline in discovered links may reflect reporting differences or recrawl timing, while a clear increase in links to broken or irrelevant destinations is actionable. Compare the referring-page list before and after launch, reclaim high-value lost backlinks, and ask priority publishers to update important links when appropriate.
Keep a decision log. For every significant change, record the evidence, action taken, expected outcome, and review date. This prevents teams from repeatedly changing redirects or templates without understanding which intervention helped.
When to revisit
Run a focused migration review daily during the first week, then at least weekly until traffic, indexing, errors, and backlinks show a stable pattern. Continue a monthly or quarterly review of redirected URLs, crawl activity, lost backlinks, index coverage, and high-value landing pages. Re-crawl after major template, hosting, CMS, CDN, or URL changes.
Update this checklist whenever your platform introduces new routing behavior, your analytics setup changes, search-engine documentation changes, or your site adopts a new rendering and deployment process. Before the next migration, do the following:
- Refresh the URL and backlink inventory.
- Reconfirm the redirect map with content and development owners.
- Run a staging crawl and test production safeguards.
- Prepare launch-day dashboards, annotations, and error alerts.
- Schedule post-launch checkpoints before deployment begins.
A migration is complete only when users reach the right pages, search engines can crawl and index the intended URLs, internal links are current, and valuable backlinks lead to relevant destinations. Save the final worksheet and results with the project documentation so the next URL change starts with evidence instead of guesswork.
