What it does
Perplexity-User is Perplexity's user action crawler. A live fetch made because a human asked the assistant about your page right now. Closest thing to a real visitor; several of these (Perplexity-User, meta-externalfetcher) ignore robots.txt by design because the request is user-initiated.
Vendor's own docs: 'Since a user requested the fetch, this fetcher generally ignores robots.txt rules.' Blocking requires WAF/IP rules, not robots.
Full UA: not captured in our July 2026 roster review — match log hits on the token Perplexity-User (case-insensitive substring) and verify by IP before acting.
How to verify a hit is really Perplexity-User
Verification method (July 2026): Published IP list: https://www.perplexity.com/perplexity-user.json (fetched live 2026-08-22)
Strongest available check: the vendor publishes the crawler's egress IPs. Fetch the list, then confirm the hit's source IP falls inside it — a UA match from any other IP is a spoofer.
User-agent strings are freely spoofed, so a UA match alone proves nothing. Full step-by-step method: verify by IP.
Allow or block in robots.txt
Match the exact token Perplexity-User in robots.txt:
# Block Perplexity-User site-wide
User-agent: Perplexity-User
Disallow: /# Explicitly allow Perplexity-User
User-agent: Perplexity-User
Allow: /For the allow-search-block-training combined pattern (and the Allow-directive gotcha that silently kills carve-outs), see the robots.txt guide. robots.txt governs whether Perplexity-User may fetch; llms.txt is the separate, curated map AI assistants read once allowed in.
Vendor documentation: https://docs.perplexity.ai/guides/bots
The Perplexity family
Perplexity operates 2 distinct tokens in this roster, and they do not block each other: a robots.txt line for Perplexity-User does nothing to its siblings — each needs its own User-agent: entry (the robots.txt guide has combined patterns).
| Token | Role | robots.txt |
|---|---|---|
| PerplexityBot | AI search | claims robots compliance |
Frequently asked questions
What is Perplexity-User?
Perplexity-User is Perplexity's user action crawler. A live fetch made because a human asked the assistant about your page right now. Closest thing to a real visitor; several of these (Perplexity-User, meta-externalfetcher) ignore robots.txt by design because the request is user-initiated.
Does Perplexity-User respect robots.txt?
No — Perplexity-User does not treat robots.txt as binding. Blocking it requires WAF or IP-level rules.
How do I block Perplexity-User?
robots.txt cannot stop Perplexity-User; block it with WAF or IP-level firewall rules instead.
How do I verify Perplexity-User traffic by IP?
Fetch Perplexity's published IP list for Perplexity-User and confirm the hit's source IP falls inside it — a Perplexity-User user-agent from any other IP is a spoofer.
Related bots
Same vendor, then other user-action fetchers — the full directory profiles all 34.