You can tell a Google update hit your site when three things line up: your clicks fell inside a confirmed rollout window, the drop came as a slide or a step rather than a random wobble, and it hit groups of similar pages. If all three match, an update is the most likely cause. If one does not, look harder at other causes first.
Line up the drop date with confirmed update dates
Start with the date, because it rules out the most.
Open Google Search Console, go to Performance, then Search results. Set the date range to the last 16 months so you can see the long view, and look at clicks and impressions together. Find the first day of the fall. Not the day you noticed it, the day it started.
Then open the Google Search Status Dashboard. Google lists its confirmed ranking updates there, including core updates and spam updates, each with a start date and a completion date. If your drop begins inside one of those windows, write it down. If it begins on a day with nothing listed, keep that in mind as you check the other causes below.
Google changes Search constantly, and only a small share of those changes are announced. Our short answer on how often Google updates its algorithm explains why a drop can still be algorithmic on a quiet day, and why the confirmed dates are still the best place to begin.
Check the shape of the drop
The shape of the line on the chart is evidence.
A slide across the rollout
Core updates roll out over days to a couple of weeks. Sites hit by them often lose ground in stages across the rollout, then settle at a new, lower level. That shape is a slide.
A cliff on one day
A drop that falls off a cliff overnight, to almost nothing, rarely comes from an update. It usually means a noindex tag went live, robots.txt blocked the site, the server started returning errors, or tracking broke. Check the Pages report under Indexing and the URL Inspection tool before anything else.
A slow fade over months
A gradual decline that started long before any update is more often content decay, competitors getting stronger, or demand falling. An update may speed it up, but it did not start it.
Find which pages and queries lost
In the Performance report, use Compare to set the weeks after the rollout against the same length of time before it. Then open the Pages tab and sort by the difference in clicks.
Look for a pattern in the losers. Updates tend to hit groups:
- All your blog posts, but not your product pages.
- One topic, such as reviews or how to content.
- Pages written quickly at volume during one period.
- Pages where forums or expert sites now rank above you.
Then switch to the Queries tab. Search a few of your biggest lost queries yourself and see who ranks now. The pages that replaced you are the best clue to what the update rewarded.
Rule out the lookalikes
Several causes produce a chart that looks like an update hit. This table shows how to tell them apart.
| What you see | Points to an update | Points to something else |
|---|---|---|
| Drop starts inside a confirmed rollout window | Yes | Drop starts on the day you launched a redesign or migration |
| Groups of similar pages lose | Yes | Every page falls by the same amount on one day |
| Average position falls on lost queries | Yes | Position holds but impressions fall, which suggests lower demand or a seasonal dip |
| Pages still indexed and crawlable | Yes | Pages drop out of the index or show errors in the Pages report |
| No message in Manual actions | Yes | A manual action is listed, which is a penalty, not an update |
| Same dip does not repeat in past years | Yes | The same dip appears at the same time every year |
Also check your own release history. A theme change, new plugin, CMS upgrade or URL change in the same week as an update makes the evidence harder to read, and it is often the real cause.
What to do if an update did hit your site
If the evidence points to a core update, do not rush to undo changes or file requests. A core update is not a penalty. There is no notice to answer and nothing to reconsider.
The work is to understand why the pages that replaced you are rated higher, then close that gap. That usually means improving or merging weak pages, removing content with no value, and making it clear who wrote your pages and why they can be trusted. Our guide to recovering from helpful content signals in core updates covers the content side in detail. The full process we use is on the core update recovery page.
Write down what you find as you go: drop date, update name, the page groups that lost, and who replaced you. That record is the starting point for any fix, whether you do it yourself or hand it to someone.
When to call for help
Call for help when the evidence does not line up cleanly, when several causes overlap, or when the drop is costing you leads and sales every day. Mixed signals are common: an update and a redesign in the same month, or a drop that started before the rollout and got worse during it. Untangling that is forensic work.
Send us the drop date and Search Console access and we will tell you what the evidence says in a free SEO triage. If it is a core update, our core update recovery work picks up from there. If it is not, we will say so.
FAQ
Questions owners ask us
Can a Google update hit only some of my pages?
Yes, and it usually does. Core updates tend to hit groups of similar pages, such as one template, one topic area or one type of content. A drop spread evenly across every page on one day points more often to a technical fault or a tracking change.
My traffic dropped but my rankings look fine. Was it an update?
Maybe not. If average position held but clicks fell, check impressions and click through rate. Fewer impressions can mean lower demand or a seasonal dip. Lower click through rate at the same position can mean new results features, such as AI Overviews, are taking clicks above you.
How long after an update should I wait before checking?
You can start checking as soon as the drop shows, but judge it after the rollout is marked complete on the Google Search Status Dashboard. Rankings often move around during a rollout. Comparing the full weeks after completion with the weeks before gives you a cleaner read.
Get started