Perplexity-User
Perplexity · User-requested fetches
What Perplexity says it does
“supports user actions within Perplexity. When users ask Perplexity a question, it might visit a web page to help provide an accurate answer and include a link to the page in its response.”
The facts
| Operator | Perplexity |
| robots.txt token | Perplexity-User |
| Appears in access logs | Yes |
| User-agent string | Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; Perplexity-User/1.0; +https://perplexity.ai/perplexity-user) |
| robots.txt | Generally ignores robots.txt. Perplexity's own words: since a user requested the fetch, this fetcher generally ignores robots.txt rules. |
| IP list | https://www.perplexity.com/perplexity-user.json |
| Documentation | https://docs.perplexity.ai/guides/bots, read 4 Aug 2026 |
Allow or block it in robots.txt
To block Perplexity-User entirely:
User-agent: Perplexity-User Disallow: /
To allow it everywhere:
User-agent: Perplexity-User Allow: /
Perplexity's stated position: generally ignores robots.txt. Perplexity's own words: since a user requested the fetch, this fetcher generally ignores robots.txt rules. Blocking it reliably means blocking at the server, not in robots.txt.
Verify a request is really Perplexity-User
Match the requesting IP against the published list.
A hit from Perplexity-User means a person asked Perplexity something and it opened this page to answer.
Observed on this property
| First seen here | 24 Aug 2026 |
| Most recent | 13 Sep 2026 |
| Requests, last 30 days | 149 |
| Requests, all time | 149 |
| robots.txt fetches | 0 |
Most requested paths:
/@fs/root/.aws/credentials.backup(3)/privatekey.key(3)/aws-exports.js(2)/client_secret.json(2)/config.env(2)/.env(2)/.env.backup(2)/fetch/(2)
Also run by Perplexity
- PerplexityBot | AI search index