Why vague copy loses
An assistant answering “best linen shirt for hot weather” needs to know the shirt is linen, that it's breathable and how it fits. If your page says “our best summer shirt, crafted with care”, it can't use you, so it uses someone else. Vague praise also can't be checked, so it adds no trust.
A structure that works
- 01Open with what it is and its key fact“Breathable 100% European linen shirt with a relaxed camp collar.”
- 02Answer the questions people askFit, size, material, care, what it's for. Use reviews: “Customers say it runs half a size large.”
- 03Give the specifics in a listMaterial, dimensions, weight, origin, care. Short lines are easy for people and machines to read.
- 04Finish with who it's for“Made for hot days and travel. Packs flat and creases softly.”
Rules worth keeping
- Never state what you can't back up. If you don't know the material, don't guess.
- Keep one product, one description. Copied text makes products indistinguishable.
- Use your shoppers' words. Reviews and support emails tell you what they actually ask.
- Keep your formatting. Tables, size charts and images help; keep them when you rewrite.
Catalog Studio follows these rules automatically, with fact lock on every plan: every claim shows its source, and anything unsupported is left out.
Questions
- How long should a product description be?
- Long enough to answer the obvious questions. Under 50 words is usually too thin; past 300 words, make sure it's still facts and not filler.
- Should I use AI to write them?
- AI is great at structure and tone, and bad at facts it doesn't have. Use it with your real product data and review every claim, or use a tool with a fact lock.