Restore / Research / Update Tracking Update Tracking Algorithm update tracker. The dashboard for the confirmed updates, the third-party trackers for the SERP volatility window.
The Google Search Status Dashboard is the authoritative source for confirmed updates: Core Updates, Spam Updates, Reviews Updates, Helpful Content Updates. Third-party trackers (Semrush Sensor, Mozcast, RankRanger, SISTRIX) detect SERP volatility daily and surface unannounced rollouts. Correlate the traffic-loss date against both surfaces to name the cause.
The authoritative source: Google Search Status Dashboard
Google publishes confirmed algorithm updates on the Search Status Dashboard. Each entry names the update type (Core Update, Spam Update, Reviews Update, Helpful Content Update), the rollout start date, and the rollout end date when it has completed. This is the source of truth for the named-update calendar; everything downstream of an algorithmic-demotion diagnostic reads against this surface.
Reading the dashboard end-to-end takes minutes. The diagnostic asks two questions of it: did Google roll out a named update in a window that brackets the traffic-loss date, and if so, which update class was it. The answers route the remediation to the per-system recovery surface. Panda-class signature → Panda recovery. Helpful-Content-class signature → Helpful Content recovery. Reviews-Update-class signature → Reviews System recovery. Penguin-class signature → Penguin recovery.
Third-party trackers for the unannounced and the scope read
Semrush Sensor. Daily SERP volatility score across vertical query samples (Health, Finance, Real Estate, e-commerce, etc.). Spikes flag windows where rankings moved widely across the index even when no named update has been confirmed. Useful for catching the unannounced rollout before the dashboard surfaces it.
Mozcast. Daily SERP volatility score with historical trend lines. Reads the same surface from a different sampling base; cross-checking Mozcast against Semrush Sensor reduces single-tracker noise.
RankRanger. SERP volatility plus rank-change distribution per vertical. Useful for confirming whether a movement window hit one vertical or several.
SISTRIX. European tracker with strong .de / .uk coverage and a per-domain visibility index that detects sitewide impact at the domain level. Useful when the traffic loss correlates with a sitewide signal redistribution rather than a per-query movement.
The trackers detect volatility; they do not name the update. Once a window is identified, the dashboard read or Google Search Liaison's announcements name the cause. The third-party surface is for catching the window and reading the scope; the dashboard is for the confirmation.
Recent named updates the diagnostic reads against
August 18, 2022 launched the Helpful Content System as a continuous sitewide weighted classifier. The original signature was sitewide-even decay over a single classifier evaluation cycle.
March 5, 2024 Core Update retired the single Helpful Content System classifier and redistributed its signals across multiple core ranking systems. The same window formalized three spam policies: scaled-content-abuse, site-reputation-abuse, and expired-domain-abuse. Recovery from a post-March-2024 HCS-pattern demotion no longer relies on a single classifier rollback; it requires broad improvements across multiple quality signals the core systems evaluate continuously.
May 5, 2024 began enforcement for site-reputation abuse (parasite SEO). The pattern is third-party commercial content published on a highly authoritative domain without close oversight.
September 2024 began enforcement for expired-domain abuse. The pattern is purchasing domains with historical authority and repurposing them for low-quality unrelated content.
Subsequent Core Updates have continued the post-HCS-redistribution pattern. The diagnostic in front of any algorithmic-correlation read runs at forensic SEO audit; the parent hub on the named-update surface is Google search updates; the practice that runs the correlation work is SEO Penalty Removal.
What operators ask when correlating a traffic drop to a specific update.
- 01.
What is the authoritative source for confirmed Google updates?
The Google Search Status Dashboard. Google publishes confirmed updates there with start and end dates and the named update type (Core Update, Spam Update, Reviews Update, Helpful Content Update). Third-party trackers detect SERP volatility but the dashboard is the source of truth for whether a named update has been rolled out and what it was.
- 02.
Which third-party trackers do operators read against?
Semrush Sensor, Mozcast, RankRanger, and SISTRIX track SERP volatility daily across query samples and surface spikes that correlate with named updates. They are useful for catching unannounced rollouts and for confirming the scope of an announced update across verticals. They do not replace the Search Status Dashboard for the named-update confirmation.
- 03.
What named updates have rolled out recently?
March 5, 2024 Core Update retired the single Helpful Content System classifier and redistributed its signals across multiple core ranking systems. The same window formalized the scaled-content-abuse, site-reputation-abuse, and expired-domain-abuse spam policies. Site-reputation-abuse enforcement began May 5, 2024. Expired-domain-abuse enforcement followed in September 2024. Subsequent Core Updates have continued the post-HCS-redistribution pattern.
- 04.
How do I correlate my traffic drop to a specific update?
Pull the exact date or date range of the traffic loss. Line the date up against the Google Search Status Dashboard for any update window that brackets the loss. Cross-check the third-party trackers for SERP volatility spikes around the same dates. Read the signature pattern in the data: HCS-pattern demotions hit the site evenly; Panda-pattern demotions hit specific thin-content sections; Reviews System-pattern demotions hit review-content pages; Penguin-pattern demotions discount link signals at URL level. The forensic SEO audit runs the correlation end to end.
- 05.
What if the dashboard shows no named update around my traffic-loss date?
Two common causes. First, an unannounced rollout or signal redistribution that the dashboard does not flag. The third-party trackers can surface the SERP volatility window instead. Second, a manual action that lands without an algorithmic correlate; the Search Console Manual Actions report names the category. Why did my rankings drop covers the broader diagnostic framework.
If your traffic drop correlates with a named-update window and you need the per-system signature read, book the diagnostic.
We line the loss date up against the Google Search Status Dashboard and the third-party trackers, read the signature pattern in the data per Google system, separate algorithmic correlation from manual action, and scope the remediation to the correct per-system workflow.