Google Core Update History (2020-2026): Every Update and What It Changed

Why a core update history is worth keeping

A core update is not a one-off event you survive and forget; it is one move in a six-year pattern, and the sites that read the pattern recover faster than the sites that react to each update in isolation.

Google has confirmed 21 broad core updates since January 2020, plus the first Discover-only core update in February 2026. Each was a recalibration of how Google's interconnected ranking systems weigh quality and relevance, not a targeted penalty. Read together, they show a clear arc: the systems matured, the standalone Helpful Content System dissolved into core in March 2024, and the cadence has tightened from months between updates to weeks.

This page is the index. The complete timeline is below, followed by the six patterns that recur across every update and a short framework for using this history the next time your rankings move. Each update name links to a full dispatch with that update's verbatim announcement, named winners and losers, and recovery notes.

Every confirmed core update, 2020 to 2026

Broad core updates are listed chronologically with their rollout window and the single change each one is best remembered for. Dates are from Google's Search Status Dashboard and Search Central announcements.

Six patterns that repeat across every core update

Read end to end, the six-year record keeps teaching the same lessons. These are the patterns we hold every client site against before we touch anything after an update.

• Quality is re-ranked everywhere, not just YMYL: from the January 2020 hit on UK car-buying sites onward, every core update has moved commercial, editorial, and reference verticals, not only health and finance.
• Movement is not locked in on day one: December 2020 and May 2022 both saw week-one winners give the gains back by completion. Intra-rollout positions are not the verdict.
• Recovery is a multi-update arc: from June and July 2021 onward, Google has shipped updates that partly reverse the previous one. A drop is judged again at the next update, not frozen until then.
• The aggregator and UGC pendulum swings: March 2023 demoted aggregators, August 2023 elevated Reddit and forums, and March 2025 began unwinding that forum boost. The direction reverses; the underlying question of who adds original value does not.
• March 2024 changed the rules permanently: folding the Helpful Content System into core means there is no separate helpful-content event to wait for, and assessment shifted toward the page and site as a whole.
• Stacked windows break single-cause diagnosis: September 2022, October 2023, November 2024, and December 2024 all overlapped other updates or enforcement, so attributing a move to the core update alone was often wrong.

How to use this history when your rankings move

The point of a timeline is not nostalgia; it is a faster, calmer diagnosis the next time you are hit. The sequence we run is the same one these updates taught.

1. Confirm it was the update. Check the dates against the Search Status Dashboard and rule out technical and tracking causes first. Our diagnosis framework walks through it.
2. Check what else was rolling out. The stacked-window pattern above means a concurrent spam update or enforcement action may be the real cause; do not assume the core update alone moved you.
3. Wait for the rollout to settle. Day-one positions are noise. Judge after completion, when the picture stabilizes.
4. Improve quality site-wide, then hold. Since March 2024 the assessment is holistic. Follow the 30-day recovery plan and resist mass deletion.
5. Expect the verdict at a later update. Recovery typically lands on a subsequent core update, and with the tightening cadence the next one is rarely far away.

Where the cadence is heading

The clearest 2026 signal is speed. Google historically spaced core updates months apart; the March and May 2026 updates landed about six weeks apart, which collapses the quiet window sites once used to recover and be re-assessed. When updates arrive that close together, recovery work from one update is re-graded by the next before it has been credited.

The practical takeaway is to stop treating updates as discrete events and treat quality as a standing posture. We unpack that overlap in the May 2026 core update dispatch, which is the most recent entry in this history and the live example of the pattern. This page is updated as each new core update completes.