Perplexity-User
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 does not honour robots.txt, and a request claiming to be Perplexity-User can be checked against a published IP range file.
Perplexity-User at a glance
| User agent | Perplexity-UserToken only. The operator has not published a full user-agent string, so match on the substring rather than an exact header. |
|---|---|
| Operator | Perplexity |
| Purpose | Assistant fetchers |
| Respects robots.txt | Nosource |
| Verification method | Published 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. https://www.perplexity.com/perplexity-user.json |
| 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 …
Allow or block Perplexity-User
Paste one of these into the robots.txt file at the root of your domain. Rules are per token, so a block on one crawler leaves every other bot untouched. Perplexity-User is documented as ignoring robots.txt, so treat the block below as a statement of intent and enforce it at your CDN.
User-agent: Perplexity-User
Disallow: /Blocks every path for this crawler only.
User-agent: Perplexity-User
Allow: /Explicit allow. Useful when a wildcard rule above it would otherwise catch this crawler.
User-agent: Perplexity-User
Allow: /
Disallow: /account/
Disallow: /checkout/
Disallow: /searchEdit the Disallow paths to match your own account, checkout and search URLs.
What blocking actually costs you
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.
Block every crawler in the directory at onceIs that really Perplexity-User?
A user-agent header is a string the client chooses. Scrapers copy Perplexity-User precisely because site owners allow it. User-triggered fetch with its own published range file. Perplexity documents that this agent ignores robots.txt because a person asked for the page.
Paste the IP address from your access log below. You will see whether it belongs to a hosting provider, a residential proxy pool or a Tor exit, plus the ASN that announces it, which is what tells you whether the claim holds up.
Other crawlers run by Perplexity
Related crawlers
Identify crawlers automatically instead of by hand
Agentscan checks a request against published crawler ranges, reverse DNS and hosting data, then returns a verdict your edge can act on. One call per request, no range files to keep up to date.