Traffic dropped after a website redesign: how to find out why and get it back

Check the drop is real, find the pages that lost it, then work through the five usual causes in order. A recovery checklist for a site that lost traffic in a rebuild.

Nitesh PadghanNitesh PadghanFounder, Storifex Media
8 min read
On this page (12)
  1. 01The short answer
  2. 02Step one: check the drop is real
  3. 03Step two: find which pages lost the traffic
  4. 04Cause 1: old addresses now go nowhere
  5. 05Cause 2: the staging block is still switched on
  6. 06Cause 3: the content that ranked was cut
  7. 07Cause 4: important pages lost their internal links
  8. 08Cause 5: the titles, canonicals or structured data changed
  9. 09When it is not the redesign at all
  10. 10How it went on this site
  11. 11The checklist, in one place
  12. 12Where to start

The new site went live. It looks better, it loads faster, everybody likes it. Then three weeks later somebody opens the traffic graph and there is a cliff in it.

If your traffic dropped after a website redesign, the cause is usually findable in an afternoon and fixable within a week. What matters is checking things in the right order, because the most common causes are also the quickest to rule out. This is that order.

The short answer

First, make sure the drop is real. A new site very often breaks the tracking rather than the traffic, and Search Console will tell you which in two minutes.

If it is real, find the pages that lost it. It is almost never the whole site evenly. Then check five causes in this order:

  1. Old addresses that now return a 404, or all redirect to the homepage.
  2. A block left over from the staging site, telling Google not to index.
  3. Content cut from the pages that used to rank.
  4. Internal links lost, so important pages are buried.
  5. Titles, canonical tags or structured data regenerated or broken.

Fix them in that order, ask Google to recrawl the pages that matter, and expect most of the traffic back within weeks once the cause is gone. Content that was cut takes longest to recover, because it has to be put back first.

Step one: check the drop is real

Before touching the site, check the measurement. A redesign changes every page template at once, and analytics lives in the templates.

What you see What usually caused it How to tell
Visits fell overnight, on launch day The analytics tag is missing from the new templates Search Console clicks did not fall
Visits fell, but only some days A new cookie banner blocks analytics until visitors accept Search Console clicks did not fall
Visits split between two sites www and non-www, or http and https, now count separately Two properties both show traffic
A drop that matches last year Seasonality Compare with the same weeks a year ago
Search Console clicks fell too A real drop Carry on below

Search Console is the referee here. It counts clicks from Google search on Google's side, so a missing tag or a cookie banner cannot change it. If its clicks held steady while your analytics fell, you have a tracking problem, not a ranking problem, and the fix is in the templates.

Step two: find which pages lost the traffic

In Search Console, open the Performance report, choose Compare, and set the four weeks before launch against the four weeks after. Then switch to the Pages tab and sort by the difference in clicks.

It is rarely the whole site evenly. Usually a small number of pages account for most of the loss. That list is your work queue. For each page on it, open the Queries tab to see which searches it stopped winning. Those searches tell you what Google used to think the page was for.

Note the old address of each page as well. If it is not in the new site's Pages report at all, that is your first clue to cause one.

Cause 1: old addresses now go nowhere

This is the most common cause. The old site had addresses, people and other websites linked to them, and Google ranked them. The new site uses different addresses, and nothing tells Google where each old page went.

How to check: open the Pages report in Search Console and look at "Not found (404)". Then build a list of the old addresses from anywhere you can: the old sitemap if you kept it, a Search Console export from before launch, or the Wayback Machine's copy of the old site. Run the list through any free status checker. Every address should answer with a 301 and land on a real page in one hop.

Two traps. Redirecting every old page to the homepage looks tidy and fails. Google treats a page that redirects to an unrelated homepage much like a page that does not exist, so the ranking goes anyway. And redirect chains, old to older to new, slow the whole recovery down.

The fix: point each old address at its nearest real equivalent on the new site. A page with no equivalent goes to the closest section page, or returns a plain "gone" if nothing links to it. The homepage is only the right answer for the homepage.

Cause 2: the staging block is still switched on

A site being built is hidden from Google on purpose, and sometimes the hiding survives the launch. It takes one line to do it, so it takes one line to miss.

How to check:

  • Open your robots.txt (your domain followed by /robots.txt). If it says "Disallow: /" under "User-agent: *", Google is told to stay out of the whole site.
  • View the source of an important page and search for "noindex".
  • Use URL Inspection in Search Console on that page. It says plainly whether indexing is allowed.
  • Check the canonical tag points at your real domain, not at a staging address.

