Fix the catalog
Writing product descriptions for AI discovery and human conversion
By Ankit Minocha, founding team at Atomz. Updated January 21, 2026.
A product description now has two readers: the shopper who buys and the assistant that recommends. Here is how to write one that serves both without sounding like a spec sheet.
A product description used to have one job, which was to persuade the person reading it. Now it has two readers, because before a shopper ever sees the page an assistant may have read it and decided whether to recommend the product at all. The trap is treating these as opposing goals, writing either evocative copy that converts but cannot be matched, or a dry spec dump that matches but does not sell. The good descriptions do both, and the way they do it is by separating the two layers rather than blending them.
Two readers, two layers
The shopper reads prose and responds to feeling and benefit, while the assistant reads fields and matches on facts. You do not have to choose, because they consume different parts of the page.
| The shopper reads | The assistant reads | |
|---|---|---|
| Wants | Benefit, feeling, reassurance | Attributes it can match |
| Responds to | "Keeps you warm without the bulk" | Material: merino, Weight: lightweight |
| Lives in | The description prose | The structured attributes and schema |
| Fails on | A spec sheet with no story | A story with no structured facts |
The move is to write the persuasive prose for the human and encode the matchable facts as structured attributes, so the same product page serves both readers from different layers instead of forcing one voice to do both jobs.
How to write the prose
Keep the copy genuinely useful and specific. Lead with what the product is for and who it suits, because that context is also what helps an assistant place it. Name the concrete details inside the story rather than gesturing at them, so 'merino wool, light enough to layer' beats 'premium materials and effortless versatility.' Say who it is not for where that helps, because precision builds trust with both readers.
How to encode the facts
Everything a shopper might search on should also exist as a structured attribute, written to your metafields and surfaced in schema: material, fit, use case, size, and the category-specific fields that matter. That is the layer the assistant matches, and it is invisible to the human, so it never makes your copy read like a database.
The test for a description
Read your description with the styling stripped away and ask two questions. Would a shopper still understand why to buy it? And could an assistant pull the attributes it would need to match a real query? A good description answers yes to both, from two different layers.
Descriptions written this way convert on the page and get recommended off it, because they stop forcing one paragraph to do two incompatible jobs. The audit shows which of your products carry the structured layer an assistant needs.
Subscribe to The Agentic Operator