How to redesign without losing the rankings you paid for
Your current site may be ugly, but its URLs have spent years earning trust with Google. A careless relaunch throws that equity away in one afternoon. Here is the checklist we run on every rebuild — and the order matters.
First, understand what you are protecting
Rankings do not belong to your website as a whole. They belong to individual URLs. That page about “aluminium formwork rental in Selangor” that quietly brings you twelve enquiries a month has its own history, its own backlinks and its own standing. Delete or rename it carelessly and its standing dies with it — Google does not forward goodwill to whatever page you built instead unless you tell it to.
So the first task of any redesign is an inventory. Before a single wireframe exists, export every URL on the current site and mark which ones earn organic visits, which have backlinks from other sites, and which convert. Search Console and one crawl with any reputable tool gives you all three columns in an hour. This spreadsheet is now a protected asset of the project.
The redirect map is the real deliverable
Every URL in that inventory needs a written destiny: it survives unchanged, it moves to a new address, or it dies deliberately. Moves get a one-to-one 301 redirect to the page that genuinely replaces them — not a lazy blanket redirect to the homepage, which search engines treat as a soft deletion and users experience as a broken promise.
Deliberate deletions are allowed. Pages that earn nothing and say nothing can go. But that is a decision recorded in the map, not an accident discovered in a crawl report three months later when the traffic graph has already sagged.
Carry the metadata, not just the words
- Title tags and meta descriptions that perform should move to the new page nearly verbatim. Rewrite them later, one at a time, when you can measure the effect.
- Heading structure matters more than most designers admit. If the old page ranked with a plain H1 that names the service and the place, the beautiful new page needs the same information in its H1 — beauty and clarity are not rivals.
- Structured data — organisation details, FAQs, products — should be rebuilt on the new templates before launch, not backfilled afterwards.
Launch day, in order
Ship the redirects in the same deployment as the new site, never a day later. Verify them immediately with a crawl of the old URL list — every address in your inventory should answer with a 301 to a sensible destination, not a 404. Submit the new sitemap the same hour. Then leave the old sitemap accessible for a few weeks; it helps crawlers discover the redirects faster.
For the next month, Search Console is your morning newspaper. Coverage errors, sudden 404 clusters and slow-motion ranking slides all announce themselves there first. Small drops in the first fortnight are normal while Google re-evaluates; drops that persist past week four mean a redirect or a content gap you missed — go back to the inventory and find it.
What usually goes wrong
In our experience three mistakes cause almost all migration damage. Blanket redirects to the homepage, already mentioned. Staging sites that go live with a leftover noindex tag — check this twice, it happens to careful people. And quietly thinning content during the redesign: the old page answered nine questions in fifteen hundred words, the new one answers three in two hundred, and everyone is surprised the rankings noticed.
None of this is exotic work. It is bookkeeping, done stubbornly. Which is also why it is so often skipped — and why insisting on it is one of the cheapest forms of insurance a business can buy. If you are planning a rebuild, our custom web design service treats this checklist as part of the job, not an optional extra.