To check whether a Google update hit your site, match the date your Search Console clicks started falling against confirmed update rollout windows. If the drop begins inside a rollout and affects many pages at once, it is very likely algorithmic. If no update was running that day, the cause is usually technical, a manual action, click displacement from an AI Overview, seasonality, or a competitor. Enter your drop date below and the tool will check it against every confirmed update since 2020.
Free tool
Was my site hit by a Google update?
Enter the date your Search Console clicks started falling. The tool checks that date against every confirmed Google ranking update since 2020 and against the daily volatility record, then tells you what the pattern most likely means.
Tip: in Search Console set the range to 16 months and daily granularity, then find the first day the click line breaks from its normal pattern. That day, not the day you noticed.
Checking 50 confirmed updates. This tool matches dates. It cannot see your site, so treat the result as a starting point, not a diagnosis.
How to find your drop date
The date you enter matters more than anything else, and most people get it wrong by three to seven days because they use the day they noticed rather than the day it started.
- Open Search Console, go to Performance, and set the date range to the last 16 months. Why: Sixteen months is the maximum Search Console holds. Anything older is gone, which is why exporting early matters.
- Switch the chart to daily rather than weekly. Why: Weekly averaging hides the exact break point and can shift your date by several days.
- Find the first day the click line breaks from its normal weekly rhythm. Why: Traffic has a natural weekday and weekend shape. You are looking for the day that pattern stops holding, not the lowest point.
- If the decline is gradual with no clear break, you are probably looking at content decay or competitor gains rather than an update. Why: Algorithm updates produce a visible step. Decay produces a slope.
How to read the result
The tool matches dates. It cannot see your site, so a match is a strong lead rather than a diagnosis. Use this table to interpret what it returns.
| Result | What it means | Measurement (confirm it with this) | Next step |
|---|---|---|---|
| Your date falls inside a rollout | Likely algorithmic, if the drop is broad | Many page templates lost clicks together | Follow the recovery path for that update type |
| An update ended a few days before | Possible delayed effect | Loss concentrated in one page group | Check scope before acting |
| No update, volatility high | Unconfirmed adjustment | Sensor above 5 on the drop date | Wait two weeks, then work on the affected template |
| No update, volatility normal | Cause is on your side | Check indexing, manual actions, impressions | Work through the seven causes in order |
What this tool cannot tell you
Being honest about the limits is what makes the result useful.
- It cannot confirm causation. Why: A confirmed update running on your drop date is correlation. Sites drop during core updates for technical reasons too, and the fix is completely different.
- It cannot see whether you have a manual action. Why: Only your Search Console shows that, and it overrides everything else. Check the Manual Actions report before you accept an algorithmic explanation.
- It cannot detect AI Overview click loss. Why: That shows as flat impressions with falling clicks in your own data, which the tool has no access to.
- It only knows confirmed updates and this site’s volatility record. Why: Google ships most changes silently. An empty result means no confirmed update, not that nothing happened.
After you have your date
Whatever the tool returns, the sequence from here is the same. Read the first 48 hours checklist for what to export and what never to touch. If no update matched, work through the seven causes of a drop with no update in diagnostic order. To plan the timeline once you know the cause, see how long recovery takes. For the full confirmed history, open the live update tracker, and for today’s reading, the volatility sensor.
Frequently asked questions
How do I check if a Google update hit my site?
Find the first day your Search Console clicks fell, then match that date against confirmed update rollout windows. If the drop starts inside a rollout and covers many pages at once, it is very likely algorithmic. The tool on this page does the matching for you.
Is there a Google penalty checker tool?
No tool can detect an algorithmic demotion directly, because Google publishes no signal for it. Manual actions are the exception and appear in the Manual Actions report in your own Search Console. Everything else is diagnosed from the drop date, the scope and the update timeline.
What if my drop date does not match any update?
That is common and often good news. Site-side causes such as indexing faults, manual actions and click displacement are faster to fix than a core update demotion, which has to wait for the next core update to be reassessed.
How accurate are the update dates?
Dates from February 2023 onward come directly from the Google Search Status Dashboard and sync twice a day. Earlier dates come from Google announcements. Rollouts take 12 to 24 days, so effects can land on any day inside the window.
Got a match and want to know if it is really the cause?
Send your Search Console access or export. Within 48 hours I confirm whether that update is responsible, which page groups it hit, and what the fix sequence should be. Free, no obligation.
Get free recovery audit