Perplexity-User

What does Perplexity-User do?

Perplexity-User fetches web pages on demand when a Perplexity user asks a question that requires live web content. It gathers the information needed to generate an answer in the Perplexity answer engine. Perplexity includes clickable citation links back to source pages in its responses, creating a direct referral traffic path to your site.

Should I allow and optimize for Perplexity-User to drive organic growth?

Perplexity-User directly powers the Perplexity answer engine, which includes clickable citation links to source pages in every response. This is one of the most direct referral traffic paths among AI agents. Allowing Perplexity-User means your content can appear as a cited source when millions of Perplexity users ask relevant questions. Blocking it removes your site from real-time answer generation entirely, even if PerplexityBot has already indexed your pages.

Data Usage & Training

Content fetched by Perplexity-User is not used to train foundation AI models. Perplexity states that user-driven fetches are used immediately to satisfy the user's query and are not used for pre-training. A separate crawler, PerplexityBot, handles indexing, and its data usage policies differ.

How Perplexity-User Accesses Content

Here's how Perplexity-User accesses your site and understands your content:

• Fetches HTML via standard HTTP requests when triggered by a user query
• Partial JavaScript rendering support
• Identifies as Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; Perplexity-User/1.0; +https://perplexity.ai/perplexity-user)
• Published IP ranges available at https://www.perplexity.com/perplexity-user.json
• Does not support Crawl-delay directives

Strictly on-demand. Perplexity-User only fetches pages when a user's query requires live web content. There is no scheduled or continuous crawling from this agent.

How to Block or Control Perplexity-User

To block Perplexity-User via robots.txt: User-agent: Perplexity-User Disallow: / However, Perplexity-User may not fully respect robots.txt for user-initiated fetches. Perplexity's own documentation describes it as a user-requested fetcher that generally bypasses robots.txt. For reliable blocking, combine User-Agent matching with IP prefix checks using the published ranges at https://www.perplexity.com/perplexity-user.json. Configure WAF rules that match both the User-Agent header and source IP prefixes. Robots.txt alone is frequently insufficient.

Common Issues & Troubleshooting

Watch out for these common problems when working with Perplexity-User:

• Robots.txt directives alone may not block Perplexity-User, since user-initiated fetches can bypass them
• Some requests arrive with generic or browser-like User-Agent strings rather than the declared Perplexity-User UA
• Requests sometimes originate from IPs or ASNs not listed in the published JSON endpoints
• CloudFlare and other CDN bot protection may not recognize Perplexity-User by default, requiring custom WAF rules
• Crawl-delay is not supported, so you cannot rate-limit through robots.txt alone
• BrowserBase or proxy-based traffic from Perplexity may appear under different fingerprints in your logs