A traffic drop after a website redesign usually comes from one of four things: broken tracking, pages Google can’t reach, old URLs that don’t redirect properly, or content that got stripped out of the new design. Check them in that order, because the first three can be confirmed in an afternoon and fixed without touching a word of copy. Some wobble is normal. Google says to expect temporary ranking fluctuation during a move, but that’s no reason to sit on your hands.
Most guides on this give you a long list of possible causes. This one gives you a sequence, a way to calculate what the redesign really cost, and an email you can send your web team today.
Should you wait, or start checking now?
Check now. Wait on the content.
Agency rules of thumb vary. SALT.agency treats a 5 to 10% dip as something that often corrects itself, and a sudden 30 to 50% fall as a likely technical fault. LOW/CODE calls 5 to 15% normal in the first 30 days and says anything above 20% needs immediate investigation. Neither page cites data for those numbers, so treat them as opinions.
My rule ignores the percentage. Tracking, crawl and redirect checks are free and fast, so run them the day you notice the drop, at any size. A broken redirect won’t heal itself while you wait. Hold off on rewriting content until those checks are clean and the dust has settled. Google says a small to medium site can take a few weeks for most pages to move, and larger sites take longer. Four weeks after launch is the point where I’d start judging content on a small or medium site.
Check 1: Did traffic fall, or did your tracking break?
Open Google Search Console and GA4 side by side. Search Console counts clicks from Google’s side, so a broken analytics tag can’t affect it.
- Search Console clicks steady, GA4 organic sessions down: tracking problem. Check the tag is on every template and your conversion events still exist. Sudden falls to zero or strange spikes are typical signs.
- Both down: the drop is real. Keep going.
Don’t skip this. It’s the cheapest possible outcome, and you’d hate to spend a month fixing an SEO problem that was a missing script.
Check 2: How much did the redesign actually cost you?
Your before-and-after number is probably wrong, because it includes seasonality. Google’s own guide suggests using the 16-month view to rule out a drop that happens every year and comparing year over year. Do the sum properly.
A hypothetical example. A service business launches a new site. These numbers are invented to show the method.
| Step | Calculation | Result |
|---|---|---|
| Clicks, 28 days before launch | From Search Console | 40,000 |
| Clicks, 28 days after launch | From Search Console | 24,000 |
| Raw drop | 40,000 – 24,000 | 16,000 (40%) |
| Same two periods last year | Seasonal change | -10% |
| Expected clicks without the redesign | 40,000 x 0.90 | 36,000 |
| Real loss | 36,000 – 24,000 | 12,000 (33%) |
Now turn that into money, using your own rates. Say 1% of those visitors become leads, 25% of leads close, and a customer is worth $500 in gross profit. 12,000 x 1% = 120 leads. 120 x 25% = 30 customers. 30 x $500 = $15,000 a month.
That figure decides how much the fix is worth. If you’re losing $15,000 a month, a few days of developer time is an easy yes. If you’re losing $300, fix the redirects yourself and move on.
Also check the start date. If the fall began before launch or weeks after it, the redesign may not be the cause. A Google core update landing around the same time can muddy the picture, so compare your dates with Google’s ranking updates list before you blame your developer.
Check 3: Can Google get into the new site?
The classic launch mistake is a staging setting that went live with the site. Google’s site move guide says to remove any noindex or robots.txt blocks that were only needed for the migration. Check these three places:
- Your live robots.txt file. A blanket
Disallow: /means stop everything. - The Page indexing report in Search Console. Look for a jump in pages excluded by noindex or blocked by robots.txt since launch.
- URL Inspection, using a live test on your five most valuable pages. Look at the rendered result. If the main copy only exists after JavaScript runs and it’s missing here, you’ve found your problem.
While you’re in there, confirm your sitemap lists the new URLs. Google lists outdated sitemaps among the common migration mistakes.
Check 4: Do your old URLs land on the right pages?
This is where I’d bet my money on most redesign drops, and it’s the check that’s easiest to do badly. Testing the homepage and a couple of top pages proves nothing.
In Search Console, compare the periods before and after launch on the Pages tab, then sort by click difference. Those are your test URLs. Search Engine Land’s guide suggests about 10. I’d test every URL that makes up 80% of the lost clicks, however many that takes. Then run this for each one, from any Mac or Linux terminal:
curl -s -o /dev/null -w "%{http_code} %{redirect_url}\n" https://example.com/old-page/It prints the status code and where the URL points. Read the result like this:
| Result | What it means | What to do |
|---|---|---|
| 301 to the matching new page | Correct | Nothing, unless the target redirects again. Run the command on the target to check for chains. |
| 302 to the matching new page | Temporary redirect. Google doesn’t use it as a signal that the target should be canonical. | Change to 301. Search Engine Land’s author describes a client whose traffic began climbing back after exactly this fix. |
| 301 to the homepage | Lazy mapping. Google says irrelevant redirects might be treated as a soft 404. | Point it at the closest real page. |
| 404 | Page is gone | If it earned traffic or links, restore it or redirect it. If you retired it on purpose, a 404 or 410 is the right response. |
| 200 with no redirect | Old URL still loads | Possible duplicate or leftover page. Check it and redirect it if the new version lives elsewhere. |
If your platform uses JavaScript redirects, get them replaced. Google says server-side redirects have the highest chance of being interpreted correctly, and that it might never see a JavaScript one if rendering fails.
Don’t forget older domains and URLs. Search Engine Land describes a case where a redesign missed the redirect from a previous domain, cutting off more than 10 years of history. If your business has ever changed domain, test those URLs too.
Stuck on this step? We can go through your old URLs against the new site and hand you a redirect list ranked by lost clicks. Ask SEOIndexr to look at it.
Check 5: Did the new design remove what was ranking?
If the plumbing is clean and the drop persists, compare old and new versions of your biggest losers. The Wayback Machine usually has the old page if you didn’t keep a copy. Put them side by side and look for:
- Body copy cut to make the layout prettier. A 900-word service page that became three lines and an icon row is a different page to Google.
- Title tags and headings replaced with brand slogans.
- Internal links lost when the navigation was simplified. Check whether your big losers dropped out of the menu.
- Copy moved into tabs, sliders or scripts that don’t show in the URL Inspection render.
- Slower pages. Run old and new versions through PageSpeed Insights if you can still reach both.
The fix is usually dull: put the useful content back. You can keep the new look.
One more possibility. If impressions and average position held but clicks fell, your rankings may be fine and the results page changed around you. Search Engine Land also lists SERP layout changes among causes to rule out, and I’ve covered what to do about zero-click results separately. No redirect will fix that.
What should you fix first?
Go back to the hypothetical. Say the 12,000 lost clicks break down like this after the checks above:
| Cause | Lost clicks | Share | Monthly value at $1.25 per click |
|---|---|---|---|
| Bad or missing redirects | 6,000 | 50% | $7,500 |
| Stripped page content | 3,000 | 25% | $3,750 |
| Lost internal links | 1,500 | 12.5% | $1,875 |
| Unexplained | 1,500 | 12.5% | $1,875 |
The $1.25 is simply $15,000 divided by 12,000 clicks. Rank the work by value per hour of effort, not by what’s most interesting. Redirects nearly always win, since a spreadsheet and a developer can clear them in a day or two. Leave the unexplained slice alone until everything else is done. It may close by itself.
What isn’t worth doing?
- Hammering Request Indexing. Google says the tool is for a few URLs, and that asking repeatedly for the same URL won’t speed up the crawl.
- Mass redirects to the homepage to clear 404s. It tidies up a report and helps nobody.
- Redirecting pages that never earned anything. Retired pages with no clicks and no links can return 404. A 404 report full of junk URLs isn’t an emergency.
- Launching a batch of new blog posts. You haven’t got a content shortage. You’ve got a repair job.
- A second redesign. In my opinion, rolling back is usually a mistake too, since it changes your URLs again. The exception is a new site Google can’t crawl and your developer can’t repair within days.
The email to send your web team today
Copy it and change the bits in brackets. If the answer is a shrug, read our notes on what SEO and web contracts should say about responsibility before you sign the next one.
Subject: Organic traffic drop since launch: need these by [date]
Hi [name],
Search Console shows organic clicks down since the new site launched on [date]. To find the cause, please send me:
1. The full redirect map, old URL to new URL, plus how the redirects are implemented (server, plugin or JavaScript).
2. Confirmation that no noindex tags or robots.txt blocks from staging are live.
3. The sitemap URL submitted after launch.
4. A list of pages removed or merged in the redesign.
5. A copy of the old site or its content, if you kept one.Please don’t remove any redirects or change URLs until we’ve reviewed this.
Thanks,
[you]
FAQs
How long does recovery take after a website redesign?
Nobody can give you an honest fixed number. Google only says a small to medium site can take a few weeks for most pages to move and that a recrawl can take a few days to a few weeks. LOW/CODE quotes 60 to 180 days, without citing data. Be wary of anyone promising a date, and remember the clock doesn’t really start until the cause is fixed.
Will my rankings come back to where they were?
Not guaranteed. Google says rankings settle down over time, but that’s about the move, not your new content. If you fixed a redirect, there’s a fair chance you get back what you lost. If you cut the content that earned the ranking and left it out, don’t expect the old position back.
How long should I keep the redirects?
Google says as long as possible, generally at least a year. I’d never remove ones that still get traffic or have links pointing at them. Write that into your handover if a new agency takes over the site.
Can a redesign hurt SEO if the URLs didn’t change?
Yes. Check 5 is the reason. Same URLs with less copy, fewer internal links or content that doesn’t render can lose rankings with not a single redirect involved.
We’ll review your Search Console data, redirects and rebuilt pages, then tell you what’s causing the drop and what to fix first. Talk to SEOIndexr or email seoindexr@gmail.com.
Sources
- Google Search Central: Site moves with URL changes
- Google Search Central: Redirects and Google Search
- Google Search Central: Debugging drops in Google Search traffic
- Google Search Central: Ask Google to recrawl your URLs
- Search Engine Land: Recovering SEO traffic and rankings after a website redesign
- SALT.agency: Why your organic traffic dropped after your website redesign
- LOW/CODE Agency: Why did website traffic drop after redesign?