A website migration can improve performance, but it can also disrupt organic visibility, conversions and reporting if important URLs, redirects or tracking are missed. This SEO website migration checklist gives you a staged process for protecting search traffic, validating technical changes and monitoring business impact before and after launch.
Overview
Website migration SEO is the process of preserving a site’s search accessibility, URL equity, content relevance and measurement setup while moving to a new design, CMS, domain, URL structure, hosting environment or technology stack. A redesign that appears successful visually may still create SEO problems if old URLs disappear, canonical tags change incorrectly, staging controls remain active or analytics stops recording conversions.
The safest approach is to treat migration as a controlled project with three phases:
- Before launch: establish a reliable baseline, inventory important URLs and test the new site in a protected staging environment.
- At launch: deploy redirects, technical directives, analytics and sitemaps in a planned sequence, then check the live site immediately.
- After launch: compare organic performance and conversions with the baseline, crawl the live site and resolve errors according to business risk.
Keep a dated record of the old site, new site, launch time, releases and fixes. This makes it easier to distinguish migration effects from normal seasonal changes, campaign activity or unrelated technical issues. For wider technical checks, use this technical SEO audit checklist for UK websites alongside the migration plan.
What to track
1. Create a complete URL inventory
Export URLs from the current XML sitemap, analytics platform, Google Search Console, server logs if available, internal links and backlink tools. Do not rely on the sitemap alone: it may omit old but valuable pages, redirected URLs or pages that still receive external links.
For each URL, record its status code, indexability, canonical URL, organic clicks, impressions, key queries, landing-page conversions, backlinks and business purpose. Group pages into categories such as product, service, location, blog, resource and utility pages. This inventory becomes both your baseline and your redirect source list.
2. Map old URLs to the most relevant new destinations
Use a permanent server-side redirect when a page has a clear replacement. Map an old product page to its equivalent product page, not automatically to the homepage. If content has genuinely been retired and no relevant replacement exists, document the decision rather than creating a chain of irrelevant redirects.
A practical redirect-mapping template looks like this:
| Old URL | New URL | Redirect | Reason | Checked |
|---|---|---|---|---|
| /old-service/ | /services/new-service/ | 301 | Direct replacement | Yes/No |
| /old-guide/ | /resources/guide/ | 301 | Moved content | Yes/No |
| /retired-item/ | — | Review | No suitable replacement | Yes/No |
Check for redirect chains, loops, mixed protocols, incorrect capitalisation and rules that redirect every missing URL to one generic page. Update internal links so the new site links directly to final URLs rather than relying on redirects. For principles covering site structure and anchor text, see Internal Linking for SEO.
3. Validate technical signals on the new site
Before launch, crawl the staging site or a representative sample and check:
- HTTP status codes and redirect destinations.
- Indexability, including noindex directives and X-Robots-Tag headers.
- Canonical tags, especially on filtered, paginated and parameter-based URLs.
- Title tags, meta descriptions, headings, structured data and key body content.
- Internal links, image paths, downloadable files and navigation.
- XML sitemap content, URL format and last-modified data where used.
- Robots.txt rules and whether they accidentally block important resources or pages.
- Mobile rendering, templates, page speed and Core Web Vitals opportunities.
Keep staging inaccessible to search engines through authentication or an appropriate temporary control. Confirm that the control is removed or changed correctly at launch. A common failure is carrying a staging noindex directive or robots.txt block onto the production domain.
4. Protect measurement and revenue reporting
SEO performance is not only rankings and clicks. Confirm that analytics tags, consent settings, Search Console verification, form submissions, telephone clicks, ecommerce events and lead-source data work on the new templates. Test important journeys on desktop and mobile, including landing page, contact or checkout, confirmation and recorded conversion.
Save a pre-launch report containing organic sessions or users, Search Console clicks and impressions, landing-page performance, conversions, revenue where relevant, indexed-page counts, crawl errors and rankings for a stable set of priority queries. The SEO reporting guide to GA4, Search Console and ROI metrics can help structure this baseline.
5. Prioritise risk instead of treating every URL equally
| Priority | Typical issue | Action |
|---|---|---|
| Critical | Production site blocked, major URLs return errors, analytics or conversion tracking fails | Investigate immediately and pause non-essential changes |
| High | Top landing pages lack redirects, canonicals are wrong or key content is missing | Fix the affected templates or URL rules first |
| Medium | Broken internal links, sitemap inconsistencies or isolated metadata losses | Assign and resolve during the first monitoring cycle |
| Low | Minor metadata improvements or low-value legacy URLs | Schedule after stability is confirmed |
Cadence and checkpoints
Use a clear launch checklist rather than waiting for a ranking report to reveal problems.
Pre-launch
- Freeze or record the final old-site URL inventory.
- Complete redirect mapping for important pages and backlinks.
- Compare staging templates with the current site for content and metadata.
- Test canonicals, robots.txt, XML sitemaps and structured data.
- Verify analytics, consent, forms, calls, ecommerce and Search Console access.
- Prepare rollback instructions and named owners for technical, content and measurement issues.
Launch day
Test the homepage, priority services, location pages, product pages, blog content, contact journey and several old URLs immediately. Crawl the live domain after DNS and deployment changes have settled. Confirm that HTTPS works consistently, the preferred hostname resolves correctly, redirects return the intended status and the live XML sitemap contains only suitable canonical URLs.
First 30 days
| Period | Checks |
|---|---|
| Hours 0–24 | Live crawl, redirects, indexability, analytics events, forms, robots.txt and sitemap |
| Days 2–3 | Coverage and crawl errors, server responses, organic landing pages and conversion recording |
| Week 1 | Compare clicks, impressions, indexed URLs, priority queries and revenue or leads with the baseline |
| Weeks 2–4 | Repeat the crawl, review trends, inspect affected pages and resolve remaining high-priority defects |
How to interpret changes
Do not diagnose a migration from one ranking screenshot. Compare like-for-like periods where possible and segment the data by page type, device, country, brand versus non-brand queries and conversion action. A fall in clicks with stable impressions may point to changes in click-through rate or result presentation. A fall in both clicks and impressions may indicate reduced visibility, missing content, incorrect canonicals or indexing problems.
Check technical evidence before changing content. If many URLs show errors after launch, inspect redirect rules and templates. If only one group of pages is affected, compare its canonical tags, internal links and content with unaffected groups. If traffic appears stable but leads or sales fall, test forms, consent handling, phone tracking, checkout events and attribution before assuming an SEO decline.
Watch for misleading signals. A temporary fluctuation does not prove permanent damage, while a healthy homepage does not confirm that deep pages are accessible. Review server logs or crawl data where available, and inspect important URLs individually in the relevant search-engine tools. Record each hypothesis, test and outcome in the migration log.
When to revisit
Revisit this checklist before every redesign, CMS or hosting move, domain change, HTTPS change, international expansion and major URL restructuring. Run a focused post-migration review at 30 days, then add the checks to a monthly or quarterly technical SEO routine. This is particularly useful for sites that publish frequently, add local landing pages or change templates regularly.
Refresh the checklist when the CMS, analytics implementation, consent configuration, crawler, sitemap process or search-engine guidance changes. Update screenshots and platform-specific instructions when interfaces change, but keep the underlying controls consistent: inventory, map, test, measure and monitor.
For your next migration, start by exporting the old URL and analytics data before development begins. Assign an owner to every critical check, set a launch-day crawl window, save the baseline report and schedule the 2–3 day, one-week and 30-day reviews in advance. That small amount of preparation turns migration monitoring into a repeatable SEO and ROI process rather than a post-launch investigation.