LLM visibility:
memory, retrieval and drift
When a language model describes your organisation, the description comes from two very different places: what it absorbed during training, and what it retrieved just now. Those fail differently and are fixed differently. Stale training-era memory produces confident, outdated statements you cannot edit; weak retrieval produces omission you can. An LLM visibility audit separates the two, records what is actually returned, and measures the retrieval-side conditions you can change.
Two sources, two failure modes
Training-era memory is whatever a model absorbed about you before it was deployed. It is not a database you can update. If your company rebranded, moved, changed ownership or pivoted, a model may keep describing the earlier version fluently and with no signal to the reader that it is out of date. You cannot correct this directly — you can only make the current, correct picture overwhelmingly well-established so that retrieval supplies it and future training absorbs it.
Live retrieval is what the system fetches at question time. This is the half you control. If your pages cannot be fetched, your organisation resolves ambiguously, or your claims exist nowhere but your own site, retrieval returns thin material and the model falls back on memory or on a competitor's better-evidenced page.
Prompt variance, handled honestly
Language models do not return stable answers. The same question phrased two ways, or asked twice, can produce different businesses named and different attributes asserted. Any product presenting an "LLM ranking" as a stable position is smoothing over that variance and selling you a chart of noise.
OG01 handles it the only defensible way: responses are recorded as observations at a moment, with the prompt shown, rather than aggregated into a position. The durable part of the audit is the retrieval-side condition of your domain, which is stable, repeatable and yours — and which is what a rescore compares.
Four retrieval-side conditions, and what comes back
Access sits underneath all four as a prerequisite: if pages cannot be fetched, the reading returns Not Rated instead of inventing the missing evidence. The explanation guides the next step; the linked FAQ covers retries and support. Forensic access investigation is not a service OG01 provides.
Adjacent readings
LLM visibility questions
An AI is stating something false about our company. Can you get it removed?
Why do you not publish an LLM ranking or share-of-voice score?
How is this different from the AI visibility audit?
Does having more content help a model describe us correctly?
Which models do you test against?
Memory and retrieval fail differently. The free reading measures the retrieval side, which is the half you can change.