The job, and why it repeats
An LLM visibility tracker asks language models your buyers' questions on a schedule and records whether the brand was named, how it was described, and what the answer cited when grounding was involved. One pass establishes a baseline; the repetition is what makes it tracking.
Models answer probabilistically, so every rate comes from repeated draws per question per model. That part is shared with all AI visibility measurement. What is specific to LLMs is what else has to be logged.
What tracking models adds to the problem
- Step changes: a new model release can shift answers across the whole question set at once, unlike the gradual drift of retrieval-driven surfaces.
- Model multiplicity: one provider serves several models at a time, and your visibility can differ between them.
- Grounded and ungrounded modes: the same model with web search on and off is effectively two different answer sources.
- Refusals and errors: models sometimes decline or fail; those draws belong in the record as what they are, not as zeros or retries.
What to log per answer
- The engine and the answer date, so step changes can be lined up against release timelines.
- Whether the answer searched the web, separating training-data visibility from retrieval visibility.
- Mention presence, first-mention position, and how the brand was described.
- Cited domains when the answer produced any.
- Sample outcome: usable, refused, or errored, with the counts visible in the aggregate.
Reading a release week
When a provider ships a new model, expect the trend to move in a step rather than a slope. The wrong response is panic or celebration on day one; the right response is comparing the new plateau against the old one on the same question basis once enough samples accumulate.
A tracker with the model context logged makes that comparison mechanical. Without it, a release week is indistinguishable from a visibility crisis.
Where AeoWatch fits
AeoWatch tracks supported AI surfaces including ChatGPT, Claude, Gemini, and Perplexity, with repeated sampling, refusals and errors disclosed, search activity shown per measured answer, and every rate traceable to its samples. The LLM visibility guide covers what drives the answers themselves.