You launched a new website, and a few weeks later organic traffic is down. Calls are slower, form submissions dropped and nobody is sure why.
Don't panic, and don't start changing things at random. Most traffic drops after a redesign have a specific, fixable cause. This guide shows how to confirm the drop is real, find exactly which pages lost traffic and fix the most common causes in order of impact.
Step 1: Confirm the drop is real
Before blaming Google, rule out a measurement problem. After a redesign, tracking breaks more often than rankings do.
- Is Google Analytics installed on every template? New templates sometimes miss the tracking code.
- Did conversion tracking change? Form IDs, thank-you pages and button names often change in a redesign.
- Is the cookie consent banner blocking analytics? A new banner can hide a large share of visits.
- Compare with Search Console. Search Console data doesn't depend on your tracking code. If clicks in Search Console are stable but Analytics dropped, the problem is tracking, not SEO.
Step 2: Find which pages lost traffic
In Google Search Console:
- Open Performance and set the date range to compare the weeks after launch with the same period before.
- Open the Pages tab and sort by the difference in clicks.
- Note the pages with the biggest losses.
- Check the Queries tab for those pages to see which searches were lost.
Usually a small number of pages explain most of the drop. That's where to focus.
Step 3: Check the most common causes
Work through these in order. The first ones cause the biggest losses and are the fastest to fix.
1. Pages blocked from Google
- A
noindextag left over from the staging site robots.txtblocking important folders- Pages requiring a login or password
How to check: use the URL Inspection tool in Search Console on a page that lost traffic. It shows whether the page can be indexed and why not.
2. Missing or broken redirects
- Old URLs returning 404 errors
- Redirects pointing to the homepage instead of the equivalent page
- Redirect chains with several hops
- Temporary 302 redirects instead of permanent 301s
How to check: export the old URLs that had traffic and crawl them in list mode. Each should return a single 301 to a relevant page. If you didn't build a redirect map before launch, build one now with our guide on how to build a 301 redirect map.
3. Content that was removed or cut
Compare the old version of the page (use the Wayback Machine at archive.org if you don't have a copy) with the new one. Common problems:
- Long, detailed text replaced by short marketing copy
- Sections, FAQs or service details removed
- Several pages merged into one that no longer covers each topic well
4. Titles and headings changed
If the old page ranked for "emergency plumber in Miami" and the new title says "Welcome to Our Services", Google has less reason to rank it for that search. Restore the keywords that ranked in titles, H1s and headings.
5. Wrong canonical tags
Canonical tags pointing to the staging domain, the homepage or the wrong language version tell Google to ignore the page. Check the canonical in the page source or with URL Inspection.
6. Internal links weakened
Important pages that used to be linked from the main menu may now be buried. Pages with fewer internal links often lose positions.
7. Slower pages or rendering problems
Heavy images, new scripts or content that only loads with JavaScript can hurt both rankings and conversions. Check Core Web Vitals in Search Console and PageSpeed Insights, and use URL Inspection's "View crawled page" to confirm Google sees the content.
8. Bilingual site issues
If your site has English and Spanish versions, check that hreflang tags point to the right URLs and that the language versions weren't redirected automatically based on the visitor's browser.
Step 4: Rule out a Google update
Sometimes the timing is a coincidence. If the drop started on a date Google confirmed a core or spam update, and the affected pages didn't change in the redesign, the cause may be the update rather than the migration. In that case, the fix is improving content quality, not redirects.
Step 5: Fix in order of impact
- Remove any
noindexorrobots.txtblocks - Fix redirects for pages that had traffic or backlinks
- Restore the content and keywords of pages that lost the most clicks
- Correct canonicals and hreflang
- Strengthen internal links to key pages
- Improve speed on the main templates
After fixing, request indexing for the most important pages in Search Console and resubmit your sitemap.
How long does recovery take?
- Blocking issues (noindex, robots.txt): often days to a few weeks after the fix
- Redirects: usually a few weeks as Google recrawls the old URLs
- Content and relevance issues: several weeks to a few months
The sooner you fix it, the better. Old URLs that stay broken for months lose more of their value and are harder to recover.
Frequently asked questions
Is it normal for traffic to drop after a website redesign? Small fluctuations in the first two to four weeks are normal while Google processes the changes. A drop that keeps growing after a month usually has a technical or content cause.
Can I recover SEO rankings after a redesign? In most cases, yes. When the cause is redirects, indexing or removed content, fixing it usually brings rankings back, although not always to exactly the same positions.
Should I go back to the old website? Rarely. It's usually faster to fix the specific problems on the new site. Rolling back creates a second migration with its own risks.
How do I prevent this next time? Follow a migration process before launch: benchmark, URL inventory, redirect map and post-launch monitoring. Our guide to redesigning a website without losing SEO covers every step.
Need a second pair of eyes?
If you've checked the basics and still can't find the cause, our SEO audit reviews indexing, redirects, content and tracking to pinpoint what's costing you traffic. If you're planning another redesign, see how we protect SEO in our website redesign services.