Product page design: what converts, and what is decoration
Product pages convert when they answer the buyer's questions first: real size, delivered price, delivery date, fit and returns. What to show, and where.
By Sohail Hussain21 November 20265 min read
A product page converts when it answers the buyer's questions before they have to ask: what it looks like at real size, what it costs delivered, when it will arrive, whether it fits or works for them, and what happens if it does not. On a phone, the photo, title, price, variant choice, add-to-cart button and delivery estimate belong on the first screen. Everything else, from the description to reviews to cross-sells, goes below in the order buyers look for it. Most of what makes a product page pretty does not make it sell.
What must be visible before the shopper scrolls?
Design the mobile version first; it is where most shoppers see the page. The first screen should hold:
- The main photo, large, swipeable to the others.
- The product name, in plain words a buyer would search for.
- The price, including tax where buyers expect it, and the saving if it is on sale.
- A rating summary, if you have enough real reviews to show one.
- Variant choice, such as size or colour, if the product has them.
- The add-to-cart button, unmissable.
- Delivery estimate, as a date or a range of days, not just "fast shipping".
Shopify and WooCommerce themes put most of this in place. The gaps we see most often are the delivery estimate, which themes rarely show by default, and a price that excludes costs the buyer discovers at checkout. Both feed directly into cart abandonment. When we design storefronts as part of our e-commerce development work, the product page template gets more time than the homepage, because it is where buying decisions happen.
Which elements earn their place, and which do not?
| Element | Why it helps | Common mistake |
|---|---|---|
| Six to eight photos | Answers visual questions without words | Several near-identical angles; no sense of scale |
| Size guide next to the size selector | Reduces wrong sizes and returns | Hidden in the footer or a PDF |
| Delivery date estimate | Removes the biggest unknown | Shown only at checkout |
| Returns summary near the button | Lowers the risk of buying | A link to a long policy page |
| Specifications table | Lets comparers scan | Specs buried in paragraphs |
| Reviews with photos | Shows the product in real homes | Only star ratings, or obviously filtered reviews |
| Cross-sells | Raises order value | Placed above the add-to-cart button |
| Autoplay carousel or video at the top | Rarely helps | Slows the page and pushes the button down |
How many photos, and which ones?
Each photo should answer a question. A typical set: front, back or side, a close detail of material or finish, the product in use, and one that shows scale, such as in a hand or next to a familiar object. Clothing needs it worn, on more than one body type if you can. Furniture needs it in a room with dimensions shown.
Keep a consistent aspect ratio so the gallery does not jump, allow zoom on tap, and compress every image. A product page with five 2 MB photos is slow on mobile data, and the main image is usually what Google measures as the page's Largest Contentful Paint. The image compressor shows how much your photos can shrink without visible loss.
How should variants, sizes and stock be shown?
Show colour as swatches and size as buttons, not dropdowns, so every option is visible at once. Make unavailable combinations visibly unavailable instead of letting the shopper pick one and fail. Update the photo when the colour changes. Put the size guide right next to the size selector, with measurements in the units your buyers use.
Show stock only when it helps the buyer: "In stock, ships tomorrow" is useful. "Only 2 left" is useful only when true. Fake scarcity is a regulatory risk as well as a trust problem; India's dark patterns guidelines name false urgency as a prohibited practice.
What belongs in the description?
Write for someone scanning on a phone. Open with two or three sentences on what the product is and who it suits. Follow with short sections: what it is made of, how big it is, what is in the box, how to care for it. Put technical details in a table. Add a short FAQ for the questions customer service actually gets.
Write your own copy. Manufacturer descriptions appear on every site selling the same item, give Google no reason to rank your page over theirs, and rarely answer the questions your buyers ask. The e-commerce SEO checklist covers the search side of product pages.
Where do reviews and trust details go?
Put the rating summary near the title and the full reviews further down, with photos from buyers if you have them. Do not hide negative reviews; a product with only five-star reviews looks filtered.
Next to the add-to-cart button, add three short lines: delivery time, returns window, and accepted payment methods. Those three answer most of the doubts that stop a purchase.
Some details are legal requirements, not design choices. In India, the Consumer Protection (E-Commerce) Rules require sellers to show information such as the seller's details, return and refund terms and, for imported goods, country of origin, and packaged goods have Legal Metrology labelling rules. Other countries have their own. Ask your lawyer which apply to your products.
Add Product structured data so search results can show price, availability and ratings. Google's product structured data documentation lists the required and recommended fields, and our product schema generator builds the JSON-LD for a page. Mark up only reviews that are real and visible on the page.
How do you know whether a change worked?
With enough traffic, run an A/B test on one change at a time: the delivery estimate, the photo order, the button position. Most small stores do not have the traffic for a test to reach a clear answer in a reasonable time. In that case, make changes you are confident in, compare add-to-cart rate for a few weeks before and after, and note anything else that changed, such as a sale or a new traffic source. Simple A/B tests covers how much traffic a test needs.
The product page is one template applied to every product, so improvements multiply across the catalogue. If your theme makes these changes hard, that is a platform question; how to choose an e-commerce platform covers the options.
Was this guide useful?