There are two kinds of sites in this world: those that have migrated, and those that will. Because at some point, a business redeploys — a redesign, a rebrand, a move to a new platform — and in doing so, it puts its entire organic visibility on the table.
Here's the thing that should give you confidence and also a little fear: the technical side of migration is the easy part. The losses come from the planning, and almost all of them are avoidable.
Why sites actually bleed rankings
It's rarely the redirection software failing. It's the human steps around it:
- A URL changes with no redirect at all — the old page just ghosts.
- A redirect points to the homepage instead of the specific new page, dumping equity and confusing intent.
- The sitemap lists pages that 404.
- Metadata and content got dropped in the redesign's rush.
- The whole thing shipped to production without testing, and nobody noticed until traffic spoke.
None of these are glamorous technical failures. They're oversights. And they're 90% of migration damage.
The migration checklist that protects you
This is the order we insist on, and it's mostly paperwork you can't skip:
Inventory everything first. Crawl the live site, export every URL, and note which carry actual value — rankings, links, traffic. That's your protected list.
Build the redirect map before you touch anything. Every URL on the inventory gets a decision: old-to-new 1:1, old-to-best-match-on-new, or gone. Gone pages get a 404 or a sensible redirect, never a silent hole.
One redirect per change. When a page moves, the only redirect you need is old URL to new page. Avoid chains — old to intermediary to final — and keep redirects one hop.
Test on staging, hard. Redirect each old URL on staging and confirm it lands where intended with the right status code. Crawl staging the way you'll crawl production.
Preserve what ranks. Keep title tags, metadata, and content in place wherever the intent didn't change. Redesigns love to rewrite perfectly good copy about which content you rank and lose it.
Launch, then monitor. After go-live, watch Search Console and logs for 404s, unindexed pages, and crawl-rate drops. Expect a temporary dip; that's normal recrawling. Watch for the avoidable losses — the 404s and missing redirects — and fix them the moment they appear.
The cost of skipping
A clean migration costs a few days of tedious mapping. A broken one costs months of traffic and the reputation that goes with it. Every time I see a site in freefall after a relaunch, the cause is the same: someone was in a hurry and skipped the mapping. The ranking loss wasn't fated. It was checked into production.
Treat it as change management
A migration isn't a technical deploy. It's a change-management project where the most valuable asset — your established visibility — is the thing most at risk. Give the mapping the respect it deserves, and the migration becomes a short dip instead of a long recovery.
We run migration prep for clients so the scariest project in SEO becomes the most routine. If you're planning a relaunch and don't want to lose what you've built, book a free website teardown first and we'll scope the redirect map before you schedule the deploy.