The May 2026 core update finished after 11 days, its second this year

Google’s May 2026 broad core update is finished. The Search Status Dashboard records the rollout as starting 21 May and completing 2 June, 11 days and 21 hours, the second core update Google has confirmed in 2026 after March. That is inside the roughly two-week window Google typically gives for a broad core update, and short enough that a decline showing up after 2 June belongs to something else.

What a core update does#

A core update re-scores the index against a revised sense of relevance and quality. Nothing is flagged and nothing is penalized in the way a spam action penalizes a specific practice. A page can lose visibility without anything new having gone wrong on it, and the only real recovery path runs through the content itself, not through a fix-and-resubmit cycle.

What independent analysis found#

Glenn Gabe of GSQi, who tracks core updates across a large set of client and public sites, called May “much more like a typical core update” than March, which he described as comparatively mild. His review found early, severe volatility concentrated in health, finance and gambling, the kind of YMYL sectors that tend to move hardest and fastest once a core update starts landing. Sites that had already lost visibility in January 2026’s action against listicle and self-serving commodity content mostly stayed down through May, and some declined further. Gabe also documented a case of a site scaling lower-quality content and AI-generated translations across multiple languages, which saw a significant ranking drop once the update reached it.

How to check your own data#

Mark the two dates on your own series first. 21 May and 2 June are the edges; movement that starts well before the first or persists well past the second is a different problem wearing the update’s name.

Segment by content type before concluding anything. Gabe’s cases moved at the level of a content programme, not a whole site. A YMYL section swinging while the rest of the site holds steady is consistent with what this update did elsewhere.

Check whether the page was already depressed. A page that lost visibility in an earlier update and never recovered is not new evidence about May; it is old evidence still sitting in the data.

Why we care#

If your traffic moved between 21 May and 2 June, the diagnostic question is whether the pages that moved sit in a sector this update visibly touched, or carry a content pattern - AI translation at scale, thin commodity pages, YMYL claims without backing - that shows up in the case reviews above. That framing separates a real core-update effect from a coincidence that happened to land in the same eleven days, and it is the same test to apply the next time a core update rolls through.