JOURNALSEO & GROWTH

Traffic dropped after a website redesign? What to check first

Search clicks fell after your new site went live? Confirm the drop is real, rule out other causes, then check redirects, indexing, content and links.

October 21, 202618 min readBy Alex Jardine
SEOTechnical SEO

Start in Search Console, before you touch the site. First, confirm the drop is real and that tracking didn't break. Next, rule out causes that have nothing to do with the redesign: a yearly dip, a Google update, a manual action. Then check what the launch changed: page addresses, leftover blocks on indexing, the content that ranked, internal links, and whether Google can render what visitors see. You can read the evidence for each yourself, and once you know the cause, the choice gets simpler: fix it yourself, wait and measure, or get help.

Before you change anythingYour answers stay on this page
Do Search Console clicks show the same drop as your analytics?
Did any page addresses change at launch, even slightly?
Did the staging site use noindex or a robots.txt block?
Were the pages that ranked shortened, retitled or moved into tabs?
Did any important pages leave the main menu or footer?
0 of 5 clear 5 still to answer
AnswersDoes Search Console show the same drop?

Is the traffic drop real, or is tracking broken?

Check it in Search Console before you change anything. Compare clicks and impressions there with your analytics for the same dates. If both show the same fall, the drop is real. If Search Console is steady and analytics fell, the problem is tracking, so fix the tag first and leave the pages alone.

GA4 only counts what its tag records. Pages that lost the tag in the rebuild, visitors who decline tracking in a consent banner and different time zone settings all open gaps. Google's Using Search Console and Google Analytics data for SEO expects the totals to differ: "what's important is that the general trends have the same pattern." If the lines split at launch, check the new templates for the tag.

Line up the dates carefully. Performance report (Search results): Troubleshooting data discrepancies says Search Console labels daily data in Pacific Time, and collected data is usually available in 2 to 3 days, so ignore the last few days. Then open Data anomalies in Search Console for known reporting changes. It records, for example, that FAQ rich results stopped appearing on May 7, 2026, which lowers reported FAQ impressions.

Once the drop is confirmed, read the shape of the chart. Google's Debugging drops in Google Search traffic helps you tell two patterns apart:

  • Clicks and impressions both down. You lost visibility, or fewer people are searching. Keep going in order.
  • Impressions steady, clicks down. People see you but click less. Compare your old titles and descriptions with the new ones, and check whether another site now has "a more appealing rich result."

Could something else explain the drop, not the redesign?

It can. A yearly dip, a Google ranking update, a change in demand or a manual action can all land in the same weeks as a launch. Rule these out before you blame the new site, because each one calls for a different response, and some call for leaving the site exactly as it is.

Start with the calendar. Set the Performance report to the last 16 months so you can see the same weeks last year. If clicks dipped then too, it is probably seasonal. Then check your top queries in Google Trends to see whether people are simply searching less.

Next, line your launch date up with the ranking updates on the Google Search Status Dashboard's History for Ranking. So far in 2026, it lists these ranking updates, plus a February update to Discover:

  • March spam update, started March 24 and ran 19 hours and 30 minutes
  • March core update, started March 27
  • May core update, started May 21
  • June spam update, started June 24
  • August spam update, started August 18
  • September spam update, started September 24 and ran 13 days and 16 hours

If your drop starts inside one of those windows, the update may explain it better than the redesign. Open the Manual Actions and Security Issues reports in Search Console too. An entry in either one comes first.

Google's debugging guide says that after an update "there might not be anything fundamentally wrong with your content." Small position changes, such as a page moving from position 2 to 4, can happen at any time, and Google recommends "avoiding making radical changes if your page is already performing well." If the timing matches an update or a yearly dip, measure and wait.

Did the whole site fall, or only some pages?

Find out which pages lost clicks before you look for causes. A site-wide fall points to a setting that touches every page, such as a redirect rule, robots.txt or noindex. A fall in one group of pages points to what changed on those pages: their addresses, their content or the links to them.

In the Performance report, compare the weeks after launch with the same stretch before it, open the Pages tab and sort by Clicks Difference. If nearly every page fell together, open the Page indexing report and look for a jump in pages excluded by noindex, blocked by robots.txt or redirected. If only a group fell, run URL Inspection on a few of them.

If addresses changed, match each old URL that lost clicks to its new URL, then check whether the new one picked them up. Google's How to move a site says to monitor both old and new URLs during a move. When clicks vanish and no page gains them, go to the next section.

AnswersDid any page addresses change?

Did any page addresses change when you launched?

Check this even if you think nothing changed. Any change to an address counts, even a trailing slash or a dropped .html, as Google's John Mueller explains in Do URL structure changes affect SEO? Every old address that had traffic or links needs a permanent redirect to its matching new page.

