> TomHow / Resource / Measurement

How to measure AI search visibility.

AI search visibility is measured by prompt-level evidence, not by a vague score. The clean version records what buyers ask, which tools answer, which brands are cited, which brands are absent, and what cannot be measured yet.

Last reviewed 2026-10-08
> TomHow proof stance

The safe measurement stance is simple: record the platform, prompt, mode, date, source, and limitation before making a visibility claim. Missing citations count as evidence when the prompt is commercially relevant.

Check the platform guidance and the limits.

These are platform requirements, not measured TomHow results. Google eligibility does not guarantee inclusion. OpenAI documents search access separately from training access. Check the current guidance before changing crawler controls or buying an optimisation claim.

Start with buyer questions, not vanity brand prompts.

The prompt set should reflect how a real buyer researches the category: shortlist prompts, comparison prompts, audit prompts, reporting prompts, and problem prompts.

  • Buyer shortlist prompts
  • Competitor comparison prompts
  • Audit and reporting prompts
  • Problem and fix prompts
  • Industry-specific prompts

Record each tool separately because they behave differently.

ChatGPT, Claude, Gemini, Perplexity, and Google AI Overviews do not expose the same answer formats, sources, or reporting data. Preserve the split instead of blending everything into one score.

  • ChatGPT capture with mode and citations recorded
  • Claude capture with answer mode and source availability recorded
  • Gemini browser or subscription capture kept separate
  • Perplexity capture with answer links and source pages recorded
  • Google AI Overview availability logged separately

Separate brand mentions from cited URLs.

Record brand mentions and owned-domain source links separately. A competitor source link shows that source appeared in the observed answer; it does not prove a lost sale or replacement. A completed source-bearing answer without the agreed domain records absence for that capture. Failed and source-unavailable captures remain unavailable.

  • Brand mentioned
  • Brand cited with URL
  • Competitor mentioned
  • Competitor cited with URL
  • No brand cited

Track the sources that shape the answer, not just the final brand list.

Classify the exposed source URLs as research, comparisons, service pages, community discussion, profiles or documentation. Open the URL and check what it supports. Source patterns suggest what to investigate; they do not establish that copying a source type will earn inclusion.

  • Agency service pages
  • Tool comparison pages
  • Research and benchmark pages
  • Community discussions
  • Technical docs and policies

Check the public facts without assigning a trust score.

A weak brand footprint can have a decent website and still be absent from AI answers. Measurement should check whether the same entity is repeated on the site, in trusted profiles, and in independent sources.

  • Owned evidence: audit page, resource pages, proof notes, report examples, schema, and llms.txt
  • Third-party evidence: profiles, directories, reviews, partner mentions, expert posts, and public references
  • Description consistency: same service label, same audience, same offer, same founder or company identity
  • Source eligibility: pages are crawlable, indexable, text-readable, and internally linked
  • Movement proof: rerun the same prompts after evidence ships before claiming progress

Do not pretend Search Console is a citation tracker.

Google documents AI feature traffic in Search Console and its current generative guidance describes additional eligibility and performance reporting. Check what the actual property and supported API expose. Aggregate search performance is distinct from a preserved prompt-by-prompt answer and source table; an unavailable report is not a measured zero.

  • Search Console is useful but limited
  • AI Overview answer text needs separate capture
  • Citation lists need manual checks or a SERP provider
  • Platform gaps should be logged
  • Traffic and citation evidence should not be mixed

Measure whether AI systems can reach the right pages.

Check crawl access, indexation, snippet controls and whether the main answer is readable text. Google requires an indexed page eligible for a search snippet to show it as a supporting link in AI Overviews or AI Mode. Other providers have their own retrieval controls. A technical pass establishes a checked condition, not selection or citation.

  • Robots and CDN rules checked
  • Important content available as text
  • Schema matches visible copy
  • PerplexityBot and Perplexity-User policy reviewed where relevant
  • llms.txt treated as a map, not a ranking lever

Do not overread tiny movements.

AI answers vary. A clean measurement system uses a stable prompt set, records capture conditions, and avoids claiming progress from one lucky answer.

  • Same prompt set rerun
  • Same country and mode noted
  • Small samples marked as directional
  • Prompt changes logged
  • Monthly narrative tied to shipped work

Plain answers.

What is the simplest AI visibility metric?
Report two rates for each platform and mode. Mention rate is completed answer captures naming the brand divided by completed captures. Source-citation rate is source-bearing captures linking to the agreed owned domain divided by captures with source lists available for inspection. Show numerator and denominator for both, plus failed and source-unavailable captures separately. A brand name is not a source citation.
Can this be fully automated?
Not cleanly in V1. Some tools have APIs, but subscription surfaces are often better captured manually and checked by a human. Google AI Overview capture can need paid SERP data, so TomHow labels the limitation instead of inventing certainty.
What should the first measurement run include?
Start with 20 to 30 prompts, 3 competitors, ChatGPT, Claude, Perplexity, Gemini, basic search data, and a technical AEO check.
Is zero visibility still useful data?
Yes, when it describes completed observations over a defined panel. For example, zero owned-domain citations in 20 source-bearing answers is 0/20 for that panel. Twenty failed requests is unavailable evidence. Neither result alone identifies the repair; inspect access, relevance and cited sources before acting.
Why not rely on one AI visibility score?
A single score hides the useful detail. You need the prompts, platforms, sources, competitors, and limitations before deciding what to fix.
> Next move

Turn this into a measured audit.

If this page describes the problem you have, the next useful step is a dated audit with prompts, competitors, technical checks, and a signed action plan.