Obenan Briefing · Signal
Google turned AI visibility into a control plane. A control plane is not a verdict.
On June 3, 2026, Google published Search Console generative AI performance reports for Search and Discover, plus an eligibility control with include, exclude, and inherit states, effective for the first cohort on June 17, 2026. AI visibility is now first-party, reportable, and governable. Include does not guarantee appearance, ranking, or recommendation. What the report counts is impressions, not clicks, rankings, recommendation quality, business impact, or whether the facts in the answer were correct.
Published June 14, 2026
The one line
Google now lets you report AI participation and set eligibility for generative AI features. That is a governance step worth taking. It still does not make include a guarantee of appearance, ranking, or recommendation, and it does not tell you whether the answer was good, whether your facts were right, or whether a customer acted. Those remain yours to verify.
- Published
- June 14, 2026
- Format
- Signal briefing
- Sources
- 5 public, primary
- Development
- Google, June 3, 2026
Public sources only. Observed facts and our interpretation are labeled separately.
The 60-second read
Three questions, three answers.
What Google shipped on June 3, why a first-party AI visibility layer matters to a multi-location brand, and the line between what the report counts and what it does not.
Google added generative AI performance reports and a control inside Search Console.
On June 3, 2026, Google published a Search Central post and public help docs describing a generative AI performance report for Search and a companion report for Discover, plus an eligibility control with include, exclude, and inherit states. The first cohort control takes effect on June 17, 2026, and the rollout starts with a subset of sites.
AI visibility becomes governable and board-reportable, not just observable.
For a multi-location brand, AI visibility moves from an outside estimate into the same first-party console that already tracks Search. You can report impressions for AI Overviews and AI Mode by page, country, device, and date, and set whether a property is included in or excluded from eligibility for those AI features. Inclusion still does not guarantee appearance, ranking, or recommendation.
Whether the appearance was good, correct, or earned a customer.
The report counts impressions. It does not count clicks, rank you inside an answer, measure recommendation quality, prove the facts the answer repeated were right, or show whether a booking or visit followed. Those stay on separate lanes.
The evidence, dated
One announcement, two reports, one control.
Google's public materials, in the order they describe the surface. Read together, they turn AI visibility into a first-party layer, and they are explicit about what that layer does not include.
Search Central announces generative AI performance reports
Google published a Search Central blog post introducing dedicated generative AI performance reports in Search Console for Search and for Discover, said the rollout starts with a subset of sites, and said it may add further metrics over time.
The Search report covers AI Overviews and AI Mode
The public help doc for the Search report says it covers AI Overviews and AI Mode, exposes impressions, pages, countries, devices, and dates, and excludes Search Labs experiments. It is an impressions surface, not a clicks surface.
A companion report covers Discover
A separate public help doc describes a generative AI performance report for Discover, listing generative AI impressions with page, country, and date dimensions for the Discover surface.
An eligibility control with a dated, limited rollout
The Search generative AI control supports include, exclude, and inherit from parent, and the help doc says the first cohort control takes effect on June 17, 2026. The include state preserves eligibility. It does not guarantee appearance, ranking, or recommendation. Search Engine Roundtable independently corroborated the limited rollout, the absence of click data, and the June 17 timing.
Four public materials, one development date. The pattern is a first-party AI visibility layer. The boundary is stated by Google itself: impressions and participation, not clicks, ranking, or outcomes.
What it measures, and what it does not
A control plane reports participation. It does not report the result.
The new reports make a genuine thing visible for the first time: whether your pages helped ground an answer in AI Overviews and AI Mode, by page, country, device, and date, with a companion view for Discover. For a brand that could previously only estimate this from the outside, that visibility is real progress.
What the report does not touch is everything that happens after the recorded impression. An impression is not a click, a ranking, a recommendation quality, a business outcome, or a guarantee that the facts the answer repeated were correct. Keeping those apart is the whole job.
Shows impressions, not clicks
An AI impression is a recorded impression in an AI Overview or AI Mode answer. It is not a click, a session, or a visit to your site.
Shows participation, not ranking
The report shows participation, while the control sets include, exclude, or inherit eligibility for those AI features. Include does not guarantee appearance, ranking, or recommendation, and the control is not a ranking signal in ordinary Search.
Shows pages, not recommendation quality
You can see which pages drew impressions. You cannot see whether the answer recommended you well, neutrally, or alongside a competitor.
Shows the surface, not the outcome
Impressions read the answer surface. Whether a booking, a call, or a visit followed is a business outcome the report does not measure.
Shows impressions, not correctness
An impression records participation in an AI answer. It does not confirm the hours, services, or policy the answer repeated were correct.
Shows a cohort, not the whole web
The reports and the control are rolling out to a subset of sites first, with the first cohort control effective June 17, 2026. Coverage is partial by design at launch.
Where reading it wrong costs you
Four ways an impressions chart misleads a board.
The risk is not the report. The risk is reading an impression count as if it were a business result. Four ways that goes wrong in the room where the quarter is judged.
A brand reports rising AI impressions to the board as demand, when an impression is a recorded AI participation event, not a customer who acted.
A portfolio reads flat impressions in one market as a visibility loss, when the report is still rolling out to a subset of properties and coverage is incomplete.
A team treats the generative AI control as a ranking lever, when Google states it does not change ordinary Search rankings outside the AI features it governs.
An operator celebrates strong AI impressions while the answer grounding them repeats hours a location changed last quarter, which the report still records as a healthy impression.
In each case the chart is accurate and the conclusion is wrong. Impressions measure recorded AI participation. They do not measure whether the customer was served correctly or acted at all.
Three proof lanes
Three lanes of proof. Google now supplies one of them.
Google has moved AI Search visibility from something you could only observe from the outside toward a first-party layer you can report on and set eligibility for. For a multi-location operator, that is a real governance step: AI visibility becomes measurable and board-reportable in the same console that already tracks Search.
But a first-party impressions report is one lane of proof, not the whole road. Treat it as the Google-owned participation layer, and keep two independent lanes beside it: what the live answer actually says about each location, and whether that visibility produced a business outcome.
First-party AI participation proof
Search Console now reports generative AI impressions for AI Overviews and AI Mode, with pages, countries, devices, and dates, plus a companion Discover report and an include, exclude, or inherit eligibility control. This lane is new, first-party, and inspectable.
Google-controlled
Live-surface presence proof
What an AI answer actually says about your locations across engines, on the day a customer asks, is an independent check. A first-party impression count does not replace looking at the live answer.
Independently verified
Business-impact proof
Whether AI visibility produced a booking, a call, a visit, or revenue is a business outcome measured in your own systems. No impressions report supplies it.
Operator-measured
Google now supplies the first lane. The second and third remain yours to verify.
The operator rail
What to do now, what to monitor, what not to assume.
A bounded action set for the people who will report AI visibility upward. Separate what Google now supplies from what still has to be verified independently.
Do now
- Inventory which web properties have Search Console access, and record whether the generative AI reports and the eligibility control are available for them yet.
- Separate first-party Google impression evidence from independent live-surface checks of what AI answers say about each location.
- Decide a default include, exclude, or inherit eligibility state per property before it takes effect, not after.
Monitor
- Cohort expansion beyond the first subset of sites, and how Search and Discover report coverage differs.
- The June 17, 2026 control behavior for the first cohort, and any metrics Google adds beyond impressions over time.
- Whether the live answer about each location stays correct as impressions move.
Do not assume
- Do not assume the generative AI control changes ordinary Google Search rankings. Google states it does not, outside the AI features it governs.
- Do not assume impressions equal traffic, clicks, or revenue.
- Do not assume a Search Console impression proves an AI assistant holds correct facts about your business.
The Obenan point of view
A control plane for visibility is not a verdict on it.
We welcome a first-party AI visibility layer inside the console operators already trust. For years the honest answer to whether a brand appeared in AI answers was an outside estimate. A reported impression for AI Overviews and AI Mode, paired with an eligibility control, is a genuine step toward governable, board-reportable AI visibility. It is not a guarantee of appearance, ranking, or recommendation.
But the report measures participation, not the things a CMO is ultimately judged on: whether the recommendation was good, whether the facts were right, and whether a customer acted. Our position is unchanged. The console can now show that an AI impression was recorded. Whether the answer about your business is correct, and whether it earned a customer, is still authored by the merchant truth behind it, and verified on the live surface, not inside an impressions chart.
Observed versus inferred
What we saw, what we concluded, what we are watching.
The release is observed fact, dated and publicly documented. The governance reading and the proof-lane conclusion are our interpretation. We keep them apart on purpose.
Observed
On June 3, 2026, Google published a Search Central blog post and public Search Console help documents describing dedicated generative AI performance reports for Search and Discover. The Search report covers AI Overviews and AI Mode and exposes impressions, pages, countries, devices, and dates while excluding Search Labs experiments. The Search generative AI eligibility control supports include, exclude, and inherit from parent, and the help doc states the first cohort control takes effect on June 17, 2026. Checked June 5, 2026.
Inferred
That for multi-location operators this turns AI visibility into a governance surface, not only a prompt-testing one, and that the new report is best read as one proof lane beside live-surface checks and business-outcome measurement. This is our reading, not a Google claim.
Watching
Cohort expansion, the June 17 control behavior, how Search and Discover coverage differs, and whether Google adds metrics beyond impressions. If clicks or outcome data arrive, the claim boundary changes and this reading is revisited.
What we are not claiming
Five things this briefing does not say.
The evidence is real and bounded. To keep it honest, here is what we deliberately do not claim.
- 01
We do not claim Obenan is part of Google, Google Search Console, AI Overviews, AI Mode, or Discover, or that Obenan controls whether a business appears in them.
- 02
We do not claim Search Console AI impressions are clicks, rankings, conversions, recommendation quality, business impact, or proof that the merchant facts in an answer are correct.
- 03
We do not claim any partnership, integration, certification, endorsement, membership, special access, or trusted-by status with Google. We read public releases as an outside observer.
- 04
We do not claim the generative AI control changes ordinary Google Search rankings outside the AI features it governs.
- 05
We do not claim the reports or the control are generally available. They are rolling out to a subset of sites, with the first cohort control effective June 17, 2026.
Keep reading
Where this fits.
Reporting AI visibility to the board this quarter?
If you need to separate what Google now reports from what still has to be verified on the live surface and proven in business outcomes, that boundary is the work we operate on.
Public sources only. Observed facts and our interpretation are labeled separately.
Sources
Primary, public sources only. The development date and the date we checked are kept separate so the chronology stays inspectable.
Primary sources
- 1.Google Search Central: generative AI performance reportsdevelopers.google.com · Published June 3, 2026 · Checked June 5, 2026
Primary source for the announcement of the Search and Discover generative AI performance reports.
- 2.Search Console Help: Generative AI performance report (Search)support.google.com · Public product documentation · Checked June 5, 2026
Primary source for the Search report dimensions, AI Overviews and AI Mode coverage, and Search Labs exclusion.
- 3.Search Console Help: Generative AI performance report (Discover)support.google.com · Public product documentation · Checked June 5, 2026
Primary source for the Discover generative AI impressions report and its dimensions.
- 4.Search Console Help: Search generative AI controlsupport.google.com · Public product documentation · Checked June 5, 2026
Primary source for the include, exclude, and inherit eligibility control and the June 17, 2026 first-cohort effective date.
- 5.Search Engine Roundtable: AI performance report and blocking controls (limited)seroundtable.com · Published June 3, 2026 · Checked June 5, 2026
Independent corroboration of the limited rollout, the absence of click data, and the June 17 timing.
Obenan is an independent observer of this release. Obenan is not part of Google, Google Search Console, or any Google AI surface, holds no partnership, integration, certification, or endorsement with Google, and this briefing reflects only public information available on the checked dates.