Perplexity · User-triggered fetch
Perplexity-User
- Operator
- Perplexity
- Purpose
- User-triggered fetch
- Verification
- Published IP ranges
- Follows robots.txt
- Operator says it may ignore robots.txt
01Identify and verify
How it shows up in your logs
User-agent contains
Perplexity-User
Matching is case-insensitive. Anyone can send this string, so a match alone says only what the request claims to be.
Is it really Perplexity-User?
Plumb checks the request IP against the operator's published ranges.
Range checked: perplexity:user
02Publishers
How major publishers treat it
30%of 319 publishers on the leaderboard block
Perplexity-User outright (97). 154 more close some sections. 97 name it explicitly in their robots.txt.03robots.txt
A rule you can paste
The group names Perplexity-User exactly. A group for a different token from the same company does not cover it.
Perplexity says Perplexity-User generally ignores robots.txt, since a person asked for the page. A rule here records your preference; enforcing it takes a block at your CDN or firewall.
# Perplexity-User (Perplexity) User-agent: Perplexity-User Disallow: /
04Same operator
Perplexity's other agents
- PerplexityBotAI search indexing