AI crawler · registry

Perplexity-User

Perplexity · Live retrieval · robots.txt token perplexity-user

ignores robotsMeasured across 30,177 sites with a robots.txt policy record for this agent, out of 30,185 on record.
The measurement

2% of 30,177 measured domains disallow perplexity-user in robots.txt at the site root. Separately, and independently of robots.txt, 17.4% of 30,185 reachable domains refuse an AI crawler user agent at the network edge on two consecutive probes from different locations - a refusal the site's own robots.txt does not declare and its owner often has not chosen.

Measured 2026-10-06 by direct request to every domain in the corpus. Method: how this is measured. Reuse under CC BY 4.0 with attribution.

Cite as: Crawl Census, "Perplexity-User blocking rate", measured 2026-10-06. https://crawlcensus.com/bot/perplexity-user

2%
of measured sites block it
469
sites blocking
29,708
sites allowing
no
honors robots.txt

What it is definition

Fetches a page for a specific user question; Perplexity documents that it generally ignores robots.txt.

Perplexity-User is operated by Perplexity and classified here as live retrieval. These agents fetch a single URL because a user asked about it. Disallowing one means the assistant answers from an older copy or from someone else's summary instead of the live page. Several are documented as not bound by robots.txt, because the request is user-initiated rather than a crawl.

Disallowing perplexity-user stops the fetch that happens when a user asks Perplexity about one of your URLs. The answer still gets written, from an older copy or from a third party's description of the page, and you no longer control what it says.

Perplexity documents that this agent may fetch pages regardless of robots.txt. A disallow is recorded here because it states intent, but it is not the control.
robots.txt token
perplexity-user
Operator
Perplexity
Purpose
Live retrieval
Honors robots.txt
no
Documentation
https://docs.perplexity.ai/docs/resources/perplexity-crawlers

Identity on the wire exact string

User-agent string
Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; Perplexity-User/1.0; +https://perplexity.ai/perplexity-user)
Verify your own edge is not refusing it
curl -A 'Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; Perplexity-User/1.0; +https://perplexity.ai/perplexity-user)' https://example.com/

Replace the host with your own. A 403, a challenge page or an empty body means the edge is blocking the agent whatever robots.txt says.

How to allow it, how to block it robots.txt

Allow it
User-agent: perplexity-user
Allow: /

Absent any rule, the agent is already allowed, so this group only matters when your * group disallows something. Naming the agent replaces the * group for it entirely, so repeat here every disallow you still want to apply to it.

Block it
User-agent: perplexity-user
Disallow: /

Disallowing perplexity-user stops the fetch that happens when a user asks Perplexity about one of your URLs. The answer still gets written, from an older copy or from a third party's description of the page, and you no longer control what it says.

robots.txt is not sufficient for this agent. Block on the user-agent string at the edge, and back it with a deny rule covering the address ranges Perplexity publishes for this agent. Independent testing has recorded retrieval from addresses outside those ranges and without the declared token, so a managed bot rule that scores the request holds up better than a static list.

Sites that block it 60 shown

DomainAI access scoreRank
amazon.com 40 26
tiktok.com 47 54
msn.com 41 62
nytimes.com 48 157
cnn.com 50 190
bbc.com 77 207
bbc.co.uk 78 226
amazon.co.uk 40 318
amazon.de 40 377
amazon.co.jp 40 494
ft.com 58 519
wired.com 81 533
usatoday.com 75 552
uol.com.br 82 571
telegraph.co.uk 52 580
amazon.fr 40 609
amazon.co.za 40 623
dailymail.co.uk 57 627
amazon.ca 40 635
elpais.com 85 647
amazon.in 40 659
cnet.com 79 662
dailymail.com 57 681
primevideo.com 71 682
amazon.it 40 706
amazon.es 40 725
mercadolivre.com.br 67 740
bild.de 81 763
welt.de 61 800
people.com 44 801
amazon.com.au 40 812
theverge.com 77 815
nbcnews.com 60 823
amazon.com.br 40 833
investopedia.com 44 913
mercadolibre.com.ar 67 931
theatlantic.com 52 980
theconversation.com 62 1,019
huffpost.com 88 1,027
amazon.com.mx 40 1,032
as.com 84 1,061
bfmtv.com 80 1,073
franceinfo.fr 62 1,098
mercadolibre.com.mx 67 1,125
mercadolibre.com 40 1,165
ad.nl 52 1,190
nu.nl 52 1,191
furaffinity.net 39 1,223
hln.be 52 1,251
huffingtonpost.com 85 1,275
dw.com 42 1,305
iltalehti.fi 58 1,409
buzzfeed.com 65 1,442
ekstrabladet.dk 67 1,446
eenadu.net 67 1,456
twkan.com 43 1,641
newyorker.com 64 1,793
zdnet.com 72 1,831
arstechnica.com 81 1,847
kicker.de 51 1,955

See every measured domain that blocks Perplexity-User

This list is served from a cache rebuilt just now. It is discarded the moment a rescan records a policy change for this agent, so a site that has just changed its robots.txt will drop off it within one scan rather than waiting for the cache to expire.

Compare Perplexity

Perplexity runs 2 agents in this registry, and they do different jobs. Blocking one says nothing about the others.

Common questions answered

Does blocking Perplexity-User remove me from Perplexity?

Partly. Perplexity-User fetches a page only when a user asks about it, so disallowing it does not delist you from Perplexity. It does mean the answer is composed without your live page, from a stale copy or a third-party summary. Perplexity documents this agent as not bound by robots.txt, so the disallow is a request rather than a control; see the blocking section for the edge rule that is.

How do I verify Perplexity-User requests are genuine?

Perplexity publishes the address ranges its agents fetch from in its crawler documentation. Compare the source address against that list. Independent testing has recorded retrieval from addresses outside the published ranges and without the declared token, so a match confirms a genuine request but a miss does not prove the traffic is not Perplexity.

Check your own site free

See whether your robots.txt admits Perplexity-User today, and whether your edge agrees with it.