What you can conclude
- PerplexityBot requested the recorded path.
- The server returned the recorded HTTP status.
- Published network evidence can strengthen verification.
See which pages Perplexity’s automated search crawler requests and whether your server returns successful, redirected, or missing responses.
PerplexityBot is Perplexity’s automated crawler for search discovery and index maintenance.
A PerplexityBot request is search-oriented crawler activity. Perplexity publishes crawler network information, while Talivia still reports verification as evidence-based confidence rather than cryptographic identity.
PerplexityBot/1.0Talivia looks for the stable PerplexityBot token in the normalized User-Agent.
User-agent: PerplexityBot
Allow: /
# To block instead:
# Disallow: /Use robots.txt to express an allow or block preference for this crawler.
When the integration supplies a source IP from a trusted network boundary, Talivia can compare it with provider-published ranges.
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 first matches the PerplexityBot User-Agent token. When a trusted source IP matches provider-published ranges, the request can receive stronger verification confidence.
Add a rule for PerplexityBot 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