Loading today’s stories
Build1 distinct publisher3 min readPublished
Google's generative AI performance reports went worldwide on August 31, 2026, so web teams get a first-party count of URL appearances in AI Overviews, AI Mode and Discover, sliced by page, country, device and date.
The Engineer · Build desk
product
Google's new Preferred Sources button hands publishers the recruiting job2 distinct publishers
build
Search Console starts reporting on posts you do not host, if you can verify them1 distinct publisher
build
Search Console measures verified social posts on the same four metrics as owned pages1 distinct publisher
build
Under 30% citation overlap between engines makes pooled AI visibility scores unbuyable1 distinct publisher
Compiled by The EngineerSomething wrong?How this is made
An AI impression fires when a URL appears in a generative AI feature, and per the dev.to write-up of Google's materials that is the whole definition [6]. There is no query column. The companion piece is explicit that the reports emphasise impressions and surface-level reporting rather than a full per-query account of every AI answer appearance [9]. So the thing your content lead wants to know, which prompts surfaced the page, is not in this dataset. What is in it is page-first: you can see which URLs carry the exposure and whether that concentration moves by market [4].
Two conditions have to hold before an aggregate trend across those surfaces means anything. The impression has to count the same way in an AI Overview, in AI Mode, and in Discover; the second dev.to piece says an impression's meaning depends on the AI surface where it was counted [10], which means a rising total can be a mix shift rather than growth. And appearance has to stay separated from outcome. The first piece calls the reports evidence of appearance, not a blanket measure of search performance, and warns they do not explain why Google selected a URL or guarantee traffic or rankings [11]. The second adds that the data does not prove a relationship to leads or sales, and that analytics still has to cover behaviour after the visit [12].
Here is where the two accounts diverge. One account says the AI reports do not merge AI appearances into a traditional-search metric and sit apart from core Performance data [7]. The other describes the change as a dedicated reporting lens within the Performance report for AI-driven surfaces [8]. Those imply different arithmetic. If it is a lens, your existing Performance impressions already contain the AI appearances, and your organic trend has been absorbing them quietly. If it is a separate surface, you can add the two. Both articles are on dev.to and both point back at Google's own Search Central announcement and Search Console documentation [16], so read the doc before you wire the dashboard, not the summary.
The 90-day window is short for a number that will end up in a board deck. Google introduced the reports on June 3, 2026 to a subset of sites for testing and feedback [2] and made them global on August 31, 2026 [3], an 89-day pilot [14]. More practically, a site that was not in the test group has no history before the global date, so the first honest year-over-year comparison is available on August 31, 2027 [15]. Everything before that is within-year, which means seasonality and your own publishing cadence are confounded with any AI-visibility story you tell.
Low counts are a legitimate result here, and the first piece says so [13]. That is worth stating in advance, because a near-empty report will otherwise be read as an instrumentation bug. The design detail I like is the pairing: the same console that counts the exposure also carries a separate generative AI control for publishers who want to manage whether their content appears in these features [5]. Measure the volume, then decide whether to withhold it. Screenshots never let you sequence it that way.
Ranked by verification strength, evidence, and original report placement.
Google's generative AI performance reports in Search Console give site owners a separate view of when their URLs appear in Google Search generative AI features, including AI Overviews and AI Mode, as well as in Discover.
Google introduced the reports on June 3, 2026, initially to a subset of sites for testing and feedback.
According to Google's Search Central announcement, the reporting was subsequently made available globally on August 31, 2026.
The reports include impressions (appearances of URLs in generative AI features), pages, countries, devices where available for Search results, and dates with hourly, daily, weekly or monthly granularity as described in Google's reporting materials.
An AI impression occurs when a URL appears in a generative AI feature.
The primary research emphasises impressions and surface-level reporting, not a full per-query account of every AI answer appearance; a report can show a trend without explaining every query or answer composition.
Distinct publishers with included, body-backed reporting in this cluster.
dev.to
2 articles · August 31, 2026
Follow any of these and your For You feed starts watching them — no settings page required.
Evidence-backed comparisons of source perspectives and observed adoption signals. Read the methodology
Which Builder, Operator, and Investor concerns the observed source mix emphasized—not a truth score.
Evidence, demonstrated adoption, hype gap, incentives, and confidence are assessed independently, each on its own current evidence. How these are measured.
One author, two posts, no primary document
Every checkable detail in this story — the June 3 pilot, the August 31 worldwide switch, the impressions-pages-countries-devices-dates lineup, the opt-out and its propagation lag — reaches us through two dev.to posts by the same writer, filed fifteen minutes apart. Google's Search Central announcement and Search Console documentation are named repeatedly and quoted nowhere, so nothing in our coverage functions as a second pair of eyes. What keeps this from the floor is falsifiability rather than sourcing: any site owner can open Search Console and confirm or kill the claims in a minute.
Shipped everywhere, measured nowhere
Distribution is the strong half: after 89 days with a test group, the reports went to sites worldwide on August 31, 2026, which means availability is effectively universal by decree rather than by uptake. The other half is missing entirely. Not one impression figure, screenshot or named site appears in either write-up, and dev.to itself concedes low counts are likely early on — so we can confirm the feature landed and say nothing about whether teams have opened it.
Hedged prose, sales-shaped framing
Give the posts credit: they repeatedly say an impression is not a ranking, not a conversion and not a query log, which is more discipline than most coverage of anything with 'AI' in the name. The stretch is structural. A reporting change gets presented as a measurement practice your organisation needs installed, and the installer is on sale in the final paragraph — so the tone is cautious while the shape of the piece still oversells the significance of a new tab.
Both posts end at the same checkout
Two write-ups, one author, and both terminate in a Scalevise offer — an AI Visibility scan in one, the GEO Checker in the other. That does not make the feature description wrong; it is largely a restatement of Google's own notes. It does explain the emphasis: baselines, reporting cadence and 'pages worth improving' are billable, whereas what AI Overviews do to a publisher's clicks is not, and goes unmentioned.
Plausible, unverified, single-voiced
The substance is mundane enough to believe — a platform vendor shipping a reporting view, described in terms that match how such views usually work. What we lack is any independent voice, and the one internal inconsistency we can see concerns exactly the detail a builder needs first: whether this data sits inside the Performance report or beside it. Treat the timeline and dimension list as a working assumption to verify in the product, not as settled record.