Assistant fetchers
Perplexity-User is a bot operated by Perplexity that fetches single pages on demand for an AI assistant. Perplexity-User supports user actions within Perplexity. It is documented as not following robots.txt, and a request claiming to be Perplexity-User can be checked against a published IP range file.
Request says
"Perplexity-User"
Checked against
Perplexity's published IP ranges
Live check
Paste the address from the log line. It is checked against what the operator publishes.
Reference
| User agent | Perplexity-UserToken only: match on the substring. |
|---|---|
| Operator | Perplexity |
| Purpose | Assistant fetchers |
| Respects robots.txt | Ignoressource |
| Verification method | IP rangesPublished IP range file User-triggered fetch with its own published range file. Perplexity documents that this agent ignores robots.txt because a person asked for the page. |
| Crawl pattern | Only when prompted by a user. |
| Robots.txt tokens | Perplexity-User |
| Operator documentation | https://docs.perplexity.ai/guides/bots |
Perplexity-User 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 …
robots.txt
Perplexity-User is documented as ignoring robots.txt. Enforce a block at your CDN too.
User-agent: Perplexity-User
Disallow: /User-agent: Perplexity-User
Allow: /User-agent: Perplexity-User
Allow: /
Disallow: /account/
Disallow: /checkout/
Disallow: /searchEdit the Disallow paths to match your own URLs.
Blocking Perplexity-User means a person who asks about one of your URLs gets an error instead of a summary. That is a support and reputation trade-off, not a training one.
Build a file for every crawlerFAQ
Perplexity-User is a bot operated by Perplexity that fetches single pages on demand for an AI assistant. Perplexity-User supports user actions within Perplexity. It is documented as not following robots.txt, and a request claiming to be Perplexity-User can be checked against a published IP range file.
No. Perplexity-User is documented as not following robots.txt, so a Disallow line will not stop it. Blocking needs to happen at the edge, by user agent or by source address.
User-triggered fetch with its own published range file. Perplexity documents that this agent ignores robots.txt because a person asked for the page. The reference is published at https://www.perplexity.com/perplexity-user.json.
Add the Perplexity-User token to robots.txt with Disallow: /. If the crawler ignores robots.txt, match the user agent at your CDN or reverse proxy and return 403 there instead.
Blocking Perplexity-User means a person who asks about one of your URLs gets an error instead of a summary. That is a support and reputation trade-off, not a training one.