A product description has one job: remove the reason someone hesitates. Everything else — brand voice, keyword placement, storytelling — is secondary to that.

The hesitation is usually specific. Will it fit? Will it last? Is it the same as the photo? What is missing from the listing that made them open a new tab to compare?

Lead with the outcome, not the specification

Specifications are evidence. They are not the argument. Translate the first into the second:

  • Spec: 320 gsm cotton.
  • Outcome: Heavy enough to hang straight and survive a hundred washes without going see-through.

Keep the specification — shoppers compare on numbers — but put it after the sentence that tells them why it matters.

Answer the top three questions in the first paragraph

Read your support tickets and returns reasons. The same three questions appear in almost every category:

  1. What exactly is this, and what is it not?
  2. Will it work for my situation — size, device, climate, skill level?
  3. What happens if it does not?

If those three are answered above the fold, the rest of the page can do its job.

Structure that scans well

  1. One-sentence summary — what it is and who it is for
  2. Three benefit bullets — each tied to a feature
  3. A short paragraph of context — when to choose this over the alternative
  4. Specification table — dimensions, materials, compatibility, care
  5. What is in the box — prevents a specific and common complaint
  6. Shipping and returns — one line, linked to the policy

This order matches how people actually read: skim the claim, check the benefits, verify the details, then look for risk.

Write for the comparison shopper

Most visitors have at least one other tab open. Help them compare honestly:

  • Say what the product is best for — and what it is not.
  • Name the trade-off. A lighter version is easier to carry and less stable; saying so builds trust and reduces returns.
  • Avoid vague superlatives. "Premium quality" is not a comparison; "thicker than the standard 180 gsm version" is.

Use the language customers use

Search and support both run on customer vocabulary, not internal vocabulary. If people search "waterproof phone pouch for swimming" and your page says "aquatic device enclosure", you have written for your catalogue team, not your buyer.

Mine reviews and tickets for the exact phrases people use, then use them in the description and the meta title.

Five mistakes that cause returns

  • Missing dimensions. Especially on furniture, apparel and anything that must fit into a space.
  • Ambiguous sizing. Give a measurement chart and say whether the fit is relaxed or true to size.
  • Unstated incompatibility. Model numbers, voltage, software versions.
  • Colour optimism. "Charcoal" that looks black on screen creates a predictable complaint. Describe the tone.
  • Hidden assembly or consumables. Batteries not included is fine — as long as it is said before checkout.

Keywords, without ruining the page

Place the primary term in the title, the first sentence and the meta description. Then write naturally. Variations belong in the specification table and the FAQ, where they read as information rather than repetition.

One clean mention in a useful sentence beats five awkward ones. Keyword stuffing is a conversion problem before it is an SEO problem.

A before-and-after test

Take your worst-performing product page and rewrite only the first paragraph using the three-question rule. Leave everything else untouched for two weeks. If the add-to-cart rate moves, you have found the lever — and the rest of the catalogue is now a priority list.

Writing that catalogue by hand does not scale past a few dozen products. That is exactly the work in our product copy service — templates per category, written per product.