Aizii Learn · AI Search

[← Back to Learn](https://aizii.ai/learn)

# AEO for Perplexity: the technical checklist

Perplexity reads your brand through two agents, and they follow different rules. PerplexityBot crawls pages so they can surface and link in Perplexity search results. Perplexity-User visits a page when a person asks Perplexity a question that needs it. Perplexity says neither agent is used to crawl content for training foundation models. The checklist in this guide is short: allow PerplexityBot, allow its published IP ranges at the firewall, do not expect robots.txt to stop Perplexity-User, and make the product facts true, complete, and readable in the first wave of HTML. No vendor publishes a formula for what Perplexity recommends, and this guide does not claim one. It covers only the technical ground a brand controls.

This is a developer-led job with marketer checks. The developer owns robots.txt, the firewall, and the markup. The marketer owns the product facts and the page copy. If you are both people, check the firewall first, because for Perplexity the firewall is the control that most often blocks a site, not the file.

## Where it goes wrong

Perplexity checklists fail in a small number of repeatable ways, and the most common one is not in robots.txt at all.

-   PerplexityBot is blocked by a blanket rule. A broad Disallow aimed at all crawlers catches the search crawler too. Perplexity recommends allowing PerplexityBot in robots.txt if you want to appear in its results. A brand that blocks it and then wonders why Perplexity never links it has answered its own question.
-   The firewall challenges the crawler. Perplexity publishes its own firewall guidance, for Cloudflare and for AWS, because a bot rule or a challenge page in front of the site stops its agents before robots.txt is ever read. The fix is an allow rule at the firewall that matches the user agent and the published IP ranges together, not one or the other alone. A 403 or a challenge page in the logs is the warning sign, and the fix lives at the edge.
-   Perplexity-User is blocked in robots.txt and the team expects the block to hold. Perplexity says that since a user requested the fetch, this fetcher generally ignores robots.txt rules. It is also not used for web crawling or to collect training content. A rule aimed at it is a statement of preference, not a control. If you need those fetches kept out, the enforceable route is a firewall rule keyed to the user agent and the published IP ranges together.
-   The user agent is trusted on its own. A user agent string can be faked by anyone, so finding PerplexityBot in a log does not prove the request came from Perplexity. Perplexity publishes IP ranges for each agent, and its guidance is to verify by user agent and source IP together. A log line that claims to be PerplexityBot from an address outside the published ranges is not Perplexity.
-   The product facts are wrong or late. A price in the page copy that disagrees with the structured data, a size that is gone but marked in stock, a shipping promise the checkout cannot keep. Perplexity cites pages it can verify, and a page that disagrees with itself gives it nothing to cite with confidence. The fix is one true price, one true stock state, and one true shipping promise, in words and in code, at the same time.
-   The content arrives only after JavaScript runs. If the price, the stock state, or the product description loads only in the browser, a fetcher that reads the first wave of HTML may never see it. Serve the product facts as server-rendered HTML, and check the raw HTML, not the rendered page in a browser, to confirm they are there.
-   The brand tests once and stops. Perplexity says it may take up to 24 hours for its systems to reflect a robots.txt change. A same-day retest proves nothing either way. Test, wait, then test again.

## The steps

**Step 1. Allow PerplexityBot in robots.txt, on its own line.** The developer opens the robots.txt file at the site root and adds a group that names PerplexityBot and allows it. Do not hide it inside a wildcard group and hope the wildcard carries it. Name the token. The sample in the machine-readable section below shows the shape. If the file already has a group for PerplexityBot that disallows it, change that group. Do not add a second group for the same token and leave the old one in place.

**Step 2. Allow the published IP ranges at the firewall, matched with the user agent.** The developer follows Perplexity's firewall guidance for the provider in front of the site, Cloudflare or AWS, and builds an allow rule that matches two conditions together: the user agent contains PerplexityBot or Perplexity-User, and the source IP sits in the ranges published at the perplexitybot.json and perplexity-user.json addresses in Sources. One condition alone is not enough, because a user agent string can be faked and an IP range alone says nothing about which agent is calling. Check the firewall logs after the change and confirm genuine requests return 200.

**Step 3. Leave Perplexity-User out of the robots.txt file.** The developer does not add a rule for Perplexity-User, because Perplexity says this fetcher generally ignores robots.txt rules. Its job is to visit a page when a person asks a question that needs it, and it may link the page in the answer. If the team wants those fetches kept out for a section of the site, the developer builds that control at the firewall, keyed to the user agent and the published IP ranges together, and says so plainly in the change notes. Do not write a robots.txt rule and call the job done.

**Step 4. Make the product facts true, complete, and in the first wave of HTML.** The marketer writes the product facts once, in plain words: the name, the price, the stock state, the shipping promise, and the return policy. The developer puts the same facts in Product structured data on the page, with the price, the availability, and the shipping details matching the visible text. Then the developer fetches the raw HTML of a product page, with curl or view source, and confirms the price and the stock state are in it before any JavaScript runs. If they are not, the page needs server-side rendering for those facts. A page that looks right in a browser and wrong in raw HTML is a page Perplexity cannot cite with confidence.

**Step 5. Check the sitemap, the llms.txt file, and the crawl path, then retest after a day.** The developer confirms the sitemap lists the product pages, the category pages, and the guides at their canonical addresses, and that robots.txt points at the sitemap. The marketer confirms the llms.txt file lists the pages that matter most, with a short note each. Then the team asks Perplexity the questions a customer would ask, notes whether the brand appears and which pages it cites, and waits. Perplexity says a robots.txt change can take up to 24 hours to be reflected, so a retest the same afternoon is not a verdict. Retest the next day, and fix the gap the comparison shows.

## The machine-readable piece

This robots.txt sample names PerplexityBot on its own line. Replace the placeholder with your own sitemap address. Perplexity-User is left out on purpose, for the reason given in step three.

```
User-agent: PerplexityBot
Allow: /

Sitemap: https://[yourdomain.com]/sitemap.xml
```

This Product JSON-LD block is the machine-readable version of one product page. It uses only fields from the Product structured data guide in Sources. Replace the placeholders with your real price, your real stock state, and your real shipping details, and make sure every value matches the visible text on the page. The priceValidUntil value is a placeholder shape: replace YYYY-MM-DD with the real date the price is valid until, or remove the field.

```
{
  "@context": "https://schema.org",
  "@type": "Product",
  "name": "[Product name]",
  "description": "[One plain sentence about the product]",
  "offers": {
    "@type": "Offer",
    "priceCurrency": "USD",
    "price": "[Price]",
    "priceValidUntil": "YYYY-MM-DD",
    "availability": "https://schema.org/InStock",
    "itemCondition": "https://schema.org/NewCondition"
  }
}
```

Check the file before you rely on it. Open your domain followed by /robots.txt in a browser and confirm the group loads. Fetch a product page as raw HTML and confirm the price and the stock state are in it. Search your server logs for PerplexityBot and confirm the source IP sits in the published ranges and the response is 200. If a log line claims to be PerplexityBot from an address outside the published ranges, it is not Perplexity, and the fix is at the edge.

## What it looks like when it works

Say you run a bike shop with a small catalog, selling commuter bikes, parts, and accessories, with a guide on fitting a bike to its rider. The developer finds that a Cloudflare bot rule has been challenging PerplexityBot for months, and the marketer finds a blanket Disallow in robots.txt that nobody remembers adding. They allow PerplexityBot on its own line in the file, and they build a firewall allow rule that matches the user agent and the published IP ranges together. They leave Perplexity-User out of the file, because the vendor says it generally ignores it. The marketer rewrites the product facts so the price, the stock state, and the shipping promise agree in words and in code, and the developer confirms the price is in the raw HTML before any JavaScript runs. They ask Perplexity the questions a customer would ask about commuter bikes, wait a day, and ask again. The brand appears, with links to the product pages and the fitting guide. The fix was a file, a firewall rule, and true facts, in that order.

### The fundamentals

These mechanics are shared across every engine and covered in full in their own guides:

-   •The llms.txt format and a complete sample, see our [guide to writing a good llms.txt file](https://aizii.ai/learn/ai-search/how-to-write-a-good-llms-txt-file)
-   •The markup AI systems read to verify facts, see our [product schema guide](https://aizii.ai/learn/ai-search/how-to-add-product-schema-markup-for-ai-search)
-   •The complete crawler rule reference, see our [robots.txt guide for AI search](https://aizii.ai/learn/ai-search/how-to-write-robots-txt-for-ai-search)

## What this guide does not cover

This guide covers the technical checklist for Perplexity: the two Perplexity agents, the robots.txt line for PerplexityBot, the firewall allow rule, and the product facts. It does not cover the full technical audit that checks every crawler and every page, the transaction layer that lets an agent complete a purchase, or the per-engine playbooks for ChatGPT, Gemini, and Claude. It does not cover what Perplexity says about your brand over time, or how to correct a wrong answer once it appears. Those are separate jobs, and this guide is the map, not the whole trip.

## Check your own store now

Run the free scan. One click, no signup, and it shows whether AI crawlers can read your store today: aizii.ai/aeo-scan

[Run the free scan](https://aizii.ai/aeo-audit)

## Sources

-   Perplexity, Perplexity crawlers (specific): [https://docs.perplexity.ai/guides/bots](https://docs.perplexity.ai/guides/bots)
-   Google Search Central, Product structured data (specific): [https://developers.google.com/search/docs/appearance/structured-data/product](https://developers.google.com/search/docs/appearance/structured-data/product)
-   Schema.org, Product type (specific): [https://schema.org/Product](https://schema.org/Product)
-   RFC 9309, Robots Exclusion Protocol (general standard): [https://www.rfc-editor.org/rfc/rfc9309.html](https://www.rfc-editor.org/rfc/rfc9309.html)
-   llms.txt proposal (specific): [https://llmstxt.org](https://llmstxt.org/)

Note: links marked specific point to the page that supports the claim in this guide. Links marked general docs point to the vendor's general docs section for that topic, not to a page that proves every step. Check the vendor docs for the current path before relying on a menu name or click path in this guide.
