A redesign can look like progress on launch day and still erase years of organic growth by the following month. That is why a website migration SEO checklist is not a technical formality. It is the operating plan that protects the pages, signals, and conversion paths already producing traffic, leads, and revenue.
A migration includes more than moving a site to a new domain. Replatforming from one CMS to another, restructuring URLs, consolidating content, changing international targeting, moving from HTTP to HTTPS, and rebuilding a site on WordPress can all affect how search engines crawl, understand, and rank your business.
The goal is not to preserve every old URL at any cost. The goal is to retain valuable search equity while launching a faster, clearer, more conversion-focused website that can outperform the one it replaces.
Start With a Migration Strategy, Not a Design Approval
The highest-risk migrations start when the project is treated as a visual rebuild. Design, development, content, SEO, analytics, and conversion paths are connected systems. If any team works from a different version of the plan, the site can launch with missing pages, broken tracking, or redirects that send high-value traffic to irrelevant destinations.
Set the business case first. Is the migration meant to improve Core Web Vitals, support ecommerce growth, consolidate several sites, reposition services, or increase qualified lead volume? The answer determines what must be measured before and after launch.
Establish a migration owner with authority to pause launch if critical checks fail. Define the launch window, approval process, rollback plan, technical contacts, and reporting cadence. For revenue-driving sites, avoid launching before a major promotion, seasonal peak, or period when the internal team cannot respond quickly.
Build a Baseline Before You Touch the New Site
You cannot prove a migration succeeded if you do not know what the old site was delivering. Export enough historical data to separate normal seasonal movement from migration-related losses.
Record organic sessions, conversions, conversion rate, revenue, assisted conversions, branded and non-branded rankings, indexed pages, crawl errors, and backlink data. Segment the numbers by market, device, content type, and key landing page where relevant. A B2B firm may prioritize demo requests and contact forms. An ecommerce brand should also track product revenue, category-page performance, and internal search behavior.
Then crawl the existing site. The crawl becomes the source of truth for current URLs, title tags, meta descriptions, headings, canonicals, status codes, internal links, image assets, and indexability. Do not rely on a sitemap alone. Sitemaps are often outdated, incomplete, or full of URLs that should not be indexed.
Identify the Pages That Cannot Lose Visibility
Not every page deserves the same level of protection. Create a priority list of URLs that generate organic traffic, conversions, revenue, backlinks, or strategic rankings. Include pages with no recent traffic if they have strong external links or support key site architecture.
This distinction matters when consolidating content. Combining five thin service pages into one authoritative page may be the right decision. Redirecting five established pages to the homepage because the new navigation is cleaner is not. Search engines need a clear, relevant replacement for the page they previously ranked.
Map Every Valuable URL to Its Best Destination
Redirect mapping is where migrations either preserve authority or leak it. Build a one-to-one spreadsheet that pairs each legacy URL with the most relevant live URL on the new site. Use a 301 permanent redirect for pages that have moved for good.
A useful redirect map includes the old URL, new URL, redirect type, page purpose, traffic level, backlink value, and implementation status. It should cover both primary pages and less obvious assets such as PDFs, old campaign pages, blog posts, product variants, and URLs with historic links.
Use these rules to make better decisions:
- Redirect an old page to its closest equivalent when the intent and topic remain substantially the same.
- Consolidate overlapping pages into a stronger destination only when that destination genuinely answers the old page’s query.
- Return a 410 or 404 only for content with no relevant replacement and no material search, link, or commercial value.
- Eliminate redirect chains. An old URL should redirect once, directly to the final destination.
- Preserve URL parameters where they support valid campaign tracking or functionality, while preventing duplicate indexed versions.
Avoid blanket redirects to the homepage. They frustrate visitors, waste link equity, and signal that the replacement is not relevant. A migration is an opportunity to improve information architecture, not permission to discard user intent.
Validate the Staging Environment Before Launch
A staging site should be protected from indexing, but it still needs a complete technical review. Developers often block staging with robots directives, password protection, or noindex tags. That is correct before launch. The risk is forgetting to remove those controls when the production site goes live.
Crawl the staging environment and test the essentials. Confirm that important pages return a 200 status code, canonical tags point to their preferred live URLs, headings and metadata are present, and internal links resolve correctly. Check pagination, filters, faceted navigation, site search, forms, product availability, downloadable assets, and mobile layouts.
For CMS migrations, also check template logic. A single faulty canonical rule can point thousands of pages to the wrong location. A default noindex setting can suppress an entire content section. These are not cosmetic defects. They can stop organic growth at the source.
Protect Content Quality and Search Intent
Content should not be copied blindly, but it should not be cut casually either. During a rebuild, teams often remove copy to create a cleaner layout. The result can be a page with less topical relevance, fewer supporting details, and weaker alignment with the queries that used to bring qualified visitors.
Review priority pages against their target intent. Retain useful subject-matter depth, improve outdated claims, make service pages more specific, and strengthen calls to action. If you are merging pages, ensure the new version covers the questions and terms that made each legacy page valuable.
The best migration does more than preserve rankings. It gives search engines and buyers a clearer reason to choose the new site.
Complete This Website Migration SEO Checklist at Launch
Launch day requires a controlled sequence, not a hopeful click of the publish button. Once the production environment is live, work through the checks immediately:
- Confirm the preferred domain, HTTPS version, and trailing-slash convention resolve consistently.
- Remove temporary noindex tags, robots blocks, and staging password restrictions from pages intended for search.
- Activate and test all 301 redirects, especially priority URLs and pages with valuable backlinks.
- Crawl the live site for 4xx errors, 5xx errors, redirect loops, redirect chains, missing canonicals, and broken internal links.
- Verify XML sitemaps contain only canonical, indexable URLs that return a 200 status code.
- Check robots.txt permits crawling of necessary pages, CSS, JavaScript, and media resources.
- Validate analytics, consent settings, conversion events, ecommerce tracking, call tracking, and form notifications.
- Add the verified property to search monitoring tools, submit the updated sitemap, and inspect critical URLs.
- Test page speed and mobile usability on high-traffic templates, not just the homepage.
Do not assume a successful redirect test on five pages proves the entire mapping works. Test samples from every URL group: service pages, blog posts, product pages, categories, resources, regional pages, and retired content.
Monitor the First 90 Days Like a Growth Campaign
Search engines need time to recrawl, process redirects, and reassess the new architecture. Some ranking movement is normal. A sharp drop in indexation, organic sessions, or conversion volume is not something to watch passively for a quarter.
Review crawl errors and indexed-page counts daily during the first two weeks. Monitor priority keyword positions, organic landing-page traffic, conversions, revenue, and server errors weekly. Compare performance to the pre-launch baseline and the same period last year when seasonality matters.
Investigate patterns rather than reacting to a single ranking change. If traffic falls across one folder, check redirects, canonicals, internal links, and indexability for that template. If rankings hold but leads decline, the problem may be page speed, form behavior, messaging, or a changed call to action. SEO protection and conversion performance must be measured together.
Keep redirects in place for at least a year, and longer for URLs with durable backlinks or recurring traffic. Removing them after a few months can reintroduce broken paths that affect visitors and authority long after launch.
Treat Migration as a Foundation for Compounding Growth
A site migration is one of the few moments when a business can improve technical performance, content structure, measurement, and conversion journeys in the same project. That creates upside, but only when launch discipline is matched by ongoing optimization.
The practical next step is to assign owners, complete the baseline, and review the redirect map before the new design is approved. A website should not simply look finished at launch. It should be ready to attract, convert, and scale with every month of work that follows.
