The May core update lands, Search Console learns AI, and Google offers an opt-out.

The week of 1–7 June 2026 was the week the May core update stopped being a live event and became a scoreboard. Google confirmed the rollout complete on Tuesday 2 June — after one final spike of volatility — and then, two days later, quietly changed the AI visibility game: Search Console got its first AI performance reports and, for the first time ever, a switch that pulls a site out of AI Overviews without touching its rankings. Add Google's new guidance on optimising for AI search, a Gutenberg release that pushes responsive block styling forward, and a fresh batch of baseline CSS, and this was one of the most consequential quiet weeks of the year for anyone who owns a business website.

1. The May 2026 core update is done — winners and losers are now official

What happened

Google announced on Tuesday 2 June that the May 2026 core update — its second core update of the year, launched 21 May — had finished rolling out after roughly 12 days. The rollout was anything but smooth: significant ranking volatility hit the first weekend, more the second weekend, and one final spike landed on 2 June itself, hours before Google called it done. Community consensus is that this one felt bigger than the March 2026 core update.

How to read your own scoreboard

• Compare stable-to-stable. In Search Console, compare the fortnight before 21 May against the days after 2 June. Mid-rollout numbers are noise; ignore them.
• Segment by page template. Core updates rarely hit a site evenly. If service pages held but blog posts dropped, that's a content-quality verdict, not a site-wide penalty.
• If you gained, protect it. Winners should document what's working — page structure, depth, internal linking — and extend it before the next update redistributes attention again.
• If you lost, resist quick fixes. Core update recovery means genuinely improving the pages that fell, and Google typically reassesses at future updates. There is no fast lane.

2. Search Console gets AI performance reports — your first real AI visibility data

What happened

On 3 June, Google announced Search Generative AI performance reports in Search Console: dedicated reporting on how your content appears in AI Mode and AI Overviews, covering impressions, pages, countries, devices and dates — though notably no click data. The rollout began with a subset of properties.

This matters because until now, AI visibility was guesswork. Businesses knew AI answers were absorbing informational queries, but had no first-party data on whether their own pages were being surfaced. Now the black box has a window — and every claim an agency makes about "AI SEO" can finally be checked against a Google report.

What to do the day you get access

• Baseline immediately. Screenshot or export the first full week of AI impressions so you can measure every future change against it.
• Find your cited pages. The pages earning AI impressions are your templates — study their heading structure, answer placement and schema, then replicate.
• Watch the impressions-without-clicks gap. If AI surfaces show your content but classic clicks fall, your pages are informing the journey without capturing it — a conversion optimization problem as much as a search one.

3. An official opt-out of AI Overviews — launched UK-first under regulator pressure

The second half of the 3 June announcement was historic in its own quiet way: a Search Console toggle to block your content from AI Mode and AI Overviews while remaining fully indexed and ranked in classic results. Google launched it UK-first under a binding order from the UK's competition regulator, taking effect from 17 June.

For most business websites, the interesting part isn't the toggle — it's the precedent. Regulators have now forced a separation between "being in Google" and "being in Google's AI answers," and that split will shape how the rest of the world's search markets evolve. Should you flip it? Almost certainly not if you sell services or products: AI surfaces are where buying research increasingly starts, and being the cited answer is the new position one. The opt-out is built for publishers whose content is the product, not for sites that want the visit.

4. Google publishes guidance on optimising for AI search — and a warning

Rounding out an AI-heavy week, the June 2026 Google Webmaster Report (published 4 June) collected two notable Google positions: fresh official guidance on how to optimise for AI search, and a blunt warning against manipulating or buying citations to game AI search features. A grey market for "guaranteed AI mentions" had been forming for months; Google just put it on notice, the same way it did paid links fifteen years ago.

The legitimate playbook Google describes is unfashionably technical: clear structure, direct answers, real authority signals, and clean crawlable markup. In other words, AI visibility is largely decided at the html web development layer — heading hierarchy, semantic elements, structured data, and pages that render fast without a JavaScript excavation. You can't bolt that on after launch, and you can't buy it from a citation broker.

5. Platform notes: Gutenberg 23.3, and a new baseline for CSS

WordPress: Gutenberg 23.3 ships 3 June

