Here’s the redesign horror story we’re hired to fix several times a year: business launches a beautiful new website, and within a month, Google traffic falls off a cliff. Enquiries dry up. Nobody knows why — the new site is BETTER. The cause is almost always the same invisible mistake, and it’s completely preventable. This is the process that prevents it.
Why Redesigns Kill Rankings
Google doesn’t rank your website; it ranks your URLs — individual pages that earned trust over years. When a redesign changes URLs (and most do: new structure, new page names) without telling Google where everything went, Google finds hundreds of dead ends where trusted pages used to be. It doesn’t transfer the trust. It deletes it. We’ve audited sites that lost 70% of their traffic to exactly this.
The Protection Process, Step by Step
Step 1 — Inventory before anything else. Crawl the current site and export every URL, plus Search Console data showing which pages earn traffic and rankings. You cannot protect what you haven’t listed. This snapshot is also your evidence baseline for afterwards.
Step 2 — Map every old URL to its new home. A spreadsheet, old URL to new URL, no exceptions. Pages being retired map to their closest relevant replacement — never to the homepage in bulk, which Google treats as a soft deletion.
Step 3 — Keep URLs identical where you can. The safest redirect is the one you never need. If /services/roofing/ works, the new site keeps /services/roofing/. Change URLs for genuine structural reasons, not cosmetic ones.
Step 4 — Implement 301 redirects BEFORE launch. Every changed URL gets a 301 (permanent) redirect, live from the moment the new site is. 301s pass along the ranking trust; their absence burns it. Test them on staging — every single row of the map.
Step 5 — Preserve what was ranking. Redesign the design, not the substance that earned positions: page titles, heading structure and core content of ranking pages transfer unless there’s a strategic reason to improve them. ‘The new copywriter didn’t like it’ is not a strategic reason.
Step 6 — Launch-day technical sweep: XML sitemap resubmitted in Search Console, no leftover ‘noindex’ from the staging build (the classic self-inflicted wound), analytics carried over, SSL intact.
Step 7 — Watch for 30 days. Search Console’s Pages report shows Google digesting the change: 404 errors mean a redirect was missed (fix same day); ranking wobbles for 1–2 weeks are normal; sustained drops mean something structural needs attention NOW, not in month three.
The Payoff Done Right
A properly protected redesign doesn’t just preserve rankings — it usually improves them, because the new site is faster, mobile-cleaner and better structured. Google re-evaluates and upgrades. The difference between that outcome and the horror story is entirely in the boring spreadsheet steps above.
My redesign already tanked my traffic. Is it recoverable?
Usually, yes — if caught within weeks: reconstruct the URL map from crawl archives and Search Console, implement the missing redirects, and rankings typically rebuild over 1–3 months. The longer it’s left, the more permanent the loss becomes.
Do I need redirects if only the design changed, not the URLs?
No redirects needed if every URL is truly identical — but verify rather than assume; page builders and new themes quietly change URL patterns more often than owners realise.
How long do 301 redirects need to stay in place?
Treat them as permanent. Google recommends at least a year; old links from other websites live forever. Redirects cost nothing to keep and traffic to remove.