resulthack

All AI crawlers /

Perplexity-User

Perplexity · User fetch · robots.txt: Not always

Visits a web page when a Perplexity user's question needs it, and may link that page in the answer; Perplexity says it is not used for crawling or for training AI models.

Block Perplexity-User

User-agent: Perplexity-User
Disallow: /

A Disallow line will generally not stop Perplexity-User, because Perplexity says it generally ignores robots.txt. Its published IP list is how the operator lets you identify it, for example in a firewall rule.

Allow Perplexity-User

User-agent: Perplexity-User
Allow: /

An allow group only changes anything if a broader rule would block Perplexity-User. Under the robots.txt standard (RFC 9309, section 2.2.1) a crawler follows the group that names it and uses the User-agent: * group only when no group does — so this group lets it in even if your * group says Disallow: /. Token matching is case-insensitive.

Put these lines in /robots.txt at the root of each host (each subdomain has its own file). robots.txt is a request to well-behaved crawlers, not access control.

Block or allow it at the server

robots.txt asks; a server rule refuses. Every rule here matches Perplexity-User, spelled as in the User-Agent Perplexity documents (“Perplexity-User/1.0”), and matches it case-sensitively. The server answers 403.

What a User-Agent rule cannot do: any client can send any User-Agent. Access control by User-Agent is an unreliable technique, since the User-Agent header can be set to anything at all, at the whim of the end user. (Apache HTTP Server 2.4 documentation). A fake Perplexity-User is refused by the block rule along with the real one, and a crawler that hides its name passes. The “only the real one” rule is the check: it lets the name in only from Perplexity's published addresses.

Your server

To block it: refuse every request that says Perplexity-User

In the server block (or a location)

if ($http_user_agent ~ Perplexity-User) {
    return 403;
}

To allow only the real one: refuse Perplexity-User claims from outside Perplexity's list

In the http block

geo $perplexity_user_unlisted {
    default 1;
    44.208.221.197/32 0;
    34.193.163.52/32 0;
    18.97.21.0/30 0;
    18.97.43.80/29 0;
}
map $http_user_agent $perplexity_user_fake {
    default 0;
    "~Perplexity-User" $perplexity_user_unlisted;
}

In the server block (or a location)

if ($perplexity_user_fake) {
    return 403;
}

The geo and map blocks go at http level; nginx's docs give Context: http for both, and for if Context: server, location. By default, the address is taken from the $remote_addr variable (nginx documentation).

To block it: refuse every request that says Perplexity-User

In the virtual host, a <Directory> block or .htaccess

<If "%{HTTP_USER_AGENT} =~ /Perplexity-User/">
    Require all denied
</If>

To allow only the real one: refuse Perplexity-User claims from outside Perplexity's list

In the virtual host, a <Directory> block or .htaccess

<If "%{HTTP_USER_AGENT} =~ /Perplexity-User/">
    Require ip 44.208.221.197/32 34.193.163.52/32 18.97.21.0/30 18.97.43.80/29
</If>

Apache httpd 2.4. Syntax: <If expression> ... </If> Context: server config, virtual host, directory, .htaccess (Apache HTTP Server 2.4 documentation). Several Require ip lines in one block: When multiple Require directives are used in a single configuration section and are not contained in another authorization directive like <RequireAll>, they are implicitly contained within a <RequireAny> directive. (Apache HTTP Server 2.4 documentation)

To block it: refuse every request that says Perplexity-User

Inside the site block

@perplexity-user header User-Agent *Perplexity-User*
respond @perplexity-user 403

To allow only the real one: refuse Perplexity-User claims from outside Perplexity's list

Inside the site block

@fake-perplexity-user {
    header User-Agent *Perplexity-User*
    not {
        client_ip 44.208.221.197/32 34.193.163.52/32 18.97.21.0/30 18.97.43.80/29
    }
}
respond @fake-perplexity-user 403

Like directives, named matcher definitions must go inside the site blocks that use them. (Caddy documentation) On client_ip: This matcher is best used when the trusted_proxies global option is configured, otherwise it acts identically to the remote_ip matcher. (Caddy documentation)

To block it: refuse every request that says Perplexity-User

Expression of a custom rule; action Block

