How we measure AI visibility.

Sampling design

A single query run tells you almost nothing. Day-to-day overlap in cited sources for the same prompt averages a Jaccard score of 0.34 to 0.42 across 45 days of live engine monitoring: roughly two-thirds of cited sources change day to day with no content change anywhere on the underlying pages. Same-day repeated prompts come back nearly as unstable. One snapshot is a coin flip dressed up as a fact.

So we run every prompt multiple times per engine per day. The literature floor for a brand-rate standard error under 0.10 is 7 runs; that is our minimum, not our ceiling.

The schedule is adaptive, not flat. About 77.5% of prompt-engine cells are deterministic: your brand is always mentioned or never mentioned. After 14 days of history, a stable cell drops to 2 runs a day; a flipping cell (mentioned somewhere between 30% and 70% of the time) keeps the full 7. Same statistical confidence where it matters, roughly half the query volume overall.

Confidence intervals

Every trend line we publish carries a Wilson 95% confidence band, computed from the actual run count behind that cell. A narrow band means we ran enough queries to trust the point estimate. A wide band means we did not, and we show that width instead of hiding it behind a clean-looking line.

A change only counts as movement when the bands for two periods stop overlapping. If they still touch, we label it “no significant change,” full stop, even when the point estimate moved. Most of this category screenshots every uptick and calls it progress. We would rather tell you the data is flat than sell you a story it cannot support.

Share of voice

Share of voice for brand b on a given prompt set:

M(b) is how often your brand is mentioned across the prompt set. The sum in the denominator runs over qualified competitors only: brands that appear repeatedly or resolve to a real, checkable domain. A model hallucinating a made-up competitor name once does not earn a seat in the denominator, so it cannot quietly dilute your score. Most tools count every name the model happens to say; we filter first.

Per-engine isolation

ChatGPT, Gemini, and Perplexity draw from almost entirely separate source pools for the same prompt: cross-engine cited-source overlap sits around 0.12 Jaccard. They are not three windows onto the same answer. They are three different answers built from three different sets of sources.

That is why we never publish a blended “AI visibility score” across engines. Every number on this site and in your dashboard is reported per engine. Averaging them would smooth over the exact differences you need to see to know which engine actually needs fixing.

Sentiment, honestly

Sentiment is the least stable signal we measure. Across repeated runs of the same prompt, sentiment flips 45.5% of the time, 6.7 times noisier than a simple mention. A single answer’s sentiment is close to a coin flip.

We only report sentiment aggregated across 10 or more prompts per platform, with the sample size printed next to the number. No per-answer sentiment badges, no green or red chip on a single response. When the sample is too thin, we show no sentiment number at all rather than a false one.

API versus UI

We sample ChatGPT, Gemini, and Perplexity through their published APIs and label them API-sampled in your dashboard. That is a deliberate, repeatable, billable query path, and it can diverge from what a person sees typing into the consumer app: consumer interfaces layer on personalization, memory, and product-specific ranking that the API does not expose.

Google AI Overviews, Google AI Mode, and Microsoft Copilot have no equivalent API for this. We sample those from the real user-facing surface through data providers who scrape the actual product, not a proxy endpoint. Both approaches are labeled in the dashboard so you always know which surface produced a number.

Crawler verification

When we report AI crawler traffic on your site, we check the requesting IP against the vendor’s published range for that bot, not just the user-agent string a request can forge. A bot with a published range gets a verified badge. A bot without one gets labeled UA-only, because nobody, including the vendor running it, can currently prove a given request came from them.

Prior art

The design choices above are not opinions. They trace back to three 2026 papers and one public metric glossary, listed here so anyone can check our work.