How to tell which Google update hit your site: a 5-step method
Match a Search Console drop to confirmed Google update dates using 7-day windows, search types and a manual actions check, then rule out overlaps.
Upload your Search Console clicks and see every Google-confirmed update on the same chart, with a week-before and week-after comparison for each. Free.
Runs entirely in your browser. Nothing you enter is uploaded, logged or stored.
Add a Dates.csv export to see your clicks against 40 confirmed updates.
| Update | Week before | Week after | Change | Overlaps |
|---|
Week before: the 7 days before the start. Week after: days 7 to 13 after completion, as Google advises. Timing is not cause: check seasonality and site changes too. Nothing you upload leaves this page.
When traffic drops, the first question is whether a Google update did it. This Google algorithm update checker puts your daily clicks and every Google-confirmed update on one chart, then measures each update the way Google suggests. It runs in your browser; your data stays with you.
The overlay. Your daily clicks from Search Console, with each confirmed update’s rollout shaded from its start date to its completion date. The dates come from our Google Algorithm Updates timeline, where every entry links to the Google page that confirms it.
The comparison. Google’s core update guidance says to wait at least a full week after a rollout finishes, then compare traffic with a period before the update began. The tool takes the average daily clicks over the 7 days before the start and over days 7 to 13 after completion, and reports the percentage change.
The overlaps. Google often runs updates close together. When another update falls inside the compared span, the tool names it, because the change cannot then be pinned on one update.
In the Performance report, choose a date range, then Export. Google’s export help lists Google Sheets, Excel and CSV; the CSV download is a zip file. Since February 2020 the performance export includes every table, Dates among them. Dates.csv holds one row per day with clicks, which is all this tool needs.
A drop that lines up with an update is correlation, not cause. Seasonality, a site migration, a tracking change or a competitor can all move clicks in the same week. Google also notes that pages losing rank are not necessarily bad; other pages may serve the searcher better. Use the result to decide which update page to read, then follow the guidance there.
Compare traffic from a full week that starts a week after the rollout finished with the week before it began, as Google recommends. If clicks moved sharply between those windows and nothing else changed on your site, the update is a likely cause. This tool runs that comparison for every confirmed update in your data.
Google's core update guidance says to wait at least a full week after a rollout completes before analysing, then compare with a period before it started. Rankings still move during a rollout, so the rollout window itself is not a fair comparison.
Every update Google confirmed on its Search Status Dashboard, which covers November 2021 onward. Older updates in our timeline predate any Search Console export, which keeps 16 months, and unconfirmed volatility has no official dates.
No. The file is read and analysed in your browser and is never sent to a server. Closing the page discards it.
One of the two seven-day windows falls outside your export or has a missing day. Export a longer date range that covers a week before the start and two weeks after the completion.
Match a Search Console drop to confirmed Google update dates using 7-day windows, search types and a manual actions check, then rule out overlaps.
Eight confirmed updates, with Google's own start dates and rollout durations, and what the pattern says about when to judge a decline in your data.
Google started the September 2026 spam update on 24 September. It is the fourth spam update of 2026, 37 days after August's, with a two-week window.
Google's own recovery steps after a core update: wait a week, compare the right dates, size the drop, self-assess and avoid quick fixes.