E-commerce product page: how to write one that helps buyers decide

An e-commerce product page has one objective: to help the buyer decide, then move them to act. Depending on the site, that action is adding to the basket, requesting a quote or downloading a document. The page follows a fixed order: use, benefit, proof, action, and the product description — the text of that page — carries most of it. Anything that does not serve this decision comes out.

We audited the product page for a corner desk at a distributor of office furniture for businesses. The page was complete: dimensions, materials, environmental and quality certifications, warranty, assembly service. For a business buyer, the last three were the strongest arguments. Yet they sat in the middle of long paragraphs. The description listed the features without saying what they did for the buyer, and it ended without a call to action. The content was all there, but its order did not serve the decision.

Three notions to settle before writing

Our template rests on three definitions that the whole team must share.

• Intent is what the buyer wants to do on the page: compare, understand, buy, ask for a price.
• Promise is the practical benefit, stated simply: time saved, comfort, lower cost.
• Proof is any verifiable element that reduces perceived risk: a figure, a customer review, a label, a warranty.

Without proof, the buyer has to take the brand at its word. Without a promise, the buyer has to work out the advantage of each feature on their own.

The order that helps buyers decide: use, benefit, proof, action

The buyer first wants to know whether the product fits the use they have in mind. Next they want to know what they gain, then to check that it is true. They act last. The page follows this reasoning.

The corner desk page did not keep to this order: the main arguments did not appear at the top, the benefits were not stated, and the action was missing. Our audit recommended a box at the top of the page gathering the key selling points, then subheadings to break up the text.

The six-block template

1. The title (H1) promises a use and a benefit: “{product} for {specific use}, {benefit}”. It is never just the product name.
2. The standfirst is two sentences long. The first sets the context of use, the second the promise.
3. The benefits, three to five of them, are ranked from most to least important. Each one carries a short proof.
4. Proof and reassurance bring together the review rating, the returns policy, warranties, labels and certifications.
5. The calls to action are limited to one main call (buy, request a quote, try) and at most one secondary call (download the guide, see the comparison).
6. Useful links and the FAQ close the page. The links lead to variants, the user guide, the comparison and the returns policy; the FAQ answers the three main purchase objections in three questions at most.

A reconstructed example

The example below applies the template to a fictitious product; its figures are invented for illustration.

• Title: Noise-cancelling headset for open-plan offices: stay focused for four hours at a stretch
• Standfirst: In an open-plan office, noise interrupts your work. This headset reduces background noise and stays comfortable during video calls.
• Benefits: fewer interruptions, thanks to active noise reduction; a clear voice on video calls, thanks to a dual microphone that filters background noise; comfort all day long, thanks to a weight of 260 g and breathable ear cushions.
• Reassurance: rated 4.6 out of 5 (312 reviews), 30-day returns, replaceable parts.
• Calls to action: “Add to basket”; “Download the Working in Peace guide”.

Writing rules

• Short words and short sentences.
• One strong verb per sentence.
• Parallel lists: every bullet has the same grammatical form.
• The key message at the end of the sentence.
• No technical term without an explanation.

These rules belong to the brand voice. When several writers produce the descriptions, the rules are documented with the rest of the voice, for example in a Brand Voice Framework.

Search optimisation for the page

• The SEO title runs to 50–60 characters, the meta description to 140–155.
• The H1 and the SEO title differ.
• Product structured data, and FAQ structured data where relevant, are in place.
• Internal links lead to variants, the guide and the comparison.

Customer reviews play two roles: they serve as proof for the buyer, and they add text unique to each product.

Measuring, then keeping the catalogue alive

Track three measures over 28 days:

• the click-through rate from the category page and from search results;
• the add-to-basket rate, or the quote request rate;
• the share of visitors who read half of the page.

Test one element at a time, over 14 to 28 days: the title (use or quantified benefit), the standfirst (the buyer’s problem or strong proof), the call to action (precise verb or generic verb), the presence of a comparison. Keep the winning version and record its effect.

In a catalogue, every page sooner or later calls for one of three decisions:

• merge two pages that target the same intent: keep the stronger one and carry over the other’s reviews and proof;
• update a page whose impressions rise while conversions fall, or whose proof is out of date;
• delete or rebuild a page with no clicks over a long period, outside the remit or with too weak a promise.

In every case, record the reason, the date and the action. A content inventory gives you the starting list.

Writing product descriptions with AI

The template serves as instructions for an AI tool: the title, the standfirst, the benefits and their proof, one main call to action, three FAQ questions, the writing rules. The AI then produces descriptions with the same structure.

It does not have the proof: you have to give it the review rating, the warranty or the certification. A person reviews each description against the same checklist. Does the title promise a use and a benefit? Does each benefit have verifiable proof? Is the call to action single and precise? Does the FAQ cover the three main objections?

The template sets the order in which the buyer receives the information, whoever the writer is.

Frequently asked questions about the e-commerce product page

How do you write a product page?

Write it in the order use, benefit, proof, action. The title promises a use and a benefit. The standfirst sets the context and the promise in two sentences. Three to five benefits follow, each with its proof. The page ends with one main call to action and a three-question FAQ.

How do you give a product page context?

The standfirst carries the context. Its first sentence describes the buyer’s situation when they use the product: a noisy office, a building site, a remote meeting. Its second sentence says what the product changes in that situation.

What should you check before publishing a product page?

The title contains a use and a benefit. Each benefit has proof. The page has only one main call to action. The SEO title and meta description are the right length, the H1 differs from the SEO title, and structured data is in place. Finally, reading the page aloud reveals no unexplained technical term.

To rework an entire catalogue, contact us.