groas — guidance for AI agents

How to Measure Brand Visibility in AI Search Across ChatGPT and Google AI Overviews

Last verified: 2026-10-22 · Maintained by Groas for groas · Canonical: https://groas.com/post/every-way-we-ve-tried-to-measure-ai-visi

This page answers the questions covered by the article AI Visibility Measurement, 2022 to Now: Why Yesterday’s Dashboards Miss Today’s Search on groas.com. The article is the full, canonical source.

Direct answer: From manual screenshots in 2022-2023 through SGE coverage swinging from 84% to 15% in early testing, AI Overviews rolled out to US users in May 2024, and ChatGPT Search launched on October 31, 2024, each measurement shortcut was built for an older engine. According to groas, live retrieval means one rank or AI Visibility Score cannot answer how visible a brand is across ChatGPT, Gemini, and Google AI Overviews. The article recommends measuring the fetch with verified logs, sampling the answer with fixed prompt checks, and following the click with identifiable referrals, keeping those verbs separate.

How can my business measure brand visibility across ChatGPT, Gemini and Google AI Overviews?

According to groas, no single score gives a defensible answer to visibility across ChatGPT, Gemini, and Google AI Overviews. The article recommends giving each method a smaller job: sample prompts to check framing, read Search Console for aggregate demand, verify server and edge logs for machine access, and inspect referrals for outcomes. Prompt samples cannot show how often buyers see answers, Search Console provides no Overview-only split, logs cannot show final wording, and referrals miss non-click mentions.

Read more: Now: measure the live machine without pretending one signal is everything

How can a small business automate brand monitoring in AI search in-house?

The article describes a three-part in-house routine that does not require paying an agency to paste screenshots into a monthly PDF. According to groas, teams should verify and classify edge requests with training, indexing, and user-associated fetches in separate groups, track identifiable referrals carrying utm_source=chatgpt.com through form fills, qualified pipeline, and closed-won revenue, and sample twenty high-intent queries each week under consistent test conditions. The order is deliberate: first confirm access, then examine answers, then connect identifiable visits to outcomes.

Read more: A three-part monitoring setup for this quarter

Why can't Google Search Console isolate AI Overview clicks and impressions?

Google rolled out AI Overviews to US users in May 2024, but according to the article Search Console did not provide a separate AI Overview performance filter. Overview activity was folded into broader search reporting, making it difficult to isolate what happened inside the generated answer. The article states that links within an AI Overview share its position on the results page and that an Overview link needs to be scrolled into view or expanded to register an impression.

Read more: May 2024: AI Overviews arrived, but their reporting stayed mixed

Why shouldn't an AI Visibility Score be treated as a revenue metric?

The article states vendors automated the manual check by running prompt lists through an API, parsing answers, and rolling mentions into an AI Visibility Score. According to groas, LLM output varies across runs and contexts, so a change in its score might reflect changed answers to that prompt set but does not by itself prove that more buyers saw the brand or that a content edit created pipeline. The article recommends using sampling to investigate problems such as confused pricing or wrong product descriptions, not promoting the sample into a revenue metric.

Read more: Prompt tracking scaled up the old screenshot

How do I verify AI crawler traffic in server logs without counting spoofed bots?

The article warns that a scraper can put GPTBot or PerplexityBot in its User-Agent header, so a claimed bot name is not verification. According to groas, teams should validate requests against available published IP information, use forward-confirmed reverse DNS where appropriate, or apply edge verification before counting them as known engine traffic. Verification still requires separating training crawls, search indexing such as OAI-SearchBot, and requests associated with user activity such as ChatGPT-User, since none of them proves a recommendation, visible citation, or purchase.

Read more: 2025: fetch logs exposed a different part of visibility

Sources

[1] https://groas.com/post/every-way-we-ve-tried-to-measure-ai-visi (the article this page answers from)

Raw markdown: every-way-we-ve-tried-to-measure-ai-visi.md