The fix: remove the block, then request indexing for your most important pages in URL Inspection. This one recovers fastest of all, often within days, because nothing about the pages themselves was wrong.

Cause 3: the content that ranked was cut

A redesign is usually also a tidy up, and the paragraph somebody deleted as waffle was often the paragraph answering the search the page ranked for. This is the quiet one. The address still works and the page simply stops performing.

How to check: compare the old page with the new one. The Wayback Machine usually has the old version. Then look at the queries the page lost in step two and ask whether the new page still answers them. If a page used to rank for "how long does X take" and the new page no longer says how long X takes, you have found it.

The fix: put the answering content back. It can be shorter and better laid out than before. It cannot be absent.

Navigation gets simplified in a redesign. Footer links get trimmed. A page that was one click from the homepage is now four clicks deep, or only reachable through search. Google reads internal links as a signal of what you think matters, and you have just told it that page does not.

How to check: for each page on your list, count how many other pages on your site link to it now, and how many did before. A crawler will do this for you, and many have a free tier for small sites.

The fix: link to the pages that matter from the pages that are strong. That can be the navigation, a hub page for the topic, or a sentence in a related article. Use anchor text that names the page, not "read more".

Cause 5: the titles, canonicals or structured data changed

New templates often generate page titles automatically, and an automatic title is usually worse than the one somebody wrote. A canonical tag can point every page at the homepage after a template mistake. Structured data from the old site can disappear entirely.

How to check: compare the old and new titles for the pages on your list. In URL Inspection, look at the canonical Google chose against the one you declared. Run one page through Google's Rich Results Test.

The fix: restore the titles that worked, then improve them one at a time once traffic has settled, so you can see what each change did.

Two rarer causes are worth ruling out while you are in there: a new site that is far slower than the old one, and a page whose main content only appears after JavaScript runs. URL Inspection's view of the rendered page shows both.

When it is not the redesign at all

Sometimes the timing is a coincidence. Before rebuilding anything twice, check:

  • Google's ranking updates. Google lists its confirmed updates on its Search Status Dashboard. A drop across many sites in your field the same week points there.
  • Seasonality. Compare year on year, not month on month.
  • Lost links. If a site that sent you traffic removed its link, the drop will be concentrated on the page it pointed at.

How it went on this site

We have been through a version of this ourselves. Until July 2026 this domain ran a different business, on WordPress, and when the new site launched every old address stopped working. In August, Google knew eleven addresses on the domain, eight of them dead, and had one page of the new site indexed.

The fix was the list above. The one old service page with a live equivalent went to it. The other two sold something we no longer do and had none, so they went to the homepage. That was the honest exception, not the rule. WordPress's own address patterns, its tag, category, author and archive pages, were sent somewhere sensible rather than left to 404. Then the sitemap went in. By November, Google had 29 pages of the new site indexed.

For a client, the same work is part of the build. When we moved Jay Yang's site to a new build and host, the old addresses were mapped before launch, which is written up in the Jay Yang case study.

The checklist, in one place

Check Where Good looks like
Is the drop real? Search Console Performance, clicks Clicks fell, not just analytics visits
Which pages lost it? Performance, Compare, Pages tab A short list of pages
Old addresses Pages report, a status checker Every old address is one 301 to a real page
Staging block robots.txt, page source, URL Inspection No noindex, no "Disallow: /", indexing allowed
Lost content Wayback Machine, Queries tab The new page still answers the old searches
Internal links A crawl Important pages linked from strong ones
Titles and canonicals Page source, URL Inspection Titles kept, canonicals on your own domain
Not the redesign? Search Status Dashboard, last year's data No update or season explains it

Where to start

Check the drop is real, find the pages, then work down the five causes. Most recoveries are a redirect map and a few restored paragraphs.

If the redesign has not happened yet, the cheaper version of all of this is doing it beforehand: how to redesign a website without losing your search traffic is the checklist for that. And if you would rather hand the whole thing over, a rebuild of a site that already ranks is what our enterprise website development is for, with the redirect map handed over as a document at the end.

Found this useful?
LinkedInX
Nitesh Padghan

Nitesh Padghan

Founder, Storifex Media

I build websites that turn visitors into revenue, and rebuild the LinkedIn profiles that send people to them. Clients in six countries, most of them shipped in two weeks.

Connect on LinkedIn

The rest of this guide

Related reading