# [LLM brand visibility: retrieval is the part you can fix](https://rebilder.com/solutions/llm-brand-visibility)

> What a model absorbed in training is fixed. What it retrieves at answer time is not. Knowing which is which tells you what you can actually fix.

- **Updated:** 2026-08-17

A model knows two things about your brand: what it absorbed during training and what it fetched a second ago. You cannot change the first. The second is served by your own web server.



## What you get

- Understand which brand errors are fixable and which are frozen
- Make the retrieved version of your facts authoritative
- Measure what models fetch from you, on your own infrastructure
- Keep every published claim traceable to a stored value

## Training and retrieval are different problems

Brand teams often treat an assistant’s wrong answer as one problem. It is two, with different time constants and different remedies, and the useful diagnostic is whether the answer changes when the model is allowed to browse.

|  | Training knowledge | Retrieved knowledge |
| --- | --- | --- |
| Where it came from | A corpus frozen at some past date | A live fetch of a URL |
| How stale it can be | Arbitrarily | As stale as your page |
| Can you correct it | Not directly | Yes, by changing the page |
| How long a fix takes | A model generation, if ever | The next fetch |
| Who controls it | The model provider | You |

This is why the practical brand strategy is to make retrieval win. A model that can cheaply fetch a current, unambiguous page about you has less reason to fall back on whatever it half-remembers, and that is the entire mechanism available to you.

## Making the retrieved version authoritative

Three properties decide whether your page is used once it is fetched, and all three are ordinary engineering rather than content strategy.

- **Reachable.** No bot rule, CDN filter or challenge page between the agent and the content. Most blocks on assistants were inherited from an old anti-scraping policy rather than chosen.
- **Complete.** The facts a person would ask about are present in the text a parser sees, not rendered client-side and not implied by an image.
- **Cheap.** On the reference document capture, the same page fell from 13,581 bytes to 1,412 and the first fact moved from character 10,152 to line 8. Cheap pages survive truncation; expensive ones get summarised badly.

> **Nothing about your brand is generated** The validator rejects a variant containing a number or claim that did not come from a source field. A summary of your brand can be laid out by software; its substance is only ever your stored values.

## What to report internally

Report the measurements, label the samples, and resist converting the two into one number. A single blended "visibility score" combining exact server data with sampled prompt results is the metric most likely to be quietly wrong in a quarterly review.

1. **Baseline the templates.** One readability score per page kind, taken before any change.
2. **Report fetches and answer rate monthly.** Exact, from your own logs, and defensible.
3. **Track the miss log as a backlog**, not as a metric. It is a to-do list that happens to be ranked by demand.
4. **If you sample assistant answers, say so on the slide.** It is indicative, and treating it as a target invites optimising for a number nobody controls.

## What this does not do

- It cannot make an assistant mention you. Assistants are not deterministic and no vendor controls their output, so a guaranteed citation is not a thing anyone can sell.
- It does not watch assistants answer questions on your behalf. What it measures is your own server: who asked, what you served, and what you missed.
- It cannot correct what a model learned in training. Nothing published on your site edits an existing model’s weights, and no product can.
- It does not compare your brand to named competitors. Publication about any third party requires that domain owner’s verified opt-in.

## What is LLM brand visibility?

How well large language models can find and correctly state facts about your brand. It splits into training knowledge, which is frozen and not correctable by you, and retrieved knowledge, which comes from a live fetch of your pages and is entirely yours to fix.

## Why does an assistant describe our brand with outdated information?

Usually because it fell back on training knowledge instead of fetching you, and the common reason for that is that fetching you did not work or did not pay. Check whether the answer changes when the model is allowed to browse: if it does, the fix is on your server.

## How long until a change to our site shows up?

The retrieved half changes as soon as the page is fetched again, which depends on the platform and is outside your control. The training half does not change on any timeline you can plan around, so do not budget against it.

## Is there anything we can do about training data?

Very little, honestly. Publishing clear, current, machine-readable facts is the only durable input, and its effect is on future corpora rather than on the model answering today. Anyone offering to edit what a shipped model already believes is selling something that does not exist.

## Related

- [AI brand visibility](https://rebilder.com/solutions/ai-brand-visibility)
- [LLM visibility](https://rebilder.com/solutions/llm-visibility)
- [AI visibility: the half you control](https://rebilder.com/solutions/ai-visibility)
- [LLM SEO: what transfers from SEO](https://rebilder.com/learn/llm-seo)
- [Scan any URL free](https://rebilder.com/scan)