Google’s May 2026 Core Update completed on June 2 and Google launched its first dedicated AI visibility reports. Two changes that simultaneously and change how marketing teams should be measuring organic performance from this week forward. If your organic traffic looked unusual in the last two weeks of May, you now have both a cause and a new measurement tool, but only if you know which one to use first.
Week in Brief
- Google confirmed the May 2026 Core Update finished rolling out on June 2, completing a 12-day run with notable volatility spikes on May 30, and the final 24 hours before completion.
- Google launched dedicated Search Generative AI performance reports in Search Console on June 3, inside AI Overviews, AI Mode, and generative Discover features. The declaration shows impressions only data, no click data, and are currently limited to a subset of properties. If you have access, establish your baseline now before drawing trend conclusions.
- Google’s back button hijacking spam policy enforcement begins June 15, giving site owners one more week to audit and remove any scripts that intercept or redirect browser back-button behaviour before manual spam actions and automated demotions begin. The manual check takes under five minutes and is worth doing before the enforcement window opens.
Google May 2026 Core Update completes after 12-day rollout (June 2, 2026)
Google confirmed via the Google Search Status Dashboard that the May 2026 Core Update finished rolling out on June 2, 2026 at 5:40 AM PDT, after starting on May 21. The rollout ran for approximately 12 days, identical in duration to the March 2026 Core Update. Semrush Sensor documented significant volatility spikes on May 30, and in the final 24 hours before completion. This is the second confirmed broad core update of 2026 and arrived only 43 days after the March update completed, a substantially shorter cadence than the three-to-four month spacing that has been typical in recent years.
Source: Semrush Sensor, SERP Volatility on Desktop, Data May, 2026 and June 2026
What this update means for B2B, ITES, and SaaS Marketing Team
Even high-authority domains experienced measurable visibility shifts, indicating that site authority alone is no longer a sufficient buffer. The pattern in early data points to Google tightening topical boundary enforcement. Sites with content that straddles multiple topic clusters are showing more movement than those with tightly defined topical authority.
Marketing Teams running broad informational content libraries that were built for keyword coverage rather than topical depth are the most exposed.
Action After May 2026 Core Update
The 2-3 day Search Console reporting lag means reliable before-and-after comparison data becomes available around June 9 at the earliest, treating any Search Console data pulled before that date as indicative, not conclusive.
From June 9 onwards, pull a Search Console comparison between the week ending May 20 and the week ending June 8, isolate your top 25 non-branded traffic pages, and check whether the pages showing drops are clustered around specific topic areas or spread across your whole domain.
Google launches dedicated AI visibility reports in Search Console
Google announced on June 3, 2026 via the Google Search Central Blog that dedicated Search Generative AI performance reports are now available in Search Console. The announcement was authored by Hillel Maoz, Search Ecosystem Engineering Manager, and Moshe Samet, Product Manager Lead for Search Console. The reports cover two surfaces; generative AI features within Google Search (including AI Overviews and AI Mode) and generative AI features within Discover. Data dimensions include impressions, pages, countries, devices, and dates. Critically, as confirmed in the blog, the reports provide impressions data only. Click data from AI responses is not included. The rollout is currently limited to a subset of websites, with broader global availability to follow after testing.
What this AI Visibility Report means for B2B, ITES, and SaaS
This is the first time ITES and SaaS SEO teams have had a native Google tool to distinguish AI-surface visibility from standard organic performance. Until now, any impression driven by an AI Overview or AI Mode response was bundled into the general performance report with no way to separate it. For SaaS companies with content appearing in AI Overviews, this new view will likely reveal that AI impression volume is higher than assumed and that the absence of click data from those impressions explains part of the gap between impression growth and traffic growth that many B2B teams have been trying to account for.
Next Action
Check whether your Search Console property has access to the new AI performance report this week, if it does, pull the impressions breakdown by page and note which URLs are generating AI surface impressions before drawing conclusions about CTR changes.
Google back button hijacking spam policy enforcement begins June 15
Google announced on April 13, 2026 via the Google Search Central Blog that back button hijacking has been classified as an explicit violation of its malicious practices policy. The practice, where a site interferes with the browser back button to prevent users returning to the previous page, instead pushing them to ads, recommendation pages, or navigation loops will trigger manual spam actions or automated ranking demotions from June 15, 2026 onwards.
Google gave site owners a two-month grace period between the announcement and enforcement, as confirmed in the original Google Search Central Blog post. This action is largely the outcome of a mismatch between user expectations and the actual outcome, leading to a negative and deceptive user experience.
Why Do Websites Hijack Back Button?
Websites use this technique for a few self-serving reasons:
More ad revenue: Ad monetization plugins push extra entries into the browser history to increase ad impressions by keeping users cycling through pages they have already seen, generating additional revenue for the site at the cost of a terrible user experience.
Inflate session metrics: The goal is almost always to inflate session duration metrics or squeeze one more ad impression out of someone who’s already trying to leave.
Exit-intent tools: Exit-intent tools detect when a user’s cursor moves toward the browser bar or address field and fire a popup or redirect before the user can leave the page. Many of these tools also hook directly into back button events as part of their retention logic.
Unintentional: Most websites practicing back button hijacking are not run by intentionally deceptive people. A large proportion of affected sites are using third-party tools and plugins that introduce the behavior without the site owner ever realizing it.
What enquiry does it warrant for B2B, ITES, and SaaS Companies
Most Business sites do not deliberately implement back button hijacking as a tactic, but it can be introduced unintentionally through third-party scripts, ad networks, exit-intent popups, or JavaScript frameworks that manipulate browser history for legitimate UX reasons. The risk is highest for ITES companies and SaaS platforms that run display monetisation alongside their content, or that use engagement tools that insert pages into browser history. The enforcement mechanism covers both manual spam actions and automated demotions, meaning some affected sites will receive formal notifications via Search Console while others will see ranking drops with no direct alert.
Action needed before Back Button Hijack Policy get enforced
Before June 15, open all of your pages as listed in sitemap. Press the browser back button on both desktop and mobile. If you land anywhere other than the Google results page, you have a problem to investigate. This check takes under two minutes per page and requires no paid tools.
What to Watch in Coming Weeks
Google’s new AI performance reports launched in Search Console this week for a small subset of properties. Watch for announcements of broader global availability in the coming days, once available, the data will require a baseline period before meaningful trend analysis is possible. Teams who gain access early are in a better position to establish that baseline.
What our SEO Team at White Bunnie has Experienced
Across the B2B SaaS client accounts we reviewed this week in the context of the May Core Update, we are seeing a consistent pattern; pages that lost visibility are concentrated in topic areas where the client’s content competes with the same cluster of queries across multiple pages, what we internally track as topic fragmentation.
Core update had a measurably different impact on SaaS platforms depending on whether they serve broad or niche markets. Semrush data tracking organic traffic across HubSpot, Monday, and Procore during the update window reveals a clear pattern. Horizontal SaaS platforms lost visibility faster, but recovered faster as well. While vertical SaaS showed the resilient character during update, but lost the ground after update is complete.
Beyond organic visibility, Semrush reported a decline in branded traffic for all three platforms. This signals a structural shift rather than a site-specific penalty, as Google’s AI Overviews and AI Mode increasingly intercept navigational and brand queries, fewer users are clicking through to websites even when searching for them by name.
Source: Domain overview data for Procore as obtained from Semrush
Source: Domain overview data for Hubspot as obtained from Semrush
Source: Domain overview data for Monday as obtained from Semrush
When to expect recovery after this Core Update
We are watching whether recovery follows the same consolidation pattern we saw after March. In the four accounts we tracked through the March update, consolidated pages recovered to pre-update levels within 30 days. That timeline should become testable from June 9.
