resulthack

All AI crawlers /

PerplexityBot

Perplexity · AI search · robots.txt: Yes

Crawls the web to surface and link websites in Perplexity's search results; Perplexity says it is not used to crawl content for AI foundation models.

Block PerplexityBot

User-agent: PerplexityBot
Disallow: /

Blocking PerplexityBot keeps your site out of Perplexity's search results, since Perplexity recommends allowing it to appear there. Perplexity says PerplexityBot does not collect content for AI foundation models, so there is no training opt-out to gain from blocking it.

Allow PerplexityBot

User-agent: PerplexityBot
Allow: /

An allow group only changes anything if a broader rule would block PerplexityBot. 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 PerplexityBot, spelled as in the User-Agent Perplexity documents (“PerplexityBot/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 PerplexityBot 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 PerplexityBot

In the server block (or a location)

if ($http_user_agent ~ PerplexityBot) {
    return 403;
}

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

In the http block

geo $perplexitybot_unlisted {
    default 1;
    107.20.236.150/32 0;
    3.224.62.45/32 0;
    18.210.92.235/32 0;
    3.222.232.239/32 0;
    3.211.124.183/32 0;
    3.231.139.107/32 0;
    18.97.1.228/30 0;
    18.97.9.96/29 0;
}
map $http_user_agent $perplexitybot_fake {
    default 0;
    "~PerplexityBot" $perplexitybot_unlisted;
}

In the server block (or a location)

if ($perplexitybot_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 PerplexityBot

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

<If "%{HTTP_USER_AGENT} =~ /PerplexityBot/">
    Require all denied
</If>

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

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

<If "%{HTTP_USER_AGENT} =~ /PerplexityBot/">
    Require ip 107.20.236.150/32 3.224.62.45/32 18.210.92.235/32 3.222.232.239/32 3.211.124.183/32 3.231.139.107/32
    Require ip 18.97.1.228/30 18.97.9.96/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 PerplexityBot

Inside the site block

@perplexitybot header User-Agent *PerplexityBot*
respond @perplexitybot 403

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

Inside the site block

@fake-perplexitybot {
    header User-Agent *PerplexityBot*
    not {
        client_ip 107.20.236.150/32 3.224.62.45/32 18.210.92.235/32 3.222.232.239/32 3.211.124.183/32 3.231.139.107/32
        client_ip 18.97.1.228/30 18.97.9.96/29
    }
}
respond @fake-perplexitybot 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 PerplexityBot

Expression of a custom rule; action Block

(http.user_agent contains "PerplexityBot")

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

Expression of a custom rule; action Block

(http.user_agent contains "PerplexityBot" and not ip.src in {107.20.236.150/32 3.224.62.45/32 18.210.92.235/32 3.222.232.239/32 3.211.124.183/32 3.231.139.107/32 18.97.1.228/30 18.97.9.96/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/perplexitybot.json, 8 ranges, fetched 8 Oct 2026, list dated 7 Feb 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 /. 62 block PerplexityBot from the whole site by name, 22 block it through their User-agent: * group, and 36 name it with partial rules (some paths closed, the home page open). 17 more name it only to let it in.

62

block it by name 12.2%

22

block it through * 4.3%

36

name it, partial rules 7.1%

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

Highest-ranked sites that block PerplexityBot by name

  1. fbcdn.net rank 12
  2. amazon.com rank 27
  3. whatsapp.net rank 32
  4. whatsapp.com rank 57
  5. tiktok.com rank 58
  6. yahoo.com rank 61
  7. msn.com rank 72
  8. chatgpt.com rank 87
  9. amazonvideo.com rank 111
  10. nytimes.com rank 157

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
AI search index
Obeys robots.txt
Yes. Perplexity documents PerplexityBot as a robots.txt token and says changes can take up to 24 hours to take effect.
In your server logs
The user-agent string contains "PerplexityBot/1.0".
How to verify it
Match the request's IP address against Perplexity's published PerplexityBot IP list. For firewalls, Perplexity suggests rules that combine the user-agent with those IP ranges.

Published list: www.perplexity.com/perplexitybot.json — 8 IPv4 ranges when we fetched it, list dated 7 Feb 2025. Always match against the live list; operators update them. To count real and fake PerplexityBot 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.

“is designed to surface and link websites in search results on Perplexity. It is not used to crawl content for AI foundation models.”

“To ensure your site appears in search results, we recommend allowing PerplexityBot in your site’s robots.txt file and permitting requests from our published IP ranges listed below.”

“Webmasters can use the following robots.txt tags to manage how their sites and content interact with Perplexity. Each setting works independently, and it may take up to 24 hours for our systems to reflect changes.”

“Set up a rule that combines both User-Agent and IP address conditions:”

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

Sources

Other crawlers from Perplexity

Same purpose, other operators

← All 49 AI crawlers

Made with AI tools. · Privacy