Perplexity-User
Perplexity · User-triggered fetcher
Visits a page when a Perplexity user asks a question, to help answer it and link to the page.
Perplexity says that because a user requested the fetch, Perplexity-User generally ignores robots.txt rules.
- User-agent contains
Perplexity-User- robots.txt token
Perplexity-User- Respects robots.txt
- No
- Official IP ranges
- 4 prefixes
How to verify Perplexity-User
Matching the user agent isn't enough, because any client can send it. A real Perplexity-User request comes from an IP address inside Perplexity's published list:
- https://www.perplexity.ai/perplexity-user.json4 prefixes · list dated 2025-10-17 · fetched 2026-10-21
The quickest way to check a whole log is our free log checker. It runs in your browser and splits Perplexity-User requests into real and fake.
First 4 prefixes
44.208.221.197/32 34.193.163.52/32 18.97.21.0/30 18.97.43.80/29
Block or allow Perplexity-User in robots.txt
User-agent: Perplexity-User Disallow: /
Use Allow: / instead to explicitly permit it, or build a full file with the AI robots.txt generator. robots.txt is a request, not a lock: it only works for bots that honor it, and only real Perplexity-User traffic would.
Source: Perplexity documentation
Verify Perplexity-User automatically
One API call tells your app, WAF or middleware whether a request claiming to be Perplexity-User really comes from Perplexity's official IP ranges.