---
language: en
title: "Perplexity-User"
description: "Perplexity-User retrieves pages in response to user actions. See the caveat about robots.txt and how to distinguish access from use in the response."
canonical: "https://tropk.ai/en/resources/glossary/perplexity-user"
last_modified: "2026-10-12T16:11:25.802Z"
---

# Perplexity-User

Reviewed on 2026-10-06.

## What it means

[Perplexity](/en/resources/glossary/perplexity)-User identifies page [retrieval](/en/resources/glossary/information-retrieval) for user actions on Perplexity. When it receives a question, the service may visit a page to support its response and include a link to it. According to documentation reviewed in October 2026, this agent does not crawl the web or collect data to train foundation models; it generally ignores [robots.txt](/en/resources/glossary/robots-txt).

## Why it matters for marketing

For content publishers, this changes how permissions and reports should be interpreted. Blocking the [PerplexityBot](/en/resources/glossary/perplexitybot) [crawler](/en/resources/glossary/crawler) in robots.txt is not enough to conclude that a person-initiated query will not access the page. Marketing teams should define their intended access policy and ask infrastructure teams to verify Perplexity-User’s specific behavior, without conflating distinct purposes.

## Example in practice

Imagine a manufacturer with a public installation manual. After someone asks Perplexity a question about the manual, the team observes a request identified by the combination of User-Agent and Perplexity-User’s official IP, despite a robots.txt rule. The team keeps the manual available for requested queries and corrects the report that classified the event as collection for training.

## How to apply or verify

Compare the time of the controlled query, the requested URL, and the response recorded on the server. To identify the source, match the User-Agent against the current list of Perplexity-User IPs published by the company. Also check firewall blocks: access allowed by the server is different evidence from the response actually using or citing the manual.

## Important distinctions

Perplexity-User is not synonymous with PerplexityBot, and the name User does not show that a human clicked through to the site. The phrase generally ignores robots.txt describes the stated behavior of this retriever, not a universal guarantee of access. Robots.txt provides guidance to agents; to restrict actual access, assess server controls. No single visit proves [citation](/en/resources/glossary/ai-citation) or conversion.

## Sources and references

- [Perplexity Crawlers](<https://docs.perplexity.ai/docs/resources/perplexity-crawlers>) — Perplexity

## Continue a leitura

- [PerplexityBot](</en/resources/glossary/perplexitybot>)
- [User agent](</en/resources/glossary/user-agent>)
- [robots.txt](</en/resources/glossary/robots-txt>)

## About the author

[Vinicius Pacheco](</en/team/vinicius-pacheco>)

Responsible for Tropk’s technical content, focusing on crawling, indexing, structured data, and agent access to content.

---

[All pages in Markdown](<https://tropk.ai/sitemap.md>)