{"id":2601,"date":"2026-09-24T03:20:38","date_gmt":"2026-09-24T03:20:38","guid":{"rendered":"https:\/\/maxaeo.ai\/blog\/allow-perplexitybot-robots-txt-guide\/"},"modified":"2026-09-24T03:20:38","modified_gmt":"2026-09-24T03:20:38","slug":"allow-perplexitybot-robots-txt-guide","status":"publish","type":"post","link":"https:\/\/maxaeo.ai\/blog\/allow-perplexitybot-robots-txt-guide\/","title":{"rendered":"Allow PerplexityBot robots.txt guide: Setup and Verification"},"content":{"rendered":"

By maxaeo.ai \uff5c Published 2026-09-24 \uff5c Updated 2026-09-24<\/em><\/p>\n

An allow PerplexityBot robots.txt guide<\/strong> should cover more than one directive. You need to configure the crawler, check catch-all rules, review your firewall, and confirm that the live page is accessible. This guide explains the correct syntax, the difference between PerplexityBot and Perplexity-User, and a practical verification method for AI citation visibility.<\/p>\n

\"allow<\/figure>\n

What is PerplexityBot?<\/h2>\n

PerplexityBot is Perplexity\u2019s search crawler for discovering and linking websites in Perplexity search results.<\/strong> Perplexity says it is not used to crawl content for AI foundation-model training, and recommends allowing the bot if you want your pages to appear as sources in its search results. (docs.perplexity.ai<\/a>)<\/p>\n

That makes PerplexityBot different from a general-purpose training crawler. Blocking it is primarily a search-discovery decision: your public pages may become less available for retrieval and citation in Perplexity answers.<\/p>\n

Perplexity also documents a separate user agent, Perplexity-User<\/code>. This fetcher may access a page after a user asks a question. Perplexity states that this user-requested fetch generally ignores robots.txt rules, so a robots.txt rule for PerplexityBot<\/code> should not be treated as a complete access-control system. (docs.perplexity.ai<\/a>)<\/p>\n

How do you allow PerplexityBot in robots.txt?<\/h2>\n

Add an explicit user-agent group to the root-level \/robots.txt<\/code> file:<\/p>\n

User-agent: PerplexityBot\nAllow: \/\n<\/code><\/pre>\n
This tells a compliant PerplexityBot crawler that it may request URLs across the site. The exact token matters: use PerplexityBot<\/code> with the same capitalization shown in Perplexity\u2019s documentation. Its documented full user-agent string includes PerplexityBot\/1.0<\/code>, but robots.txt matching should target the product token rather than the entire browser string. (docs.perplexity.ai<\/a>)<\/p>\n
If your existing file already permits all crawlers, the explicit block may appear redundant. It is still useful as an operational signal because it makes your policy visible to developers, SEO teams, and security tools.<\/p>\n
A typical public-site configuration might look like this:<\/p>\n
User-agent: PerplexityBot\nAllow: \/\n\nUser-agent: *\nAllow: \/\nDisallow: \/admin\/\nDisallow: \/account\/\nDisallow: \/api\/\n<\/code><\/pre>\n
Do not copy this example over your entire file without checking your current Googlebot, sitemap, staging, and private-path rules. Add the PerplexityBot group while preserving directives that serve other parts of your technical SEO setup.<\/p>\n
For broader context, compare this configuration with MaxAEO\u2019s guide to robots.txt for LLMs and AI crawlers<\/a>.<\/p>\n
How do you allow only selected sections?<\/h2>\n
You can allow PerplexityBot to crawl public content while excluding sensitive or low-value paths:<\/p>\n
User-agent: PerplexityBot\nAllow: \/\nDisallow: \/admin\/\nDisallow: \/account\/\nDisallow: \/checkout\/\nDisallow: \/internal-search\/\nDisallow: \/api\/\n<\/code><\/pre>\n
The goal is to expose pages that can legitimately answer public questions: product documentation, comparison pages, research, pricing explanations, and editorial content. Avoid placing customer records, authenticated dashboards, private support content, or unpublished assets behind a robots.txt assumption.<\/p>\n
Google Search Central emphasizes that robots.txt controls crawling, not security. A disallowed URL can still be discovered, and robots.txt should not be used to protect confidential information. Use authentication, authorization, or server-side access controls for private material. (developers.google.com<\/a>)<\/p>\n
There is also an important distinction between crawling and indexing. If a page must not appear in search results, a noindex<\/code> directive is usually more appropriate\u2014but crawlers must be able to access the page to see that directive. Blocking the same URL in robots.txt can prevent crawlers from discovering the noindex<\/code> instruction. (developers.google.com<\/a>)<\/p>\n
Why can PerplexityBot still fail after you add Allow?<\/h2>\n
An Allow: \/<\/code> rule only addresses robots.txt; it does not guarantee that your server, CDN, WAF, or page rendering layer will admit the request.<\/strong> In practice, AI crawler visibility should be checked as a layered access problem.<\/p>\n
Use this four-layer model:<\/p>\n
\n\n\n\n\n\n\n\n\n
Layer<\/th>\nWhat to check<\/th>\nTypical failure<\/th>\n<\/tr>\n<\/thead>\n
Robots policy<\/td>\n\/robots.txt<\/code> returns HTTP 200 and contains the correct token<\/td>\nA wildcard Disallow: \/<\/code> still applies<\/td>\n<\/tr>\n
Network access<\/td>\nCDN, WAF, and rate limits permit the request<\/td>\nBot challenge or 403 response<\/td>\n<\/tr>\n
Origin response<\/td>\nThe page returns useful HTML<\/td>\nEmpty shell, redirect loop, or 5xx error<\/td>\n<\/tr>\n
Content eligibility<\/td>\nThe page contains clear, public, indexable information<\/td>\nThin, duplicated, or blocked content<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n
Perplexity\u2019s documentation specifically recommends combining user-agent matching with published IP ranges when configuring a WAF. Its guidance for Cloudflare and AWS WAF uses both signals, and says the current IP ranges should come from Perplexity\u2019s official JSON endpoints rather than from a static third-party list. (docs.perplexity.ai<\/a>)<\/p>\n
This is the most commonly missed point in competing setup guides: a permissive robots.txt does not override a firewall rule<\/strong>. If your WAF blocks the request before it reaches the origin, the crawler never gets a chance to read your Allow<\/code> directive.<\/p>\n
How do you verify that Perplexity can access your site?<\/h2>\n
Use a repeatable verification sequence after publishing the file:<\/p>\n
    \n
  1. \n
    Fetch the live robots.txt file.<\/strong>
    \nOpen https:\/\/example.com\/robots.txt<\/code> in a browser or use:<\/p>\n
    curl -i https:\/\/example.com\/robots.txt\n<\/code><\/pre>\n
    Confirm the response is successful, the file is served from the correct hostname, and the content is not being generated differently for regions or user agents.<\/p>\n<\/li>\n
  2. \n
    Search for the exact bot token.<\/strong>
    \nLook for:<\/p>\n
    User-agent: PerplexityBot\n<\/code><\/pre>\n
    Check whether a later or broader group contains a conflicting Disallow: \/<\/code>. Also inspect rules inherited through your CMS or deployment system.<\/p>\n<\/li>\n
  3. \n
    Request a public page with the documented user agent.<\/strong><\/p>\n
    curl -A "PerplexityBot" -I https:\/\/example.com\/your-public-page\/\n<\/code><\/pre>\n
    A successful status does not prove that the page is eligible for citation, but a 403, 429, 503, or challenge page identifies an access problem.<\/p>\n<\/li>\n
  4. \n
    Inspect server and WAF logs.<\/strong>
    \nLook for the user-agent, response code, requested path, and security action. For stronger verification, compare the request source with Perplexity\u2019s current published IP ranges. Perplexity advises keeping those ranges updated because they can change. (docs.perplexity.ai<\/a>)<\/p>\n<\/li>\n
  5. \n
    Test actual citation visibility.<\/strong>
    \nSearch Perplexity using buyer questions that should reasonably surface your page. Record whether the page is cited, which passage is used, and whether competitors appear instead. Crawling access is a prerequisite, not a ranking guarantee.<\/p>\n<\/li>\n<\/ol>\n
    MaxAEO can support this final measurement layer by tracking brand mentions, competitive visibility, citation sources, sentiment, and recommendation position across eight AI engines with daily updates. Its AI citation tracking guide<\/a> explains how to evaluate whether technical access translates into observable source inclusion.<\/p>\n
    \"PerplexityBot<\/figure>\n
    Should you allow PerplexityBot or block it?<\/h2>\n
    For most public SaaS, publishing, documentation, and ecommerce websites, allowing PerplexityBot is the logical default when AI search discovery is part of the acquisition strategy. It gives Perplexity\u2019s search crawler permission to discover and link eligible pages, while you can still exclude private paths and protect sensitive systems through authentication and firewall controls.<\/p>\n
    Blocking may be appropriate when you have a deliberate policy against Perplexity search discovery, operate a private or restricted site, or need to reduce crawler traffic during an infrastructure incident. Use:<\/p>\n
    User-agent: PerplexityBot\nDisallow: \/\n<\/code><\/pre>\n
    Treat the decision separately from Perplexity-User<\/code>. Perplexity documents that Perplexity-User<\/code> handles user-requested page access and generally ignores robots.txt, so access control for sensitive content must come from authentication or network policy\u2014not from a crawler directive alone. (docs.perplexity.ai<\/a>)<\/p>\n
    Common questions<\/h2>\n
    Does allowing PerplexityBot guarantee a citation?<\/h3>\n
    No. Allowing the crawler only makes eligible content available for discovery. Citation decisions can depend on relevance, freshness, authority, query intent, page quality, and competing sources.<\/p>\n
    Is Allow: \/<\/code> required if there is no Disallow<\/code> rule?<\/h3>\n
    No. An empty or absent restriction can already permit crawling, depending on the rest of the file. An explicit Allow: \/<\/code> is useful for clarity and for sites that maintain an intentional allowlist.<\/p>\n
    Should PerplexityBot be grouped with Googlebot?<\/h3>\n
    No. Give it its own User-agent<\/code> group. A rule written only for Googlebot does not automatically create an equivalent policy for PerplexityBot.<\/p>\n
    Does robots.txt protect private content?<\/h3>\n
    No. Robots.txt is a crawler instruction, not an access-control mechanism. Use login requirements, permissions, and server-side protection for confidential pages.<\/p>\n
    How long do changes take to appear?<\/h3>\n
    Perplexity says changes to crawler settings may take up to 24 hours to be reflected in its systems. (docs.perplexity.ai<\/a>) Continue checking logs and citation results after the change rather than judging visibility immediately.<\/p>\n