36.4%

Not from Perplexity AI

7

Verified source IPs

19

Impostor source IPs

Published IP ranges

Verification

Measured across detections recorded by WebDecoy, mostly on WebDecoy's own properties, 2025-11-14 to 2026-08-19. A small sample, not the whole web.

What PerplexityBot is

Indexes pages so Perplexity can cite them in answers.

It identifies itself with a User-Agent containing PerplexityBot/1.0; +https://perplexity.ai/perplexitybot. Its robots.txt token is PerplexityBot , and it is listed as honouring robots.txt. Operator documentation: Perplexity AI .

How much of this traffic is actually PerplexityBot

Perplexity AI publishes the IP ranges its crawler operates from, so this has a real answer rather than an opinion. We took every request in our corpus declaring this User-Agent and checked its source address against that published list.

ResultSource addressesShare of traffic
Verified. Inside a published Perplexity AI range763.6%
Failed. Outside every published range1936.4%

36.4% of traffic claiming to be PerplexityBot could not be traced back to Perplexity AI. It is something else wearing the name. Most sites wave this User-Agent straight through without checking, which is exactly why the name is worth wearing.

Verifying it yourself

Perplexity AI publishes the ranges PerplexityBot crawls from. Fetch them and test the source address:

# 1. fetch the published ranges
curl -s -o ranges.json \
  https://www.perplexity.ai/perplexitybot.json

# 2. check an address against them
python3 - 203.0.113.42 <<'PY'
import json, sys, ipaddress
ip = ipaddress.ip_address(sys.argv[1])
data = json.load(open('ranges.json'))
hit = any(ip in ipaddress.ip_network(p.get('ipv4Prefix') or p['ipv6Prefix'])
          for p in data['prefixes'])
print('verified' if hit else 'NOT VERIFIED')
PY

Swap in the address you are checking. Never trust the User-Agent on its own: it is a header the client picks for itself.

Blocking it

If you want the real crawler to stay away, robots.txt is the polite way to ask:

User-agent: PerplexityBot
Disallow: /

robots.txt only works on a client willing to obey it, which rules out every request that was already lying about who it is. Stopping those takes enforcement at the network or application layer, keyed on something the client cannot simply retype. That is the problem WebDecoy exists to solve.

Frequently Asked Questions

What is PerplexityBot? +

PerplexityBot is an ai search crawler operated by Perplexity AI. Indexes pages so Perplexity can cite them in answers.

Is PerplexityBot a real crawler or is it being faked? +

Both. PerplexityBot is a genuine crawler operated by Perplexity AI, but 36.4% of the traffic we observed carrying its User-Agent did not come from an IP address in Perplexity AI's published range list. Only 7 of the source addresses using this name verified against that list; 19 did not.

How do I verify PerplexityBot? +

Perplexity AI publishes the IP ranges PerplexityBot uses at https://www.perplexity.ai/perplexitybot.json. Check whether the request's source address falls inside one of those prefixes, and reject it if it does not. Never match on the User-Agent alone, because that is the part a client chooses for itself.

How do I block PerplexityBot? +

Add a robots.txt rule for the token PerplexityBot. That stops the real crawler, but not clients that only borrow its name, so pair it with verification and enforcement at your edge.

Methodology

Every request recorded by WebDecoy's sensors, mostly on WebDecoy's own properties, whose User-Agent declares one of these crawlers, checked IP-by-IP against the operator's own published IP range list. A request is counted as verified when its source IP falls inside a published prefix, and forged when it does not. Operators that publish no machine-readable range list cannot be checked this way and are reported without a forgery figure. Corpus: 81,034 detections from 17,187 distinct addresses, 2025-11-14 to 2026-08-19. Published ranges retrieved 2026-08-19. Operators revise their ranges over time, so a request logged months ago is checked against today's list; we re-ran the comparison over a recent 30-day window and the rates held.

This crawler dataset is licensed under CC BY 4.0; reuse is permitted with attribution to WebDecoy.

See which PerplexityBot requests are real

WebDecoy verifies declared crawlers against what their operators publish and identifies the ones that fail, as persistent actors rather than disposable IPs.

Start Free Trial