Google's ranking systems change all the time, but the biggest broad changes are announced as core updates. A useful tracker helps SEO teams answer a practical question: did the site change at the same time as a confirmed Google update, or are we looking at something else?
What is a Google core update?
Google describes core updates as broad changes to Search systems. They are not designed to target a specific site or page. The right way to investigate a change is to compare what happened on the site with what changed in Google's systems and with other causes such as seasonality or technical problems.
Which Google core updates are in the current tracker?
The Google Search Status Dashboard lists March 2026, May 2026 and December 2025 core updates, along with other ranking and spam updates. The dashboard also records rollout duration, which makes it the best source for the event timeline.
How should you use the update dates?
Use the rollout window as a correlation period, not as proof of causation. Ranking changes can appear at different times across queries, countries and page types. Compare daily data first, then weekly aggregates after the rollout has finished.
What should you check before blaming a core update?
Check Search Console, Analytics, indexing, manual actions, recent deployments, migrations, redirects, content changes and demand trends. Google recommends checking the Search Console data-anomalies documentation because reporting problems can create misleading drops or spikes.
Why is a core update not the same as a penalty?
A core update is a broad ranking-system change. Google says pages that perform worse after a core update are not necessarily violating a policy. Think in terms of relevance, usefulness and competition rather than a simple penalty score.
What does a good SEO update tracker record?
Record update name, product area, start date, completion date, source, site sections affected, important traffic changes and your own site changes. Keep official facts separate from your observations so the record remains useful later.
Should you wait for the next core update before improving a page?
No. Google says its systems are updated continuously, including smaller core changes that are not separately announced. Improvements can therefore produce gains without waiting for another named core update.
How should you analyze a suspected update hit?
Start with page groups, not the site average. Find URLs with the largest percentage changes, identify shared templates or intents, and compare them with pages that improved. For another current Search change, see our guide to Google's regional Search experience documentation.
What is the safest response after a ranking drop?
Do not mass-delete or rewrite pages on day one. Give the rollout time to finish, confirm the change is real, assess the affected page groups, and then improve the parts that are genuinely weak.
Related ToolBoxKart guides
For AI-search visibility, read the Google AI Search Visibility Report. For Search Console AI metrics, see the Search Console AI Performance Report Guide. For regional Search changes, read Google Regional Search Experience: What Changed. For content strategy after a ranking shift, use SEO Content Refresh vs New Page.