# Perplexity-User

Operator: Perplexity
Purpose: User-requested fetch
Reviewed: 2026-09-14
HTTP identifier: Perplexity-User
robots.txt token: Perplexity-User

## What is Perplexity-User?

Fetches pages on behalf of Perplexity users.

## How to identify it

Look for the Perplexity-User identifier in a request’s User-Agent. This is a name match, not identity verification. Version strings may change.

## How to check identity

Compare the request IP with the current operator-published ranges linked in the source. A matching name alone does not verify identity.

## Access and robots.txt

Generally ignores robots.txt because visits are user-requested.

## What it means in your analytics

An on-demand fetch suggests a retrieval task. The log cannot reveal whether the resulting answer persuaded a buyer.

## Useful measures

Requested public pages; Public-page 403 and 404 responses; Subsequent page requests.

## What to check next

Investigate public-page 403s alongside authentication and edge rules. Keep protected account pages protected.

## Sources

- [docs.perplexity.ai](https://docs.perplexity.ai/docs/resources/perplexity-crawlers)

Operator facts are source-backed; interpretation and actions are Apostl guidance.

## Related profiles

- [PerplexityBot](https://apostl.dev/bots/perplexitybot)
- [ChatGPT-User](https://apostl.dev/bots/chatgpt-user)

[Start measuring agent traffic](https://apostl.dev/start/agent-analytics)