AI search
Has ChatGPT actually read your website?
It is a knowable thing, and almost nobody is told the answer. Your server sees every one of these visits.
When an assistant reads a web page it identifies itself, the same way Google’s crawler has for twenty years. It says which company it belongs to and, usefully, why it has come.
That second part is the one worth understanding, because the two reasons are worth very different things to you.
Indexing, and answering
An indexing visit is a crawler building its picture of the web. It is reading you so that months from now, when somebody asks a question you can answer, you are a candidate. This is the groundwork, and it is what makes you eligible to be quoted at all.
A live visit is different, and it is the one that should make you sit up. Somebody is in a conversation with an assistant right now, they asked something, and the assistant has come to your page to answer them. It is the closest thing that exists to watching yourself be looked up.
The names to look for
If you can reach your server logs, these are what to search for.
| It calls itself | Who it is | What it means |
|---|---|---|
| GPTBot | OpenAI | Indexing. Reading your pages so ChatGPT can draw on them later. |
| OAI-SearchBot | OpenAI | Indexing, for the search side of ChatGPT. |
| ChatGPT-User | OpenAI | Live. Somebody asked ChatGPT a question and it came to read your page to answer them. |
| ClaudeBot | Anthropic | Indexing. |
| Claude-User | Anthropic | Live. A person is in a conversation with Claude right now. |
| PerplexityBot | Perplexity | Indexing. |
| Perplexity-User | Perplexity | Live, on behalf of somebody asking. |
| Google-Extended | Indexing, for Gemini and AI answers. | |
| Applebot-Extended | Apple | Indexing, for Apple Intelligence. |
Why your analytics shows none of this
Nearly every website statistics tool works by running a small piece of JavaScript in your visitor’s browser. That is how it knows somebody arrived, how long they stayed and what they clicked.
An assistant runs no JavaScript. It asks the server for the page, reads the text, and goes. There is no browser, so the counter never fires, and your dashboard says nothing happened.
Counting these means counting on the server, where the request actually arrives. That is what we do on every site we run, and it is why we can tell you which assistant, which page, and whether it was indexing or answering somebody live.
A user agent is a claim, not proof
Anyone can send a request calling itself GPTBot. It takes one line on a laptop. A number built from those claims without checking them is a number you should not act on.
The check is the network address. Each of these companies publishes the ranges its crawlers come from, and a read from outside them is a claim rather than a fact. We show those as unconfirmed instead of throwing them away, because a genuine crawler on a newly published address is not a liar either.
What nobody can tell you
Whether the assistant then recommended you. Those conversations are private and no one outside those companies can see inside them.
Reading is not citing. If somebody offers to report how many times ChatGPT recommended your business, they are estimating, and you should ask them how before you pay for it.
Questions people ask
How do I know if ChatGPT has read my website?
Why does my analytics not show this?
Does an assistant reading my site mean it is recommending me?
Can somebody fake being ChatGPT?
Should I block AI crawlers?
Related: why an assistant might not be mentioning you and what llms.txt is.
We show you every one of these.
Which assistant, which page, and whether somebody was asking. On every site we run.
Start your free websiteWould rather talk to someone first? Ask us to come out
