How to Measure Visibility in AI Search
Founder, SEO and GEO Consultant | · updated: | 10 min read

AI search visibility measurement is a practice that tracks how a brand appears in Google's AI Overviews and AI Mode, and in answers from assistants like ChatGPT, Gemini and Perplexity. It draws on five sources: Search Console reports, Google Analytics 4 (GA4) data, server logs, manual tracking and measurement tools.
The subject here is measurement, not the definition of generative engine optimisation (GEO) or answer engine optimisation (AEO). I summarised Google's position in the AI in Search section of my SEO guide.
What is AI search visibility?
AI search visibility is the extent to which a brand is named or cited as a source in answers generated by AI search systems. Those systems are Google's AI Overviews and AI Mode, and assistants like ChatGPT, Gemini and Perplexity. The same idea is also called AI visibility or visibility in AI. AI search visibility is not a rank position for one keyword. It is expressed as a mention rate and a citation rate across a fixed set of questions.
Why measure visibility in AI search?
Measuring visibility in AI search matters because an AI answer can show a brand without a click. In an answer a brand is named in the text, linked as a source, or absent. Classic rank tracking does not separate those three states.
Google's documentation says AI Overviews and AI Mode may use "query fan-out", which issues multiple related searches across subtopics. Your page can be a source for a generated subquery, not for the query the user typed. Measurement therefore covers a set of questions, not a single keyword.
How does AI search visibility differ from traditional search?
AI search visibility differs from traditional search visibility in what is counted. Traditional SEO tracks a URL's rank for a keyword. AI search measurement tracks whether the answer to a prompt names the brand and cites its site. The table below compares four aspects.
| Aspect | Traditional search | AI search |
|---|---|---|
| Result | A ranked list of links | An answer generated by a large language model (LLM) that names brands and cites sources |
| Unit tracked | Keyword | Prompt, plus the subqueries the system fans out |
| Main metric | Rank position | Mention rate and citation rate |
| Traffic signal | Clicks from the results page | Clicks only from linked answers, unlinked mentions leave no trace |
What can and cannot be measured in AI search visibility?
AI search visibility can be measured as impressions, clicks, referral traffic, bot requests and a sampled mention rate. Five data points are measurable.
- Impressions in Google's generative AI features, by page.
- Clicks from AI Overviews and AI Mode, inside Search Console's total Web data.
- Sessions from AI assistants, in GA4.
- Requests from AI bots, in server logs.
- The share of answers that mention the brand, in a fixed question set.
Three data points cannot be measured.
- The total number of answers that name the brand without a link: with no click, nothing reaches GA4 or the server log.
- A separate click total and a query breakdown for AI features in Google's reports: Google's documentation describes neither.
- The answer each user sees: manual tracking and tools return a sample, not a full count.
How do you measure Google's AI features in Search Console?
Search Console measures visibility in Google's AI features with two reports: the Performance report and the generative AI performance report.
How does the Performance report count AI features?
The Performance report counts sites that appear in AI Overviews and AI Mode within the Web search type. Google states this in its AI features and your website document. Search Console Help lists no Search appearance type for AI features and gives three counting rules.
- Click: a click on a link to an external page in an AI Overview or AI Mode is counted.
- Position: an AI Overview occupies a single position, and every link inside it gets that position.
- New query: each follow-up question in AI Mode counts as a new query.
I covered querying performance data with SQL in my post on the Search Console BigQuery export.
What does the generative AI performance report show?
The generative AI performance report shows how many times links to your site were shown in AI Overviews and AI Mode. In the help page for the report, Google says the data reached all websites worldwide as of 31 August 2026. The report groups data in four tabs: pages, countries, dates and devices. The report has three limits.
- The chart is aggregated by property: two links from your site in one answer count as a single impression.
- The 1,000 row limit of the Performance report applies to this report too.
- The report may be missing if the site has too few impressions or was excluded with the Search generative AI control under Settings.
How do you track brand visibility in Google AI Mode?
You track brand visibility in Google AI Mode with two Search Console reports and a manual question set. The Performance report folds AI Mode into the Web search type, so a brand mention only becomes visible when you ask AI Mode the questions yourself. The table below shows what each source records for AI Mode.
| Source | What it records for AI Mode | Limit |
|---|---|---|
| Performance report | Clicks on links in AI Mode, with each follow-up question counted as a new query | No Search appearance type for AI features, so the clicks stay inside total Web data |
| Generative AI performance report | How many times links to your site were shown in AI Overviews and AI Mode, by page | No documented query dimension |
| GA4 | No separate AI Mode data | The AI Assistant channel excludes AI Overviews and AI Mode |
| Manual question set | Whether the AI Mode answer mentions the brand, and which page it cites | A sample, not a full count |
For the manual part, ask the question set in AI Mode with the same language, country and device every round. Record AI Mode as the surface, then fill in three fields per answer: brand mentioned, site cited, cited URL. AI Mode may fan one question out into related searches, so track a set of questions per topic, not a single keyword. Repeat the round at a fixed interval and compare the mention rate with the previous round.
How do you separate AI assistant traffic in GA4?
GA4 separates AI assistant traffic with the AI Assistant channel in the default channel group. Google's default channel group documentation defines the channel as users who arrive from sources like ChatGPT, Gemini, Deepseek, Copilot or Grok. When the referrer matches Google's list of AI assistants, GA4 sets the session medium to ai-assistant. The channel excludes AI Overviews and AI Mode.
The channel appears under Reports, Acquisition, in the Traffic acquisition report. Change the dimension to "Session source / medium" to see which assistant sent the visits. OpenAI says ChatGPT automatically adds the utm_source=chatgpt.com parameter to its referral URLs. Read the source values of other assistants from your own report.
The default channel group cannot be edited. To set the assistant list yourself, build a custom channel group in four steps.
- In Admin, open Channel groups under Data display and click "Create new channel group".
- Click "Add new channel" and name the channel "AI assistants".
- Add a condition on the Source dimension, choose "matches regex" and enter the regular expression.
- Move the channel above Referral in the list and save the group.
The regular expression below is an example based on the assistants named in Google's custom channel groups documentation.
.*(chatgpt|openai|perplexity|copilot|gemini|claude).*
Custom channel groups apply to reports retroactively. Google asks you to update the expression when the assistant list changes.
How do you tell AI bots apart in server logs?
AI bots in server logs fall into three classes by user agent name: training bots, search bots and user-triggered bots. The table below lists the bot names that OpenAI, Anthropic and Perplexity document.
| Company | Training bot | Search bot | User-triggered bot |
|---|---|---|---|
| OpenAI | GPTBot | OAI-SearchBot | ChatGPT-User |
| Anthropic | ClaudeBot | Claude-SearchBot | Claude-User |
| Perplexity | None documented | PerplexityBot | Perplexity-User |
A training bot request means the content may be collected for model training, not that it appeared in an answer. A search bot request means the page was crawled for the assistant's search results. A user-triggered bot may visit a page when a user asks the assistant a question, so it is the closest signal to an answer. OpenAI's bot documentation and Perplexity's crawler documentation publish user agent strings and IP address lists.
The example command below counts requests per bot in a combined-format access log.
grep -oE "GPTBot|OAI-SearchBot|ChatGPT-User|ClaudeBot|Claude-SearchBot|Claude-User|PerplexityBot|Perplexity-User" access.log | sort | uniq -c | sort -rn
Bot counts have two limits. A user agent name can be spoofed, so compare the request's IP address with the list the company publishes. Google-Extended is a token used only in robots.txt and has no separate user agent string in logs. I covered reading an access log in my post on log file analysis for SEO.
How do you track brand visibility in AI answers by hand?
Tracking brand visibility in AI answers by hand means asking assistants a fixed question set at regular intervals and recording every answer in the same fields. It takes six steps.
- Build the question set: group your customers' decision questions by informational, comparison and purchase intent. I covered ways to find intent in my post on user intent in SEO.
- Fix the surfaces: for example AI Overviews, AI Mode, ChatGPT, Gemini and Perplexity.
- Fix the conditions: use the same language, country and device every round, and ask each question in a new chat.
- Ask each question with the same wording every round, and store the full answer text with its date.
- Fill in three fields per answer: is the brand mentioned, is your site cited, which page is cited.
- Repeat the round at a fixed interval and calculate the mention rate: answers that mention the brand divided by total answers.
Example column headers and one row for the record table are below.
date,surface,question,brand_mentioned,site_cited,cited_url
2026-10-05,ChatGPT,"how to choose running shoes",yes,yes,https://example.com/running-shoe-guide/
Manual tracking has three limits. The same question can return a different answer each time. The answer can change with the user's location, language and account. Google says AI Overviews appear only when its systems determine that they add to classic Search. The resulting rate is a sample: it shows direction, not an exact count.
How do the sources for measuring AI search visibility compare?
The sources for measuring AI search visibility differ in the stage each one shows: impression, click, visit, crawl or mention. The table below compares six sources by data shown and by limit.
| Source | What it shows | Limit |
|---|---|---|
| Search Console Performance report | Clicks, impressions and position for Web search, AI features included | The AI share is not shown separately |
| Generative AI performance report | Impressions in AI Overviews and AI Mode, by page | Google only, no documented query dimension |
| GA4 AI Assistant channel | Sessions, engagement and key events from assistants | Mentions without a click are invisible |
| Server logs | Which bot requested which page and when | A request is not an appearance in an answer |
| Manual tracking | Mentions, citations and cited pages for chosen questions | Small sample, answers can change each time |
| Visibility measurement tools | The same tracking across more questions, at regular intervals | Still a sample, no access to Google's internal data |
Why track classic rankings and AI citations separately?
Classic rankings and AI citations are tracked separately because an AI answer can draw its sources from a different list than the ranked results. In the US Department of Justice (DOJ) case against Google, Judge Amit Mehta's September 2025 remedies decision says Google grounds its Gemini models with FastSearch. FastSearch is based on RankEmbed signals and generates abbreviated, ranked web results that a model can use for a grounded response. It retrieves fewer documents than Search, and the decision rates its results below Search's fully ranked results.
A January 2025 DOJ note of a call with Google engineer Pandu Nayak says FastSearch grounds responses on Vertex AI and in the Gemini app. Neither document says that AI Overviews or AI Mode use FastSearch, so treat that link as an inference. The table below splits the two results into separate columns.
| Column | Classic results | AI answer |
|---|---|---|
| What you record | Your page's position for the typed query | Whether the answer cites your page |
| Data source | Search Console Performance report or a rank tracker | Question set record, generative AI performance report |
| Field in the record table | classic_position (new) | site_cited, cited_url |
Compare the two columns page by page. A page can rank without a citation, or earn one without ranking for the typed query. The second case fits query fan-out, where AI Overviews and AI Mode may run related searches on subtopics. To review the pages themselves, run the checks in my Google leak signal audit.
Which metrics and KPIs measure AI search visibility?
Six metrics measure AI search visibility, and each one works as a key performance indicator (KPI). Four come from the prompts you track by hand or with a tool, and two come from Google's reports. The table below gives each KPI with its formula and source.
| KPI | Formula | Source |
|---|---|---|
| Mention rate | Answers that mention the brand divided by total answers | Question set |
| Citation rate | Answers that cite your site divided by total answers | Question set |
| Share of voice | Your brand's mentions divided by the mentions of all tracked brands | Question set that records competitors |
| Sentiment | Share of mentions that describe the brand positively, neutrally or negatively | Question set, read by hand or by a tool |
| AI impressions | Impressions in AI Overviews and AI Mode, by page | Generative AI performance report |
| AI assistant sessions | Sessions and key events in the AI Assistant channel | GA4 |
Share of voice needs competitor data, so add a competitors_mentioned column and a sentiment column to the record table. Tools name and calculate their visibility score in different ways. Compare a score only within the same tool and the same question set. A rising score with a falling citation rate means the brand is named more but cited less.
How do you connect AI search visibility to revenue?
AI search visibility connects to revenue through GA4 attribution and through what customers report. In the Traffic acquisition report, the AI Assistant channel row shows key events, session key event rate and total revenue next to sessions. Unlinked mentions send no session, so add an AI assistant option to the "How did you hear about us?" field on your forms. Run the first round of the question set before you change any content. That round establishes the baseline, and later rounds show the change in percentage points.
What do AI visibility measurement tools do?
AI visibility measurement tools automate the manual tracking method: they ask assistants a question set at regular intervals and record the answers that mention the brand.
rankzup.ai, a tool I founded, measures how visible a brand is in ChatGPT, Gemini and AI Overviews answers. Ask three questions when you choose a tool.
- Which assistants does the tool query, and in which country and language?
- Do you define the question set yourself?
- Does the tool store the full text of the answer?
Google's generative AI guide says to be wary of third-party tools that promise ranking success or claim to use "internal" Google metrics. The guide adds that no such tool has access to Google's internal ranking or AI systems.
What does Google say about visibility in AI search?
Google says visibility in AI search needs no additional requirements and no special optimisation. Google's generative AI optimisation guide treats the work as SEO and lists five tactics you can ignore for Google Search.
- llms.txt files and other "special" markup.
- "Chunking" content into small pieces.
- Rewriting content just for AI systems.
- Seeking inauthentic "mentions".
- Overfocusing on structured data.
The consequence for measurement: indicators tied to those tactics do not measure visibility on Google. Requests to an llms.txt file, for example, say nothing about visibility on Google, because Google Search does not use the file. The guide points to the generative AI performance report for measurement.
Which mistakes are common when measuring AI search visibility?
The common mistakes in measuring AI search visibility are trusting a single answer, chasing a rank and looking only at traffic. Four mistakes follow.
- Drawing a conclusion from one query: the answer can change on the next attempt.
- Rank obsession: Search Console assigns one position to every link in an AI Overview, so track the mention rate instead.
- Looking only at traffic: an answer can name the brand without a link, and GA4 then shows nothing.
- Changing the question set every round: the rounds can no longer be compared.
How do you monitor AI search visibility over time?
You monitor AI search visibility over time by repeating the same measurement on a fixed schedule, with a short weekly check and a monthly report. A single measurement gives a baseline. Monitoring, also called tracking, compares every new round with that baseline, so the question set, the surfaces and the conditions stay the same. The weekly check has two tasks.
- Ask the question set, and record the mention rate and the citation rate.
- Check sessions and key events for the AI Assistant channel in GA4.
The monthly report has four tasks.
- Export the generative AI performance report from the pages tab, and compare impressions with the previous month.
- Count bot requests in the server logs by the three classes.
- Update the custom channel group's regular expression for new source values in the report.
- Add questions about new products to the question set, and keep the wording of existing questions.
Join the data from the four sources in one table keyed by page URL. I covered the joining method in my post on data-driven SEO.
Taha Yelkenci
Started in SEO in 2010. Founder of rankZup. Got a question? Write to me →
Comments
Be the first to comment
← Previous post
You may also like
April 15, 2019 · 5 min
September 1, 2019 · 3 min
January 3, 2021 · 3 min