Why redesigns actually tank rankings
Nobody sets out to lose rankings during a redesign. It happens as a side effect of five things that keep repeating across the client sites we've inherited after a botched rebuild: URLs that changed without redirects, entire pages of ranking content that got "simplified" out of existence, an internal linking structure that got flattened by a new template, a new site that's slower than the old one despite looking nicer, and thin rewritten copy that traded specificity for generic marketing language. Any one of these can cost you 20-40% of organic traffic. Combined, we've seen sites lose 70% within a month.
If you're planning a rebuild, start by reading our guide to website redesign services to understand the scope of what a properly sequenced redesign actually involves — the design is the visible 20% of the work; the migration mechanics are the other 80% that determines whether you keep what you've already earned.
The pre-redesign audit
Before a single new page gets built, we crawl the existing site with Screaming Frog or Sitebulb and export every URL that returns a 200 status. Then we cross-reference that list against Google Search Console's Pages report and the Performance report filtered to the last 16 months, so we know exactly which URLs are indexed, which ones actually receive clicks, and which ones rank for anything meaningful.
This produces a benchmark, not just a list: current keyword rankings for the top 50-100 queries, current organic sessions by landing page, current backlink-earning pages from Ahrefs or Search Console's link report, and current Core Web Vitals scores. Without this baseline, you have no way of proving a ranking drop after launch is actually a drop — or catching it early enough to fix.
A site with 340 indexed URLs and 12 pages earning 90% of the traffic doesn't need 340 redirects treated equally — it needs those 12 pages mapped with surgical precision and everything else handled sensibly. Prioritise by traffic and backlinks, not by URL count.
The redirect map: the single most important step
If you do only one thing right in a redesign, make it this. A redirect map is a spreadsheet — old URL in column A, new URL in column B, one row per indexed page — that becomes the literal 301 redirect rules implemented at launch. We cover how to build one properly in our dedicated guide to planning a 301 redirect map for a website migration, but the short version is: every URL that has ever ranked, been linked to, or received organic traffic needs its own specific redirect to the new page that most closely replaces it. Redirecting everything to the homepage — which we still see agencies do to save time — is the fastest way to lose rankings, because Google treats a blanket homepage redirect as a signal the old content simply disappeared.
Staging and before/after comparison
The new site gets built on a staging subdomain, blocked from indexing with a noindex header (not robots.txt, which Google sometimes ignores for staging environments). Before launch, we run a side-by-side comparison: does every URL on the old-site crawl have a mapped destination? Does the new page's word count and heading structure cover what the old page covered, or did something get cut in the redesign? Is the new template's load time actually faster, using the same Lighthouse settings as the baseline audit? If the new site is heavier — more scripts, more web fonts, a page builder with more overhead than the old hand-coded theme — that's a real problem worth solving before launch, not after. Our guide on fixing a slow website covers the usual culprits if this shows up in testing.
The post-launch monitoring window
Launch day isn't the finish line. For the first two weeks, check Search Console daily: the Coverage report for a spike in 404s or "submitted URL not found," the Page Indexing report for pages stuck as "Discovered, not indexed," and the Performance report filtered by query to catch specific rankings that moved. From week three through six, check twice weekly. A temporary dip of 5-15% during this window is normal — Google needs time to recrawl and re-associate signals with the new URLs. A dip that doesn't start recovering by week four, or one that exceeds 25-30%, means something in the redirect map or internal linking is broken and needs fixing immediately, not "given more time."
We've caught and fixed redirect gaps on day nine of a launch that would have cost a client's top three ranking pages permanently if left until the standard monthly report. Daily monitoring in the first two weeks isn't paranoia — it's the difference between a five-minute htaccess fix and a six-month recovery.
Internal linking and content parity
A redesign changes more than the visual chrome around your content — it usually changes the navigation, the footer, and the "related articles" logic that used to funnel authority between pages. If your old site linked from every blog post to your three core service pages, and the new template drops that pattern in favour of a generic sidebar widget, you've quietly cut off the internal link equity those service pages depended on. Before launch, map the old site's internal linking patterns the same way you mapped its URLs, and rebuild the equivalent structure — or something stronger — in the new template.
Content parity matters just as much. "Simplifying" copy during a redesign is a common trap: a 900-word service page that ranked for a dozen long-tail variations gets trimmed to 300 words of punchy marketing copy because it "reads better," and the rankings that depended on that depth and specificity evaporate along with it. Good design and thorough content aren't in tension — the best redesigns we've run tightened the visual presentation while keeping or expanding the substance underneath.
Coordinating design, dev and SEO timelines
The most common cause of redirect map failures isn't ignorance — it's timing. Design finalises page structure late, development builds against a moving target, and by the time someone remembers to update the redirect spreadsheet to match the URLs that actually shipped, launch is two days away and nobody has time to re-verify it properly. Build the redirect map as a living document from day one, owned by one person, and treat any late URL structure change as an event that requires updating it immediately — not a footnote to catch up on later.
If you're weighing whether your current site's issues are even worth this level of process, it's worth stepping back first and checking our list of signs your website needs a redesign — some problems are better solved with targeted fixes than a full rebuild, and knowing which category you're in changes how much of this process you actually need to run.