Why your redesign lost your rankings (and how to get them back)

Every few months someone forwards us a Search Console screenshot with a cliff in it. The date on the cliff is always the same date the new site went live.

The conversation that follows is always the same too. The agency says traffic dips are normal after a redesign. The client waits. Three months later it hasn't recovered, and by then the people who could have fixed it in week one have moved on.

Ranking loss during a redesign is not normal, and it is not inevitable. It is an execution failure with a small number of specific, well-understood causes.

The five things that actually cause it

In order of how often we find them:

1. URLs changed without redirects

The single most common cause, and the most avoidable. /services/freight-forwarding becomes /what-we-do/freight and nothing connects them. Every link every other site on the internet built to that page for nine years now returns a 404.

Google eventually drops the old URL and starts the new one from zero — with none of the accumulated authority.

The fix is boring and mandatory: export every indexed URL from Search Console before launch, map each one to its new destination, and implement 301s. Not 302s. Not a blanket redirect to the homepage, which Google treats as a soft 404.

2. Content was cut because it looked dated

A designer looks at a 1,400-word service page and sees a wall of text. It becomes a 120-word page with a nice photograph.

That wall of text was the reason the page ranked. Search engines cannot rank a page for depth it no longer has.

You can absolutely redesign the presentation. But before deleting body copy, check what the page currently ranks for. If it holds positions for a set of terms, the content covering those terms has to survive the redesign in some form.

3. The new site is slower than the old one

Ironic, and common. The rebuild ships with a heavier framework, unoptimised hero imagery, and four new marketing tags. Core Web Vitals degrade. Rankings follow, particularly on mobile.

4. Staging was indexed, or production wasn't

Two versions of the same failure. Either the staging site got crawled and now competes with production for the same terms, or robots.txt shipped with Disallow: / still in it from the staging environment.

The second one is catastrophic and takes about fifteen seconds to check.

5. Structured data and metadata were rebuilt from scratch

Titles get shortened for visual balance. Meta descriptions get dropped because the CMS field wasn't migrated. Schema markup disappears entirely, taking the rich results with it.

The recovery order

If you're already in the cliff, work in this sequence. Doing it out of order wastes weeks.

1. Check robots.txt and the noindex meta tag on production. Thirty seconds. Rules out the catastrophic case.
2. Pull your top 200 pre-launch URLs by clicks. Search Console, 16-month window, filtered to before launch.
3. Request each one. Any that 404 or land somewhere irrelevant gets a 301 today.
4. Compare content depth on your ten highest-value pages, before versus after. Restore what was cut.
5. Re-run Core Web Vitals on mobile, field data not lab data.
6. Validate structured data on every template.
7. Resubmit your sitemap and request indexing on the highest-value URLs.

Steps one through three usually recover the majority of the loss, and often within two to three weeks.

The uncomfortable part

Most of this is checkable in an afternoon. Which means when an agency tells you a three-month traffic decline is a normal post-launch dip, one of two things is true: they haven't looked, or they have looked and would rather you didn't.

Ask them for the redirect map. If one exists, it took real work and they'll be glad to show you. If one doesn't, you have your answer.

A redesign should be the safest possible time to move rankings, because you know exactly what changed and when. Losing them is a choice somebody made — usually by omission.

---

We do migrations without ranking loss as a matter of routine — it's part of how we work. If your traffic hasn't recovered, send us the Search Console screenshot.