# Claude-User

Claude-User fetches a page live when a Claude user's question needs it, for example when the user pastes a link or the assistant decides to read a source. A visit from it is a strong signal that your page is being used in a real answer.

## Should you allow Claude-User?

**Allow it.** Claude-User acts for a person who is asking about your page right now. Blocking it means the assistant answers without your page, often citing someone else instead.

## robots.txt

To allow Claude-User everywhere:

```text
User-agent: Claude-User
Allow: /
```

To block it:

```text
User-agent: Claude-User
Disallow: /
```

Bots follow the most specific `User-agent` group that matches them. If you have a `User-agent: Claude-User` group, the rules under `User-agent: *` no longer apply to it. Matching on the token is case-insensitive.

## Identifying Claude-User

Claude-User identifies itself with `Claude-User` in its `User-Agent` header. It **does not run JavaScript**: it reads the raw HTML only. Content your site adds with JavaScript is invisible to it.

Anthropic doesn't publish a machine-readable IP range list for Claude-User that we verify against, so treat the user agent alone as unverified. `bots_report` marks these hits as unverifiable rather than genuine.

## Check your site

```bash
llmentions audit example.com            # is Claude-User allowed by robots.txt, and what does it see?
llmentions bots /var/log/nginx/access.log   # did Claude-User really visit, and is it genuine?
```

Or identify any user agent over REST (free): `GET https://api.llmentions.com/v1/bots/lookup?ua=Claude-User`.

## Other Anthropic bots

- [ClaudeBot](/bots/claudebot/): AI training crawler
- [Claude-SearchBot](/bots/claude-searchbot/): AI search indexer

---
https://llmentions.com/bots/claude-user/
