Website migration SEO is the work of moving, redesigning, or replatforming a site without losing the rankings you already earned. Get it right and nobody notices. Get it wrong and your traffic falls off a cliff the week you launch the shiny new site. The single biggest cause of that cliff is almost always the same thing: broken or missing redirects.
A migration is any big change to how your site is addressed or built: a new domain, a new platform, a switch to HTTPS, a URL structure change, or a redesign. If you are planning one, here is how to move without telling Google to start over from zero.
Benchmark everything before you touch anything
You cannot tell if a migration went well if you never recorded where you started. Before launch, write down your current rankings, organic traffic, top pages, and key metrics. Then export a full list of your existing URLs. That URL list becomes your redirect map, and the benchmark becomes your early-warning system if something breaks.
Skipping this step is like renovating a house with no before photos and then arguing about what changed. Measure first. It takes an afternoon and saves a quarter.
Redirects are the whole ballgame
When a URL changes, a 301 redirect tells Google “this page moved here permanently,” and it passes the old page’s ranking signals to the new one. No redirect, and the old page 404s while the new one starts from scratch. Moving a site without redirects is like changing your phone number and telling none of your customers.
The rules that matter:
- Map one-to-one. Each old URL should redirect to the single most relevant new URL. Google’s guidance on site moves with URL changes walks through this.
- Avoid redirect chains. If A points to B and B points to C, fix it so A points straight to C. Google’s 301 redirect documentation explains why chains bleed signal.
- Use server-level redirects, not JavaScript hacks, so they are fast and reliable.
Do not make Google solve a puzzle to find your pages. Hand it a clean map.
The quiet killer: a redesign that strips content
Here is the mistake nobody sees coming. A redesign makes the site prettier and, in the process, quietly deletes content. I have watched a redesign trade 800 words of ranking copy for 200 words and a big hero image, and the rankings followed the content straight down. Nobody connects the redesign to the traffic drop until it is too late. Pretty is not the same as findable.
Before launch, also update your sitemap to the new URLs, and watch for the staging traps covered further down, which sink more migrations than anything except broken redirects. If the new build is fast and cleanly structured, even better; that is the whole point of caring about SEO-friendly website design in the first place.
After launch, watch like a hawk
The day you go live, submit the new sitemap in Google Search Console and start watching. Track rankings, organic traffic, and crawl errors daily for the first couple of weeks. A clean migration usually settles within a few weeks, while a messy one can drag on much longer. Sharp drops almost always mean a missed redirect or a blocked page, and the sooner you catch it, the smaller the damage.
This is exactly the kind of moment a website audit earns its keep, and where the technical SEO basics you set up beforehand pay off. Migrations are stressful, but they are survivable when the redirect map is clean and someone is actually watching the dashboards.
Know which kind of migration you are doing
“Migration” covers several different moves, and the risk changes with each. A domain change (an entirely new URL) and a platform change (new CMS, new URL structure) are the highest-risk, because almost every URL changes and needs a redirect. An HTTPS move or a redesign on the same URLs is lower-risk but still needs care.
Name your migration type before you start, because it tells you how big the redirect map needs to be and where the danger sits. A cosmetic redesign that keeps every URL is a different job from moving to a new domain, even though people call both “the new site.”
Test on staging before you flip the switch
The cheapest place to catch a migration disaster is before launch. Build and check the new site on a staging environment, then walk through it deliberately: are the redirects mapped and working, is the content preserved, are titles and meta descriptions intact, is the sitemap updated?
Then do the one check that catches the most catastrophic mistake: make sure the staging site’s noindex tag and robots.txt block are removed before you go live. Launching a new site that is still telling Google “do not index me” is the fastest way to erase your rankings overnight, and it is depressingly common. Test like you expect something to be broken, because on a migration, something usually is.
Frequently asked questions
Will a website migration hurt my SEO?
It can if done poorly, but a well-planned migration protects your rankings. The biggest risks are broken redirects, lost content, and accidental crawl blocks. With a one-to-one redirect map, preserved content, and careful post-launch monitoring, a clean migration usually settles within a few weeks; a messy one takes longer until the redirects and content are fixed.
Do I need redirects when I change my website?
Almost always, yes. Any time a URL changes, a 301 redirect passes the old page’s ranking signals to the new URL and prevents 404 errors. Without redirects, Google treats the new pages as brand new and you lose the authority the old pages had earned.
How long does it take to recover rankings after a migration?
It depends on how clean the migration was. A well-executed one usually settles within a few weeks, while a poorly executed migration, with missing redirects or stripped content, can take much longer or stall until the problems are fixed. Careful redirects and preserved content are what keep the recovery short.
What is the most common website migration SEO mistake?
Broken or missing redirects, followed closely by redesigns that quietly delete content. Both cut the ranking signals a page had built, and both are easy to miss because the new site still looks fine to a human.
Should I migrate my site all at once or in phases?
It depends on size and risk tolerance. Smaller sites often migrate all at once with a complete redirect map. Large or complex sites sometimes phase the move to limit risk and make problems easier to isolate. Either way, benchmark first and monitor closely afterward.
Does changing to HTTPS count as a migration?
Yes. Moving from HTTP to HTTPS changes your URLs, so it needs redirects and the same care as any migration. It is worth doing, since security is a ranking signal and browsers flag non-secure sites, but treat it as a real migration, not a checkbox.
What types of website migration are there?
Common ones include domain changes, platform or CMS changes, URL structure changes, HTTP-to-HTTPS moves, and redesigns. Domain and platform changes are highest-risk because nearly every URL changes and needs a redirect. Redesigns look safe but often quietly strip ranking content. Identify your type first, since it defines the redirect work ahead.
Should I test a migration on staging first?
Yes, always. A staging environment lets you verify redirects, preserved content, intact metadata, and an updated sitemap before customers and Google see it. Critically, confirm the staging noindex tag and robots.txt block are removed before launch. Launching a site still telling Google not to index it erases rankings overnight and is a common, avoidable mistake.
Move deliberately, not hopefully
A migration is not the time to wing it. Benchmark your starting point, map every redirect one-to-one, keep your content, and watch the dashboards after launch. Boring discipline beats a dramatic recovery every time.
Planning a redesign or a move? Run a free audit first so you have a clean record of what is ranking before anything changes, or read up on technical SEO basics to prep the new build. Measure first. Then move.