Ranking loss is preventable, and preventing it is unglamorous
A redesign does not damage rankings because Google dislikes new designs. It damages rankings for a small number of mechanical reasons, each of which is avoidable and none of which is interesting enough to feature in a proposal.
That is why the work gets skipped. If a supplier's proposal does not mention migration explicitly, ask why before signing rather than after launch.
Cause one: URLs change without a complete map
Every URL that changes needs a 301 to its closest equivalent. Not the homepage — search engines treat a mass redirect to the root as a soft 404 and the accumulated signals are lost. This is the single most common cause.
The map must be built from the union of your sitemap, Search Console, analytics and a crawl. Each source misses different pages, and the pages any one source misses are usually the older ones carrying the most earned links.
Cause two: content depth is rewritten away
Pages rank partly because they cover a topic thoroughly. A redesign that rewrites everything for a new tone of voice frequently shortens exactly the pages that were working. Migrate performing content intact; change the wrapper, not the substance.
Cause three: rendering changes
A site rebuilt as a client-rendered application can serve an empty document to a crawler that does not execute JavaScript. The content is there for humans and absent for machines — including AI retrieval agents. Check by viewing source, not the inspector.
Cause four: staging settings ship to production
A noindex directive or a Disallow inherited from staging is the most damaging launch-day error, and it happens on real projects with experienced teams. It is also the fastest to check and the fastest to fix, provided someone checks.
Cause five: redirects are removed later
Redirects are not temporary. Removing them after six months discards the equity the migration existed to preserve. Keep them permanently.
What protects you
- A baseline taken before any work: what ranks, what converts, what earns links. You keep it regardless of who does the build.
- A complete one-to-one URL map, built before development starts rather than retrofitted.
- Performing content migrated intact.
- Indexation and ranking monitored daily for two weeks and weekly for two months. Problems surface between weeks two and eight, not on day one.