PerplexityBot: robots token, verification and how to allow or disallow it
PerplexityBot is an AI crawler operated by Perplexity. Its robots.txt token is PerplexityBot, and the vendor documentation we fetched on 2026-09-06 is the source for every statement on this page.
| Robots token | PerplexityBot |
|---|---|
| Vendor | Perplexity |
| Purpose | search index |
| Documented verification | published IP ranges |
| Vendor documentation last verified | 2026-09-06 |
| Share of read domains disallowing it for / | 7.8% of 128 |
| Last verified |
Identity
| Robots token | PerplexityBot |
|---|---|
| Matched as | perplexitybot |
| Vendor | Perplexity |
| Purpose | search index |
| Documentation | https://docs.perplexity.ai/guides/bots |
| Documented verification | published IP ranges: https://www.perplexity.ai/perplexitybot.json |
Vendor documents the full UA 'PerplexityBot/1.0; +https://perplexity.ai/perplexitybot' and recommends combining UA matching with IP verification when writing WAF rules.
Allow or disallow it
User-agent: PerplexityBot Allow: /
User-agent: PerplexityBot Disallow: /
A robots.txt rule is a request that a well behaved crawler honours. It is not an access control, and this page does not tell anyone what to choose.
Questions
Does PerplexityBot obey robots.txt?
The vendor documentation at https://docs.perplexity.ai/guides/bots states that PerplexityBot respects robots.txt. We fetched that page and it answered our checker on 2026-09-06. This records what the vendor documents, not what any individual request did.
How do I allow PerplexityBot in robots.txt?
Add this group to the robots.txt at the root of the host: User-agent: PerplexityBot Allow: /. The token is matched case insensitively as a substring of the user agent by RFC 9309, and the longest matching rule wins.
How do I disallow PerplexityBot in robots.txt?
Add this group to the robots.txt at the root of the host: User-agent: PerplexityBot Disallow: /. A robots.txt rule is a request that a well behaved crawler honours; it is not an access control.
How do I verify a request really came from PerplexityBot?
The vendor publishes the IP ranges this crawler fetches from at https://www.perplexity.ai/perplexitybot.json. Check the address of the request against that file. A user agent string on its own proves nothing, because anyone can send one.
What we measure
Of the 128 seeded domains whose robots.txt we have read, 10 disallow PerplexityBot for / and 118 allow it, which is 7.8% disallowed, week 2026-W37. Counts only: no domain is named.
The weekly AI crawler access index
Sources
| Source | Type | HTTP | Verified | Note |
|---|---|---|---|---|
| https://docs.perplexity.ai/guides/bots | vendor | 200 | 2026-09-06 | 24 occurrences of PerplexityBot in the fetched body |
| https://www.perplexity.ai/perplexitybot.json | vendor | 200 | 2026-09-06 | published IP ranges |
Free data
Check a domain against every token
AEO Watch is an independent, factual monitor. It is not affiliated with, endorsed by or speaking for any crawler vendor. Every statement is an observation with the date it was made and the raw evidence behind it: a robots.txt line, an HTTP status code, a header. There are no scores, no grades and no verdicts here, and nothing on this page is advice. A site opts out at any time and the opt out is honoured automatically and permanently.