A traffic drop right after a redesign is almost never Google punishing your new look. It’s mechanical: page addresses changed with no forwarding in place, pages or text got deleted, a hidden keep-out switch shipped from staging, or the words people searched for were designed away. Start by opening your old page addresses. If they come back “page not found,” you’ve found the leak, and every day it stays open costs a little more of the traffic you built.
The good news, such as it is: of all the ways to lose traffic, this one has the clearest fixes. The causes below are ordered by how often they turn out to be the answer. Work down the list and stop when the evidence says stop. One exception: if the drop is total, everything falling at once rather than a handful of pages, jump to Cause 3 first; its check takes two minutes.
First, confirm the timing actually matches the launch
Before blaming the redesign, check that the drop starts when the redesign did. Open Search Console’s Performance report, set a date comparison around your launch week, and look at the shape: traffic level before, falling within days after. If the slide started three weeks before launch, or months later, the redesign is probably innocent and you want the general traffic-drop diagnosis instead, which walks through updates, slipping rankings, and the other usual suspects.
One coincidence to rule out: Google ships updates on its own calendar, and sometimes one lands the same week as your launch. Its Search Status Dashboard lists the dates. If an update overlaps your launch window, keep both suspects on the list; the checks below will separate them, because a redesign leaves physical evidence and an update doesn’t.
Timing confirmed? Then the redesign changed something Google was relying on. Here’s what it usually is.
Cause 1: Pages moved and nobody left a forwarding address
Moved pages with no forwarding address are the cause most of the time, so they earn the first check. Redesigns love to reorganize: /services.html becomes /what-we-do/, the blog moves from /news/ to /blog/, the builder platform changes and every address changes with it. Each old address that isn’t forwarded to its new home now returns “page not found.”
Visitors arriving from Google, from other sites’ links, and from old bookmarks hit a dead end. Google notices too, and it stops sending people to addresses that no longer work.
The check takes ten minutes and no tools. Collect your old page addresses: from Search Console’s Performance report set to the months before launch (the Pages tab lists the addresses that were earning clicks), from an old sitemap, or from your browser history. Open the top ones, the pages that had the most traffic, in a private window. Each one should land on its matching new page.
What you’re looking for is the two ways this fails: the address returns an error page, or it dumps you on the homepage instead of the page you asked for.
What to do about it: forward each old address to its matching new page. The technical name is a redirect, and every platform has a way to add them: WordPress has free redirect plugins, most hosts have a redirects section in the control panel, and site builders keep it under settings. And if an agency or developer built the redesign, say so out loud: mapping old addresses to new ones is part of the launch job. Send them your traffic list and ask them to wire the forwards; you shouldn’t have to reverse-engineer their new structure yourself.
Two rules make the difference. Forward to the matching page, because sending everything to the homepage doesn’t count; when every old address dumps visitors on the homepage, Google treats those pages as gone, not moved. And work from your traffic list, biggest pages first: forwarding the page that earned 700 visits a month matters today, the page that earned four can wait until Friday.
For everything below your top pages, Search Console’s Page indexing report lists the addresses Google tried and couldn’t reach, free. What it won’t show you is your own site’s internal links still pointing at dead addresses, since finding those means visiting every page and link, which is what a crawl automates.
Cause 2: Pages, or the words on them, got deleted
Redesigns slim things down. Old blog posts don’t fit the new look, three service pages become one, and long “wordy” pages get cut to a headline and a photo because it looks cleaner. Sometimes that’s good judgment. But if a deleted or trimmed page was earning search traffic, that traffic went with it, and no forwarding address fully brings back a page whose content no longer exists anywhere.
The tell is in Search Console’s Performance report, comparing before and after launch on the Pages tab: the pages that lost the most clicks either don’t exist anymore or exist as much thinner versions of themselves. To see exactly what a page used to say, look it up in the Wayback Machine, the Internet Archive’s free snapshot library. If it never captured your page, the old site still exists as a backup; hosts and developers keep one through a relaunch, so ask for the old page’s text before it’s rotated away.
Put the old version next to the new one and read them as a stranger: the old page answered a question in three paragraphs; the new one asserts a slogan in six words. Google ranked the paragraphs. It has no reason to rank the slogan, and the same goes for page titles and headings that were rewritten from “Emergency plumber in Leeds” to “Here when you need us.”
What to do about it: bring the substance back, on the new design’s terms. Restore the pages that were earning their keep, or fold their actual answers (not a summary of them) into the pages that replaced them, with a forwarding address from the old spot.
Where the words were polished away, put the plain version back in titles, headings, and body text. Your designer may sigh. Your traffic pays the bills.
Cause 3: A keep-out switch shipped from staging
While it was being built, the new site almost certainly lived on a staging copy, the private under-construction version of the site, hidden from Google on purpose so half-finished pages wouldn’t show up in search. That hiding is done with a keep-out switch, and the single most expensive redesign mistake is launching with it still on. In WordPress it’s one checkbox: Settings → Reading → “Discourage search engines from indexing this site.” Other platforms bury the same switch under privacy or visibility settings.
The check takes two minutes. Paste your homepage and a couple of important pages into Search Console’s URL inspection box. It answers plainly whether the page can appear on Google and, if not, why. If the whole site has gone dark rather than a few pages, that’s its own diagnosis, and the site-not-showing-up-on-Google walkthrough covers it top to bottom.
What to do about it: turn the switch off, then use Request indexing in that same URL inspection view to ask Google for a fresh look. Expect days rather than hours. Of everything on this list it’s the most complete recovery, because nothing was lost; the door was just locked.
Cause 4: The new design is heavier than the old one
New themes arrive loaded: full-screen video, animation on every scroll, a photo on the homepage weighing more than the rest of the site combined. Speed rarely explains a cliff by itself, but a redesign that doubled page weight gives visitors a reason to leave before the page shows, and Google a reason to prefer faster pages, especially on phones.
Paste your homepage and a suspect page into PageSpeed Insights, Google’s free tester, and trust the section based on real visitors’ experience over the simulated score. If that real-visitor section says the page fails, treat speed as a live suspect; if it passes, move on. The culprits are usually oversized images and features nobody asked for, so compress the images and turn off what you don’t need. Just don’t let speed tuning distract from causes 1 to 3; a fast page at an unforwarded address is still invisible.
How long until the traffic comes back?
Honestly: even a clean redesign, every forwarding address in place, usually wobbles for a few weeks while Google re-reads the site and updates its map of what lives where. A dip that recovers on its own inside a month, on a site where the checks above come back clean, is normal and needs nothing from you but patience.
The dangerous version is the leak left open. Missing forwards and deleted content don’t heal by themselves; they compound, because every week Google grows more certain those pages are simply gone.
Found and fixed in week one, most redesign drops recover most of the way. Discovered in month four, some of those rankings have been re-awarded to other sites and have to be earned back the slow way. The difference between those two outcomes is nothing but how soon you looked.
So look on a schedule, not on a bad feeling. After any launch, check the old addresses the same week, re-check Search Console the next, and watch the numbers weekly for a couple of months. Sites break quietly, and launch week is the quietest.
This diagnosis, run every week without you remembering to, is what SEO Audit Flow is for: it crawls your site, flags broken pages and keep-out switches, and ranks each problem by the traffic it’s costing you. For a first look right now, the free 60-second check reads any page from the outside, no account, and flags what a stranger’s browser can see — keep-out settings, missing basics, slow loading. Run it on the new site before your traffic tells you what it finds.