What you can conclude
- A request matching Perplexity-User reached the page.
- The path, method, timestamp, and status can be inspected.
- The request is excluded from human analytics totals.
Inspect Perplexity user-triggered page retrieval without treating a server request as proof of a citation, click, or conversion.
Perplexity-User represents a page fetch associated with a person using a Perplexity product.
The identity describes a user-triggered fetch, not the autonomous PerplexityBot indexing crawler. Talivia keeps the request separate while avoiding claims about the person, query, or final answer.
Perplexity-User/1.0Talivia looks for the stable Perplexity-User token in the normalized User-Agent.
User-agent: Perplexity-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 Perplexity-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 Perplexity-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