← All postsHow-to

Product description: answering the question that stops the purchase

A product description exists to remove doubt, not to praise. What to include, the specifics buyers actually search for, and why copying the manufacturer text costs you traffic.

How-toP

A product description is not advertising. By the time somebody is reading it they have already decided they want this kind of thing — what remains is a short list of doubts, and the description either resolves them or loses the sale to a competitor whose page answered the same question. Writing it as praise rather than as answers is the commonest and most expensive mistake in online selling.

What a product description has to answer

  • Will it fit, physically — dimensions, weight, capacity, in numbers rather than adjectives.
  • Will it work with what I already have: compatibility, voltage, thread size, version.
  • What exactly is in the box, which is the question support answers most often after the sale.
  • What it is made of and how it is finished, because that decides perceived quality more than any claim.
  • How it is cared for, where that affects whether somebody can live with it.
  • What it is not suitable for, which builds more trust than any amount of enthusiasm.

The specifics buyers search for

People searching with intent use exact terms: a model number, a measurement, a material, a compatibility. Those are the phrases that bring somebody ready to buy, and they are precisely what gets edited out in favour of smoother prose. Keep the numbers, keep the model references, keep the awkward technical words — a page that reads slightly like a specification sheet will outperform a beautifully written one that never states the diameter.

Do not paste the manufacturer's text. Hundreds of retailers have the same paragraphs, so the page has nothing of its own to rank with, and search engines have no reason to prefer yours. Rewriting the same facts in your own words, with the details your customers ask about, is the cheapest competitive advantage available on a product page.

Structure that gets read

  1. Open with one sentence stating what it is and who it suits, so somebody in the wrong place can leave immediately.
  2. Put the specifications in a list rather than in prose — nobody reads a paragraph to find a measurement.
  3. Answer the top three support questions for that product in the description itself.
  4. Keep claims checkable, since one exaggeration undermines the specification next to it.
  5. Say what is missing or limited, which reduces returns more than any policy change.
  6. Write for somebody who has never seen the product and cannot pick it up.

Where to find the content

In your own support history. The questions people ask before buying are the missing parts of the description, and the ones they ask after buying are the parts that caused a return. Both lists are already in your inbox, and working through them is faster and more accurate than any exercise in rewriting copy — the words that sell a product are usually the answers to the questions somebody already asked about it.

Ettex Web keeps the product page and its content in one place, so updating a description is an edit rather than a project, and the specifics stay where buyers and search engines both look for them. Whether the page actually sells belongs with the conversion tracking, since a description that reads well and converts nobody is still the wrong description.

Frequently asked

How long should a product description be?

Long enough to answer the doubts and no longer. Specifications in a list, the three commonest questions answered, and nothing written purely to fill space.

Can I use the manufacturer's description?

You can, and hundreds of other retailers already have. The page then has nothing distinctive to rank with, which is why rewriting the same facts yourself pays off.

Should a description mention limitations?

Yes. Stating what something is not suitable for builds trust and reduces returns more effectively than changing the returns policy.

MI
Written by Maria I.

Part of the Ettex team — writing about product, engineering and the future of work.

More posts
Get the best of the Ettex blogProduct news, guides and tips — straight to your inbox, no spam.