What is PerplexityBot?

How does PerplexityBot work?

PerplexityBot requests public web resources as part of Perplexity’s documented search discovery workflow. The provider gives website owners a named user-agent token for expressing crawler preferences.

This agent should be distinguished from Perplexity-User, which serves a different function.

A request can collect available content, but the resulting use depends on the provider’s systems and policies rather than anything implied by the bot name alone.

• Use the exact PerplexityBot token when configuring its robots.txt group.
• Review the current provider documentation before changing production rules.
• Treat crawler permission and successful delivery as separate technical checks.

Why does PerplexityBot matter for B2B SaaS?

Search crawlers can discover public product descriptions, integration guides, and comparison content that helps answer software purchasing questions.

Allowing access can support discovery, but it does not guarantee indexing or citation. A SaaS publisher should define its preference for PerplexityBot explicitly instead of inheriting a blanket policy for all automation.

That decision should also consider infrastructure controls and the sensitivity of published material.

• Separate public documentation from authenticated customer information.
• Keep a written reason for provider-specific crawl permissions.
• Review related agents independently rather than assuming shared behavior.

What is an example of PerplexityBot?

A SaaS publisher could inspect a request claiming to be PerplexityBot for a public integration guide. The operator checks the requested path, HTTP response, and available provider verification guidance.

The robots.txt policy should match the intended search discovery decision. If the request succeeds, the evidence supports successful access to that resource.

It does not establish that a customer saw a recommendation or that a particular answer used the guide.

• Record the requested URL and response rather than only a visit total.
• Check identity using supported provider guidance where available.
• Keep unverified user-agent claims separate from confirmed crawler traffic.

How do you improve or measure PerplexityBot?

Audit how the website handles PerplexityBot rather than attempting to optimize the bot itself. Inspect robots.txt alongside CDN rules, firewall challenges, authentication requirements, and server responses.

Test the actual documentation paths that matter to buyers. Revisit the policy when Perplexity changes its crawler documentation. Measure observed search inclusion and citations separately from access logs.

• Investigate repeated failures on paths intended to remain public.
• Do not infer human referral traffic from automated requests.
• Recheck crawler access after migrations and security-policy deployments.

Frequently asked questions about PerplexityBot