Claude-User
Anthropic documents Claude-User as a fetch made because a person asked Claude to retrieve a page. It remains a crawler User-Agent.
- Operator
- Anthropic
- Motif family
- anthropic
- Motif class
- User-requested fetch
- In Motif classifier
- Yes
- robots.txt
- Often a user-initiated fetch; do not assume robots.txt applies
- Executes JavaScript
- No
- Verified in Motif
- Vendor IP guidance exists. Motif does not check source IPs
What Motif will and will not claim
Motif classifies Claude-User as family anthropic, class user, on tracker or collector hits. It is not a visitor and is not the claude.ai referrer channel.
Revenue
The human click from claude.ai is first-touch Claude. Claude-User is a separate series on Insights.
Vendor documentation
Start with the vendor page at https://support.anthropic.com/en/articles/8896518-does-anthropic-crawl-data-from-the-web. Motif stores the controlled token from a self-reported User-Agent.
Claude-User User-Agent example
Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko); compatible; Claude-User/1.0; +Claude-User@anthropic.comAllow Claude-User in robots.txt
User-agent: Claude-User
Allow: /Block Claude-User in robots.txt
User-agent: Claude-User
Disallow: /Does Claude-User count as a visit in Motif?
No. If Claude-User hits the Motif tracker or collector it increments AI crawlers. It does not create a visitor and cannot win a recommendation.
Will Motif show Claude-User on my HTML pages?
Only if that client requested /m.js or POST /v1/events. HTML-only crawls of the origin never reach Motif. Saying otherwise would be a product lie.
Should I block Claude-User?
User-requested fetchers often ignore robots.txt because a person asked for the page. Blocking them in robots.txt may do nothing. They are still not visitors in Motif.