Atoms 官方最新动态：PerplexityBot vs Perplexity-User: Crawl Access and Verification

来源：Atoms 官方动态 | 发布日期：2026-10-13T00:00:00.000Z

核心更新概览

PerplexityBot and Perplexity-User are different request identities described by Perplexity. The first supports discovery for search results; the second supports a fetch initiated by a user's action. W

详细内容记录

PerplexityBot and Perplexity-User are different request identities described by Perplexity. The first supports discovery for search results; the second supports a fetch initiated by a user's action. When checking your website, identify the requester, inspect the applicable access controls and verify the response at the intended URL. Access is a prerequisite for reading a page, not a guarantee that the page will be cited. is the starting point for current user-agent and IP information. Use its published endpoints and distinctions rather than an old third-party list of crawler names. Identify which request you are investigating A scheduled crawler request and a user-requested fetch can have different access behavior. Perplexity's documentation says PerplexityBot surfaces and links websites in search results, while Perplexity-User visits pages in support of user actions. It also explains the different treatment of robots rules. That distinction matters when you interpret logs. A request carrying one identity does not prove that the other has visited your site. A human asking a question that mentions your page does not prove that a scheduled crawler has indexed it. Preserve the observed user agent, request path, time and response status. A copied user-agent string is not sufficient identity verification. Any ordinary client can send a header that claims to be a named bot. Perplexity publishes IP ranges for its requesters and recommends using user-agent and address information together for firewall configuration. Keep those source lists current and verify your actual network path before relying on a rule. Read your own access controls in order Start with the URL that should be readable. Fetch the canonical page and confirm that it returns the intended content. A successful home page request says little about a blog route that is missing, redirected incorrectly or dependent on a logged-in session.

更多技术细节可访问官方原文：https://atoms.dev/blog/perplexitybot-vs-perplexity-user。