A website migration can improve performance, structure, or maintainability, but an incomplete move can also disrupt rankings, indexed URLs, referral traffic, and valuable backlinks. This SEO migration checklist gives you a repeatable workflow for auditing the existing site, mapping URLs, testing redirects, checking launch settings, and monitoring the transition after release.
Overview
Website migration SEO is the process of preserving a site's search signals while changing its domain, platform, hosting environment, URL structure, design, or content system. The safest approach is to treat the migration as a controlled comparison between a known pre-launch state and a post-launch state.
Before making changes, create a baseline of organic clicks, impressions, indexed pages, rankings, conversions, crawl issues, and important backlinks. Then crawl the current site and record the URLs that receive traffic, attract links, rank for valuable queries, or support important user journeys. These records become the reference point for your 301 redirect migration plan and post-launch checks.
Not every migration needs the same level of work. A hosting change may require fewer URL changes than a domain or CMS migration. A redesign may preserve URLs but alter headings, internal links, structured data, or rendered content. A change to HTTP status, language folders, faceted navigation, or trailing-slash conventions can affect hundreds or thousands of URLs. Define the exact scope before preparing the redirect map.
Keep a shared migration workbook with separate tabs for the following:
- Current URL inventory and crawl data
- New URL mapping and redirect status
- Priority pages and backlinks
- Pre-launch and post-launch metrics
- Technical checks, owners, and completion dates
What to track
1. Build the URL map
Export URLs from several sources rather than relying on one crawl. Combine a crawl of the live site with XML sitemaps, analytics landing pages, Search Console pages, CMS exports, and a backlink report. This helps identify URLs that are not currently linked internally but still receive search traffic or external links.
Use a spreadsheet with columns such as:
| Column | Purpose |
|---|---|
| Old URL | The canonical URL on the current site |
| New URL | The closest equivalent destination after migration |
| Redirect type | Usually a permanent server-side redirect when the move is permanent |
| Page status | Keep, merge, replace, or intentionally retire |
| Organic clicks | Baseline search demand from the selected comparison period |
| Backlinks and referring domains | Evidence of external value and referral potential |
| Primary query or topic | Context for judging the replacement page |
| Redirect tested | Date and result of validation |
Map each retired page to the most relevant surviving destination. Avoid sending unrelated URLs to the homepage simply because it is available. If no useful replacement exists, document the decision and check whether the old URL should return an intentional status instead of redirecting visitors to a confusing page.
2. Prioritize backlinks and important pages
Backlinks should influence migration priorities. Mark pages that earn links from relevant sites, generate referral visits, rank for valuable buyer-intent keywords, or support conversions. A backlink audit can help identify these URLs and separate meaningful links from low-value or obsolete references. For a related recovery workflow, see Backlink Audit & Recovery.
After launch, check that priority old URLs redirect to the intended new pages and that the new pages contain the content users and linking sites expect. Where practical, update important external links directly, especially links controlled by partners, profiles, resource pages, or business listings. A redirect can preserve much of the journey, but a direct link reduces unnecessary dependence on the old URL.
3. Review staging before launch
A staging site should be crawlable by your team but protected from unintended indexing. Check its robots directives, access controls, canonical tags, and generated sitemaps before release. Do not assume the production settings will replace staging settings correctly.
Crawl the staging environment with the same user-agent and rendering options used for the live site. Review status codes, indexability, canonical URLs, pagination, hreflang where applicable, structured data, image references, JavaScript-rendered content, and internal links. A JavaScript-heavy migration deserves extra attention to rendered HTML and discoverable links; the technical SEO audit for JavaScript websites provides a useful complementary checklist.
4. Validate redirects, canonicals, and sitemaps
Before launch, test a representative sample and then plan an automated test of the complete redirect list. Look for redirect chains, loops, incorrect destinations, unexpected soft error pages, and redirects that point to irrelevant content. Confirm that the new pages return the expected successful response and that their canonical tags point to the preferred new URLs.
The production XML sitemap should contain the intended indexable URLs, use the correct protocol and host, and exclude redirected, blocked, duplicate, or non-canonical URLs. Internal links should point directly to new URLs rather than relying on redirects. Review navigation, breadcrumbs, related-content modules, and important contextual links. The guide to internal linking best practices can help with this site-wide review.
Cadence and checkpoints
Pre-launch: two to four weeks before release
- Confirm the migration type, scope, owners, rollback plan, and launch window.
- Capture baseline analytics, Search Console, ranking, crawl, and backlink data.
- Crawl the current site and export indexable URLs, metadata, canonicals, status codes, and internal links.
- Complete the old-to-new URL map and flag unresolved pages.
- Test templates, redirects, canonicals, structured data, robots directives, and XML sitemaps in staging.
- Check analytics, consent, tag management, and conversion tracking on the new templates.
Launch day
- Confirm DNS, hosting, HTTPS, preferred hostname, and server response behavior.
- Publish the redirect rules and test high-priority URLs first.
- Check that staging protections are removed only from the production site.
- Verify canonical tags, robots directives, internal links, and the production sitemap.
- Submit or resubmit the relevant sitemap in Search Console and inspect representative new URLs.
- Test organic landing pages, forms, checkout or lead flows, events, and referral links.
- Record the time of each major change so later traffic movement can be matched to an event.
First week after launch
Crawl the new site and the redirect list daily or whenever significant problems appear. Watch for spikes in server errors, redirect failures, blocked pages, duplicate canonicals, missing metadata, and unexpected changes in indexed URLs. Compare Search Console clicks and impressions with the equivalent pre-launch period, but avoid judging the migration from a single day of data.
Use analytics to check organic sessions, landing pages, conversions, and referral traffic. Search Console is useful for query, page, click, impression, and position comparisons; analytics helps determine whether users still complete important actions. A combined reporting process is described in GA4 and Search Console SEO Reporting.
Weeks two to six
Repeat crawls at a consistent interval and maintain an issue log. Investigate pages that lose impressions, clicks, or conversions rather than changing everything at once. Confirm that important backlinks still resolve correctly and that high-value referring pages do not encounter redirect chains or broken destinations.
How to interpret changes
Traffic movement after a migration has several possible causes. Separate technical evidence from normal demand variation by comparing page-level data, query groups, device types, countries, and landing-page conversions. A site-wide decline accompanied by blocked crawling, incorrect canonicals, or missing redirects points to a technical issue. A decline limited to redesigned templates may indicate lost content, changed internal links, weaker titles, or altered search intent alignment.
Use this diagnostic order:
- Availability: Can users and crawlers reach the new URLs, and do important old URLs redirect correctly?
- Indexability: Are robots directives, canonicals, status codes, and sitemap entries consistent?
- Content equivalence: Does each replacement page retain the key topic, useful information, headings, and relevant internal links?
- Measurement: Are analytics tags, Search Console properties, conversions, and filters working as intended?
- Search presentation: Have titles, descriptions, snippets, or page layouts changed enough to affect click-through behavior?
Do not respond to every ranking fluctuation by rewriting pages or removing redirects. First compare the affected URLs with the migration log and inspect patterns. If impressions remain stable but clicks fall, review search-result presentation and use a controlled title and meta description workflow, such as the process in SEO Title and Meta Description Testing. If impressions and indexing fall together, prioritize crawl and indexability checks.
When to revisit
Revisit this SEO site move checklist before every domain change, CMS replacement, URL restructuring, hosting move, major redesign, or international expansion. Do not reuse an old redirect file without recrawling the current site; the URL inventory, content set, backlink profile, and business priorities may have changed.
After launch, schedule formal reviews at the end of the first week, around the first month, and then monthly or quarterly depending on site size and migration risk. At each review, compare the same core measures: organic clicks, impressions, landing-page sessions, conversions, indexed pages, crawl errors, redirect errors, top queries, priority rankings, referral visits, and high-value backlinks.
Update the checklist when your CMS, hosting configuration, analytics setup, crawler behavior, or Search Console workflow changes. Refresh platform-specific instructions and screenshots periodically, and revise the worked URL-mapping example when the site's templates or migration process changes. Keep the final migration workbook with the project record so the next team can understand what moved, what was intentionally retired, and which issues remain open.
The practical rule is simple: crawl before you change, map before you redirect, test before you launch, and compare after release. A migration is complete only when users, search engines, analytics systems, and important referring sites can all follow the new structure.