Product page structure: what a buyer needs before deciding
Product pages are usually designed as compositions and should be designed as answers. A buyer arrives with a short, predictable list of questions, and the page either answers them in order or loses to a competitor who does.
The same structure that converts also ranks, because search engines reward pages that resolve the query rather than decorate it.
The questions, in the order they arrive#
- Is this the right thing? Title, key image, one line that names what it is.
- Which one do I want? Variant selection with real availability, not a dropdown of disappointments.
- What does it cost me in total? Price, tax status, and a shipping estimate before checkout.
- When will it arrive? A date range beats "fast delivery" every time.
- Will it fit or work? Dimensions, materials, compatibility, sizing guidance.
- What if I am wrong? Return window and who pays return postage.
- Do others agree? Reviews, close to the decision, not buried at the bottom.
What belongs above the fold on a phone#
| Element | Why it earns the space |
|---|---|
| Image with a real sense of scale | Answers the first question instantly |
| Name and one-line description | Confirms the arrival was correct |
| Price with tax status | Prevents the last-step surprise |
| Variant selector with stock state | Prevents a dead end |
| Delivery estimate | The second most common pre-purchase question |
Description writing that does two jobs#
Write the description for the buyer who is about to spend money, using the words they used to search. Structured attributes go in fields, not prose; prose covers what the fields cannot — how it feels, what it is for, what it is not for.
Saying what a product is not suitable for reduces returns measurably and costs nothing.
Structured data and images#
Mark up product, price, availability and reviews so results carry them. Serve images in a modern format at the size actually displayed, with the first image never lazy-loaded — it is what the buyer is waiting for.
Frequently asked questions
How long should a product description be?
Long enough to answer the questions above and no longer. Length itself ranks nothing.
Should reviews sit near the price?
Near the decision. For considered purchases that means close to the buy area, not at the page bottom.
Do I need structured data?
Yes. Price and availability in results affect click-through more than most on-page changes.
product page designproduct detail pageecommerce uxstructured data productsproduct descriptions
