Perplexity-User
User-requested fetch. Perplexity's user-initiated fetcher for visiting pages while answering a user's question.
Perplexity · User-requested fetch
AI crawler directory / Perplexity-User
Perplexity-User robots.txt reference.
Perplexity's user-initiated fetcher for visiting pages while answering a user's question.
20observed domains
2disallowed
13partial policies
4allowed by matched rules
What Perplexity-User is documented to do
This summary is tied to a first-party operator page reviewed on Sep 20, 2026. It should be rechecked when the registry version changes.
- Operator
- Perplexity
- Documented purpose
- User-requested fetch
- Separate HTTP fetcher
- Documented as a fetcher or crawler
- Official documentation
- https://docs.perplexity.ai/docs/resources/perplexity-crawlers
- Important operator note
- Perplexity says this user-triggered fetcher generally ignores robots.txt.
PerplexityBot vs Perplexity-User
Perplexity documents these tokens for different purposes. A rule for one does not automatically control the others.
PerplexityBot
AI search. Perplexity's automatic search crawler for surfacing and linking websites in Perplexity search results.
Common full-site robots.txt block pattern
This example states a crawl preference for the named token. It does not authenticate requests, enforce blocking, or automatically control another token from the same operator.
User-agent: Perplexity-User
Disallow: /Check the official operator source before publishing a policy. User-requested fetchers and non-fetcher control tokens can have different behavior from automatic crawlers.
Latest observed pilot policies
These states are calculated from each domain's latest available robots.txt record using the versioned CrawlLedger parser. They are observations of published text, not proof of crawler behavior.
| Domain | Parsed state | Matched group | Last observed |
|---|---|---|---|
| anthropic.com | allowed | * | |
| apnews.com | partial | * | |
| apple.com | partial | * | |
| cloudflare.com | allowed | * | |
| commoncrawl.org | partial | * | |
| google.com | partial | *, Yandex | |
| medium.com | partial | * | |
| openai.com | partial | * | |
| oreilly.com | partial | ChatGPT-User, ChatGPT-User/2.0, PerplexityBot, Perplexity-User, DuckAssistBot, Applebot, bingbot, Googlebot | |
| perplexity.ai | partial | * | |
| quora.com | partial | * | |
| reddit.com | disallowed | * | |
| rslcollective.org | allowed | * | |
| rslstandard.org | allowed | * | |
| stackoverflow.com | unverified | No matching group observed | |
| theguardian.com | partial | * | |
| usatoday.com | disallowed | Perplexity-User | |
| voxmedia.com | partial | * | |
| yahoo.com | partial | * | |
| ziffdavis.com | partial | * |
Interpret the state carefully
“Allowed” means a selected group was observed without a blocking rule for the tested policy shape. “Partial” means at least one non-empty disallow path was observed. “No matching group” is silence, not an affirmative grant. None of these states authenticate the requester or establish legal permission.