Ecommerce · 29 Oct 2026 · 10 min read
Ecommerce Product Page Checklist: What Shoppers Need
A product page checklist covering photos, descriptions, price, delivery, returns, reviews and mobile layout, plus why shoppers leave and how to test.

What a product page has to do
A product page is where a shopper decides, usually on a phone and without touching the product. Use this checklist to find what yours leaves unanswered.
An ecommerce product page needs a clear name, one price with tax and delivery made clear, honest stock status, enough clear photos, a scannable description, size or colour choices, delivery and returns details, real reviews where you have them, and a buy button that is easy to reach on a phone. Check each item against what a shopper would ask in a shop.
An ecommerce product page checklist should start from the shopper's questions. A product page has to answer, within seconds, what a shopper would ask an assistant in a shop: what exactly is this, what is the full price, will it suit me, when will it arrive, and what happens if it is wrong. A page that leaves any of these open sends the shopper to another tab.
The data behind the page, such as photographs, weights, tax codes and variants, is gathered while the store is set up. Step 5 of how to start an online store covers that. This checklist covers how to present it on the page. Shoppers also judge the store as a whole, and signals such as clear contact details and plain policies that sit outside the product page matter too.
Ecommerce product page checklist
Use the table as a review sheet. Open one of your product pages on a phone and check each row honestly.
| Area | What to check | Why shoppers care |
|---|---|---|
| Name | The title says what the product is in the words a shopper would use, with the brand or model where it matters | It confirms they are in the right place and helps the page match searches |
| Price | One clear price, with a note on whether tax is included. Show a crossed-out price only if it was a real earlier price | Costs that appear late feel like a trick |
| Availability | In stock, low stock, out of stock or a back-in-stock date, shown near the button and for each variant | It stops people ordering what you cannot supply |
| Buy button | Easy to find on a phone without hunting, large enough to tap and clearly labelled | It is the action the page exists for |
| Photos | Enough views to answer what a shopper would check in hand, in a consistent style | They cannot touch the product, so the photos stand in for it |
| Description | The main points first, then a scannable list of facts, then detail | People scan before they read |
| Options | Size, colour or other choices, with the photo, price and stock changing to match | A wrong guess at a variant leads to returns |
| Delivery | Where you deliver, what it costs and a delivery time you can keep. Add a postcode or ZIP check if your platform supports one | It answers the question that decides many orders |
| Payment | Methods accepted, including any local options you offer | Payment preferences differ, and unclear options cause drop-off |
| Returns | A one-line summary with a link to the full policy, and a note if this product cannot be returned | It lowers the risk of buying from a store they do not know |
| Reviews | Real reviews only, shown where they exist | Fake or empty review boxes damage trust |
| Questions | A visible way to ask before buying | Unanswered doubts end the visit |
| Speed | The page and its images load quickly on mobile data | Slow pages lose visitors before they see the product |
How many photos does a product need?
There is no correct number. The test is whether the photos answer what the shopper would check if they were holding the item. A simple product may need only a few images. A product with sizes, textures, parts or fit questions needs more. Cover these views where they apply:
- A clear main image on a plain background that still reads when shrunk to a small square on a category page.
- Other sides and angles.
- A close-up of the material, texture, stitching or finish.
- The product in use or on a person, to show scale.
- Measurements, on an image or in a size chart.
- What is in the box, and the packaging if it matters for gifts.
- Each colour or variant, so that the picture changes when the option changes.
Use photographs of the real product, with the same style and lighting across the catalogue. A short video can show movement or fit, and it supplements the photographs without replacing them. Keep file sizes sensible, because heavy images slow the page, as the guide to checking and improving website speed explains. Give each file a descriptive name and write alt text that says what the image shows. Google's image guidance asks for short descriptive file names and useful alt text that fits the page, without stuffing in keywords. Alt text also helps people who use screen readers.
How long should a product description be?
As long as it needs to be to answer the shopper's questions. Google says it has no preferred word count, so there is nothing to aim for except usefulness. This structure works for most products:
- Two or three sentences at the top that say what it is, who it suits and the main reason to choose it.
- A list of facts the shopper can scan: size, material, capacity, compatibility, care and what is in the box. Use real measurements instead of words such as medium.
- Detail for those who want it: how to use it, how it differs from similar products and where its limits are.
Write your own text. A description copied from the maker appears word for word on every store that sells the product, and gives yours nothing that sets it apart. The guide to ecommerce SEO for beginners covers how product pages fit into search. Answer the questions customers send before ordering, because each one points to a gap in the page.
Some categories, such as food, cosmetics, electrical goods and packaged items, carry rules about the information that must be shown. Rules differ by country and change, so check the official source or ask an adviser about yours.
Do reviews need to be on every product?
No. Show reviews where you have real ones. A review box reading no reviews yet on most products can make a store look unused, so hide the box until there is something to show. Meanwhile, let clear policies, honest descriptions and visible contact details do the reassuring.
Never write reviews yourself or ask staff and relatives to post them. It misleads shoppers, may break consumer protection rules in some countries, and goes against Google's guidelines for review markup, which say reviews should come from users and not from the business. If you add review structured data, the reviews must be visible on the page.
To collect real reviews, ask after delivery, once the customer has used the product, and make leaving one a short job. Show who wrote the review and when.
Delivery, returns and payment on the page
Say where you deliver. If your platform supports a postcode or ZIP check, use it, because a shopper who learns at the last step that you do not deliver to them feels misled. State shipping charges before checkout. Quote delivery times that you can keep, based on what your courier actually does and not on the best case. If a payment option such as cash on delivery is limited for this product, say so.
Put a one-line returns summary near the buy button, such as returns accepted if unused and in original packaging, with a link to the full policy. If some items cannot be returned, say so on those pages and not just in the policy.
What makes shoppers leave a product page
- Costs they did not expect, which appear at checkout and not on the page.
- No clear delivery information, or no confirmation that you deliver to their area.
- Too few photos, or photos that do not show size or detail.
- A description that repeats the title or contains only marketing phrases.
- An unclear stock position, or a variant that turns out to be unavailable after it is selected.
- Slow loading, or a layout that jumps while it loads, on a mobile connection.
- Pop-ups that cover the product, especially on a phone.
- No sign that a real business stands behind the store, such as contact details, a returns policy or reviews.
These are common causes, not proven rules, and your own shoppers may differ. Your analytics can show which product pages lose visitors, but they rarely show why. The questions customers send you are the most direct clue.
How to test a product page
Open the page on a phone, using mobile data, as if you had never seen the store. Give yourself ten seconds, then answer these without scrolling back:
- What is it?
- What is the total price?
- Will it suit me?
- When will it arrive?
- What if it is wrong?
The question you cannot answer is the first thing to fix. Then ask someone outside the business to buy the product while you stay quiet, and note where they hesitate. Small stores rarely have enough visitors for formal split tests, so change one thing at a time, note the date, and compare orders and questions over a reasonable period.
Ideas that help on product pages
- A size or fit guide with real measurements.
- A comparison table for similar products, so shoppers can choose without leaving the page.
- A short section on how to use or care for the product.
- A back-in-stock notification for items that are out of stock.
- Questions and answers from real customers, shown on the page they relate to.
- Related products that genuinely go with the item, not a random list.
Which of these your store can do depends on the platform and the theme. The ecommerce solutions page describes the stores Liftup builds, and a developer can tell you what your current platform supports before you pay for anything extra.
Search basics for product pages
- A unique title and main heading that name the product plainly.
- A consistent way of handling variants. Either use one page with options, or use separate pages that each have their own content. Avoid many near-identical pages.
- Short, readable addresses that describe the page.
- Product structured data can make a page eligible for richer results, such as price and availability. Do not mark up anything that readers cannot see on the page, and remember that Google does not promise any rich result. Check Google's current documentation for the fields it supports.
Questions and answers
What should a product page include?
A clear name, one price with tax and delivery made clear, stock status, enough photos, a scannable description, options that update the photo and price, delivery and returns details, real reviews if you have them, and a buy button that is easy to reach on a phone. Include a way to ask a question before buying.
How many photos does a product need?
There is no fixed number. Show what a shopper would check if they held the item: several angles, a close-up of the material, something that shows scale, measurements and each variant. A simple product needs fewer images than one with sizes or fit questions.
How long should a product description be?
Long enough to answer the shopper's questions and no longer. Google has no preferred word count. Put the main points first, then a list of facts, then extra detail for people who want it.
Do reviews need to be on every product?
No. Show real reviews where you have them and hide empty review boxes. Never write your own reviews, and only mark up reviews that are visible on the page and come from customers.
What makes shoppers leave a product page?
Common causes are costs that appear late, unclear delivery or stock, too few photos, vague descriptions, slow loading on mobile and no sign of a real business behind the store. The questions your customers send are the best clue to what your own page is missing.
Should I use the maker's product description?
It is better to write your own. The maker's text appears word for word on every store that sells the product, so it gives your page nothing distinct. Use the maker's facts, and add what you know from selling and supporting the item.
Tell us what you are building.
A short call, a written plan and a fixed quote. No obligation.