Why traffic drops after a website redesign

The pattern is familiar enough to be predictable. A new site launches, everyone agrees it looks far better, and four weeks later organic traffic is down by a third. Nobody changed the content much. Nobody was warned this could happen.

It happens because a redesign changes the things search engines use to understand a site, and those things are invisible in every design review. Here are the five causes, in the order they are worth checking.

1. The URLs changed and nothing redirects

The most common cause by a wide margin, and the most damaging.

Every page that ranked had an address. If /services/seo-agency became /what-we-do/search, then as far as a search engine is concerned the old page was deleted and an unrelated new one appeared. Whatever the old page had earned — rankings, and the value of every link pointing at it — does not transfer on its own.

It transfers if each old address permanently redirects to its new equivalent. That mapping has to be built page by page. Redirecting everything to the home page, which is the usual shortcut, does not work: search engines treat a mass redirect to one page as a soft deletion of all the others.

How to tell: find any old URL — an old Google result, a link in an old email — and open it. If it 404s, this is your problem.

2. The new site is slower

Redesigns tend to add weight. Larger images, a video header, an animation library, a chat widget, three analytics tools.

Speed matters twice over. It is a ranking factor directly, and it changes behaviour — people leave slow pages, and on mobile connections the gap between a fast and a slow site is the difference between reading and giving up. A site that looks better on your laptop can be materially worse on a mid-range phone on a poor connection, which is where a large share of your visitors actually are.

How to tell: run the new site through Google's PageSpeed Insights on mobile and compare against a copy of the old one if you can. Look at the field data rather than the lab score.

3. Content got tidied up

Design reviews cut copy. Long pages become concise pages, five service pages become one, the FAQ gets removed because it looked untidy.

That copy was often what the page ranked for. A page that answered fifteen questions and now answers four has lost eleven reasons for anyone to find it. This is the cause that surprises people most, because everyone agreed at the time that the site was better for it — and by most measures it was.

How to tell: compare word counts on your most important pages, before and after. Large reductions on pages that used to bring traffic are the ones to look at.

4. The staging site's blocking rule went live

While a site is being built it is usually hidden from search engines, either with a noindex tag or a rule in robots.txt. That protection is supposed to be removed at launch.

Sometimes it isn't. The site is live, looks perfect, and is instructing every search engine to ignore it. Traffic does not drop gradually in this case — it falls off a cliff over a fortnight or so.

How to tell: open yourdomain.com/robots.txt and look for Disallow: /. Then, in Google Search Console, use URL Inspection on a few pages and see whether it reports them as blocked.

5. The internal linking collapsed

Old sites accumulate links between pages — a services page linking to case studies, a blog post linking to a service. Those links tell search engines which pages matter, and pass authority between them.

New designs frequently replace all of that with a clean navigation bar and little else. Every page is now two clicks from the home page and linked from almost nowhere, and the pages that used to be reinforced by twenty internal links are now reinforced by one.

How to tell: pick a page that used to perform and count how many other pages on the site link to it now, compared with before.

Working out which one you have

Start with Search Console, comparing the period after launch against the same length of period before.

• Traffic falls to near zero within two weeks → cause 4
• Specific pages lose everything while others are untouched → cause 1
• A broad, even decline across most pages → cause 2, 3 or 5
• Rankings hold but clicks fall → your titles and descriptions were rewritten

The Pages report under Indexing is the other place to look. A jump in "Not found (404)" points squarely at cause 1.

How much comes back

Most of it, usually — but not instantly, and not without doing the work.

Redirects are the fastest to fix and the fastest to recover from, typically within weeks of being put in place. Restored content and repaired internal linking take longer, because search engines have to recrawl and reassess. Blocked indexing recovers quickly once unblocked.

What genuinely doesn't come back is time. A drop caught after six months has cost six months of enquiries, and the recovery still starts from the day you fix it. Which is the argument for checking in the first week rather than waiting to see whether it settles.

Avoiding it next time

The whole category is preventable, and the prevention is unglamorous:

• Export your top pages and their URLs before the build starts. You cannot build a redirect map from a site that no longer exists.
• Agree a performance budget before design begins, not after — retrofitting speed onto a finished design means removing things people have already approved.
• Make "remove the staging block" an explicit item on the launch checklist, with a name against it.
• Treat content cuts as a decision with a cost, not a tidy-up.
• Check Search Console weekly for the first month. A problem caught in week one is a fortnight of recovery; the same problem caught in month six is most of a year.

We build sites with this list as a constraint rather than an afterthought — the reasoning is on our web development page. If you have already launched and the numbers have moved, the diagnosis above will usually tell you which of the five you are dealing with before you need to ask anyone.