Google Traffic Drop Checker: When It Fell, How, and Which Update Was Rolling Out
Connect your Search Console: the biggest fall in 16 months of daily clicks, its date and shape, the same weeks a year earlier, branded vs non-branded, and Google's confirmed updates at the time.
Your own Search Console, read in your browser; a date match with an update is shown as a coincidence, never as proof, and seasonality and brand demand are checked before any update is blamed.
Needs your Search Console (read-only)
How to use this tool
This tool reads sixteen months of your daily Google clicks from your own Search Console, in your browser, and finds the biggest fall between two 28-day windows. It dates the fall, measures it, names its shape (a cliff in a few days, a step, a slow slide, a seasonal repeat), compares the same weeks a year earlier, checks whether the fall is in branded searches, and lists Google's confirmed ranking updates that were rolling out at the time.
- Click Connect Search Console and allow read-only access in the Google popup.
- Pick the property.
- Click Find the drop and read the date, the shape and the checks under it.
- Sign in to RankWhy for the full diagnosis: the pages and sections that lost, pages that left the index and who ranks above you now.
What it checks
- The day the fall starts and the clicks in the 28 days before and after.
- Its shape: cliff, step, slide or seasonal, and whether rankings, searches or click-through fell.
- The same weeks a year earlier, and the searches without your brand term over the same windows.
- Google's confirmed updates from three days before the fall to a week after a rollout ended.
Questions
Was my site penalised?
A manual action is the only penalty Google names, and it appears only in the Manual actions report of Search Console; no tool can read it, because Google offers no API for it. Algorithmic falls after core or spam updates are not penalties in Google's terms; Google says sites that drop after a core update "aren't necessarily 'bad'".
The fall matches an update. Is that the cause?
Maybe. A date match is a coincidence in time, which is why the tool checks seasonality and branded demand first. RankWhy's full diagnosis adds the pages and sections that carry the loss, index state and who replaced you, which is what tells a core update from a technical fault.
Is anything stored?
Not here: the token and the data stay in your browser. Signed in, the Search Console import stores the same series so the Why dropped tab can explain it.