Make every product page quotable
Product schema with price, stock, materials, fit and rating, in HTML rather than JavaScript. This is the difference between being priced into an answer and being invisible.
Optimise Content →Solutions · By industry
Shoppers ask AI for the best product before they browse, and the answer names a few brands with prices attached. Prefer tracks every shopping prompt in your category, shows which reviews and roundups decide them, and turns your product pages into ones AI will quote.
Shopping answers name three to five products with prices. Absence here is the whole funnel, because the buyer never browses.
The shelf math
How AI engines answer shopping questions, across 380 tracked retail domains.
The consideration set is built before the buyer browses.
Wirecutter, Reddit and Trustpilot carry the recommendation.
No Product schema means no place in a price prompt.
Faster than B2B, because retail sources re-crawl often.
Prefer benchmark · 380 D2C and retail domains · 6 engines · Q2 2026.
The shortlist · 01
Shoppers used to open five tabs. Now they ask once and get three products with prices and a verdict. Miss that answer and you are out of the comparison, and no analytics tool will show you the visit you lost.
ChatGPT, answered this morning.
Three stand out. Allbirds Tree Dasher 2, around $135, uses eucalyptus fibre and sugarcane foam and is the most comfortable for daily wear. On Cloudrunner, about $150, offers better support for longer distances. Veja Condor 3, roughly $160, is the most transparent on supply chain but runs narrow.
Who decides · 02
Retail citations go to editorial reviews, community threads and review platforms. Brand pages get cited to confirm price and specs, after the recommendation is already made.
One tracked category, 260 prompts, last 30 days.
Domains cited across 260 tracked shopping prompts, last 30 days. Editorial roundups decide the recommendation; your pages confirm the price.
The prompt map · 03
Two of them do not exist in software: price and occasion. Both move fast, both are seasonal, and both are won with data rather than copy.
Status of the best prompt in each family.
Live from the Fernwell demo workspace. Occasion prompts are tracked year-round, because Q4 answers are decided in Q3.
The playbook · 04
Each play maps to the Prefer tool that runs it, so this is a queue, not a PDF.
Product schema with price, stock, materials, fit and rating, in HTML rather than JavaScript. This is the difference between being priced into an answer and being invisible.
Optimise Content →Wirecutter, Runner's World and category guides out-cite brand pages five to one. Prefer finds the guides you are missing from and briefs the pitch.
Action Center →Prompts about fit, material and use case are where a small brand beats a giant. They need spec pages AI can read, not lifestyle copy.
Create Content →One recurring theme, sizing, shipping or returns, becomes the warning attached to your name in every answer. Prefer traces it and tracks the repair.
Answer Engine Insights →Seasonal answers are decided a quarter ahead, when AI crawls the guides. Ship in Q3 to win Q4.
Create Content →Every product named in your category, per prompt, per engine, per week. When a rival enters an answer you owned, you hear that day.
Competition →D2C vs marketplace · 05
A direct brand fights to be named at all. A marketplace seller fights to be the listing AI picks. Prefer ships a prompt set for each.
You own the product page and the reviews, so the job is making them quotable. Where you are exposed:
Exposure: a competitor's structured PDP gets priced into the answer, yours does not.
The listing is the page AI reads, and the platform controls it. Where you are exposed:
Exposure: an incomplete listing means the marketplace recommends someone else's.
Proof · 06
“We were spending on paid social to fix a problem that was really a markup problem. Once every PDP had real product data and we landed two roundups, assistants started recommending us with the price attached.”
Questions
By being readable and reviewed. Engines build shopping answers from editorial roundups, review platforms and community threads, then confirm price and specs from product pages that carry structured data. A brand with no Product schema cannot be priced into an answer at all.
Answer engine optimization for retail means earning a place in AI shopping answers rather than a rank in a results page. It combines structured product data, editorial and review placement, and fixing the complaint themes engines repeat about your brand.
Six families: category (best X for Y), comparison, attribute (fit, material, use case), price, reviews, and occasion or gifting. Price and occasion are unique to retail, both are seasonal, and both are won with data rather than copy.
Google AI Overviews draws on Merchant Center data, and every engine reads Product schema on your PDPs. Keeping price, availability and attributes accurate in both is the baseline for appearing in price and availability prompts.
Editorial roundups first, then review platforms and community threads. In Prefer's Q2 2026 benchmark of 380 retail domains, roundups took 31% of citations, review platforms 19%, community 18%, and brands' own pages 8%.
Ship and pitch early. Seasonal answers are largely decided a quarter ahead, when engines crawl the guides being published. Prefer tracks occasion prompts year-round so the pitch happens in Q3, not December.
Yes, and quietly. Engines summarise your review corpus, so a recurring theme like sizing or shipping becomes a caveat attached to your name in every consideration answer. Prefer traces the theme to its source so it can be fixed where it lives.
One to four weeks, faster than B2B, because retail sources are crawled frequently and prices change often. Structured data fixes usually show within the first crawl cycle.
See how answer engines describe your brand today, and where the openings are to outpace the competition.