techniqueNovember 18, 2026·8 min

SEO Migration: How to Move or Rebuild a Website Without Losing Traffic

Changing domains, CMS or URL structure costs many sites traffic, almost always for the same avoidable reasons. A five-step method, from the URL inventory to the weeks after launch, based on what Google documents.

By Tanguy Agostini
Bloomwise's SEO expert

Key takeaways

  • Most migrations that lose traffic fail on the same points: URLs with no redirect, redirects to the home page, and a staging noindex left live.
  • Start with the inventory: every URL that earns clicks, impressions or external links needs a precise destination.
  • A 301 redirect should lead to the exact equivalent of the old page, in a single hop.
  • Google warns of a few weeks of ranking fluctuations for small and medium sites, and advises keeping redirects for at least a year.
  • Measure before you switch. Without a baseline, you cannot tell afterwards what the migration cost you.

A website migration, from an SEO point of view, is any change that alters your page addresses or how Google reads them: a new domain, a new CMS, a new URL structure, a move to HTTPS, two sites merged into one. The danger is that everything looks fine on launch day. The new site looks better, pages load, the agency is happy. Then traffic falls 30% over three weeks and nobody knows why. This article walks through the method we use at Bloomwise to keep a redesign good news. If your site has already dropped, start with our article on why a site is not showing on Google.

Which changes count as a migration?

Whenever a URL changes or the page code changes significantly, it is a migration, even if the domain stays the same.

Type of change Do URLs change? Risk level
HTTP to HTTPS Yes, the protocol Low if everything redirects
New design, same CMS, same URLs No Low to medium, depending on the content touched
New URL structure (categories, slugs) Yes Medium to high
CMS change Almost always High
New domain All of them High
Merging two sites All of them, on one side Very high

The "design only" redesign is the most misleading. URLs do not move, so nobody plans anything. Except the new theme shortened category page copy, turned H1 headings into images and pulled half the menu out of the HTML. To Google, that is a different site.

Step 1: Inventory the URLs that matter

Before touching anything, list every URL that brings you something, because those are the URLs a migration can break.

Three sources are enough for a small site:

  1. Search Console, Performance report, Pages tab, over the last sixteen months. Export everything with at least one impression. This is your priority list.
  2. Your current sitemap, which lists the pages you declare to Google.
  3. A full crawl of the site, which surfaces orphan pages, PDFs and old URLs still linked from somewhere.

Add pages that receive external links, even without traffic: a link from a serious site to a page that ends in a 404 is a lost vote. Merge everything into a spreadsheet, one URL per row. For a brochure site, the list often fits in under a hundred rows. For a store, expect thousands.

Use the moment to record the baseline: number of indexed pages, clicks and impressions over the last three months, rankings for your top twenty queries. A technical SEO audit run before the switch gives you a point of comparison. Without it, you will never know whether a drop came from the migration or from something else.

Step 2: Build the redirect map

Every old URL in your inventory gets one destination: the page on the new site that serves the same need.

Add a "new URL" column to your spreadsheet and fill it row by row. Three rules:

  • A permanent, server-side redirect. Google recommends 301 or 308 status codes. No JavaScript redirects, and no meta refresh when you can avoid it.
  • To the exact equivalent, never to the home page out of convenience. Redirecting fifty articles to the home page is, to Google, the same as deleting them. It often treats them as disguised 404 errors.
  • In a single hop. If a page was already moved in an earlier redesign, update the old redirect so it points straight to the new address. Chains of three or four redirects slow crawling and dilute the signal.

For a page that genuinely disappears, with no equivalent, return a 410 or 404 instead of redirecting to an unrelated page.

Step 3: Build the new site without letting it get indexed

The new site gets built in staging, on an address Google should neither crawl nor index.

Protect staging with a password or a noindex directive. At Bloomwise, our test environment sends a noindex header on every page: that is deliberate, it must never appear in Google. The trap comes at launch, when that protection gets copied as is to production. The whole site deindexes within days, and the cause is a configuration line nobody looks at.

During the build, also check that content is actually carried over. Compare the title tag, the H1 and the length of the text between old and new site, page by page, at least for the fifty pages with the most clicks. A redesign that cuts your best pages from 1,200 to 300 words will lose rankings, perfect redirects or not.

Step 4: The launch-day checklist

On launch day, everything gets checked on the live production site, not on staging.

  1. Redirects: test a sample from your spreadsheet, at least the fifty most important URLs. Each must return a 301 or 308 and land on the right page in one hop.
  2. robots.txt: it should only block what you want blocked. Remove any rule added for staging.
  3. noindex directives: no page meant to be indexed should carry one, in the code or in the HTTP headers.
  4. Canonical tags: every new page points to itself, at its new address.
  5. hreflang tags, if the site is multilingual: they must use the new URLs in every language.
  6. Internal links: menus, footers and in-text links point to the new addresses, not to old ones that redirect.
  7. Sitemap: a new sitemap with the new URLs, submitted in Search Console.
  8. Search Console: if the domain changes, create the new domain's property, then use the Change of Address tool from the old one. That tool only applies to domain or subdomain changes.

For small and medium sites, Google recommends moving all URLs at once rather than section by section. Splitting the move mostly makes sense for very large sites, to isolate problems.

Step 5: Monitor the weeks that follow

After the switch, Search Console becomes your daily dashboard for at least a month.

Google warns that rankings may fluctuate while it recrawls and reindexes the site, and that a small or medium site usually takes a few weeks to be processed. A temporary dip is therefore normal. What should worry you:

  • 404 errors climbing in the indexing report: these are URLs missing from the redirect map.
  • Pages "Excluded by noindex tag" on the new site.
  • Clicks that do not recover on a specific page while the rest of the site does: compare its content with the old version.

Run a full audit of the new site one to two weeks after the switch and compare it with the one from before. That is where the baseline from step 1 pays off. With Bloomwise, the audit reruns on the new site in a few minutes, rankings are tracked from your Search Console, and the weekly report flags pages that drop without you having to open the reports yourself.

How long should you keep redirects?

Google recommends keeping redirects for as long as possible, generally at least a year.

My advice: keep them forever. A redirect costs nothing to maintain, while third-party sites, archived newsletters and bookmarks will keep pointing to your old addresses for years. The only case where you can drop one is a URL that never received traffic or links, and your step 1 inventory tells you which ones those are.

Should you hire help?

For a brochure site keeping its domain, one careful person with a spreadsheet can do the job. For a store with thousands of products, a domain change or a site merger, a specialist pays for themselves quickly, because a redirect mistake across hundreds of product pages costs months of traffic. If budget is the question, our article on SEO audit cost breaks down what gets billed and why. Either way, the inventory and the baseline are things you can do yourself.

Key takeaways

A website migration almost never fails on an obscure detail. It fails on a rushed inventory, redirects to the home page, a forgotten noindex or an old domain left to expire. Build the inventory, write the redirect map row by row, check everything in production on launch day, and watch Search Console for a month. Measure before, with Bloomwise or another tool, so you can compare after. For the full list of checks to run on the new site, our complete SEO audit guide works as a checklist.

💡
Keep the spreadsheet after the migration. The day a page shows up as a 404 in Search Console, it tells you where that page should have gone.
⚠️
Never shut down the old hosting or let the old domain lapse right after launch. The redirects live on the old domain: if it expires, they disappear with it, along with every external link you earned.

Want to know where your site stands?

bloomwise audits your site in 2 minutes and gives you an SEO score with priorities to fix.

Get started

Frequently asked questions