Build a list of old URLs from old sitemaps, analytics landing pages, the Search Console Pages tab, the old CMS or a backup. Test each important one in a browser or a redirect checker.

Each important old URL needs one server-side permanent redirect, a 301 or a 308, to the page that replaced it. Google's Redirects and Google Search explains why the type matters. Googlebot follows temporary redirects (302 and 307), but the indexing pipeline doesn't use them as a signal that the target should be canonical, meaning the version Google shows, so the old URL can stay in results. Permanent redirects "don't cause a loss in PageRank," Google says.

What you find when you test an old URL

301 or 308 to the matching page

What Google does

Treats the new URL as canonical

What to do

Keep it

302 or 307

What Google does

Follows it, may keep the old URL

What to do

Change it to a 301

Many old pages sent to the homepage

What Google does

May treat them as soft 404s

What to do

Point each to its match

A chain of several hops

What Google does

Follows up to 10

What to do

Redirect straight to the final page

No redirect, or one to a missing page

What Google does

Reports Not found

What to do

Add a 301 to the right page

Sending many old URLs to the homepage "might be treated as a soft 404 error," Google says, which means the old page can be treated as missing. A page you deleted on purpose should return a 404 or 410. Keep chains "ideally no more than 3 and fewer than 5" hops. Google "frequently" sees redirects to wrong or non-existent URLs, so watch for a spike in Not found errors, and keep redirects "generally at least 1 year."

AnswersDid staging use noindex or a robots.txt block?

Could leftover noindex, robots.txt or canonicals be blocking Google?

Yes, and it belongs near the top of your list. Staging sites are often hidden from search with a noindex tag or a robots.txt block, and those settings can carry over to the live site. Google's site move troubleshooting list puts leftover noindex and robots.txt blocks first among its common mistakes.

The two settings interact. As Block Search indexing with noindex explains, Google can't crawl a page that robots.txt blocks, so it never sees that page's noindex. Google also doesn't support noindex rules written inside robots.txt. Use URL Inspection on a live page to see what Googlebot actually received.

A misplaced noindex causes a slower drop, because Google has to recrawl each page before it sees the tag, so a gradual fall can still come from one. Work through these in order:

Indexing checks, in order
  1. Check robots.txt on the live site. Remove any Disallow rule copied from staging.
  2. Inspect your key URLs. URL Inspection shows whether Google found a noindex tag or header.
  3. Check the canonical on each new page. It should point to the page itself on the live domain.
  4. Check the sitemap. It should list the live canonical URLs. Submit it in Search Console.
  5. Check the firewall or CDN. Make sure bot protection lets Googlebot through.

Each new URL needs a self-referencing canonical, a tag that names the page itself, not the staging address or the old site. Build and submit a sitemap says Google ignores priority and changefreq, uses lastmod only when it's consistently and verifiably accurate, and treats a submitted sitemap as "merely a hint." Get the redirects and links right first.

If the host or CDN changed along with the design, Google's Changing your hosting warns you to check that firewall or denial of service protection doesn't block Googlebot. Clear all of this before you rewrite a word of content.

AnswersWere the pages that ranked cut or moved into tabs?

Did the redesign cut or rewrite the content that ranked?

It can, and it is easy to miss. A redesign can keep every URL and still change what Google ranked: shorter copy, new titles and H1s, text moved into tabs, sections removed. Compare the pages that lost the most clicks with their old versions, then restore what earned the rankings on the same URLs.

Use a backup or the Wayback Machine to compare each old page's title, H1, body length and sections.

In When Revamping a Site Can Negatively Impact Rankings, Search Engine Journal reported a July 2021 office-hours answer from Google's John Mueller. He said nothing on Google's side changes rankings just because a site is revamped. His advice was to keep the URLs, the internal linking and "the content and the layout on the pages" the same as much as possible. If those stay aligned, the only thing Google may see is "that maybe the website is a little bit faster now."

Owners often assume a redesign was safe because the URLs stayed the same. Mueller's answer shows why that isn't enough: the URLs were only one of the three things he named. Cut copy, rewritten titles and H1s, and links dropped from the menu all change what Google finds at an address that never moved.

The same URL, before and after a redesignFictional example
Before

Furnace repair page

  • Title Furnace Repair in Northgate
  • H1 Furnace repair in Northgate and nearby towns
  • Body Symptoms, brands serviced, pricing guide, questions
  • Reached from Main menu and footer
After

Furnace repair page

  • Title Comfort, Handled
  • H1 Warmth you can count on
  • Body Short intro, details hidden in tabs
  • Reached from A services overview page only

