Perplexity
Perplexity-User
Documented Provider-maintained crawler reference.
Perplexity-User supports user-requested retrieval in Perplexity. Perplexity says it is not used for automatic web crawling or foundation-model training and generally ignores robots.txt because the user requested the fetch. The provider publishes a separate IP-range endpoint for verifying legitimate Perplexity-User traffic.
Reference facts
- Provider
- Perplexity
- Provider identifier
- Reviewed provider reference mark
- robots.txt token
Perplexity-User- Purpose
- User-triggered retrieval
- Crawls pages
- Yes
- Obeys robots.txt
- No
- Search-visibility relevance
- Indirect
- Status
- active
- Information checked
Recommended policy notes
- Perplexity documents this token for user-initiated fetches.
- The provider states this fetcher generally ignores robots.txt because the user requested the retrieval; use real access controls for non-public content.
Common misconceptions
- That Perplexity-User and PerplexityBot have identical policy semantics.
- That a matching Perplexity-User robots.txt rule reliably controls every user-requested fetch.
Limitations
- A robots.txt parser can show the site's declared Perplexity-User rule, but the provider says this fetcher generally ignores robots.txt.
- Published IP ranges are time-sensitive and should be checked live for WAF or request-verification decisions.