Perplexity Not Showing Your Products? Here's Why and How to Fix It

What I Learned From 90 Perplexity API Runs

I built an AI Search Readiness scanner and used Perplexity's API (sonar-reasoning-pro) extensively for research. Over 90 API runs, 658 citations, 485 domains. The goal was to figure out what actually makes Perplexity show your products.

The honest answer is more complicated than most guides suggest. Perplexity Shopping does crawl your site directly and display product cards with images, prices, and reviews. But whether it chooses your products over competitors depends on factors that are hard to isolate cleanly.

This guide covers what you can control: the structural and technical prerequisites. I will also be upfront about what my data says regarding the limits of structural fixes alone.

Four Dimensions That Affect Perplexity Visibility

When Perplexity evaluates whether to show your products, it considers at least four things. I use the same framework in my scanner, so you can measure each one:

This article uses the same four dimensions as the AI Search Readiness Score. You can run your site through the scanner to see where you stand on each, then come back here for specific fixes.

Symptom Table: What You See vs. What Is Likely Wrong

Start here. Match what you observe in Perplexity to the most likely root cause before diving into individual fixes.

Step 1: Verify PerplexityBot Has Access

Dimension: Machine Readability

This is the one check where I can speak with confidence: if PerplexityBot is blocked, nothing else matters. Perplexity uses its own crawler with the user agent string PerplexityBot.

How to check:

1. Visit yoursite.com/robots.txt in your browser
2. Search for "PerplexityBot" — if there is a Disallow rule, that is your blocker
3. Check for blanket User-agent: * rules that might block all bots from product pages
4. Check your CDN/WAF settings (Cloudflare, Sucuri, Akamai) — some have default AI bot blocking

# Correct robots.txt for Perplexity access
User-agent: PerplexityBot
Allow: /

# Also allow other AI crawlers
User-agent: OAI-SearchBot
Allow: /

User-agent: Google-Extended
Allow: /

Sitemap: https://yoursite.com/sitemap.xml

Step 2: Check Product Schema Completeness

Dimensions: Extractability + Offering

Perplexity Shopping needs specific Product schema fields to display product cards. Here is the minimum required versus recommended:

I should note: having complete schema is a prerequisite for product cards, but I have seen sites with perfect schema that still do not appear. Schema completeness is necessary but not sufficient.

Step 3: Ensure Server-Side Rendering

Dimension: Machine Readability

PerplexityBot, like most AI crawlers, does not reliably execute JavaScript. If your product data is loaded by client-side JavaScript (React, Vue, Angular SPAs), Perplexity may see an empty page.

I confirmed this in my own scanner: sites where the static HTML word count was under 50 words had dramatically lower visibility. In the scoring model I built, I apply a 0.5x penalty to Machine Readability for JS-dependent pages. That penalty exists because the data supports it.

The test: View your product page source code (Ctrl+U or Cmd+U). If the product name, price, and description are not visible in the raw HTML, they are invisible to Perplexity.

Solutions by platform:

• Shopify, WooCommerce, Magento: Server-rendered by default — check that custom themes or plugins have not broken this
• Next.js / Nuxt.js: Use SSR or SSG for product pages — avoid client-only rendering
• Custom SPA: Implement SSR, pre-rendering, or at minimum inject JSON-LD Product schema into the static HTML shell
• Headless CMS: Ensure your frontend framework renders product data server-side, not client-side

Step 4: Add Review and Rating Data

Dimensions: Trust & Entity + Offering

Products with reviews appear more frequently in Perplexity answers. Perplexity displays star ratings in product cards when aggregateRating schema is present.

• aggregateRating with ratingValue (1-5 scale) and reviewCount
• Individual Review schema with author name, date, and review text
• Reviews must be in the server-rendered HTML (not lazy-loaded)
• At least 3 reviews recommended for credibility

Step 5: Create Content That Matches Query Intent

Dimension: Extractability

This is where my research data becomes most relevant. Content relevance to the specific query was the strongest predictor of citations I found. Sites in the same topic as the query were cited at 5.17%, versus 0.08% for off-topic sites. That is a 62x difference.

For product queries, this means your content needs to directly answer what the user is asking. Generic product descriptions do not get cited for "best [product] for [use case]" queries. You need content that explicitly addresses those use cases.

What to add to your site:

• Category page FAQ sections — answer "what is", "how to choose", "what are the differences" questions
• Comparison tables — side-by-side product comparisons with specs, prices, and "best for" recommendations
• Buying guides — comprehensive guides that match "best [category] for [use case]" query patterns
• Product page TL;DR — 2-3 sentence summary of who the product is best for and why, placed above the fold

What My Data Actually Shows

I want to be straightforward about what I found versus what the industry commonly claims. From 90 Perplexity API runs across 485 domains:

• Structural readiness scores did not predict citations. The correlation between my 26-check readiness score and whether a site got cited was r=0.009 with p=0.849. Essentially zero. I tested multiple sub-hypotheses (thresholds, necessary conditions, within-topic) and they were all null.
• Content relevance was the real signal. Same-topic sites were cited at 5.17% vs. 0.08% for cross-topic sites. No structural factor came close to that effect size.
• Citation instability is real. 29.3% of citations appeared in only one out of three identical runs on the same queries. If your product appears one day and disappears the next, that may just be Perplexity's inherent non-determinism, not something you did wrong.
• Access is still a hard prerequisite. Sites blocking PerplexityBot in robots.txt had near-zero product card visibility, even when their schema was technically complete. You cannot get cited from a page that cannot be crawled.

The practical implication: fix the structural prerequisites (crawl access, SSR, schema), but invest most of your energy in content that directly matches the queries your customers are asking. That is where the actual leverage is.

30-Day Perplexity Product Visibility Plan

A realistic week-by-week plan. I have re-ordered this based on what my data suggests matters most: prerequisites first, then content relevance.

Two Patterns I See Repeatedly

Perplexity-Specific Technical Requirements

Perplexity has some requirements that differ from other AI search engines. I have used all three APIs in my research, so these comparisons come from direct observation:

The 10-Point Perplexity Visibility Checklist

These are the structural prerequisites I would check first. They will not guarantee citations (my data is clear on that), but missing any of them can block you entirely:

I will be honest about the limits of what I know. The structural fixes in this guide are necessary prerequisites — without crawl access and server-rendered content, you are invisible to Perplexity. But my research (90 API runs, 658 citations, 485 domains) shows that structural readiness alone does not predict whether you get cited.

Content relevance to the specific query matters 62x more than structural factors. Fix the prerequisites, then invest your energy in creating content that directly answers what your customers are asking Perplexity. Run your domain through the AI Search Readiness Score to check the structural prerequisites, and see our Schema.org Markup Guide for E-Commerce for detailed schema setup.