Website Migration SEO Checklist for Relaunches

A website relaunch can improve design, speed, CMS flexibility, and conversion paths, but if the SEO migration gets treated like a design task instead of an operational one, it can quietly wipe out years of search equity. This guide walks through website migration SEO from planning to post-launch monitoring, including the part teams often rush. It’s for agency teams, SaaS marketers, e-commerce brands, and freelancers who need a repeatable website migration process for client work or in-house relaunches.
Whether the move involves a new domain, updated URL structures, a rebuilt site on a new CMS, a store replatform, or a shift to headless, the same principle usually applies: every meaningful SEO signal needs to make it through the transition. That means redirects, internal links, canonicals, sitemaps, schema, analytics, and content parity all need to be checked. Google recommends direct permanent redirects, warns against chains, says sitemaps should be updated, and advises keeping redirects in place for at least 1 year (Google Search Central). The risk is real, and teams often underestimate it. In an analysis of 50 domain changes published between June 2024 and September 2026, 64.0% lost more than 10% of organic traffic. Another 42.0% lost more than 50%, which is a sharp drop (PageSpeed Matters).
Most migration losses come from mistakes that can be avoided. Put another way, they’re usually fixable. Below is a practical SEO migration checklist with numbered steps, specific actions, common mistakes, and a verification workflow teams can reuse for future relaunches.
Before you start website migration SEO
If you’re about to start a website migration, check a few basics early so important steps don’t slip through:
- Access to Google Search Console for the old site, and for the new property if the domain is changing
- Access to Google Analytics, along with your tag manager
- A full crawl export of the current site from the preferred crawler
- A spreadsheet for mapping old URLs to new URLs
- Access to the CMS, developer environment, staging site, and redirect rules
- A list of top pages by organic traffic, backlinks, conversions, and revenue
- QA support across SEO, development, analytics, and content teams
Tip: On client migrations, it’s often easier to build one master operating checklist first and then duplicate it for each project. That tends to save time and makes missed steps less likely in repeatable processes. Platforms like Whitelabelseo.ai can often help with recurring SEO workflows, but migration controls still need human sign-off.
Step 1: Define the website migration SEO type and scope
Give the migration a clear, specific name from the start. Projects often get lumped under vague labels like “site refresh” or “new build,” which makes early risk assessment harder. Your website migration SEO plan needs to match what’s actually changing, so the team knows the likely impact before launch.
Common migration types include:
- domain change
- URL structure change
- CMS migration
- design relaunch with the same URLs
- HTTP to HTTPS cleanup
- subdomain to subfolder move
- headless or JavaScript framework migration
- e-commerce replatforming
A one-page scope document needs to cover:
- old domain and new domain
- URL changes
- what stays the same
- launch date window
- teams involved
- pages or templates affected
- countries and languages affected
- analytics setup changes
- success metrics
This matters because Google usually treats site moves with URL changes differently than moves without them. That changes the redirect plan, sitemap setup, and what you need to monitor (Google Search Central). Domain changes are especially delicate because the old and new domains have to map correctly, and there’s very little room for error. The PageSpeed Matters dataset found median traffic retention of 65.3% at 3 to 5 months after a domain migration. It also found that just 32.0% of domain migrations performed better afterward (PageSpeed Matters). That’s a strong reason to define scope early, usually in more detail than teams expect at first.
Common mistake: Treating a platform change as just a development task, even though it usually isn’t. A redesign that changes templates, canonicals, pagination, faceted navigation, or rendering behavior still counts as an SEO migration.
What to verify: Everyone on the project should be able to answer the same core question: what’s changing, what’s staying the same, and how success will be measured. If people give different answers, the scope probably still isn’t clear enough.
Step 2: Benchmark the old site before anyone touches production
Start by getting a clear baseline in place. Skip it, and it’s much harder to see whether the new site held onto its SEO value or where losses began.
Export these items before launch:
- top landing pages from organic search
- clicks, impressions, CTR, average position, and revenue by landing page where available
- all indexable URLs from a crawl
- title tags, meta descriptions, canonicals, H1s, status codes, indexability, and inlinks
- pages with backlinks from your backlink tool
- XML sitemaps and robots.txt
- structured data samples on key templates
- page speed and mobile rendering checks for key pages
When you can, pull at least 12 months of Search Console data so the benchmark reflects seasonality. Usually, that gives you a steadier read on how things change over the year. Webflow recommends benchmarking rankings and traffic, crawling all current URLs, and building the full redirect map before migration work moves forward (Webflow Blog).
Set up one “priority pages” tab in the spreadsheet and keep it tight. It doesn’t need to be elaborate. Include:
- revenue pages
- pages with backlinks
- pages ranking in positions 1 to 10
- top blog posts by clicks
- top product or category pages
- pages used in paid campaigns or email flows
This is usually the point where the team needs to get aligned on expectations, especially with lots of stakeholders involved. Teams sometimes don’t realize how much that can shape the migration. A relaunch can look better at a glance and still underperform if 20 revenue-driving URLs break, especially during launch week or the first few weeks after release.
Tip: Save screenshots of top-page performance and Search Console charts. It’s a small step, but it usually makes post-launch reporting a lot easier, especially when clients react to short-term ranking swings.
If a team needs clearer communication on a more complex project, it also helps to set expectations early with frameworks similar to those in common SEO misconceptions clients have. Teams building repeatable migration processes may also benefit from structured planning workflows such as How to Build an SEO Roadmap for Agency Teams.
Step 3: Crawl the current site and build a one-to-one redirect map for website migration SEO
At the heart of an SEO migration is this work: crawl the live site, export every indexable URL, and map each meaningful old URL to the most relevant new destination. Track it in a spreadsheet with columns for old URL, new URL, page type, status, priority, backlink value, and notes; usually, a simple setup is easier to manage.
Your redirect rules should follow these standards:
- Use
301or308for permanent moves - Redirect each old page to its direct replacement
- Never send large groups of pages to the homepage
- Avoid redirect chains and loops
- Redirect high-value PDFs, media URLs, campaign landing pages, and similar assets when relevant
Google says Googlebot can follow up to 10 redirect hops, but recommends fewer than 5, and ideally no more than 3 (Google Search Central). In practice, if you can keep it to one hop, that’s usually best. Point the old URL directly to the final URL, since that’s often the safest way to handle it.
Check redirect QA in this order:
- pages with organic traffic
- pages with backlinks
- pages with conversions or revenue
- pages linked from navigation
- pages used in ads, email, and sales collateral
Recent migration guidance from Google, Lumar, and Webflow all lands in the same place: getting redirects right matters more than just having a lot of them. In most cases, that means preserving relevance, ranking signals, and the paths users actually take through the site (Lumar).
Common mistake: Relying on pattern-based mapping alone. Pattern-based rules are efficient, but they often fail on blog slugs, products with discontinued variants, location pages, and faceted URLs, especially on larger sites.
What to verify: Start by manually testing the top 100 legacy URLs. Make sure each one reaches the correct final destination in a single step and returns the expected status code. This step often catches the issues that matter most before launch.
Step 4: Protect on-page SEO elements and content parity
A migration isn’t just about moving URLs. It can strip out the same page signals that helped those URLs rank in the first place. Before launch, put the old and new templates next to each other and compare them. It seems obvious, but teams skip it all the time. Then make a record of which elements need to stay where they are.
Go through these page-level items:
- title tags
- meta descriptions
- H1 and major headings
- body copy depth
- internal links in content
- image alt text
- canonical tags
- structured data
- hreflang where relevant
- indexability rules
In a relaunch, keep what’s working first and optimize later. If a page already ranks and converts, don’t do major rewrites in the same sprint unless there’s a strong reason. If you combine a migration with a content overhaul, it gets a lot harder to tell what actually caused a drop.
BrightEdge’s migration guidance says redirects need to be live at launch. It also says internal links, canonicals, schema, hreflang, analytics, and sitemaps need to be validated during relaunch (BrightEdge). For e-commerce and SaaS brands, this kind of template-level QA is often where big losses start. Product pages can lose supporting copy, comparison pages may lose H2s or H3s, pricing pages can drop schema markup, and help-center content often gets too thin after a redesign.
If conversion pages are also being revised during the relaunch, keep the SEO scope separate from CRO changes so cause and effect stay clear. That makes it easier to tell whether rankings fell after template updates or after conversion changes. For post-migration tuning on commercial pages, use a dedicated process like this guide to landing page SEO.
Tip: Run a diff on exports of titles, canonicals, word count, and indexability for top pages. That way, you can catch subtle template regressions fast, before they spread further.
Common mistake: Launching shorter, cleaner-looking pages that cut useful copy, FAQs, specifications, or internal links that had been supporting rankings and helping users reach related pages.
Step 5: Lock down staging so it never leaks into production
Staging issues can turn into some of the costliest website migration SEO failures, even though they’re often fairly easy to prevent. Modern sites often run on headless CMS setups, JavaScript frameworks, preview environments, and multiple deployment branches, so there are a lot of moving parts. In setups like that, SEO settings can fail in more places, including the HTML, scripts, or the deployment configuration itself.
Before launch, check the staging site for:
noindextags- robots.txt blocks
- password protection
- canonicals pointing to staging or preview URLs
- broken rendering after hydration
- missing analytics tags
- environment-specific script conflicts
Migration guidance still warns that production launches can carry over staging restrictions or staging canonicals (FocusReactive, BrightEdge). That matters even more on headless builds, because the HTML source, rendered DOM, and API-fed components don’t always line up, and teams often miss that mismatch more easily than they expect. Teams handling JavaScript-heavy relaunches may also want reference material like Headless SEO Fix: Canonicals & Sitemaps That Rank.
A pre-launch QA checklist that gives every template type a clear pass-or-fail status is usually the safest way to handle it. Don’t rely on memory; verbal confirmation from development usually isn’t enough on its own.
Exact action: Staging should intentionally block indexing. Before launch, remove those blocks from the production branch. After deployment, test the live environment itself, not just pre-production checks, to make sure the production-specific output is correct.
Common mistake: Thinking that if a page looks right in the browser, Google sees the same thing. In practice, rendering issues, canonicals, meta robots, and structured data can still be wrong, often in the rendered HTML instead of the visible layout.
What to verify: Check the rendered HTML, not just the visual output, on homepage, category, product, blog, pricing, and contact templates.
Step 6: Prepare technical launch assets before go-live
Get every asset together before launch so the team isn’t trying to build key pieces at the last minute. More teams end up scrambling on launch day than they’d like to admit, and that usually leads to confusion they could’ve avoided. For an SEO migration, the full launch pack needs to be ready before deployment starts, and everyone should be able to see what’s finalized and what’s actually going live.
Your launch pack should include:
- final redirect rules
- final XML sitemap URLs
- robots.txt file
- canonical logic documentation
- hreflang mapping, if applicable
- analytics and tag manager QA sheet
- Search Console verification for the new property
- Change of Address plan if the domain changes
- rollback plan
Google recommends submitting updated sitemaps and using Change of Address when a site moves to a new domain (Google Search Central). It also says medium-sized site moves may be recognized within weeks, while larger sites often take longer because Google needs more time to recrawl and reprocess the move (Google Search Central). In real terms, launch-day asset prep often plays a part in how fast search engines make sense of the new structure and start processing the move correctly.
For agencies, this is often the point where process maturity shows. Teams managing migrations for multiple clients should standardize file naming, approval gates, sign-off roles, and the handoff steps around them, because even small inconsistencies can slow execution. In practice, migrations usually look more like onboarding projects than routine optimization work. They run on a different operating rhythm, which helps explain why workflows such as client onboarding systems for AI-powered SEO matter for agency delivery. Agencies scaling technical operations may also compare workflows against guides like SEO Reseller Services: What Agencies Should Expect.
Tip: If possible, freeze content publishing 24 to 48 hours before launch. That helps prevent last-minute URL and metadata drift between the export and the live production state, and it’s often worth doing.
Step 7: Execute launch-day checks in the right order
On launch day for a website migration, the order of SEO checks matters. It’s not complicated, but it still matters. When the right checks happen in the wrong order, and that does happen, problems can get missed and often spread across the site.
Follow this order:
Step 7.1: Confirm crawl access and status codes
Look at robots.txt, check the homepage response code, and make sure a sitewide noindex isn’t still live, because it usually shouldn’t be.
Step 7.2: Test redirect rules
Start by checking the key legacy URLs by hand; it’s usually worth doing. After that, run a crawl list on the priority pages so you can catch issues early.
Step 7.3: Validate canonicals and internal links
Make sure canonicals point to live, final URLs. And check that navigation, breadcrumbs, and contextual links go straight to the new URLs rather than through old redirects.
Step 7.4: Submit XML sitemaps
As soon as the launch is live, submit the new sitemap(s) in Search Console. Don’t wait.
Step 7.5: Check analytics and conversions
Go over sessions, key events, ecommerce tracking, and form submissions too, if needed. Add attribution tags so you can usually track performance.
Step 7.6: Inspect core templates on mobile and desktop
Look across the main templates, ideally on mobile and desktop, and check how pages render, whether schema is present, the page titles, and what shows above the fold.
Common mistake: Teams often test just the homepage and a few obvious pages. The real damage usually shows up in templates, parameter handling, pagination, and lower-level pages people tend to miss.
What to verify: Make sure the site can be crawled and indexed where it should be. Also make sure high-value old URLs resolve cleanly to the right new destinations, usually with the appropriate status codes.
Step 8: Monitor the migration after launch and know when to intervene
You can’t really judge an SEO migration on launch day. What matters is how it performs over the next few weeks and months. Crawl the new site as soon as it’s live, then keep an eye on Search Console, analytics, and server logs when you have them, because they can add helpful context. Keep tracking rankings against the baseline you captured earlier as well.
These are usually the signals to look at first:
- spikes in 404 and soft 404 errors
- redirect misses on legacy URLs
- pages blocked in robots.txt
- incorrect canonicals
- drops in index coverage
- declines in branded queries
- traffic loss concentrated in one template or folder
- conversion drops on migrated pages
Google recommends keeping redirects live for at least 1 year after a move (Google Search Central). When traffic drops, guessing usually doesn’t get you far. A structured diagnosis process helps separate technical issues from indexing changes, seasonal shifts, and other causes, and that’s often the tricky part. Google’s traffic debugging guidance can help with that (Google Search Central).
For teams doing more technical QA, an AI-powered SEO operations platform such as an AI-powered white label SEO platform can help automate content and template checks. But that’s usually not enough on its own. The migration owner should still manually review high-risk pages, redirect exceptions, and unusual traffic patterns, especially in the first few weeks after launch, when issues often start to show up. Teams supporting multi-location brands through migrations may also use workflows similar to Local SEO Tools for Agencies Managing Many Locations.
How to verify success and what to do next
You can usually tell a website migration SEO project is on track when a few clear signs start showing up:
- high-value old URLs return the correct permanent redirects
- new URLs begin appearing in Search Console over time
- canonicals, internal links, schema, and analytics work as expected
- top landing pages keep their visibility or recover along the expected curve
- conversions from migrated pages stay stable or improve
- no major crawl, rendering, or template-wide issues appear
Don’t expect the graph to stay perfectly flat right after launch. Some movement is normal during an SEO migration. What matters more here is whether search engines can crawl the new site well, see how the pages fit together, and pass relevance from the old URLs to the new ones. That’s often the clearest sign the migration is working.
The next steps need to be practical and steady:
- monitor top pages daily during the first two weeks
- run weekly migration reviews for at least two to three months
- contact priority backlink sources and update important external links where possible
- keep redirects in place for at least a year
- document every issue and each fix so the next website migration is faster and safer
If website migration SEO is managed like a disciplined rollout rather than a last-minute checklist, the risk of traffic loss usually drops a lot. An SEO migration plan is there to protect what’s already working, support a clean launch, and give the new site a stronger base for future growth. Track the right signals and fix issues quickly, and you’re much more likely to preserve performance and make the transition smoother.