(http.user_agent contains "Perplexity-User")

To allow only the real one: refuse Perplexity-User claims from outside Perplexity's list

Expression of a custom rule; action Block

(http.user_agent contains "Perplexity-User" and not ip.src in {44.208.221.197/32 34.193.163.52/32 18.97.21.0/30 18.97.43.80/29})

Each expression is one custom rule with the action Block (Cloudflare's own example: Expression: (cf.bot_management.score lt 2 and http.user_agent contains "App_Name 2.0") Action: Block).

Addresses in the “only the real one” rules: Perplexity's list www.perplexity.com/perplexity-user.json, 4 ranges, fetched 8 Oct 2026, list dated 17 Oct 2025. Operators change their lists; compare the date with the live list before you rely on it.

The IP rules compare the address your server sees. Behind a CDN or load balancer that is the proxy's address, so every claim would be refused: restore the client address first, or put the rule at the CDN.

Syntax from each server's own documentation, fetched 9 Oct 2026: nginx (rewrite module, map module, geo module); Apache (Access Control, <If>, expressions, mod_authz_core, mod_authz_host); Caddy (request matchers, respond); Cloudflare (custom rule example, operators, values and lists, http.user_agent). Every line form above is listed with its quote in server-rules-sources.json.

Who blocks it

Of the 1,000 most-visited domains on Tranco list PY35J (generated 2026-10-08), we read 508 robots.txt files on 2026-10-09 and ran each through the same RFC 9309 matcher as the checker, for the path /. 39 block Perplexity-User from the whole site by name, 33 block it through their User-agent: * group, and 13 name it with partial rules (some paths closed, the home page open). 7 more name it only to let it in.

39

block it by name 7.7%

33

block it through * 6.5%

13

name it, partial rules 2.6%

Percentages are of the 508 files we could read, not of all 1,000 sites.

Highest-ranked sites that block Perplexity-User by name

  1. amazon.com rank 27
  2. tiktok.com rank 58
  3. msn.com rank 72
  4. amazonvideo.com rank 111
  5. nytimes.com rank 157
  6. cnn.com rank 205
  7. bbc.com rank 221
  8. sciencedirect.com rank 223
  9. bbc.co.uk rank 230
  10. weibo.com rank 311

Each links to the site's live robots.txt, which may have changed since 2026-10-09.

robots.txt is only what a site asks for. A site can also turn a crawler away at its firewall or CDN, or let an operator in under a licensing deal, and neither shows in its robots.txt. A block through * stops every crawler the file does not name, so it says nothing about this one in particular. The files we could not read are not counted: 222 of the 1,000 domains are infrastructure names with no website at the bare domain (CDN and DNS zones, for example), 59 answered our request with 401 or 403, 93 failed (timeout, TLS or server error), 59 have no robots.txt (404 and similar) and 59 answered with an HTML page instead of a robots.txt file. Every agent's count, side by side.

Facts

Operator
Perplexity
Purpose
User-requested fetch
Obeys robots.txt
Not always. Perplexity says that because a user requested the fetch, Perplexity-User generally ignores robots.txt rules.
In your server logs
The user-agent string contains "Perplexity-User/1.0".
How to verify it
Match the request's IP address against Perplexity's published Perplexity-User IP list.

Published list: www.perplexity.com/perplexity-user.json — 4 IPv4 ranges when we fetched it, list dated 17 Oct 2025. Always match against the live list; operators update them. To count real and fake Perplexity-User requests in your own server log against this list, drop the log into the log reader.

What Perplexity says

Quoted word for word from the operator's documentation.

“supports user actions within Perplexity. When users ask Perplexity a question, it might visit a web page to help provide an accurate answer and include a link to the page in its response.”

“It is not used for web crawling or to collect content for training AI foundation models.”

“Since a user requested the fetch, this fetcher generally ignores robots.txt rules.”

“Always use the most current IP ranges from the official JSON endpoints. These addresses are updated regularly and should be the source of truth for your WAF configurations.”

“Full user-agent string: Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; Perplexity-User/1.0;”

Sources

Other crawlers from Perplexity

Same purpose, other operators

← All 49 AI crawlers

Made with AI tools. · Privacy