Google confirmed on June 2 that the May 2026 broad core update has finished rolling out. The update began May 21 at 8:40 AM PDT and completed June 2 at 5:40 AM PDT — a rollout of just under 12 days. It is Google’s second confirmed core update of 2026.

What Happened

The rollout was volatile throughout. Third-party tracking tools showed elevated ranking movement at multiple points: a significant spike the first Saturday (May 23), another on May 30, and a final surge on June 2 as the update wrapped. The overall pattern was unusual — heavy, sustained volatility rather than the typical front-loaded impact.

SEO consultant Glenn Gabe, who tracks core update impact closely, described it as “powerful” and “much more like a typical core update” — a direct contrast to the March 2026 update, which he called “meh.” Impact was confirmed across multiple verticals and countries.

Search Engine Land’s report confirms that Google has marked the update as complete on the Search Status Dashboard as of June 2.

What It Means for Your Clients

The rankings you see today reflect the post-update landscape. If a client’s site moved significantly during May 21–June 2, that movement is now baked in — this is not a transitional state.

One critical detail from Search Engine Land: June 9 is the earliest clean comparison window in Search Console. You need at least one full week of settled post-rollout data before a meaningful before/after comparison is possible. Making major strategic calls based on data pulled before June 9 will give you a noisy read.

Sites that gained rankings likely saw Google re-weighting in favour of demonstrated content quality, strong E-E-A-T signals, and sound technical fundamentals. Sites that lost should not panic-publish or mass-edit — core update recoveries are built on sustained quality improvement, not reactive content changes.

What to Do Now

This week:

  • Pull rankings for your top 20–30 target keywords across all active clients. Flag significant movers in both directions.
  • Check Search Console impressions and clicks for the May 21–June 2 window. Sharp drops during that period are update-related, not technical.
  • Do not make strategic decisions based on comparison data yet. Wait until after June 9 for a clean post-update baseline.

After June 9:

  • Run a proper before/after comparison: the 7 days ending May 20 against the 7 days starting June 9.
  • For sites that lost traffic: audit at the page level for thin content, low-E-E-A-T signals, high impressions / low CTR pages, and pages with duplicate or templated content. Core update recoveries are whole-site quality problems, not single-page fixes.
  • For sites that gained: document what those pages have in common. That’s your quality baseline to replicate across weaker pages.
  • For sites that didn’t move: record that stability. It’s a useful data point for clients asking about update exposure.

Do not do:

  • Assume the update is still rolling out. It is confirmed complete.
  • Make bulk content changes before you have clean data.
  • Confuse update-related volatility with a manual action or a technical issue — check for manual actions in Search Console separately if traffic dropped sharply and did not recover at all.

Primary Sources