How to Get Cited in Perplexity Shopping

By UpGeo · 2026-09-03

Direct answer: You get cited in Perplexity Shopping for ecommerce category queries by publishing comparison-ready pages with plain-text product facts, comparison tables, clear pros and cons, and Product/Offer/Review structured data. Then make those pages crawlable by PerplexityBot and easy for LLMs to read with an llms.txt file and clean HTML. That puts your page in the position of the easiest source for Perplexity to extract, compare, and recommend products for queries like “best carry-on luggage under $200” or “best 65-inch TVs for bright rooms.”

What Perplexity Shopping actually cites

Traditional rankings alone won’t get you cited. Perplexity Shopping pulls product details from pages that give the model direct, ready-to-compare answers. Most cited pages fall into one of three buckets:

• Category buying guides that compare 5–10 products in one table or structured list.
• Product detail pages that show price, specs, availability, shipping, and warranty as readable text instead of burying them in images or JavaScript.
• Review and question content with specific pros, cons, and use-case labels like “best for small apartments” or “best for wide feet.”

Perplexity crossed 100 million weekly queries in late 2024. Its Shopping experience now surfaces product cards with prices, review sentiment, and one-click checkout. Those cards most often come from merchant feeds and pages that stick to consistent, machine-readable product data. That’s why generative engine optimization differs from classic SEO: the engine has to extract facts fast, not just interpret relevance signals.

Step 1: Build comparison-ready category pages

Most ecommerce category queries are comparative, like “best budget espresso machines,” “best hiking boots for plantar fasciitis,” or “best OLED laptops under $1,500.” A standard category grid with 200 products doesn’t help Perplexity. A focused page with 5–8 products and clear comparisons does.

Your category page needs:

• A title that matches the query pattern, such as “7 Best Budget Espresso Machines Under $500.”
• A comparison table with product name, price, rating, key spec, and a “best for” label.
• A one-sentence verdict for each product: “Best overall for milk drinks because it includes a PID and steam wand.”
• A clear summary sentence that narrows the decision: “If you mainly drink black espresso, pick X; if you need latte performance, pick Y.”

Page element	What to include	Why Perplexity uses it
Comparison table	Price, rating, weight, dimensions, warranty, key spec	Lets it pull facts quickly instead of guessing from prose
Pros and cons	2–4 bullet points per product	Hands the model quotable reasons to recommend a product
Use-case labels	“Best for small kitchens,” “Best for bright rooms”	Matches category + modifier queries
Price/stock notes	“$299 at Amazon, often drops to $249”	Helps with price-sensitive Shopping suggestions

Step 2: Add Product, Offer, and Review structured data

Structured data lets Perplexity read the page without guessing from the layout. At minimum, add JSON-LD for Product, Offer, AggregateRating, and Review. Include GTIN, MPN, SKU, brand, price, currency, availability, rating value, and review count.

A minimal Product JSON-LD block looks like this:

{
  "@context": "https://schema.org",
  "@type": "Product",
  "name": "AeroPress Clear Coffee Press",
  "brand": "AeroPress",
  "sku": "APC-001",
  "gtin13": "0810159030124",
  "image": "https://www.example.com/images/aeropress-clear.jpg",
  "description": "Manual coffee press with Tritan body, 10 oz capacity, and included filters.",
  "offers": {
    "@type": "Offer",
    "price": "49.95",
    "priceCurrency": "USD",
    "availability": "https://schema.org/InStock",
    "url": "https://www.example.com/products/aeropress-clear"
  },
  "aggregateRating": {
    "@type": "AggregateRating",
    "ratingValue": "4.7",
    "reviewCount": "1384"
  }
}

On category pages that compare multiple products, use ItemList to list the products in your recommended order. The model can then reuse that ranking logic.

Step 3: Put plain-text facts on the page, not just images

Perplexity usually skips text trapped in images, PDFs, or interactive widgets. For each product on a category or product page, add a plain-text fact block that lists:

• Price and currency
• Availability
• Shipping time and cost
• Weight and dimensions
• Battery life, power, capacity, or other decision-critical spec
• Return policy and warranty length

Place those bullets under a subheading like “Product facts.” Don’t rely on a size chart or comparison chart saved as a JPG. The model needs to read the values directly from the HTML.

Step 4: Make your site crawlable and LLM-readable

Perplexity Shopping can’t cite what it can’t fetch. Make sure robots.txt allows PerplexityBot and that key product facts appear in the initial HTML instead of loading later through JavaScript. For a large catalog, build a dedicated llms.txt file that lists your best category pages, product data endpoints, and update frequency. We cover this in our llms.txt guide, and you can create a starting file with the llms.txt generator.

Check your allowlist against the AI crawlers that matter. At minimum, PerplexityBot, GPTBot, ClaudeBot, Google-Extended, and Perplexity’s shopping-related fetchers should reach product and category pages. The AI crawlers list has current user agents and verification steps.

Step 5: Align merchant data with product page data

Perplexity Shopping mixes page citations with merchant feed data. If a product page claims “in stock” but the feed says “out of stock,” Perplexity may drop the product or cite a competitor. Keep these fields aligned across your site, Google Merchant Center, Shopify feed, and affiliate networks:

• Price
• Availability
• Shipping cost
• Product title and brand
• GTIN or MPN
• Product URL

When these match, your product is more likely to show up as a shopping card, and your category page is more likely to appear as the explanatory citation.

Step 6: Update comparisons frequently

Perplexity leans toward fresh, specific information. Category pages with outdated prices or discontinued products lose citations quickly. Recheck priority category pages every 30 days and update price, stock, rating, and “best for” labels. When a product goes out of stock, swap in a comparable alternative and revise the summary sentence. A visible “Updated: [month/year]” line gives the model a useful freshness signal.

Priority checklist for ecommerce teams

• Create one comparison page for each high-intent product category query.
• Use a table with 5–8 products, not a 200-SKU grid.
• Add Product, Offer, AggregateRating, Review, and ItemList JSON-LD.
• Keep price, spec, shipping, and stock facts in plain HTML text.
• Check that PerplexityBot can fetch the page and the content isn’t JavaScript-only.
• Create an llms.txt file for priority category and product pages.
• Sync product data across your site and merchant feeds.
• Run the query “best [category] for [use case]” weekly and note whether your page appears in citations or product cards.

Winning in Perplexity Shopping doesn’t come from writing more content. It comes from structuring product knowledge so an AI answer engine can extract, compare, and defend a recommendation from your page in under a second.