The May 2026 Google Core Update: What People Are Seeing, and What to Do Now That the Data Is Clean

Google's second core update of the year is in the books. The May 2026 core update started rolling out on May 21 and Google marked it complete on June 2 — just under twelve days. If your organic traffic moved anywhere in that window, this update is the most likely reason, and as of this week you can finally analyze it properly. Google's own guidance is to wait at least a full week after completion before reading your Search Console data, which puts the first clean comparison window at roughly June 9. In other words: now.

Here's what the SEO community has been reporting, what I think is noise, and what's actually worth doing this week.

What people are seeing

The shorthand going around is that March was quiet and May was real. The March 2026 core update came and went with a collective shrug from most practitioners — modest movement, few dramatic swings. May has been a different story. The volatility trackers lit up almost immediately after the announcement, and the people who watch this stuff full time have described impact across verticals and across countries, in both directions.

What made this rollout harder to read than most is that it didn't move in one smooth wave. There were at least three distinct volatility spikes: the first weekend after launch around May 23, another sharp burst the following weekend around May 30, and a final surge on June 2 — literally hours before Google declared the rollout complete. If you took a screenshot of your rankings on May 27 and called it your "after" picture, you measured the middle of a fight, not the outcome.

The other narrative thread you've probably seen: the timing. The update launched two days after Google I/O, where Google announced major AI-powered Search changes. Plenty of people have connected those dots publicly. Google has not confirmed any relationship between the two, and for diagnostic purposes I'd treat it as background noise — your Search Console data doesn't care which narrative is true.

What this update is not

Every core update produces the same wave of panic, so it's worth restating the fundamentals before you touch anything.

• It's not a penalty. A core update is Google broadly re-scoring which content best satisfies queries. There's no manual action to remove, no specific violation to confess to. If you dropped, something else is now being judged a better answer for queries you used to win.
• Single-day comparisons will lie to you. Because rankings shifted at multiple points during the rollout, before-and-after snapshots taken inside the window are unreliable. Compare full weeks: the week before May 21 against the week starting around June 9.
• The "X category got destroyed" hot takes are too simple. Every update produces a story about an entire class of sites getting wiped out. The reality at the page level is always messier — sites in the same category moved in opposite directions. Score your own pages; don't inherit someone else's diagnosis.

What to actually do this week

The clean window just opened, so this is the week the work starts. The sequence I run on every account after a core update:

• Pull the page-level diff. In Search Console, compare the pre-rollout week against the post-June-9 week at the page and query level — not site-wide averages, which hide everything interesting. You're looking for which specific URLs lost clicks, impressions, or position, and on which queries.
• Separate direct hits from collateral movement. Some pages dropped because Google reassessed them; others slipped a position because a competitor gained one. The fix is different in each case, and lumping them together wastes your effort.
• Study what now outranks you. For the queries that matter, look honestly at the results that moved above you and ask which result a real searcher would be more satisfied by. That comparison usually tells you more than any tool.
• Improve before you delete. Pruning content is the last resort, reserved for pages that were built for crawlers rather than people. For everything else, the answer is making the page genuinely better for the query — and then being patient.
• Set expectations on recovery. Some movement can happen between core updates, but meaningful recoveries often don't show up until the next one. That's not a reason to wait to do the work; it's a reason to start now.

The bottom line

The May 2026 core update was a real one — bigger than March, choppy through the rollout, and broad in its reach. But the playbook hasn't changed: wait for clean data, diagnose at the page level, fix what genuinely deserves fixing, and don't take dramatic action based on someone else's screenshot. The sites that handle core updates well are the ones that treat them as a measurement exercise first and an emergency second.