The address stayed the same. The words people searched for were removed.

Bring back the sections, titles and H1 wording that matched how people search, and put key text on the page instead of behind a tab. You can keep the new design and still restore the words that earned the clicks.

AnswersDid important pages leave the menu or footer?

Compare the new menu and footer with the old ones. Pages dropped from the main navigation or footer lose internal links even when their URLs stay put. Google finds pages mainly through links, so a page that is harder to reach can quietly earn fewer clicks. Restore the paths to the pages that matter.

Google's How to move a site says to change internal links on the new site from the old URLs to the new ones, instead of relying on redirects. Crawl the new site and look for internal links that still pass through a redirect.

Mueller named internal linking as one of the three things to keep stable. List the pages that bring in calls and quote requests, and give each a clear path through the menu, the footer or a related page.

Is Google seeing the same page you see?

Check the rendered HTML in URL Inspection. On sites built with JavaScript, such as Next.js, Framer, React or a headless CMS, Google runs the scripts to see the page. Content missing after that step is missing from the index, even when the page looks complete in your browser.

Understand the JavaScript SEO basics explains that Google finds links in the href attribute of HTML links, meaning real <a href> elements. In URL Inspection, run a live test, open the rendered HTML and check that it contains:

  • The main body text, including anything in tabs or accordions
  • Links to your key pages as <a href> elements
  • The title, meta description and canonical you expect
  • A robots meta tag that allows indexing

If the original page code contains a noindex, Google may skip rendering, so JavaScript that removes it "may not work as expected." Google calls server-side or pre-rendering "still a great idea" and treats JavaScript redirects as a last resort. For your developer: put the content, links, canonical and robots tags in the server response.

Simple crawlers, free scanners included, can miss content that only appears after scripts run. When a crawler and URL Inspection disagree, go with URL Inspection: it shows what Google received.

Then check speed. Understanding page experience in Google Search results says Core Web Vitals "are used by our ranking systems," and that Google "always seeks to show the most relevant content, even if the page experience is sub-par." Interaction to Next Paint (INP) replaced FID as a Core Web Vital in March 2024, as web.dev announced in Interaction to Next Paint is officially a Core Web Vital. Judge speed with field data in Search Console's Core Web Vitals report rather than one lab run. A slower site can matter at the margin, but a missing redirect or a noindex explains a sharp drop far better.

How long should you wait before deciding something is wrong?

Long enough to see a trend. Google's own guidance talks in weeks, and it expects some movement after a site change. But if your URLs, links and content stayed aligned and the drop is sharp and sustained, treat it as a defect to find rather than something that will settle on its own.

How to move a site says to expect temporary fluctuation. For medium-sized websites, Google says "it can take a few weeks or more" before it starts showing the new URLs instead of the old ones, and larger sites can take longer. The Search Engine Optimization (SEO) Starter Guide adds that some changes take effect in a few hours and others take several months, and suggests waiting a few weeks before you judge your work.

There is no sound public study of recovery times for redesigns that keep the same domain. The nearest research measures something else. SALT.agency's Only 27% of domain migrations recover in 90 days looked at 1,052 domain migrations and only counted those where traffic fell 60% or more. That is a different event, so its timelines don't transfer to a redesign that kept its domain.

What each kind of timing evidence can tell you

Google's site move guidance

Can tell you
Fluctuation is expected, and new URLs can take a few weeks or more to show on medium sites.
Leaves open
How long a same-domain redesign takes, or when a drop signals a defect.

Domain migration studies

Can tell you
How domain changes with large traffic losses played out over time.
Leaves open
Whether those timelines apply when the domain and URLs stayed put.

Your own Search Console data

Can tell you
Which pages lost clicks, and when the fall started.
Leaves open
Why they lost them, until you run the checks above.

Should you fix it yourself, wait, or get help?

Let the checks decide. Fix it yourself when the cause is clear and within your control. Wait when the evidence points to a season, an update or a careful move that is still early and trending up. Get help when the basics are clean and the pages that bring in work are still down.

Three ways forward
Fix

Fix it yourself

  • Drop confirmed in Search Console
  • Causes noindex, robots block, missing or homepage redirects, 302s
  • Also Cut titles or H1s, lost menu links
Wait

Wait and measure

  • URLs, content and links mostly stable
  • Timing Matches a season or a Google update
  • Or A careful move, early and trending up
Help

Get help

  • Basics clean, key pages still down after a few weeks
  • Missing Old URL list or server access
  • Or JavaScript rendering you cannot read
  • Or URLs or the domain changed at scale

If you fix it yourself, re-check each page with URL Inspection, then run the free SEO audit once as a lighter recheck. It checks up to 25 pages with no signup. If you wait, keep watching the Performance report, the Status Dashboard and Manual Actions, and leave pages that still perform alone.

