Perplexity-User
- User-agent token
- Perplexity-User
- Purpose
- User-triggered
- Status
- active
- Last verified
- 2026-09-08
Perplexity documents Perplexity-User as supporting “user actions within Perplexity. When users
ask Perplexity a question, it might visit a web page to help provide an accurate answer” and
include relevant links in the response. Perplexity states it is “not employed for web crawling or
AI model training.”
Why this is different from PerplexityBot
Perplexity-User requests are triggered by a specific person’s question, not a bulk crawl. It is
tracked separately from the search-indexing PerplexityBot.
A robots.txt limitation worth knowing
Perplexity’s own documentation states that, “since a user requested the fetch, this fetcher
generally ignores robots.txt rules.” A Disallow rule aimed at Perplexity-User is not a
reliable way to prevent this specific page from being fetched on a user’s behalf — this is a
documented, deliberate design choice by Perplexity, not a CrawlPact-observed workaround. See
/limitations for what a robots.txt rule can and cannot guarantee more generally.
Site-owner controls
A robots.txt rule for Perplexity-User may not be honoured, per Perplexity’s own documentation
above — this differs from PerplexityBot, which does respect robots.txt.
Example robots.txt configuration
To disallow Perplexity-User specifically, without affecting any other crawler:
User-agent: Perplexity-User
Disallow: /If no dedicated User-agent: Perplexity-User group exists in a domain's robots.txt, this crawler falls back to whatever the wildcard User-agent: * group says (RFC 9309) — see robots.txt syntax basics for how group selection works.
Verified against the source above as of 2026-09-08 — see how CrawlPact verifies crawler information.
See how this applies to your own site
Run a free audit to check your declared AI crawler policy against your own domain, or use the AI crawler checker to check this one crawler specifically.
Audit a domain