2026 has been defined by clustering rather than volume. Three separate updates landed inside five weeks in February and March, two core updates ran within ten weeks of each other, and three spam updates arrived in a single year for the first time. The list below is generated from the Google Search Status Dashboard and refreshes twice a day, so it is current rather than a snapshot of when this page was written.
February 2026 Discover update
Feb 5, 2026 to Feb 27, 2026 · 22 daysSpamMarch 2026 spam update
Mar 24, 2026 to Mar 25, 2026 · 1 dayCoreMarch 2026 core update
Mar 27, 2026 to Apr 8, 2026 · 12 daysCoreMay 2026 core update
May 21, 2026 to Jun 2, 2026 · 12 daysSpamJune 2026 spam update
Jun 24, 2026 to Jun 26, 2026 · 2 daysSpamAugust 2026 spam update
Aug 18, 2026 to Aug 21, 2026 · 3 daysSynced with the Google Search Status Dashboard twice a day. Click any update for its dates, official rollout log and recovery path.
What made 2026 different
Three structural shifts, each of which changes how a drop this year should be diagnosed.
- Discover became its own system. Why: The February 2026 Discover core update was the first time Google adjusted feed recommendations without touching search rankings. Publishers can now lose Discover traffic while every search ranking holds, and nothing in the web Search report explains it.
- Updates arrived in clusters. Why: The Discover update ended 27 February, the March spam update ran 24 to 25 March, and the March core update began 27 March. A drop anywhere in that window could belong to any of the three, and the fixes have nothing in common.
- Spam enforcement accelerated. Why: Three spam updates in one year, more than the whole of 2025, and rollouts as short as 19 hours. Faster enforcement means date matching has to be more precise, not less.
The five weeks that caused the most confusion
February and March produced more misdiagnoses than any period since March 2024, purely because of how close the events were.
| Drop date | Most likely cause | Measurement (how to confirm) | What it needs |
|---|---|---|---|
| 5 to 27 February | Discover core update | Discover report fell, web search held | Editorial change: headlines, original reporting |
| 24 to 25 March | March spam update | Loss concentrated on pages matching a spam policy | Remove the policy violation |
| 26 March | Ambiguous | Check scope carefully before assuming either | Diagnose before acting |
| 27 March to 8 April | March core update | Broad quality reassessment across templates | Content quality and composition work |
The March spam update completed in 19 hours and 30 minutes, the fastest confirmed rollout on record. That precision helps: a drop on 24 or 25 March belongs to the spam update, while 27 March onward almost certainly belongs to the core update. Run your date through the date checker rather than eyeballing it.
The May core update
Widely reported as heavier than March, the May 2026 core update ran 21 May to 2 June with impact visible about 48 hours in, which is unusually fast. Three patterns came through consistently: topical authority outperformed broad coverage, first-hand experience separated winners from losers, and AI Overview citation share stopped tracking organic position.
One data caveat worth remembering if you are analysing that period. A confirmed Search Console reporting bug began on 21 May, the same day the update launched, showing zero or heavily reduced link counts for many sites. That was a reporting fault, not a loss of links, and it had nothing to do with the core update.
The volatility Google never confirmed
The confirmed list is only part of 2026. The week of 8 to 12 June produced some of the loudest community reports of the year, with no confirmed update at all, and more than a dozen volatility trackers stayed flat throughout because the event fell outside their samples.
That is the defining feature of the current era rather than an anomaly. Google confirmed four updates in 2025 against eleven in 2021, while measured volatility stayed high. If your drop does not match anything on this page, that is normal, and the seven causes of a drop with no update covers where to look next.
Diagnosing a 2026 drop
- Separate Discover from Search before anything else. Why: Switch Search type to Discover in Search Console. Reported together, a Discover collapse looks like a general decline and sends you to the wrong fix entirely.
- Get the exact break date, not the day you noticed. Why: With three updates inside five weeks, being three days out points at the wrong one. The drop analyzer finds it from your export.
- Check whether impressions held while clicks fell. Why: That is click displacement rather than a demotion, and no core update recovery will address it.
- Establish scope by page template. Why: Site-wide points at core, one template points at a narrower system, a handful of pages points at competitors. The page scope analyzer settles it.
For how long recovery takes once you know the cause, see how long recovery takes, and for where the current wait sits against history, the core update countdown.
Frequently asked questions
How many Google algorithm updates were there in 2026?
The confirmed count is shown live at the top of this page and updates automatically. It includes broad core updates, spam updates and the February Discover core update. Google also ships thousands of unannounced changes each year that never appear on any list.
What was the biggest Google update of 2026?
By reported impact, the May 2026 core update, widely described as heavier than March. By structural significance, the February Discover core update, because it was the first time Google adjusted Discover independently of search ranking.
Why were there three updates in five weeks?
Google has not explained the clustering. What matters practically is that a drop between early February and mid-April could belong to the Discover update, the March spam update or the March core update, and each needs a different response.
My traffic dropped in 2026 but nothing on this list matches. What now?
That is common. Google confirms only a fraction of what it ships, and June 2026 saw heavy reported volatility with no confirmation at all. Check the volatility sensor for your date, then work through the seven causes of a drop with no confirmed update.
Is this list kept up to date?
Yes, automatically. It syncs with the Google Search Status Dashboard twice a day, so a newly confirmed update appears within hours and the statistics recalculate themselves.
Dropped somewhere in February to April 2026?
Three updates landed inside five weeks and they need completely different fixes, so a three-day error in your drop date sends the whole project the wrong way. Send your Search Console access and within 48 hours I will tell you which one hit you. Free, no obligation.
Get free recovery audit