Website Migration SEO Checklist: How to Move Your Site Without Losing Traffic
A step-by-step website migration SEO checklist: baseline metrics, 301 redirect map, DNS and HTTPS cutover, launch day and 90-day monitoring, so you keep your traffic and rankings.
Louis Mauclair · CEO
Updated October 2026 · 14 min read
Moving to a new domain, CMS, host, or URL structure looks like an IT project. In practice, it is the moment a site can lose, in a few days, rankings it took years to earn. A well-planned SEO migration avoids that outcome, and can even fix old problems along the way: orphan pages, redirect chains, duplicate content.
This guide follows the order of a real project: baseline, 301 redirect map, DNS and HTTPS cutover, launch day, then 90 days of monitoring. Every step is a checkbox, with the traps we see most often on B2B sites. If your migration comes with a B2B website redesign, start this plan when the project is scoped, not the week before launch.
Key takeaways
A website migration changes a site's address, structure, or technology without losing its rankings. Every URL that has traffic, backlinks, or rankings needs a direct 301 redirect to its closest equivalent, and everything must be tested before launch.
Before: 12 months of baseline data, a complete URL inventory, a password-protected staging site, and a tested redirect map.
Launch day: 301 redirects live, noindex removed, robots.txt checked, DNS and HTTPS switched, sitemap submitted.
After: a new crawl the next day, daily monitoring in week one, reviews at 30 and 90 days.
A dip of a few weeks is common. A drop that lasts beyond three months almost always points to a technical error you can fix.
What is an SEO migration?
An SEO migration is any major change that affects how Google accesses or interprets your site, plus the safeguards that protect your visibility. If URLs change, you are running a migration, and your SEO is at risk. The main types, from lowest to highest risk:
Hosting change with no URL changes: low risk, mostly about speed and uptime.
HTTP to HTTPS: low to moderate risk if redirects are correct.
Redesign with new URLs: high risk, in proportion to how many pages change.
Platform change (for example WordPress to HubSpot CMS, or Magento to Shopify): high risk, because URLs, templates, and tags often change together.
Site merge or new language versions: high risk, because canonicals and hreflang have to be rebuilt.
Domain change: highest risk, because all of your authority has to move.
If you are stacking changes, such as a new CMS and a new domain, split them over time. Google recommends it: it is much easier to diagnose a drop when only one variable moved.
Why website migrations lose traffic
Post-migration traffic losses almost always come from the same causes, and nearly all of them are preventable.
Changed URLs with no redirect, returning 404 errors.
Bulk redirects to the homepage, which Google may treat as soft 404s.
Redirect chains that slow down crawling.
A staging robots.txt or noindex tag pushed to production.
Content removed or heavily trimmed during the move.
Canonical, hreflang, or structured data still pointing at the old site or at staging.
Internal links and images still pointing at old URLs.
A new site that is slower than the old one.
A short dip while Google recrawls the site is normal. A lasting drop means something is broken. According to Google, a medium-sized site takes a few weeks to move in its index, a larger one longer, and visibility can fluctuate in the meantime.
The SEO migration checklist in 12 steps
Here is the short version, ready to paste into your project tool. Each step is explained in the sections below.
01Export baseline metrics: 12 months of Google Analytics 4 and Search Console data.
02Inventory every URL: crawl, sitemap, Analytics, backlinks, and images.
03Flag priority pages: the ones that drive traffic, conversions, and backlinks.
04Build the 301 redirect map, page to page, in a spreadsheet.
05Set up a non-indexable staging site, protected by a password.
06Run the SEO QA: titles, meta, H1s, canonicals, hreflang, structured data, internal links.
07Test the redirects on staging or on a sample.
08Prepare the cutover: lowered TTL, HTTPS certificate, backups, calendar.
10Submit the sitemap and, for a domain change, file the change of address.
11Crawl the live site the next day: 404s, redirect chains, leftover noindex tags.
12Monitor for 90 days: indexing, Core Web Vitals, clicks, rankings, new 404s.
Before the migration: baseline, inventory, and staging
This is the most important phase, and the one teams cut first when deadlines slip. On a site with several hundred pages, the inventory and the redirect map often take more work than the build itself.
Baseline metrics
Export at least 12 months of Google Analytics 4 and Search Console data (clicks, impressions, pages, queries) and keep dated screenshots. Search Console only keeps 16 months of history, so export before you migrate. Also record rankings for your priority keywords and the Core Web Vitals of the old site. Without a baseline, you cannot tell whether the migration gained or lost traffic.
The full URL inventory
Cross-check five sources so nothing slips through:
A site crawl (Screaming Frog or similar), with the status code, title, canonical, and depth of each page.
Your XML sitemaps and the indexed pages in the Search Console Pages report.
URLs that receive traffic in Analytics.
URLs that have backlinks (Ahrefs, Semrush, or the Links report in Search Console).
Images: filter Search Console by the Image search type to find the ones that earn clicks.
Priority pages
Flag the pages that drive most of your traffic, conversions, and backlinks. They get individual testing before and after the cutover: redirect, content, tags, form, tracking. If you have already run an SEO audit, its list of strategic pages is the right starting point.
Staging and SEO QA
Build the new site on an environment bots cannot reach. Protect it with a password (HTTP authentication): it is more reliable than a noindex tag or a robots.txt rule, both of which regularly end up in production by mistake. On staging, run the SEO QA:
Titles, meta descriptions, and H1s for every page template.
Then run a full crawl of staging and compare it with the crawl of the old site. A missing page, an empty H1, or trimmed copy shows up immediately.
Timing, content freeze, and backups
Pick a slow period for your business. Avoid Friday evenings unless your developers are on call over the weekend, and the week before a trade show or campaign.
Freeze content on the old site once QA starts, so you do not migrate two versions.
Back up files, database, and server configuration, including Apache or Nginx rules.
Agree on a rollback plan: who decides, on what criteria, and how fast.
The 301 redirect map: the core of every migration
Your redirect map is the table that pairs every old URL with its new URL. It is what carries each page's history over to Google. Without it, every changed page starts from zero.
301 vs 302 vs 308: which redirect to use?
301 redirect: permanent. The default for any migration.
308 redirect: also permanent, and preserves the HTTP request method. Google treats it like a 301.
302 or 307 redirect: temporary. Only for genuinely temporary situations such as maintenance or tests.
JavaScript or meta refresh redirects: avoid them and use server-side redirects whenever possible.
Build the mapping
Start from the full inventory and match each URL to the destination that serves the same intent. A product page goes to the same product's new page, a blog post to the same post, a category to its equivalent category. For pages with no equivalent, choose the closest parent page, or return a 410 if the content is truly gone.
Keep the map in a spreadsheet, one row per URL, with these columns:
old URL and new URL;
expected status code (301 or 410);
12-month traffic and backlinks, so you can sort by priority;
test result, filled in after each check.
On a large site, pattern-based rules (one rule for every /blog/ URL, for example) are easier to maintain than thousands of one-to-one lines. Test them carefully, because a single bad pattern can break a whole section. Depending on your stack, the rule lives in the server, at the CDN level (Cloudflare bulk redirects, the URL Redirects screen in Shopify, the URL redirects tool in HubSpot CMS), or in the framework:
Redirect straight to the final destination, with no chains. Googlebot follows up to 10 hops, but Google recommends redirecting directly. If you cannot, keep chains to 3 hops, and 5 at the very most.
No bulk redirects to the homepage or to a generic category page.
No loops: A to B, then B back to A.
Update internal links to the new URLs so you do not rely on redirects.
Keep redirects in place for a long time. Google recommends at least one year, and the simplest policy is never to remove them.
Test the map before launch
Two methods complement each other. On a sample, this command shows the status code and destination of an old URL:
For the full list, use Screaming Frog in List mode with the "Always Follow Redirects" option (Configuration, Spider, Advanced). The Redirects and Redirect Chains reports show each old URL's final destination, status code, and number of hops. Any row that does not end on a 200 page needs fixing before launch.
A migration is easier with a second pair of eyes. Planning a redesign or a CMS change? Get your free action plan: we flag the SEO risks in your project before development starts.
DNS, hosting, and HTTPS: the technical cutover
Prepare the DNS switch
If you are moving to a new host or domain, DNS is the last and most delicate step. A few days ahead, lower the TTL on the affected records (300 seconds is a common value) in Cloudflare, Route 53, or your registrar, so the change propagates quickly on launch day. Keep the old server running during propagation, double-check MX records so email keeps working, and keep the old domain registered so its redirects keep working.
Move to HTTPS
Install a valid certificate that covers every hostname variant (www and non-www).
301 redirect every HTTP URL to its HTTPS version, page to page.
Remove mixed content: images, scripts, and stylesheets must all load over HTTPS.
Update canonicals, hreflang, sitemaps, and internal links to HTTPS URLs.
Once everything is stable, enable the HSTS header to enforce HTTPS in browsers.
Pick one canonical version (HTTPS, with or without www) and send every other variant to it in a single hop.
Domain change: the Change of Address tool
If your domain name changes, file it in Search Console with the Change of Address tool, once the 301 redirects are live. Validate every variant of the old domain beforehand (www and non-www, http and https, subdomains), as well as those of the new one. The tool is only for a change of domain or subdomain: it is not needed for an HTTPS move, a www change, or moving folders within the same domain.
Launch day: the migration sequence
01Freeze content changes on the old site.
02Deploy the new site and switch on the redirects.
03Remove the staging password and any noindex, then check the production robots.txt: no inherited Disallow: /.
04Switch DNS if needed.
05Test redirects for priority pages, then a broad sample.
06Check that canonicals, hreflang, and the sitemap point at production URLs, not staging.
07Check forms, analytics tracking, and lead sync to your CRM.
08Submit the new XML sitemap in Search Console.
09For a domain change, use the Change of Address tool.
10Log the exact date and time of the cutover in your tracking: without it, the charts are impossible to read.
After the migration: performance testing and monitoring
The work does not stop at launch. The first weeks are when errors are cheapest to catch and fix.
Day one: run a full crawl to catch 404s, redirect chains, and pages accidentally left on noindex, then compare it with the staging crawl.
First week: check the Pages report and crawl stats in Search Console every day.
Performance testing: compare Core Web Vitals with your pre-migration baseline (LCP under 2.5 s, INP under 200 ms, CLS under 0.1) using PageSpeed Insights, then watch field data in Search Console. Our guide to Core Web Vitals covers the fixes.
First month: compare clicks, impressions, and rankings for priority pages against the baseline period.
First three months: keep reviewing new 404s (usually forgotten legacy URLs) and add missing redirects. Do a review at 30 days and another at 90.
Set your alert thresholds before launch. For example: an alert if clicks on priority pages stay below 80% of the baseline period for two weeks in a row. A rule set in advance saves you from debating under pressure.
Update what lives outside your site too: LinkedIn and directory profiles, Google Business Profile, Google Ads and Microsoft Ads campaigns, email signatures, and ask partners who send you important backlinks to update them.
How long does an SEO migration take, and do you need an agency?
On Google's side, a medium-sized site takes a few weeks to move in the index, and a larger one longer. A domain change usually takes longer than an HTTPS move. If rankings have not come back after three months, look for an error: missing redirects, trimmed content, wrong canonicals, or an important page left on noindex.
An in-house team can manage with this checklist if the site has a few dozen pages and keeps its URLs. As soon as there is a domain change, a CMS change, or several hundred pages, the redirect map and the SEO QA justify outside help: a mistake costs more than the service.
Where to start this week
01Export 12 months of Analytics and Search Console data before you change anything.
02Crawl the old site and list the URLs that have traffic or backlinks.
03Create the redirect map spreadsheet with your priority pages.
04Set the cutover date in a slow period, and the content freeze date.
05Check that staging is password-protected.
Website migration SEO FAQ
What is SEO migration?
It is the process of moving or restructuring a website (domain, CMS, hosting, URL structure, or protocol) while preserving its rankings, authority, and indexing signals. It becomes an SEO migration as soon as the change can affect how Google crawls, indexes, and ranks the site.
How do you migrate a website without losing SEO?
Inventory every URL before the project, build a page-to-page 301 redirect map, test the new site on a password-protected staging environment, and monitor errors and indexing closely after launch. Whenever possible, change only one variable at a time.
How long does it take to recover traffic after a migration?
Google says a medium-sized site takes a few weeks to move in its index, and a larger site longer. A domain change usually takes longer than an HTTPS move. A drop that lasts beyond three months almost always points to a technical issue.
How long should you keep 301 redirects?
At least one year, per Google's guidance, and ideally permanently. Old backlinks, bookmarks, and emails keep sending visitors to legacy URLs for years. Keeping redirects costs almost nothing, and removing them can cost you visits.
Do 301 redirects lose PageRank?
No. Google states that permanent redirects (301 and 308) do not lose PageRank. Losses come from redirecting to irrelevant pages, from chains, or from missing redirects.
Do you need the Change of Address tool when moving to HTTPS?
No. The Search Console Change of Address tool is only for a change of domain or subdomain. For an HTTPS move, a www change, or moving folders, 301 redirects are enough, with both versions of the site verified in Search Console.
Can a migration hurt rankings even if you follow best practices?
Yes, temporarily. While Google replaces old URLs with new ones, visibility can fluctuate for a few weeks even with no errors. That is why you compare results with a baseline period and set alert thresholds before launch.
At Klickbee, we run SEO migrations for B2B websites end to end: URL inventory, redirect mapping, SEO QA on staging, DNS and HTTPS cutover, and post-launch monitoring. Our senior experts use in-house AI agents to validate redirect maps across thousands of URLs. Explore our technical SEO services, our B2B website redesign service, our website maintenance services for what comes after, or request a free action plan before you start.
Louis leads growth and digital acquisition for B2B and e-commerce companies in France and the UAE. Before Klickbee, he co-built and sold an e-commerce business that served more than 13,000 customers. He moved to Dubai in 2026 to work with companies across the GCC.
When is hreflang needed, which method to pick, in what order to fix errors and how to check the result? A practical guide for B2B companies with several languages or markets.
The SEO ROI formula, the data you need, worked B2B and ecommerce examples, and a one-page business case your leadership team will actually sign off on.
Louis Mauclair·6 min read
Free action plan
Grow faster. Get your free action plan.
A tailored plan to generate more leads and sales from your existing traffic.