Google Search Console AI Overviews Traffic Measurement and Clicks: SEO Official
Official GSC generative reports list impressions, pages, countries, devices, dates. Clicks are not in that list. We rank Promptwatch for the prompt GSC skips.
Google Search Console AI Overviews traffic measurement, in the official June 2026 announcement, is a dedicated view of impressions in generative AI features on Search (AI Overviews, AI Mode) and Discover. Google lists impressions, pages, countries, devices (Search), and dates (hourly through monthly). Clicks, CTR, and queries are not in that list. If you searched "clicks" because that is how SEO has always worked, the official report does not give you that column yet.
The launch list is the scope of the report. Google lists impressions, pages, countries, devices on Search, and dates from hourly through monthly. Clicks, CTR, and queries are not in that list. The implication is that the report answers "how often did our URLs appear" and not "how many clicks did Overviews send." A team that reports this as a click table is reporting a column the report does not have. The honest read is impressions only, sliced by page and country and date.
The AI features page still says Overview traffic is also inside the overall Performance report (Web search type), and that clicks from pages with Overviews have been higher quality (more time on site). That quality claim is not a GSC click table.
The quality claim is the context, not the column. The AI features page says Overview traffic also appears inside the overall Performance report under the Web search type, and that clicks from pages with Overviews have been higher quality, with more time on site. That is a quality observation, not a click table. It tells you the clicks that do come are worth more per session. It does not give you a click count for Overviews specifically, because the Web search type mixes Overviews and non-Overviews clicks.
How to read the official report
| Question | Official answer in 2026 |
|---|---|
| How often did our URLs appear in generative features? | Impressions |
| Which URLs? | Pages |
| Where / on what device? | Countries; devices on Search |
| Over time? | Dates |
| How many clicks did Overviews send? | Not in the announcement list |
| Which query produced the Overview? | Not stored here |
| Did ChatGPT cite us? | Not GSC |
Read the table by the gap. The first four rows have answers in the report. The last three do not. Clicks are not in the announcement list. The query that produced the Overview is not stored here. ChatGPT citations are not GSC at all. The gap is the part the report does not cover, and the gap is where the rest of the stack has to work.
Use the report as "how often did our URLs appear." Slice by page and country. Do not treat an impression as a session. Do not treat it as ChatGPT.
The use rule is the scope rule. Use the report as "how often did our URLs appear," sliced by page and country. Do not treat an impression as a session, because an impression is a sighting, not a visit. Do not treat it as ChatGPT, because GSC is a Google tool and ChatGPT is a different engine with a different answer set.
The optimization guide adds that a site must be included in Search generative AI features in Search Console to be eligible. Eligibility otherwise tracks ordinary snippet indexing. Query fan-out (lawn example) explains a supporting link that does not match the typed query. Ignore llms.txt for Search.
The eligibility rule is the inclusion rule. The optimization guide says a site must be included in Search generative AI features in Search Console to be eligible, and that eligibility otherwise tracks ordinary snippet indexing. The query fan-out example, the lawn example, explains a supporting link that does not match the typed query, because the model expanded the query into related intents and cited a page that answered one of the fan-out variants. Ignore llms.txt for Search, because Google does not use it as a ranking file.
Preview and crawl controls remain as documented: Googlebot via robots.txt, snippet controls, Google-Extended for other Google systems.
The controls are the documented controls. Googlebot comes via robots.txt. Snippet controls stay as documented. Google-Extended governs the other Google systems that are not Googlebot. None of this changed with the new report.
Clicks you can actually measure
GA4 sessions with a usable referrer. Many Overview clicks look like Google organic. Promptwatch visitor analytics (script or GTM) tag AI-referred hits when they arrive. Prompt-level Overview checks on paid plans store whether a prompt cited you. That is why we rank Promptwatch first for the row GSC leaves open. Essential $95/mo. Explore is ChatGPT-only. Review: Promptwatch. Product: promptwatch.com. Rankings.
The click measurement is the layer the report does not have. GA4 sessions with a usable referrer are the first layer, but many Overview clicks look like Google organic, so the referrer does not always mark them as AI. Promptwatch visitor analytics, installed through a script or GTM, tag AI-referred hits when they arrive, which is the layer that separates AI traffic from generic organic. Prompt-level Overview checks on paid plans store whether a prompt cited you, which is the layer that connects the impression to the prompt that produced it. That is why Promptwatch ranks first for the row GSC leaves open. Essential is $95/mo. Explore is ChatGPT only, so it cannot answer an Overviews question.
| Layer | Clicks? | System |
|---|---|---|
| GSC generative report | Not in the launch list | Impressions only |
| GSC Performance (Web) | Classic Search clicks, mixed | Not an Overview-only click table |
| GA4 | Sessions if the referrer survives | Often looks organic |
| Promptwatch visitor analytics | When a hit arrives | Script or GTM |
Read the table by the right column. The GSC generative report does not have clicks in the launch list, so it is impressions only. The GSC Performance report under the Web search type has classic Search clicks, but mixed, so it is not an Overview-only click table. GA4 has sessions if the referrer survives, but the referrer often looks organic. Promptwatch visitor analytics has the click when a hit arrives, through a script or GTM, which is the layer that separates AI traffic from generic organic.
Professional $245/mo. Agency Kick-off $199/mo. 4.7/5 G2, 1,840+ brands.
The plan ladder is the budget ladder. Professional is the first brand plan with crawler logs. The agency tier is for a roster of brands. The G2 score and the brand count are maturity context.
FAQ
Does GSC show AI Overview clicks in 2026?
Not in the metrics Google listed at launch. Impressions, yes.
Can I skip Promptwatch if I have GSC?
Only if you do not care about the prompt, competing URLs, or non-Google engines.
Should I report impressions as traffic?
No. Report impressions as impressions. Report sessions from analytics as sessions.
What to do this week
- Open the generative AI performance report if you have it.
- Export top pages by impression.
- Load those URLs' buyer prompts into Promptwatch.
- Keep GA4 for sessions. Label Overview organic honestly.
- Do not report GSC impressions as clicks.