Why your website redesign lost your rankings
Traffic drops after a relaunch are almost always caused by the same handful of mistakes — and most of them are preventable in an afternoon of planning.
A redesign is the most common way a business accidentally loses organic traffic. The site looks better, everyone is pleased, and six weeks later enquiries are down by a third.
The causes are unglamorous and repeat almost every time.
The URLs changed and nobody mapped them
This is the big one. The old site had /services/web-design-services/ and the new one has /what-we-do/design/. Without a redirect, every link and every accumulated ranking signal pointing at the old URL now points at a 404.
The fix is a redirect map: every URL on the old site, matched to its closest equivalent on the new one, implemented as permanent redirects before launch. Not after the drop is noticed.
Export the old URL list from your analytics, your sitemap and a crawl of the live site before you take it down. Three sources, because each will miss something.
The content got shorter
Redesigns often trim copy for visual reasons. A page that ranked because it answered a question thoroughly gets cut to a headline and three bullet points, and it stops ranking because it stopped being the best answer.
If a page currently earns organic traffic, the content on it is an asset. Redesign around it rather than through it.
The new site is slower
This surprises people, because the new site looks lighter. But modern builds frequently ship more JavaScript, larger hero imagery and a font stack nobody audited.
Check Core Web Vitals before launch, on a throttled mobile connection rather than on the office network. The difference is usually substantial.
Noindex made it to production
A staging site is normally blocked from search engines. Occasionally that block ships with the launch, and the site quietly disappears from the index over the following days.
It takes ten seconds to check robots.txt and the page-level robots directives after go-live. Do it on launch day and again a week later.
Internal links were rebuilt around the navigation
Older sites accumulate contextual internal links — a service page linking to a related one, a blog post pointing at a case study. Redesigns often replace all of that with a clean nav and nothing else.
Those contextual links were doing real work distributing authority. A tidier structure with fewer links can rank worse than a messier one with more.
What a safe relaunch looks like
- Crawl and record the current site — URLs, titles, headings, traffic and rankings per page.
- Identify the pages that earn traffic, convert, or have external links pointing at them. These are constraints.
- Build the redirect map before development finishes, not after.
- Preserve or improve the content on high-performing pages. Never simply shorten it.
- Test performance on mobile, throttled, before launch.
- Launch, then verify robots directives, canonicals, sitemap submission and analytics on the same day.
- Monitor Search Console daily for the first fortnight. Coverage errors and sharp impression drops show up there before they show up in revenue.
None of this is difficult. It is just work that has to happen before launch rather than after, which is why it so often does not.
We handle relaunches this way as standard — see how we approach redesigns.