A product description has one job: close the gap between “this looks relevant” and “I will buy this”. Almost everything that fails at that job fails the same way — it describes the product to someone who has not yet been given a reason to care about it.
Open with the outcome, not the object
The first line should say what changes for the buyer. Specifications support that claim; they cannot make it. A reader still deciding whether this category of thing solves their problem will not parse a spec table to find out.
| Weak opener | Working opener |
|---|---|
| Weak openerPremium stainless steel water bottle with vacuum insulation | Working openerCold at 5pm, whatever your car did to it at noon |
| Weak openerErgonomic office chair with adjustable lumbar support | Working openerBuilt for the eighth hour, not the first |
| Weak openerAdvanced AI-powered content generation platform | Working openerA finished first draft before your coffee goes cold |
Notice that the working versions still imply the specification. Insulation, lumbar support and speed are all in there, expressed as consequences rather than attributes.
Translate every feature into a consequence
Take each feature and finish the sentence “which means…”. If you cannot, the feature does not belong in the description — put it in the spec table, where the buyers who care will find it.
- “Double-walled vacuum insulation” → which means it is still cold after eight hours in a hot car.
- “Machine washable” → which means you are not hand-washing it after every use.
- “Unlimited posts on Pro” → which means you stop rationing drafts halfway through the month.
Answer the objection the reader already has
By the time someone reads a description they have a specific worry. Will it fit? Will it last? Is it worth twice the price of the obvious alternative? Descriptions that ignore the worry lose to the ones that name it.
You already know what the objections are: they are in your support tickets, your returns reasons and your pre-sale emails. Pick the two most common and answer them in plain language.
Use a structure that survives skimming
One-line promise
The outcome, in under fifteen words. This is the only line most visitors read in full.
Two or three sentences of context
Who it is for and the situation it is built for — naming the buyer without flattering them.
Three to five bullets
Feature plus consequence, never feature alone. Keep each under two lines.
Objection paragraph
The two worries that stop the sale, answered directly.
Specifications
Dimensions, materials, compatibility, warranty — factual, scannable, complete.
Cut these
- Superlatives you cannot evidence: “best in class”, “world-leading”, “revolutionary”.
- Filler openers: “Introducing…”, “Look no further…”, “Whether you are a beginner or a professional…”.
- Adjective stacking: “premium, high-quality, durable construction” says less than “survives a dishwasher”.
- Anything repeated from the product title. The reader has just read it.
Write for search without writing for robots
Product pages do rank, and the phrases buyers search are usually the ones they would say out loud: the category, the use case, the constraint. “Insulated water bottle for cycling” is a search. “Premium hydration solution” is not.
Put those natural phrases in the title, the first paragraph and one bullet. That is the whole optimisation — repetition beyond it hurts the copy without helping the ranking.
Test one variable at a time
When you rewrite, change the opener first and leave everything else alone. It is the highest-leverage line and the easiest to attribute. Changing the whole description at once tells you that something worked, but not what.
And give a test enough traffic to mean something. On a page with forty visitors a week, a difference of two conversions is noise, however much it looks like a result.