How the Perplexity Merchant Program works: free feed-based application, GTIN requirements, the Product schema it reads, and how to measure results.
Someone asks Perplexity "best insulated travel mug under $30" and gets back a short list of specific products with prices, images, and buy links. The Perplexity Merchant Program is how your products earn a spot on that list. It is free, the application is a product feed rather than a sales call, and the whole thing takes an afternoon if your feed already exists. This guide walks the setup end to end, names the feed fields that matter, and is honest about the parts Perplexity has not made public.
It puts your products into the pool Perplexity draws from when it answers shopping questions. When a user asks Perplexity to compare, recommend, or find a product, the engine pulls candidates from merchant feeds and live pages, then presents a curated set with images, prices, and links. Membership is what makes your catalog eligible for that set. Joining costs nothing.
Here is what it does not do. It does not guarantee that your products appear for any given query. Perplexity has not published a ranking algorithm, so nobody outside the company can tell you the exact weighting of price, relevance, feed quality, or page signals. Treat anyone selling "guaranteed Perplexity placement" with suspicion. Membership buys eligibility, not a slot.
The honest framing: this is closer to submitting a Google Shopping feed than to buying an ad. You make your catalog legible and trustworthy, then you compete on the merits of the products and the cleanliness of your data.
The application is short and feed-centric. You sign up as a merchant through Perplexity's merchant onboarding, then provide a product feed that describes your catalog. There is no long approval interview and no integration sprint. If you sell physical products and can produce a structured feed, you meet the bar.
I want to be precise about one thing the docs leave fuzzy. Perplexity has not published a fixed approval timeline, so I will not invent one. Plan for a review window rather than instant activation, and do not promise a launch date that depends on Perplexity flipping your account live. Submit early, then track when PerplexityBot starts crawling the URLs in your feed. That crawl activity is your real signal that the system is reading you.
Perplexity accepts a Google Shopping-style product feed, typically a CSV (TSV and XML feeds follow the same field model). If you already export a feed for Google Merchant Center, you are most of the way done. The field names match the Google Shopping spec, which is the point: one feed, two destinations.
These are the fields worth getting right:
id — a unique, stable SKU per product. Do not recycle IDs between products.title — specific and front-loaded. "Stainless Steel Insulated Travel Mug, 16oz" beats "Mug — Great Gift!"description — plain facts: material, size, what it fits, what is in the box.link — the live product URL, the same one carrying your Product schema.price — with currency, matching the price shown on the page.availability — in_stock, out_of_stock, or preorder, kept current.image_link — a direct, high-resolution image URL that loads without a login.gtin — the global trade item number (UPC, EAN, or ISBN). More on this below.brand — the manufacturer or your own label for private goods.google_product_category — the taxonomy value that tells the engine what shelf the item belongs on.GTINs deserve their own paragraph. A GTIN is the barcode number that uniquely identifies a manufactured product worldwide, and it is the single strongest signal for matching your item to a shopping query. A feed row with a valid GTIN lets Perplexity confirm it is looking at the exact product a user means, dedupe it against other merchants, and trust your price. Rows without GTINs still work, especially for handmade or private-label goods that genuinely have none, but they carry more burden of proof. If your supplier provides GTINs and you have left the field blank, filling it in is the highest-impact feed fix you can make.
Two failure modes show up constantly. First, feed-versus-page price drift: your feed says $24.99, the page says $27.99 after a quiet price bump, and the mismatch reads as stale data. Second, image URLs behind a CDN that blocks bots, so image_link resolves to nothing for the crawler. Both quietly suppress products without any error message telling you why.
Your feed is one input. Your live pages are the other, and Perplexity reads structured data off them to confirm and enrich what the feed claims. The markup that matters is schema.org/Product, with a nested Offer for price and availability, and AggregateRating if you have real reviews.
Keep three things straight. The Product object carries name, brand, GTIN, and image. The Offer object carries price, priceCurrency, and availability, and these must agree with your feed and with the visible page. The AggregateRating object carries your star average and review count, which gives the engine a reason to prefer a proven product over an unrated one.
One technical requirement sits underneath all of it: the markup has to be in server-rendered HTML. If your price and schema only appear after JavaScript runs in a browser, a crawler fetching the raw page sees an empty shell. Render the JSON-LD on the server, view source on a real product URL, and confirm the price is sitting there in the HTML before any script executes. This is the same readiness bar that AI search visibility on Shopify depends on, and it is where a surprising number of otherwise-good catalogs fall down.
Here is a pattern worth understanding before you spend a dollar on anything else. Perplexity leans heavily on Reddit and forum discussion when it answers product questions. Ask it "most durable hiking boots" and the citations are frequently Reddit threads, niche forums, and community roundups rather than brand pages. Your products can be in the feed and still lose to a competitor that real people are recommending in r/hiking.
Be precise about what this is. It is an observed pattern in Perplexity's citation behavior, documented by people watching their own referral logs and by Perplexity's well-known content partnership with Reddit. It is not a published ranking factor, and Perplexity has not said "Reddit mentions raise your product score." So do not treat it as a lever you can pull mechanically. Treat it as a description of where the engine looks for trust.
The practical read: genuine presence in the communities where your category gets discussed influences which products Perplexity surfaces, because those communities are part of what it cites. That argues for real participation and real product quality that earns organic mentions, not for spamming subreddits, which gets you removed and poisons the well. The feed gets you eligible. The reputation gets you recommended.
Three signals tell you whether the program is working, and you want all three.
Crawl activity comes first, because it is the earliest proof Perplexity is reading you. Watch your server logs for PerplexityBot (catalog and indexing crawls) and Perplexity-User (live fetches triggered by a real user's question). When you see PerplexityBot pulling the URLs from your feed, the pipeline is live, even before any sale shows up.
Referrals are the payoff signal, and there is good news here. Perplexity referrals are usually trackable in your analytics. Clicks from Perplexity answers tend to arrive with a perplexity.ai referrer, unlike a chunk of ChatGPT traffic that lands as direct and disappears into the dark-traffic bucket. Filter your referrer report for Perplexity and you can watch the channel grow.
Citations are the leading indicator that sits between crawl and click. Periodically run your own category queries in Perplexity and note whether your products and pages get cited, and which competitors and Reddit threads show up beside them. That tells you where you stand before the traffic numbers move. For a repeatable method, see how to track AI citations, which covers logging citation appearances over time instead of eyeballing it once.
Put together, the loop is simple. Submit a clean, GTIN-rich feed. Confirm PerplexityBot crawls it and your Product schema renders server-side. Build genuine presence where your category is discussed. Then measure citations and Perplexity referrals to see what is landing, and feed that back into your titles, descriptions, and which products you push.
Written by Crawlytics Team. Crawlytics tracks AI bots, generates llms.txt, and powers WebMCP commerce, all from one snippet on any stack. See how it works →
Yes. Joining the Perplexity Merchant Program costs nothing. You sign up as a merchant and submit a product feed, with no membership fee to be eligible for Perplexity shopping answers. Perplexity has not published per-transaction merchant fees for organic catalog inclusion, so treat the join itself as free and watch the official merchant docs for any future commercial terms. Be wary of third parties charging for "guaranteed placement," since the program grants eligibility, not a guaranteed slot, and Perplexity controls ranking.
Not for every product, but include them wherever they exist. GTINs (UPC, EAN, ISBN) are the strongest signal for matching your item to a shopping query, confirming the exact product, and validating your price against other merchants. Manufactured goods almost always have a GTIN from the supplier, and leaving that field blank is a self-inflicted disadvantage. Genuinely GTIN-less products, like handmade or private-label items, can still appear by leaning on a precise title, brand, accurate google_product_category, and clean Product schema. The rule: fill in every GTIN you legitimately have.
Perplexity has not published a fixed approval timeline, so plan for a review window rather than instant activation. The most reliable real-world signal that your account is live is PerplexityBot beginning to crawl the URLs in your feed, which you can watch in your server logs. Submit your feed early instead of waiting for a launch deadline, and avoid promising stakeholders a go-live date that depends on Perplexity flipping your account active. Once crawl activity appears, your products are entering the pool Perplexity draws shopping answers from.
Yes, and that is the intended path. Perplexity accepts a Google Shopping-style product feed using the same field model (id, title, description, link, price, availability, image_link, gtin, brand, google_product_category), so the file you already export for Google Merchant Center usually works with little change. Before submitting, confirm prices match your live pages, image_link URLs load for bots, and availability is current. The one upgrade worth making is filling any blank GTIN fields, since those carry extra weight in how Perplexity matches and trusts your products.
Because Perplexity cites Reddit and forum discussion heavily when answering product questions, so the products real communities recommend tend to surface in its answers. This is an observed pattern in Perplexity's citation behavior, reinforced by its content partnership with Reddit, not a published ranking factor Perplexity has documented. The practical takeaway is to build genuine presence and real product quality in the communities where your category gets discussed, since those threads are part of what Perplexity reads. Spamming subreddits backfires, getting you removed and damaging the trust signal you wanted.
This page is part of Crawlytics.app. View all pages: llms.txt · llms-full.txt