Traffic Dropped After a Google Update? What to Check First

A sudden drop in Google traffic usually arrives with a theory attached. Someone saw a post about a core update, the dates look close, and the team starts rewriting pages the same afternoon. Sometimes that’s right. Often the real cause is a tag that stopped firing, a page template that picked up a noindex, or a season that comes around every year.

This is the order we work through when a business calls us after a drop. It takes a few hours, it needs only Search Console and a browser, and it tells you whether you’re dealing with an update at all.

Is it really the update?

Google lists six broad causes of traffic drops: algorithm updates, technical problems, security issues, spam problems, changes in search interest, and site moves (Google Search Central). An update is only one of them, and it’s the hardest to act on. So check the others first. Each one has a clear test.

Step 1: Match the date to Google’s update list

Google posts every confirmed ranking update, with its start and end dates, on the Google Search Status Dashboard. Open Search Console, go to Performance, and find the first day clicks fell. Then check whether that day falls inside a rollout.

If your drop started three weeks before the update, the update didn’t cause it. If it started on day two of a core update and kept sliding while the rollout ran, it’s a real suspect. Keep it on the list and move on.

Don’t judge the update while it’s still rolling out. Rankings move around every day until it ends. Google suggests waiting at least a full week after an update finishes, then comparing a week after it with a week before (Google Search Central).

Step 2: Rule out tracking and reporting problems

Before you trust any chart, make sure the numbers are real. Two quick checks:

• Compare your two sources. If Analytics shows a drop and Search Console doesn’t, the problem is almost always tracking: a tag removed in a redesign, a consent banner that blocks it, a filter someone added. Search traffic didn’t change; your measuring did.
• Check Search Console’s data anomalies page. Google notes reporting glitches there, and a missing day or two in the chart can look like a crash.

Also ask what changed on the site that week. A redesign, a new plugin, a move to a new platform or a CDN switch is a better suspect than any update. If you moved or renamed pages, read our case study on recovering after a site migration.

Step 3: Check the technical basics

Technical drops are the good news: they’re usually fast to fix, and traffic comes back once Google recrawls. In Search Console, look at:

• Page indexing. A jump in “Excluded by noindex”, “Blocked by robots.txt” or “Not found (404)” around the drop date points straight at the cause.
• Crawl stats (under Settings). A spike in server errors or a fall in pages crawled per day means Google is struggling to reach the site.
• URL Inspection on two or three pages that lost the most. It shows whether Google can fetch the page and which version it indexed.

Then open your robots.txt and check it hasn’t started blocking sections that should rank. Our free robots.txt validator tests any URL against your rules. If you changed redirects recently, the .htaccess analyzer finds redirect chains and loops. For a deeper look at how Google spends its time on your site, see our guide to crawl budget.

Step 4: Check for a manual action or a hack

Two reports in Search Console settle this in a minute. Manual actions shows whether a reviewer at Google has penalized the site, and why. Security issues shows whether Google found malware, hacked pages or spam injected into the site. Both come with a request-review button once you’ve fixed the problem. If either report has something in it, that’s your cause, whatever the update calendar says.

Step 5: Read the shape of the drop

Set the Performance report to the last 16 months. The shape of the line says a lot about the cause.

An overnight cliff points to something technical, a manual action or broken tracking. Updates roll out over days, so they rarely cut traffic in one step.

A step down during a rollout is the classic update pattern. Rankings slip over several days and settle when the rollout ends.

The same dip every year is demand. Compare with the same months last year, and check the topic in Google Trends. If searches for your topic fell everywhere, your rankings didn’t.

Clicks falling while impressions hold is the pattern many sites see now. Your pages still rank, but fewer people click. Look at average position: if it held steady while the click-through rate fell, the cause is on the results page, not on your site. AI Overviews and other answers above the links take clicks that used to reach you.

That last pattern needs a different answer from an update. You can’t rank your way back above an AI Overview, but you can be one of the sources it cites. Our AI Visibility Checker shows whether AI assistants mention your business and which sites they cite instead.

Step 6: Find which pages and searches lost

If the update is still the main suspect, find out exactly what it hit. In Performance, compare the four weeks after the rollout ended with the four weeks before it started. Then:

• Sort pages by the change in clicks. See whether the loss is spread across the whole site, limited to one section or template, or concentrated on a handful of pages.
• Do the same for queries. Losing a few broad, high-volume searches is a different problem from losing hundreds of specific ones.
• Look at the pages that now outrank you for your top lost searches. What do they answer that your page doesn’t? Is the information newer, more specific, or from someone with first-hand experience?

This comparison is tedious by hand. Our free GSC Data Interpreter does it from a Search Console export: lost clicks by page and query, when the drop started, and what to look at first.

If the update was the cause: what actually helps

A core update doesn’t target sites for breaking rules. Google re-ranks results based on which pages it now judges most helpful, and some pages move down because others moved up. Google says there’s no need for drastic action if a drop is small, and that it’s best to avoid quick fixes in favor of changes that last (Google Search Central).

What lasts, in our experience:

• Improve the pages that lost, not the whole site. Start with the pages that lost the most clicks on searches that bring you business.
• Answer the question sooner and better. Put the direct answer at the top, add the detail the pages above you have, and show real examples from your own work.
• Merge pages that compete with each other. Two weak pages on the same question often both drop. One strong page usually does better. Our guide to content pruning and refreshes covers how to decide.
• Make it clear who’s behind the content. A named author with real experience, an about page, and sources for your claims.

Recovery takes time. Google says some changes take effect within days, while others can take several months for its systems to confirm, and sometimes improvement only shows at the next core update. For a real example of the process, read how Manya Group recovered after a major Google update.

Your checklist for this week

If you’d rather run the checks yourself first, our guide on how to read a technical SEO audit report helps you make sense of what you find.

FAQs

How long after a Google core update can traffic recover?

It varies. Google says some changes show within days, while others can take several months, and sometimes improvement only appears at the next core update. Technical drops recover faster: usually within days or weeks of the fix, once Google recrawls the pages.

How do I know if a drop is caused by AI Overviews and not lost rankings?

Compare average position with click-through rate in Search Console for the same searches. If position held steady while impressions stayed level and clicks fell, your ranking didn’t change. Something on the results page, often an AI Overview, is taking the clicks.

Should I disavow links after a core update?

Usually not. Core updates are about how helpful Google judges your pages to be, not about links you’ve built. Disavowing is meant for a manual action over unnatural links, or for a large set of paid or spammy links you know about.

Should I delete pages that lost traffic?

Not right away. First check whether the page answers a search people still make. If it does, improve it or merge it into a stronger page and redirect it. Delete only pages that serve no one, and redirect them where a better page exists.

Can I recover before the next core update?

Yes. Google re-evaluates pages continuously, so improvements can count before the next core update. Big shifts are more likely to show at an update, which is why it’s worth starting the fixes now.

Sources

• Debugging drops in Google Search traffic, Google Search Central
• Google Search’s core updates and your website, Google Search Central
• Google Search Status Dashboard: ranking updates
• Google users are less likely to click on links when an AI summary appears in the results, Pew Research Center, July 2025