How to make your product content readable by AI shopping agents
AI agents shortlist products by reading facts and evidence, not design. To be recommended, fix three surfaces: structured data, plain-text claims, and a review/UGC corpus an agent can reach.
The PDP read perfectly to a human shopper and almost nothing to an LLM scraping it for an answer. The gap between those two reads is not aesthetic. It is structural: paragraphs vs facts, prose vs schema, brand voice vs canonical phrasing. What follows is the audit we run on every onboarding.
In this article
Search-engine optimisation taught a generation of brands to write for a crawler. Agent readability is the next version of that discipline, sometimes called answer-engine or agent-engine optimisation, and it is stricter. A crawler indexed your page. An agent has to understand it well enough to stake a recommendation on it. The full discipline is laid out in the answer-engine optimisation playbook.
The good news: you do not need new content. You almost certainly already hold the facts and the customer proof. The work is making them legible to a literal reader, across the three surfaces below.
What does an agent actually read?
- Structured data: the machine-readable markup (Product, Offer, AggregateRating, Review schema) that states price, availability, attributes and rating as unambiguous facts.
- The plain-text description, the words an agent extracts when it strips your page to text. Vague copy here is invisible copy.
- The evidence corpus, reviews and customer photos/videos tied to the product, which the agent uses to corroborate every claim before it trusts it.
Why is structured data the floor?
If your product page does not emit clean structured data, an agent has to guess, and a cautious agent that has to guess will quietly prefer a competitor it does not have to guess about. Product, Offer and AggregateRating schema are not optional SEO garnish any more; they are the contract that says "here are my facts, unambiguously". Get them complete, accurate and consistent with what is on the visible page. The schemas worth prioritising are ranked in the twelve JSON-LD shapes agents quote.
Reviews and UGC are the evidence layer
Structured data tells an agent what you claim. Reviews and customer media tell it whether the claim holds up. An agent comparing two similar products leans toward the one whose claims are corroborated by a deep, recent, specific body of customer evidence, because that is the recommendation it can defend. A page with rich specs and no evidence reads, to an agent, like a confident stranger.
Structured data gets you into the agent’s consideration set. Customer evidence is what gets you out of it with a recommendation.
Rohin Aggarwal · Co-founder, Idukki
Agent-friendly vs agent-invisible
Agent-invisible page
Beautiful to a human, opaque to a machine.
Wins at
- Strong photography and brand feel
Struggles with
- Specs live only inside images
- Reviews load in a slow third-party iframe
- Claims are adjectives with no corroboration
- Structured data missing or inconsistent
Agent-readable page
Works for the human and the machine at once.
Wins at
- Complete, accurate Product + Review schema
- Specific, plain-text claims
- Customer photos/videos tied to the SKU, inline and fast
- Every claim has evidence behind it
Struggles with
- Takes a deliberate audit to get right the first time
The difference is rarely content quality. It is whether the content is reachable.
A checklist for this quarter
- 1Validate Product, Offer and AggregateRating schema on your top product pages.
- 2Rewrite vague claims as specific, plain-text facts that survive being stripped to text.
- 3Make sure Review schema is drawn only from real, attributable reviews with real dates.
- 4Pull customer photos and videos onto the PDP, tied to the product, rendered fast and crawlable.
- 5Tag that customer media so its subject matter is itself machine-readable.
- 6Test: paste your product URL into an AI assistant and ask it to summarise and compare the product. Read what it gets wrong.
- 7Fix the gaps it revealed, and repeat the test each month.
0%
of 18-34s use GenAI to search products
Bazaarvoice 2025 SEI
0x
AI weight on verified-buyer reviews
Industry consolidated
$0.0T
Global social commerce 2025
eMarketer
+0%
TikTok Shop US growth YoY 2025
eMarketer
Sources & notes
- 1Schema.org: Product, Offer, AggregateRating, Review types · The structured-data vocabulary agents and search engines consume.
- 2Google Search Central, structured data for products · Implementation guidance and validation.
- 3Baymard Institute, product-page UX research · What content shoppers and agents rely on.
Continue reading
2 pieces in this clusterThese long-form pieces on the Idukki blog link back to this article, go deeper on the cluster.
- AI search
Answer Engine Optimisation for Ecommerce: The Complete AEO Library
Being cited by ChatGPT, Perplexity and Google AI Overviews is the new ranking. This is the full, organised AEO library for ecommerce: foundations, crawlability, schema, evidence, and measurement, with a curated map so you can start anywhere.
- Strategy
Rights Clearance Is the Unsexy Moat: 3 Disputes We Won This Quarter
Win UGC rights disputes with a clearance ledger, not lawyers. Three real disputes resolved, plus the playbook that keeps each off your desk.
More from Rohin Aggarwal
- Industry playbook
How to run a UGC competition that fills your gallery, online and in-store
A prize plus a deadline plus a clear ask turns a trickle of UGC into a stream. The runbook: five formats, a schedule, copy templates.
- Conversational commerce
Why we built the Conversational PDP
A Conversational PDP answers the silent question that drives most product-page exits: curated Q&A first for the common doubts, an AI concierge scoped to your own data second.
- Strategy
PDP before and after UGC: what actually changes on the page
Add verified customer photos, video and reviews to the middle scroll of a brand-only PDP and conversion lifts. Here is what moves, scroll by scroll, and where "just add UGC" gets oversold.