Get help when the pages that bring in work are still down after a few weeks with no upward trend, or when you can't run the checks yourself: no old URL list, no server access, or rendered HTML you can't read.

For those cases, the studio, which has been building and improving websites since 2022, offers the Website and Search Audit: CAD 800 for Canadian clients and USD 750 for everyone else. We crawl and check every accessible page up to 200, give representative pages and the main ways customers get in touch a hands-on review, and, with your access, review Search Console and GA4. You get the fixes ranked, with hours for each. If URLs changed, the Large Site or Migration Audit also checks every old URL against the new site.

Audit sizes and prices
Small Site AuditCAD 450 / USD 395Up to 25 pages · 3 business days

For contractors and local services with a small site.

Website and Search AuditCAD 800 / USD 750Up to 200 pages · About 5 business days

For owner-led businesses weighing a redesign, ads or more SEO.

Large Site or Migration AuditFrom CAD 1,400 / USD 995Bigger, or moving to new URLs · 7 to 10 business days

For bigger sites, or any site moving to new URLs.

This is a planning range. Your written quote confirms the final price.

The audit fee is credited toward any follow-on work booked within 60 days of report delivery, including new builds and care plans. If the launch was a full migration and you want the studio to take it on, see traffic dropped after a migration.

To weigh what kind of help fits, read SEO audit vs ongoing SEO. Still deciding how much of the site to change? Website redesign vs rebuild walks through that choice.

Whatever you decide, keep the order. Confirm the drop, rule out seasons, updates and manual actions, then check addresses, indexing blocks, content, links and rendering. Start today in the Performance report: compare the weeks after launch with the weeks before, sort by Clicks Difference, and open the page at the top in URL Inspection.

References (17)
  1. Google. Debugging drops in Google Search traffic. Google Search Central. https://developers.google.com/search/docs/monitor-debug/debugging-search-traffic-drops
  2. Google. Using Search Console and Google Analytics data for SEO. Google Search Central. https://developers.google.com/search/docs/monitor-debug/google-analytics-search-console
  3. Google. Performance report (Search results): Troubleshooting data discrepancies. Search Console Help. https://support.google.com/webmasters/answer/17010575
  4. Google. Data anomalies in Search Console. Search Console Help. https://support.google.com/webmasters/answer/6211453
  5. Google. History for Ranking. Google Search Status Dashboard. https://status.search.google.com/products/rGHU1u87FJnkP6W2GwMi/history
  6. Google. How to move a site. Google Search Central. https://developers.google.com/search/docs/crawling-indexing/site-move-with-url-changes
  7. Google. Changing your hosting. Google Search Central. https://developers.google.com/search/docs/crawling-indexing/site-move-no-url-changes
  8. Google. Redirects and Google Search. Google Search Central. https://developers.google.com/search/docs/crawling-indexing/301-redirects
  9. Google. Block Search indexing with noindex. Google Search Central. https://developers.google.com/search/docs/crawling-indexing/block-indexing
  10. Google. Build and submit a sitemap. Google Search Central. https://developers.google.com/search/docs/crawling-indexing/sitemaps/build-sitemap
  11. Google. Understand the JavaScript SEO basics. Google Search Central. https://developers.google.com/search/docs/crawling-indexing/javascript/javascript-seo-basics
  12. Google. Understanding page experience in Google Search results. Google Search Central. https://developers.google.com/search/docs/appearance/page-experience
  13. Google. (2024). Interaction to Next Paint is officially a Core Web Vital. web.dev. https://web.dev/blog/inp-cwv-launch
  14. Google. Search Engine Optimization (SEO) Starter Guide. Google Search Central. https://developers.google.com/search/docs/fundamentals/seo-starter-guide
  15. Roger Montti. (2021). When Revamping a Site Can Negatively Impact Rankings. Search Engine Journal. https://www.searchenginejournal.com/revamping-website-search-impact/413039/
  16. SALT.agency. (2026). Only 27% of domain migrations recover in 90 days. SALT.agency. https://salt.agency/blog/27-of-domain-migrations-recover-in-90-days/
  17. John Mueller. (2022). Do URL structure changes affect SEO? Google Search Central (YouTube). https://www.youtube.com/watch?v=FHjVmi1tkEw
Credits

Hero illustration: an original Jardine Studio graphic made for this article, with no photograph or third-party artwork.

Want the drop traced to its cause?

The Website and Search Audit checks every accessible page up to 200, reviews Search Console and GA4 with your access, and ranks fixes with hours for each. CAD 800 for Canadian clients, USD 750 for everyone else.