Google's generative AI performance report inside Search Console now appears on every property, Search Engine Roundtable reported on 11 August 2026. Google announced nothing. Barry Schwartz checked roughly 25 Search Console profiles he has access to and found the report present on all of them, a few weeks after Google expanded access to a limited set of properties.
The report sits under the main Performance report in Search Console as an expandable tab. It shows how a site performs in generative AI features on Google Search and Discover, split by impressions, pages, countries, devices and dates. It carries no click data and no query data.
What Search Engine Roundtable reported on 11 August
Search Engine Roundtable published the item at 5:46am ET on 11 August 2026, crediting a tip from Vijay Chauhan on X, with forum discussion also on X. The claim is narrow and worth repeating precisely. Barry Schwartz has access to about 25 Search Console profiles. The generative AI performance report was present on all of them. From that sample he concluded the rollout appears to have finished. The original write-up is at Search Engine Roundtable.
The feature itself is not new. Google Search Central introduced it in June 2026 in a post titled "Introducing Search Generative AI performance reports in Search Console", and at that point access covered a limited set of properties only. What changed between June and August, going by that check of 25 profiles, is coverage rather than function. The report does the same things it did in June. More people can now open it.
The five dimensions the generative AI report gives you
Google's report shows performance in generative AI features on Google Search and Discover across five dimensions. Each one answers a different question, and each one stops short in a different place.
Impressions
Impressions count how often URLs from your site appeared in generative AI features in Search and Discover. This is the headline number and the only volume metric in the report. It tells you that Google's AI surfaces are pulling your pages in. It does not tell you what position they appeared in, how prominently they were shown, or whether anyone read them.
Pages
The Pages dimension shows which URLs appeared within AI features. For a content site this is the most operationally useful view in the report, because it names the specific documents Google's generative surfaces are drawing on. A page that shows up here is being used. A page that does not show up here is either not being used or has not cleared whatever volume floor Google applies before it reports anything.
Countries
Countries gives visibility on a country basis. For a site that sells in one market this is a sanity check. For a bilingual site serving Thailand and an international audience at the same time, it is the dimension that separates the two audiences, because it is the only split in the report that maps to a market rather than to a page or a device.
Devices
Devices shows which devices people used when they saw your site. Google makes this one available for Search results only, so Discover impressions are not broken out by device. That asymmetry matters if Discover is a meaningful traffic source for you, since a device read on your AI-surface visibility will be partial by construction.
Dates
Dates supports hourly, daily, weekly and monthly granularity. Hourly is the notable part. Most reporting in Search Console has historically been daily at best, so hourly data on AI-feature impressions gives a much finer read on whether a spike lines up with a publication, a crawl, or an update on Google's side.
Set against each other, the five dimensions and their published limits look like this.
| Report dimension | What the source says it shows |
|---|---|
| Impressions | How often URLs from the site appeared in generative AI features in Search and Discover |
| Pages | Which URLs appeared within AI features |
| Countries | Visibility on a country basis |
| Devices | Which devices people used when seeing the site, available for Search results only |
| Dates | Hourly, daily, weekly and monthly granularity |
What the report does not contain, and why that caps your reporting
Two absences define this report. There is no click data. There is no query data. Both are stated plainly in the Search Engine Roundtable write-up of 11 August, and neither is a rendering delay or a permissions issue on your end.
No click data means you cannot calculate a click-through rate for AI surfaces, cannot attribute sessions to them inside Search Console, and cannot put a traffic number against an impressions number. You know Google showed your page. You do not know whether that produced a visit.
No query data means you cannot see what someone asked to trigger the appearance. In classic Search performance reporting, queries are what turn an impressions chart into a content decision, because they tell you which topic earned the visibility. Here, the Pages dimension is the closest substitute, and it answers a different question: which document, not which intent.
The mechanism this implies, and this is analysis rather than a Google statement, is that a monthly client report built on this data can honestly say that visibility in AI features rose or fell, and can name the pages involved and the countries involved. It cannot say that AI features drove traffic, sessions or revenue, because the data needed for that claim is not in the report. Anyone presenting AI-surface impressions next to a revenue line should label the two as unconnected, since Search Console does not connect them. Teams doing serious generative engine optimisation work now have a first-party impressions feed where before they had third-party estimates, which is a real gain and still not a conversion path.
This is one practitioner's observation, not a Google announcement
Worth stating plainly, because it will get repeated as though Google said it: Google has not announced that the generative AI performance report finished rolling out. The finding in the 11 August Search Engine Roundtable report is that Barry Schwartz looked at roughly 25 Search Console profiles he has access to and saw the report on each one.
Twenty-five profiles is a real check, and it is also a sample chosen by availability rather than at random. Sites in that set skew toward whatever Schwartz and his contacts work on. The honest reading is that the report is widely available, probably broadly enough to call general, and that Google has published no confirmation of that. If your property does not show the tab, the source gives you a documented reason to consider before you assume a bug, which is covered in the threshold section below.
Where to find the tab, and what to check first
The report is an expandable tab under the main Performance report in Search Console. Working through it in a useful order:
- Open Search Console for the property and go to the Performance report. The generative AI performance report expands from there rather than sitting in the left navigation as a separate item.
- Set the date range wide before you read anything. Access expanded over time, so a short window can look like a change in performance when it is a change in reporting coverage.
- Read Pages before Impressions. The total tells you the size of the surface. The page list tells you what Google is actually using, which is the part you can act on.
- Check Countries next and note the split between Thailand and everywhere else if you serve both. On a bilingual site the two audiences behave differently and the totals hide that.
- Look at Devices with the Search-only limitation in mind, and do not read the device split as a whole-site picture if Discover matters to you.
- Use hourly granularity in Dates only when you have a specific event to test against, such as a publication date. Hourly data on a low-volume property is mostly noise.
- Write down, before you present anything, that clicks and queries are absent. That sentence belongs in the report you hand over, not in a footnote.
The impressions threshold, and why some site owners still see nothing
Google states that the report will not appear if, in its wording, "Your site hasn't received enough impressions in generative AI features on Google Search." Search Engine Roundtable pointed to this as the explanation for site owners who still report not seeing the tab.
The source does not give a number. There is no published threshold, no stated window over which impressions are counted, and no confirmation of whether the floor is fixed or relative. Anyone quoting a specific figure for it is guessing.
What follows from the threshold existing at all, framed as analysis, is that absence of the report is not evidence of zero AI visibility. It is evidence of visibility below an unpublished floor, which is a different and much weaker statement. A small site that publishes in Thai for a domestic audience may well be appearing in AI features occasionally and still sit under whatever level Google requires before it opens the report. Treating a missing tab as proof that AI surfaces ignore you would be reading more into it than the source supports.
What this means for Thai marketers
The source says nothing about Thailand. There is no Thai data in the Search Engine Roundtable report, no country-level breakdown published, and no statement from Google about rollout by market. Everything in this section is reasoning from the reported facts, not reporting.
The Countries dimension is the part that earns attention here. A Thai business running an English site for regional buyers and a Thai site for the domestic market has, for the first time, a free first-party way to see which of those two is showing up in Google's AI features. That question used to be answerable only through paid third-party visibility tools or manual prompting, both of which infer rather than measure.
The threshold cuts the other way for smaller local sites. Domestic Thai sites with modest publishing volume are the most likely to sit under the floor and see nothing at all, which makes the report most available to the sites that needed it least. Nothing in the source confirms this pattern for Thailand specifically. It follows from a volume threshold applied to sites of different sizes.
For anyone building a Thai and English content programme, the practical shift is smaller than it sounds. The report changes what you can measure, not what you should publish. Solid SEO for the Thai market still comes down to pages that answer real questions well enough to be worth citing, and this report tells you afterwards whether Google's AI surfaces agreed.
Frequently asked questions
Is the generative AI report live on my Search Console property?
Probably, but Google has not confirmed a full rollout. Search Engine Roundtable reported on 11 August 2026 that Barry Schwartz found the report on roughly 25 profiles he has access to, which is the basis for calling the rollout complete. Open the Performance report in Search Console and look for the expandable tab. If it is not there, the documented reason is insufficient impressions in generative AI features, not a broken account.
Can I see which keywords triggered my pages in AI features?
No. The report contains no query data at all. It shows impressions, the pages that appeared, countries, devices for Search results only, and dates. Query-level reporting exists in the standard Search performance report for classic results, but it does not extend to the generative AI report.
Does the report show how much traffic AI features sent me?
No, and this is the sharpest limit on it. There is no click data in the report, so impressions cannot be converted into visits, sessions or a click-through rate. A client report built on this data can describe visibility and must stop short of describing traffic.
Is this available in Thailand?
The source did not say. Search Engine Roundtable made no statement about availability by country, and Google published no rollout notes by market. The report does include a Countries dimension, so a property that has the tab can see country-level visibility including Thailand, but whether the tab itself appears for a given property comes down to the impressions threshold rather than to location, as far as the source states.
Do I need to do anything to turn it on?
Nothing in the source suggests any setup step. The report appears as an expandable tab under the existing Performance report for properties that qualify. There is no opt-in described, no tag to install and no property setting to change.
Where this leaves measurement
For two years, reporting on visibility inside Google's AI surfaces meant paying a third party to estimate it or checking prompts by hand and hoping the sample held. A free first-party impressions feed, split by page and country, with hourly dates, is a better starting point than either. It is also a partial one, and the missing click and query columns are the reason it stays partial.
The reasonable posture is to open the report, record a baseline now, and hold the interpretation loosely until Google says something official about what it covers. If you want help reading your own AI-surface visibility against the search performance you already track, Relevant Audience works on exactly that overlap, from search visibility in Thailand through to how content earns citations in AI answers.
