# [AI visibility: the half you actually control](https://rebilder.com/solutions/ai-visibility)

> AI visibility splits into two halves. One is a property of your own server and you can measure it today; the other nobody controls. Here is which is which.

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

AI visibility is usually sold as one number. It is really two things: whether assistants can read your pages at all, and whether they choose to mention you. Only the first is yours.



## What you get

- Score any URL against a published spec, free and without an account
- See exactly what an agent receives from your site, byte for byte
- Find the pages agents asked for and did not get
- Fix the serving layer in an afternoon, not a quarter

## The two halves of AI visibility

Every conversation about AI visibility mixes two questions that behave completely differently. Separating them is the first useful thing you can do, because one has a deterministic answer you can act on today and the other does not have an answer at all.

|  | Retrievability | Mention |
| --- | --- | --- |
| The question | Can an assistant read your page? | Will it name you in an answer? |
| Where it lives | Your server | Somebody else’s model |
| Is it deterministic | Yes. Same request, same response | No. Same prompt, different answers |
| Can you change it | Directly, today | Only indirectly, over time |
| How you measure it | Request it and look | Sample prompts and hope the sample holds |

Most tools sold as AI visibility platforms measure the right-hand column. That is a real thing to want to know, but it is a lagging indicator of the left-hand column, and a site that fails the left cannot be fixed by watching the right more closely.

> **The thirty-second version** Run `curl -H 'Accept: text/markdown' https://your-site/key-page` next to a plain `curl`. If both return the same theme HTML, your AI visibility problem is on your own server and no tracker will tell you anything you cannot see right there.

## What actually makes a site invisible

In the scans we run, invisibility is almost never subtle. It is one of four things, and they fail in this order, with the earlier ones making the later ones irrelevant.

1. **The fetch never lands.** A `robots.txt` line, a CDN bot rule, or a challenge page written years ago against scrapers. Nothing on your side logs an error, because from your side nothing happened.
2. **The response needs a browser.** Prices, hours or fees that appear only after JavaScript runs are absent from what the agent receives, because the fetch runs no JavaScript.
3. **The facts are too expensive to reach.** The agent reads under a token budget. A first substantive fact sitting behind tens of thousands of characters of navigation may be summarised badly or skipped for a shorter source.
4. **The facts disagree with each other.** Your prose says one thing, your structured data says another. The assistant picks one, confidently, and you do not get to choose which.

## How to measure the half you own

Three instruments, none of which is a dashboard of somebody else’s model output. Each answers a question about your own infrastructure, so each has a definite answer.

- **A readability score against a published spec.** Deterministic and rebuildable: the same page scores the same today and next month unless the page changed. The [spec is public](/spec/ars) so you can check the arithmetic.
- **Your own request log, by agent.** Which platforms fetched you, how often, and what you served each one. This is impressions for the agent era, and it comes from your server rather than a sample.
- **The miss log.** The URLs agents asked for and did not get. It is the highest-value document in the whole project, because it names your next fix in the order the market is asking for it.

> **Your analytics cannot see any of this** Agent fetches run no JavaScript and fire no beacon, so a page-view script structurally cannot record them. A team measuring AI visibility from one will conclude nothing is happening no matter what is happening.

## The fix is smaller than the category suggests

The serving-layer work is a one-time change rather than an ongoing programme, which is the part the market gets wrong. You answer `Accept: text/markdown` with the same facts in a cheaper format, and you keep serving browsers and search crawlers exactly what you served them before.

middleware.ts

```ts
import { gateway } from '@rebilder/gateway'

export default gateway({
  source: { kind: 'document', resolve: myPages },
})
```

That is the whole intervention for most sites. The free tier covers 1,000 agent visits a month, the SDK is open and self-hostable, and nothing about it is metered at the edge.

## 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 does not score your competitors, and it never will. Nothing about a named third party is published without that domain owner opting in.
- A score is not a ranking. There is no position in a generated answer to hold, so any product showing you an average position in one has invented it.

## What is AI visibility?

It is whether AI assistants can find, read and use your pages. In practice it splits in two: retrievability, which is a property of your own server and is measurable exactly, and mention, which is a property of somebody else’s model and is not controllable by anyone.

## How do I check my AI visibility?

Request one of your own pages with `Accept: text/markdown` and compare it to a plain request. Then score a page of each template against a published spec to get a number you can track. Both are free and neither needs an account.

## Is AI visibility the same as SEO?

It builds on it. Crawlability, fast responses and accurate structured data all still count. What changes is that the reader is a parser on a token budget, so layout stops helping, client-rendered content stops existing, and the size of your markup starts working against you.

## Can a tool guarantee my brand appears in AI answers?

No, and it is worth being blunt about it. Assistants are not deterministic and no vendor controls their output. What can be committed to is the layer you own: whether the fetch is answered, how big the response is, and where your facts sit in it.

## Does improving AI visibility hurt my Google rankings?

No. Content negotiation returns the same substance in a different format, and search crawlers keep receiving canonical HTML. Serving different prices or availability by requester would be cloaking; a format transformation of identical facts is not.

## Related

- [AI search optimization: the definitive guide](https://rebilder.com/learn/ai-search-optimization)
- [LLM visibility](https://rebilder.com/solutions/llm-visibility)
- [AI brand visibility](https://rebilder.com/solutions/ai-brand-visibility)
- [AI visibility tracking](https://rebilder.com/solutions/ai-visibility-tracking)
- [AI visibility tools: how to choose one](https://rebilder.com/learn/ai-visibility-tools)
- [Scan any URL free](https://rebilder.com/scan)