PerplexityBotPerplexity says PerplexityBot surfaces and links sites in Perplexity search results. It says this token is not used to crawl content for foundation models. The same section recommends allowing the token in robots.txt, and allowing requests from the published IP ranges, so the site appears in those results. Perplexity says each robots.txt setting works independently and that a change can take up to 24 hours. The page's machine-readable article metadata lists dateModified 2026-01-29 and no datePublished. Perplexity-User is a different token and generally ignores robots.txt. This card does not.
searchrecommends_allow. The vendor recommends allowing this token in robots.txt so the site appears in search results. The cited page does not say that a Disallow removes the site.Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; PerplexityBot/1.0; +https://perplexity.ai/perplexitybot) Perplexity publishes this as the full user-agent string.curl -s https://whosthatbot.com/v1/crawlers/perplexitybot
tools/call with name check_robots is the same check at POST /mcp. The pasted file disallows PerplexityBot on /docs and allows *. The call does not fetch a host.
curl -s https://whosthatbot.com/mcp -H 'content-type: application/json' -H 'accept: application/json, text/event-stream' -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"check_robots","arguments":{"robots_txt":"User-agent: PerplexityBot\nDisallow: /\n\nUser-agent: *\nAllow: /\n","path":"/docs","ids":["perplexitybot"]}}}'
That call returns fetched_target false. This row is disallow via group PerplexityBot, rule Disallow: /.