Perplexity
PerplexityBot
Indexes pages for Perplexity search, not foundation-model training.
AI searchUser-requested fetch
Perplexity-User
Fetches pages on behalf of Perplexity users.
Operated by Perplexity
See your agent traffic PurposeUser-requested fetch
HTTP identifierPerplexity-User
IdentityVerify beyond the name
THE SIGNAL
What this visit tells you
An on-demand fetch suggests a retrieval task. The log cannot reveal whether the resulting answer persuaded a buyer.
Requested public pages
Public-page 403 and 404 responses
Subsequent page requests
Your next move
Investigate public-page 403s alongside authentication and edge rules. Keep protected account pages protected.
The technical details
MarkdownHow to identify it
Look for the Perplexity-User identifier in a request’s User-Agent. This is a name match, not identity verification. Version strings may change.
How to check identity
Compare the request IP with the current operator-published ranges linked in the source. A matching name alone does not verify identity.
Access and robots.txt
Generally ignores robots.txt because visits are user-requested.
Seeing 403 or 404 responses?
403 means access was denied; 404 means the resource was not found. Compare the public path, request time, edge security event and origin response to find the cause.
Separate intended restrictions and secret-file probes from pages that should work. A User-Agent name alone does not justify allowing a request.
SourcesReviewed 2026-09-14
Identity and purpose are based on these sources. Analytics interpretation and suggested checks are Apostl guidance.
APOSTL PulseSee Perplexity-User in context
See their requests. Find the pages that matter.
See your agent trafficKEEP EXPLORING
Different bots, different intent
OpenAI
ChatGPT-User
Fetches pages for user actions in ChatGPT and custom GPTs.
User-requested fetch