Key takeaways
- Perplexity is an answer engine: it retrieves sources at query time and cites them, so the products it can surface are the ones it can crawl and quote. This is our operating model, grounded in how answer engines work, not measured Perplexity data.
- Citable and structured are the same work: the clean specs, schema, and consistent price and availability that make any page machine-readable are also what let Perplexity quote you accurately.
- Keep Perplexity's crawler allowed in robots.txt: blocking it removes the page data it would otherwise cite. The full crawler allow-list lives on our crawlers page.
- Honest caveat: the strongest public selection study, ACES, did not include Perplexity, so every recommendation here is a crawlability-and-citability hypothesis, not a measured Perplexity finding.
- Because no public dataset measures Perplexity's selections, treat your own agent win rate on Perplexity as the number that matters, and measure it directly.
How Perplexity recommends: crawl, then cite
Perplexity is built as an answer engine rather than a catalog: it responds to a shopping question by retrieving sources and citing them, rather than by surfacing items from a merchant feed a store enrolls in. That framing is where the merchant leverage lives, and it is the premise we reason from. If Perplexity assembles a recommendation from sources it retrieves and cites at answer time, then a product page it cannot crawl (or one whose facts it cannot pin to a clear, quotable passage) is one it is unlikely to surface, however good the offer isHypothesis (our analysis). We reason from that mechanism throughout this page, and we say plainly where the reasoning ends and measured evidence would need to begin.
This is the same agent selection problem the rest of AgentMint.net covers (why an engine picks one store over another), but Perplexity leans harder on retrieval and citation than on a merchant feed you enroll in. That makes it, in our reading, the platform where general answer engine optimization discipline maps most directly: be crawlable, be structured, be quotable. The shared signal set and the per-engine differences are laid out across the platform playbooks; the ChatGPT and Gemini pages cover the engines that reach you over a commerce protocol rail, which Perplexity, on the evidence we have, does not obviously do.
Make your product pages citable
If Perplexity recommends what it can quote, the work is making each product page trivially quotable. The same structured, machine-readable product data that helps any agent parse you (explicit specifications, product schema, and a price and availability that agree between page and feed) is what lets Perplexity extract an accurate, citable fact instead of guessing or skipping, so citability and structure move togetherHypothesis (our analysis). A page that buries its key facts in prose, an image, or a script an answer engine cannot read gives it nothing clean to cite.
Concretely, that means the machine-readable layer is doing double duty here: it earns eligibility with feed-driven engines and it earns quotability with a citation-first engine. Ship the product schema (JSON-LD) for AI shopping that states your Offer, price, availability, and review fields in a form a machine can lift verbatim, and keep the on-page facts consistent with it, because an answer engine that finds two prices has to choose which to trust, and inconsistency is a reason to cite a competitor instead. We label this direction a hypothesis on purpose: it follows from how citation works, and it is not a measured Perplexity result.
Keep Perplexity's crawler in your robots.txt
Retrieval only reaches what it is allowed to fetch, so crawler access is the precondition for everything above. Blocking an answer engine's crawler in robots.txt deletes the supplemental page data it would otherwise retrieve and cite, so a disallow line can quietly remove you from the set of products Perplexity is able to recommend at allHypothesis (our analysis).
Perplexity publishes a bot guide (opens in new tab)(opens in new tab) for the user agents it operates, and the practical move is to keep PerplexityBot, the indexing crawler, allowed in robots.txt for your product URLs, since that is the token whose access actually determines what gets crawled and cited later. Perplexity distinguishes PerplexityBot, an indexing crawler that honors robots.txt, from Perplexity-User, a user-triggered fetcher that generally ignores robots.txt because a real user initiated the requestSpec-factPerplexity bot documentation, docs.perplexity.ai/guides/bots, so a disallow line mainly affects PerplexityBot's indexing, not a user's live, on-demand fetch. The complete, cross-engine crawler allow-list (GPTBot, OAI-SearchBot, Google-Extended, and Perplexity's agents) and what llms.txt adds live on AI crawlers, robots.txt and llms.txt; this page only flags that a crawl-and-cite engine is the one you can least afford to block.
The evidence gap: ACES did not test Perplexity
This is the least-evidenced platform page on the site, and saying so is the point. The most rigorous public study of how buying agents choose (the ACES framework) never tested Perplexity. ACES audited a fixed set of frontier models, Claude Sonnet (up to version 4), GPT-4o and GPT-4.1, and Gemini 2.0 and 2.5 Flash, in a controlled storefront simulation, and Perplexity was not among the models it evaluatedReportedACES, Allouah et al., arXiv:2508.02630 (2025-12-17). So none of the measured selection effects you will see quoted elsewhere on AgentMint.net (position bias, price elasticity, the sponsored-tag penalty, endorsement lift) can be attributed to Perplexity. They are findings about other agents.
Because no public dataset measures how Perplexity ranks or selects products, the responsible guidance for it is the engine-agnostic foundation (be crawlable, be structured, be quotable) rather than any Perplexity-specific weighting we cannot evidenceHypothesis (our analysis). One related unknown now has a partial answer, though so far only from third parties. Shopify's guide to Perplexity Shopping states that Perplexity runs a free Merchant Program that lets retailers share product data directly with Perplexity, and that a Shopify store's product data can sync to it through Shopify's infrastructure.ReportedShopify, Perplexity Shopping guide (2026-04-02) TechCrunch reported at the program's launch that enrolled merchants give Perplexity more complete product information for its index and a better chance of being recommended, and that Perplexity said it was not taking an affiliate cut from purchases at the time.ReportedTechCrunch, Ivan Mehta (2024-11-18) The honest status, as of 2026-07-08: the two statements above are third-party sourced. Perplexity's own announcement and its Merchant Terms of Service are the primary sources for the program, so treat them as the final word on its terms. We make no claim about feed formats, enrollment terms, or any commerce-protocol rail, because no primary source we have read documents them.
Measure it on your own catalog
With no measured Perplexity data to lean on, the honest substitute is your own. Rather than trust a directional hypothesis, put real products in front of Perplexity for the queries you care about and record how often it recommends or cites you, your agent win rate on that specific engine. That is a number you can move and re-measure, where a borrowed benchmark would only be a guess.
The repeatable protocol (the prompts, the sampling plan, and the error bars that keep the result honest) is documented in how we test agent selection, which covers Perplexity alongside ChatGPT and Gemini. AgentMint.net publishes no Perplexity figures yet; when the lab produces them they will replace the hypotheses on this page, and until then the results stay in a "data collection in progress" state rather than a placeholder number.