Google Finally Gives Publishers an AI-Visibility Dashboard—But Not the Data They Want

Google’s official website-owner announcement confirms that eligible AI search activity can appear in Search Console. Search Console now offers a generative AI performance report to a subset of properties. It separates generative-AI impressions from conventional search, but combines AI Overviews and AI Mode.

The short answer: AI activity without AI-specific attribution

Search Console can indicate that a page earned impressions or clicks somewhere within Google’s Web search experience. The generative AI report distinguishes AI-feature impressions from conventional results, but it does not distinguish AI Overviews from AI Mode. That distinction matters because each surface presents sources differently and can produce a different relationship between visibility and traffic.

How Search Console counts AI Mode interactions

Google applies its existing Search Console methodology: eligible outbound interactions contribute to clicks, displayed links can contribute to impressions, and position follows Google’s standard calculation. Pages and queries remain available subject to the usual privacy limits. What publishers cannot inspect is the generated response, the passage Google retrieved, the source panel in which a link appeared, or whether a citation influenced a later conversion.

Conventional search roughly follows a query-result-click path. An answer engine may fan one prompt into several searches, retrieve passages from multiple pages, resolve entities, assemble an answer, and choose a small set of citations. Search Console exposes outcome metrics but not that chain of decisions.

Blending can conceal opposing trends. Conventional impressions might rise while AI click-through rate falls, or a page might influence generated answers without receiving a visit. A July 22, 2025 Pew Research Center analysis found that users clicked an AI-summary source link in only 1% of visits with an AI summary; this is independent research, not Google first-party reporting.

Average position is also less diagnostic in a generated answer. A link could appear in an initial citation, a carousel, an expandable panel, or a follow-up response. One blended position number cannot reveal which presentation occurred or why one source displaced another.

The highest-priority addition is a surface filter separating conventional results, AI Overviews, and AI Mode. Within each surface, publishers need citation impressions, clicks, click-through rate, cited URLs, citation placement, and source-panel expansion. These measures would distinguish exposure from selection and selection from traffic.

• Citation reporting: show which URL was cited, how frequently, where it appeared, and whether it generated an interaction.
• Demand reporting: group prompts into anonymized topics and disclose broad fan-out query categories rather than personal prompt logs.
• Passage diagnostics: identify the section selected to ground an answer and whether another passage replaced it over time.
• Freshness signals: include recent crawl or fetch timestamps so teams can diagnose stale answer material.
• Entity context: surface unresolved names or relationships that may prevent reliable source understanding and selection.

This is not a request for personally identifiable prompt histories. Aggregated topic clusters, minimum-volume thresholds, delayed reporting, and inclusion rates would support decisions without exposing individual users. Publishers could then decide whether to refresh evidence, clarify an entity, improve crawl access, or restructure a passage around a precise question.

Google has legitimate reasons to proceed carefully. Conversational prompts can contain health, financial, location, or identity details. AI Mode may create hidden fan-out searches, and answer composition can change between similar prompts. Reporting every intermediate query or retrieved passage could expose private information, produce sparse datasets, or imply a level of stability the system does not have.

Generated interfaces also make familiar measurements ambiguous. “Position” may refer to a citation beside a claim, an item in a source carousel, or a link visible only after expansion. Prematurely exposing every interface detail could encourage optimization for volatile layouts instead of durable retrieval principles such as accessibility, evidence, freshness, and entity clarity.

Technical complexity is not a complete excuse for opacity, however. Search Console already applies privacy protections, anonymization, aggregation, thresholds, and delayed reporting. Those safeguards support a cautious AI report with topic clusters and minimum volumes. They do not require Google to combine every discovery surface into a single number that publishers cannot diagnose.

Treat Search Console as a directional baseline rather than a complete AI-visibility system. Annotate major Google AI feature changes and compare page, query, device, geography, and conversion patterns before and after them. Build cohorts of informational pages likely to answer synthesized questions, then monitor impressions, clicks, click-through rate, non-brand demand, assisted conversions, server-log activity, and identifiable referrals.

Keep verified Google data separate from modeled citation observations. A citation detected externally can establish that an answer engine displayed a source at a particular time; it cannot prove Google-wide exposure, clicks, or revenue. For a broader operating model, use the comprehensive Generative Engine Optimization guide and connect measurement to crawl access, structured answers, original evidence, explicit entities, descriptive internal links, and visible update dates.

A minimum viable report should offer filters for AI Mode and AI Overviews, source-level citation impressions, clicks, cited URLs, response placement, prompt-topic clusters, and API export. Google could protect users through aggregation, reporting delays, minimum-volume thresholds, and the omission of sensitive or uniquely identifying prompts.

That specification would not reveal every retrieval decision, but it would let publishers test whether investments in content quality, freshness, technical access, and entity clarity affect AI discovery. Google’s current approach is progress for accounting because AI activity is no longer entirely absent from performance totals. It remains inadequate for optimization because publishers cannot isolate the surface or diagnose why content was selected.

As synthesized answers assume more control over discovery, transparency becomes part of the publisher-platform bargain. Platforms need source material to ground useful answers; publishers need enough attribution to understand whether maintaining that material remains sustainable. Accountability should therefore grow alongside AI’s role in search, even when the reporting must be aggregated and privacy protected.

Last reviewed: July 17, 2026. Google’s reporting interfaces and documentation can change, so verify current product behavior before using these answers operationally.