{"id":2642,"date":"2026-07-17T06:31:13","date_gmt":"2026-07-17T06:31:13","guid":{"rendered":"https:\/\/dmarketertayeeb.com\/blog\/google-search-console-generative-ai-performance-report\/"},"modified":"2026-09-01T04:27:06","modified_gmt":"2026-09-01T04:27:06","slug":"google-search-console-generative-ai-performance-report","status":"publish","type":"post","link":"https:\/\/dmarketertayeeb.com\/blog\/google-search-console-generative-ai-performance-report\/","title":{"rendered":"Google Search Console AI Performance Reports: Global Rollout and the New Visibility Control"},"content":{"rendered":"\n

Canonical refresh \u00b7 reviewed 1 September 2026<\/p>\n\n\n\n

Google\u2019s Search documentation now says two important generative-search features are available worldwide as of 31 August 2026: the Search Console AI performance report and the control for appearing in Google\u2019s generative AI features. They answer different questions. The report helps a site owner inspect impressions from AI Overviews and AI Mode. The control lets a site owner choose whether pages are included in certain generative-AI surfaces.<\/p>\n\n\n\n

This is a refresh of DMT\u2019s Search Console generative-AI report guide<\/a>. The rollout wording is current documentation, but the data limits still matter: an AI impression is not a click, a query, a citation or a revenue event.<\/p>\n\n\n\n

What changed on 31 August<\/h2>\n\n\n\n

Google\u2019s Help Center added a note that the AI performance insights have rolled out to all websites worldwide. A separate page says the generative-AI visibility control has also rolled out worldwide. The old \u201cstaged subset\u201d wording in an earlier guide is now information debt and should be replaced with the current note while keeping the eligibility and data caveats.<\/p>\n\n\n\n

Google\u2019s pages are the source of truth for availability. Search Engine Land supplied the news discovery signal, but a trade summary should not override the current first-party help documentation.<\/p>\n\n\n\n

What the AI performance report shows<\/h2>\n\n\n\n

The report covers generative AI traffic in Google Search, including AI Overviews and AI Mode. Google says the data can be viewed by pages, countries, dates and devices. That lets a site owner ask practical questions: Which pages receive AI-feature impressions? Are impressions concentrated in one country or device? Did a content change precede a change in the trend?<\/p>\n\n\n\n

The report should be read as a directional visibility measure. It does not provide clicks, queries, the text of an AI answer, the websites cited in an answer or an attribution path. Google also describes the data as preliminary and subject to limitations. DMT\u2019s GEO guide<\/a> can help with the content implications, but it does not turn the report into a citation tracker.<\/p>\n\n\n\n

What the new generative-AI visibility control does<\/h2>\n\n\n\n

The separate control lets a site owner choose Include, Exclude or Inherit for generative-AI features. Google says it applies to AI Overviews, AI Mode and Generative AI in Discover. Excluding a page from those features affects traffic and impressions from those features, but not other Google Search ranking. The control is about appearance in generative surfaces; it is not an AI-training switch.<\/p>\n\n\n\n

Google distinguishes this control from Google-Extended and from a noindex directive. A noindex directive remains a separate indexing instruction. Changes to the generative-AI control may take one to two days or longer because of caching. Use the actual Search Console and documentation state when making a site decision.<\/p>\n\n\n\n

Report versus control<\/h2>\n\n\n\n
\n\n
Question<\/th>AI performance report<\/th>Generative-AI visibility control<\/th><\/tr><\/thead>\n
Purpose<\/td>Measure reported impressions from generative features<\/td>Choose inclusion or exclusion from selected generative features<\/td><\/tr>\n
Scope<\/td>Pages, countries, dates and devices in the report<\/td>AI Overviews, AI Mode and Generative AI in Discover<\/td><\/tr>\n
Shows clicks?<\/td>No, according to Google\u2019s limitations<\/td>No; it is a visibility setting<\/td><\/tr>\n
Controls training?<\/td>No<\/td>No; Google points to Google-Extended for that concern<\/td><\/tr>\n
Timing<\/td>Use the report\u2019s data and caveats<\/td>Changes can take 1\u20132 days or longer to propagate<\/td><\/tr>\n<\/tbody>\n<\/table><\/figure>\n\n\n\n

This distinction prevents a common error: seeing zero AI-feature impressions and concluding that a page is excluded, or excluding a page and assuming it will disappear from all organic Search. Neither conclusion follows from the documentation.<\/p>\n\n\n\n

A careful workflow for SEO teams<\/h2>\n\n\n\n
    \n
  1. Record the rollout state.<\/strong> Note the date you checked the documentation and Search Console.<\/li>\n
  2. Choose a comparison window.<\/strong> Compare like-for-like dates, countries, devices and pages.<\/li>\n
  3. Annotate page changes.<\/strong> Connect content, technical and internal-link edits to the observed trend without claiming causation.<\/li>\n
  4. Separate visibility from value.<\/strong> Pair AI impressions with Search clicks, conversions and assisted outcomes from your own analytics.<\/li>\n
  5. Use the control deliberately.<\/strong> Decide whether inclusion or exclusion matches the page\u2019s business and editorial intent.<\/li>\n
  6. Wait for propagation.<\/strong> Recheck after Google\u2019s stated 1\u20132-day-or-longer window before interpreting the setting.<\/li>\n<\/ol>\n\n\n\n

    DMT\u2019s search-intent guide<\/a> helps decide what a page should answer; the internal-linking guide<\/a> helps strengthen the site context around that answer. Neither guarantees inclusion in an AI feature.<\/p>\n\n\n\n

    What the report cannot tell you<\/h2>\n\n\n\n