How to Choose an AI Visibility Tracking Tool: Five Checks That Matter
99Visibility Research · Updated October 21, 2026 · 8 min read
Short answer
Choose an AI visibility tracking tool by how honestly it measures, not by how many engines it lists. A good tool reports each engine separately and says whether each answer used live web search. It checks what AI says against your verified facts and tests whether AI crawlers can reach your site. It also publishes how its score is calculated. Reject any tool that reports an AI rank or promises citations.
Key takeaways
- A single blended AI visibility score hides the engine-by-engine differences you actually need to act on.
- Every answer a tool records was generated with or without live web search, and the tool should tell you which.
- Mention counts say nothing about whether AI states your pricing or product facts correctly, so look for accuracy checks with a real denominator.
- Tracking shows outcomes, while access checks (robots.txt per bot, firewall reachability, JavaScript rendering) show causes you can fix.
- Any tool selling an AI rank, an E-E-A-T score, or schema as a citation lever is selling claims the primary sources contradict.
What an AI visibility tracking tool actually measures
An AI visibility tracking tool sends a set of prompts to AI engines, records the answers, and reports whether and how your brand appears. That is the whole mechanism. Our definition of AI visibility tracking covers the term in more detail.
The answer you see is the end of a four-stage chain:
- Parametric: what the model knows with no web access, frozen at its training cutoff.
- Access: whether a crawler can fetch and store your page at all.
- Retrieval: whether your page enters the model's context for a given query.
- Generation: which retrieved pages the model uses and cites.
A tracker only sees the final output. So the best tools do two jobs: they record what each engine said, and they help you work out which stage caused the result. Use that as the frame for every criterion below.
Per-engine reporting, not one blended score
Engines behave differently, and a single number averages that away. Google's documentation says AI Overviews and AI Mode "may use different models and techniques" and can return different links. Citation units also differ: Anthropic cites short text spans, while Perplexity cites whole sources by index. There is no shared denominator to average across.
The gap can be large. In Otterly's 2026 experiment, 2,718 of the 3,934 citations it tracked for one test site came from Microsoft Copilot, while ChatGPT, Gemini, AI Overviews and AI Mode almost never cited it. A blended score would have hidden all of that.
What to ask a vendor
- Does the dashboard show each engine on its own line?
- Are Google AI Overviews, AI Mode and the Gemini app reported as separate surfaces?
- If there is a combined score, is it labelled as the vendor's own model rather than a measurement?
Disclosed retrieval state: the question most buyers skip
Retrieval is decided per query, and the rules differ by engine. As of October 2026, ChatGPT search runs at the model's discretion, Claude.ai search is a user toggle with no published default, and web search on Perplexity's Agent API must be switched on by the developer. An answer generated with search off reflects only what the model learned before its cutoff. OpenAI documents different knowledge cutoffs for different ChatGPT model paths, so "what ChatGPT knows" is not one value.
This matters for interpretation. A brand that launched a product last month can look invisible in an ungrounded answer and present in a grounded one. Neither result is wrong, but they mean different things and call for different fixes.
The prompts are also not what the engine searches for. OpenAI says ChatGPT search "typically rewrites your query into one or more targeted queries" before sending them to search providers.
What to ask a vendor
- For each engine, was web search on or off, and which model answered?
- Were answers collected logged out with memory off, so results are reproducible?
- Does the tool record retrieved sources separately from cited ones? OpenAI states the number of sources consulted is often greater than the number cited.
Accuracy and access checks
Accuracy: is what AI says true?
Being mentioned is only half the story. AI platforms get specific facts wrong about specific brands: prices, product names, ownership, features. A useful tool compares answers against facts you supply and flags the wrong ones by severity.
Check how the accuracy number is built. Established factuality metrics such as FActScore divide errors by a count of facts or answers. A score that simply subtracts penalty points can fall when you add more prompts, even if the error rate stays flat. Ask whether failed or empty answers are excluded from the count, and whether one serious error stays visible in a large sample.
Access: can AI crawlers reach you?
Tracking shows the outcome. Access checks show causes you can fix, and they carry the strongest evidence in the field.
- robots.txt is per bot. OpenAI's crawler page says GPTBot governs training, OAI-SearchBot governs ChatGPT search, and each setting is independent.
- Firewalls can override robots.txt. OpenAI's help centre says eligibility means allowing OAI-SearchBot and confirming your host or CDN allows traffic from its published IP addresses.
- JavaScript can hide content. Vercel found that ChatGPT and Claude crawlers fetch JavaScript files but don't execute them, so client-side rendered content can be invisible to them.
- Defaults change without you. From 2026-09-15, Cloudflare blocks training and agent crawlers by default on ad-displaying pages for new domains and existing free-tier customers.
Ask whether the tool requests your pages as each AI crawler and compares raw HTML with the rendered page. If a tool only tracks answers, pair it with something that diagnoses. Our comparison of tracking tools versus fixing tools explains the split.
Formula transparency and claims to reject
Every AI visibility score is a model built by the vendor. That is fine, as long as the vendor shows its work. Ask for the formula, the weights, and the version history. Ask whether scores from before a formula change are comparable with scores after it. If the vendor can't answer, the trend line on your dashboard may not mean what it shows. Our playbook on choosing AI visibility KPIs you can defend goes deeper on which numbers hold up.
Red flags in a sales pitch
- An AI rank or position in Google AI. Google's generative AI report exposes impressions only, so there is no ground truth to check a rank against.
- An E-E-A-T score. Google says E-E-A-T "isn't a specific ranking factor". There is no score to measure.
- Domain authority as an AI lever. It is a third-party metric that no engine computes.
- "Add schema to get cited." Ahrefs' matched-control study found AI Overview citations fell 4.6% on pages after schema was added.
- "Publish an llms.txt." Google says Search ignores it, and no other engine documents reading it.
- "Up to 40% more visibility." That figure comes from a lab engine with sources already loaded into context.
A 2026 critical survey of 45 GEO studies found no technique with a stable, longitudinal, cross-platform causal effect on discoverability. A tool that promises one is overselling.
What you control and what no tool can see
Be clear about the limits before you buy anything.
In your control:
- Crawler access: robots.txt per bot, firewall and CDN rules.
- Server-side rendering of the facts that matter, such as pricing and product names.
- Snippet controls like
noindex,nosnippetanddata-nosnippet, including ones applied by accident. - Stating specific facts clearly on pages that can be fetched, and keeping them consistent across your site.
- Being named on the third-party pages engines cite instead of yours (an association in the evidence, not a guaranteed effect).
Outside anyone's control:
- What a model learned before its cutoff.
- Whether an engine decides to search for a given query.
- Where your page lands in the model's context, and which sources it cites.
No tracker sees the real queries engines run. Every prompt set is a sample. In Otterly's experiment, Microsoft's own AI Performance report counted 42,817 citations for a site where Otterly's prompt tracker logged 3,934, though the time windows may not match. Treat any tool's numbers as a sample, and say so when you report them.
A practical order for evaluating tools
Work through these steps before signing a contract.
- Take a baseline. Run a snapshot so you know where you stand before any demo. The free checker on this site scores up to three buyer questions. A snapshot is not tracking, and our page on what a free snapshot misses explains the gap.
- Write your must-have list using the table below.
- Ask each vendor the same questions in writing. Compare answers, not demos.
- Run a short trial on your real prompts. Check whether results are reproducible across two runs.
- Check the price against coverage. Our guide to what AI visibility tools cost gives context without naming winners.
| Criterion | What good looks like | Red flag |
|---|---|---|
| Per-engine reporting | Each engine and Google surface shown separately | One blended score only |
| Retrieval state | Search on or off, and model, disclosed per answer | No disclosure |
| Accuracy | Facts checked against yours, normalised by answers returned | Mention counts only |
| Access | Pages requested as each AI crawler, rendering checked | No access checks |
| Formula | Published weights and version history | "Proprietary" with no detail |
Common mistakes when comparing tools
- Counting engines instead of checking methods. Five engines measured badly tell you less than three measured with disclosed retrieval state.
- Reading a trend across a formula change. If the vendor changed its scoring, older numbers may not be comparable.
- Treating mentions as traffic. A citation is not a visit, and Google's AI report shows no clicks.
- Over-weighting competitor prompts. Prompts that name rivals answer a different question. See whether to track competitor-name prompts.
- Switching tools without exporting history. Your baseline goes with the old account. Read what to check when switching AI visibility tools first.
- Buying a tracker to solve an access problem. If a firewall returns 403 to OAI-SearchBot, no amount of tracking will fix it. Check access first.
Frequently asked questions
Is a free AI visibility check enough on its own?
A free check is a useful baseline, but it is a snapshot. It shows what a few engines said for a few questions on one day. It cannot show trends, catch a sudden change such as a new CDN default blocking crawlers, or tell you whether results hold across runs. Use it to decide whether ongoing tracking is worth paying for, not as a substitute for it.
Can any tool tell me my rank in ChatGPT or Google AI Overviews?
No tool can verify one. Google's generative AI report in Search Console shows impressions only, with no position data, and OpenAI discloses only that ChatGPT ranks results using "multiple factors". A tool can report whether you were mentioned or cited for its prompts. It cannot report a rank that any engine confirms, so treat any rank metric as the vendor's invention.
Should Google AI Overviews and AI Mode be tracked separately?
Yes. Google says the two surfaces may use different models and techniques and can show different links. The Gemini app is a third, separate product. A tool that reports one "Google AI" number is merging surfaces that can behave differently for the same query, which makes it harder to see where a problem actually sits.
Does it matter whether the tool checks answers with search on or off?
It matters a lot. An answer with search off reflects what the model learned before its training cutoff, which nobody can change this quarter. An answer with search on reflects what the engine retrieved today, which depends on access and indexing you can fix. Without knowing which you are looking at, you can't pick the right fix.
What is the difference between a tracking tool and a fixing tool?
A tracking tool records what AI engines say about you over time. A fixing tool also diagnoses why, for example by checking robots.txt per crawler, testing whether your firewall blocks AI bots, and flagging facts that only appear after JavaScript runs. Many teams need both: tracking to see outcomes, and diagnosis to find causes they can change.
Sources
This page is AI-assisted. It was written from a verified evidence base and checked against our editorial policy. Engine behaviour changes often; facts are as of October 21, 2026.