AI crawlers · Answer engines
Perplexity-User
Perplexity-User is the user-triggered fetch run by Perplexity: Perplexity live fetch. Its operator publishes the IP ranges it crawls from (https://www.perplexity.ai/perplexity-user.json), so a request carrying the name can be checked against that list.
| User-agent token | Perplexity-User |
| Operator | Perplexity |
| What it does | Perplexity live fetch |
| Kind | user-triggered fetch |
| Can a request be verified? | Yes — published ip feed |
| Verification source | https://www.perplexity.ai/perplexity-user.json |
| In a CrawlCheck scan | Read from robots.txt; a refusal is scored |
Allow or block it in robots.txt
User-agent: Perplexity-User Disallow: /
User-agent: Perplexity-User Allow: /
Add a group that names it: "User-agent: Perplexity-User" followed by "Disallow: /". A crawler follows only the most specific group that names it, so once a group names Perplexity-User, rules under "User-agent: *" no longer apply to it; repeat in that group any Disallow lines you still want.
What blocking it changes
Yes. It is how Perplexity reaches a page to answer a question at the moment a person asks, so refusing it stops that engine reading the site.
What it actually did on crawlcheck.io
| Verified requests | 8 |
| Requests using its name from outside its operator's ranges | 51 (86.4% of claims) |
| robots.txt fetched | 0 times |
| Fetches of paths robots.txt disallows | 0 |
| Observed | 2026-08-14 to 2026-10-23 |
Measured on this site’s own traffic, verified against the operator’s published ranges. Every agent’s record: agent conduct.
Other agents from Perplexity
PerplexityBot— Perplexity index
See what Perplexity-User and every other named agent receive from your own site: run a free scan. The full catalogue is on AI crawlers and as JSON at /ai-crawlers.json.