Gutenberg 23.3 landed on 3 June, extending the responsive global block styles introduced in 23.2 with layout responsive styles, plus revisions improvements and accessibility fixes to Font Library navigation. With WordPress 7.0 "Armstrong" barely two weeks old and early 7.1 testing already underway, the direction is clear: per-viewport styling is moving into core, which will shrink the pile of custom breakpoint CSS most WordPress builds carry.

Browsers: web.dev's May roundup lands, and the floor rises

web.dev's monthly web platform roundup (published 29 May, digested by most dev teams this week) confirmed a strong batch across Chrome 148, Firefox 151 and Safari 26.5:

• Native lazy loading for <video> and <audio> via loading="lazy" in Chrome 148 — a free performance win on media-heavy pages.
• The :open pseudo-class reached Baseline with Safari 26.5 — style open/closed states of <details>, <dialog> and pickers without JavaScript.
• Name-only container queries became Baseline in Chrome 148, and container style queries for custom properties arrived in Firefox 151 — component-level responsiveness keeps getting simpler.
• Document Picture-in-Picture came to Firefox desktop, and the Web Serial API expanded to Firefox 151 and Chrome on Android.

The pattern across all of it: features that used to demand JavaScript are becoming plain markup and CSS. Less script means faster pages, and faster pages hold up better in exactly the algorithmic weather described in item one. The same logic applies in ecommerce — theme bloat is the silent conversion killer, which is why good Shopify development partners treat every new native browser feature as a chance to delete a library, not add one.

What this week means for your website strategy

Three threads worth pulling together if you own a business website or are scoping a redesign:

• Quality verdicts are now delivered twice a year, minimum. Two core updates in five months means "build it right and leave it" is dead. Design and development decisions — structure, speed, depth — are ongoing ranking inputs, and resilience to updates is a build-quality feature you specify up front.
• The AI channel just became measurable. With Search Console reporting AI impressions, "we think AI is sending traffic" turns into a line on a dashboard. Any web project starting now should be scoped for AI citability — quotable sections, direct answers, schema — as a first-class requirement.
• The platform keeps handing you performance. Between Gutenberg's responsive styles and the new Baseline CSS, the cost of a fast, genuinely responsive site keeps falling — if your build actually uses it. Whether you're searching "web developers near me" or evaluating a specialist shopify developer partner remotely, the sharpest filter is the same: ask to see how their last three builds scored on Core Web Vitals, and how much JavaScript they shipped to do it.

Frequently asked questions

How do I recover from the May 2026 Google core update?

Confirm causation first: the update ran 21 May to 2 June, so compare pre-21-May rankings with the post-2-June settled picture. Then audit the pages that fell against what now outranks them — depth, first-hand expertise, and how directly they satisfy the query. Recovery is a genuine quality rebuild, typically reassessed at future core updates, not a metadata tweak.

Was the ranking volatility after 2 June a new update?

No confirmed one. SEO chatter about fresh swings started Friday 5 June and ran through the weekend of 6–7 June, even though most tracking tools stayed fairly calm. The likeliest explanation is post-update settling. Give it a full week of data before you act on anything.

What does the new Search Console AI performance report actually show?

Impressions, pages, countries, devices and dates for your appearances in AI Mode and AI Overviews — but no clicks. It began rolling out to a subset of properties from 3 June. When your site gets it, export a baseline week immediately.

Should I use the new toggle to block my content from AI Overviews?

Almost certainly not if you're a service or ecommerce business — AI answers are where more buying research now starts, and being cited is the new position one. The opt-out, launched UK-first under a regulator's order, exists mainly for publishers whose content is the product itself.

Do the new CSS features from this week matter for my business site?

Yes, where they replace JavaScript. Lazy-loading media natively, styling <details> and dialogs with :open, and simpler container queries all mean lighter, faster pages — and page speed feeds both rankings and conversion rate. Adopt what deletes code; skip the novelty.

The takeaway

One week, one theme: accountability arrived. The core update delivered its verdict on page quality, Search Console started publishing receipts for AI visibility, and Google drew a line against buying your way into AI citations. The websites positioned to win from here are the ones where design, development and SEO were never separate line items — because everything Google measured this week was decided at build time.