What you can conclude
- A request matching Claude-User reached the page.
- You can inspect timing, path, method, and HTTP status.
- The event stays separate from human visitor analytics.
Inspect Anthropic user-triggered page retrieval without inventing a prompt, citation, or human session that the server event cannot reveal.
Claude-User represents a page retrieval initiated by a person using Claude.
The request is associated with a user-directed fetch rather than autonomous site-wide crawling. Talivia records the server event but does not receive the person, prompt, or resulting Claude response.
Claude-User/1.0Talivia looks for the stable Claude-User token in the normalized User-Agent.
User-agent: Claude-User
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 Claude-User 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 Claude-User 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