What you can conclude
- The request matched the ClaudeBot User-Agent token.
- Talivia recorded the path, method, timing, and response status.
- The request is separated from Claude search and user fetches.
Measure Anthropic’s automated crawler separately from Claude search discovery and page retrieval initiated by a user.
ClaudeBot is Anthropic’s automated crawler for model development and improvement.
A ClaudeBot token identifies automated crawling described by Anthropic. Without a trusted, crawler-specific network match, Talivia keeps the request explicitly unverified rather than presenting User-Agent text as proof.
ClaudeBot/1.0Talivia looks for the stable ClaudeBot token in the normalized User-Agent.
User-agent: ClaudeBot
Allow: /
# To block instead:
# Disallow: /Use robots.txt to express an allow or block preference for this crawler.
The provider publishes crawler behavior guidance, but Talivia does not claim network identity is verified from a User-Agent token alone.
View official sourceTurn on collection in website settings.
Send the minimal event from trusted server code or middleware.
Review pages, statuses, trends, and verification confidence.
Talivia matches the ClaudeBot User-Agent token and labels the verification confidence explicitly. User-Agent text can be spoofed, so a token match alone is not an identity guarantee.
Add a rule for ClaudeBot in robots.txt and check the provider’s official documentation for behavior. robots.txt expresses crawl preferences; it is not access control or identity verification.
Talivia stores the hostname, sanitized path, method, User-Agent, optional status, classification, and verification result. It does not store page bodies, cookies, authorization headers, query strings, or raw IP addresses.
Start recording real requests with server-side tracking.
Add your website