How to build an e-commerce product page

From title and photos to price, delivery, variants and stock, from the description to reviews, from Product markup to measuring which pages lose buyers.

· 12 min readE-commerce

Short answer

A good product page answers the buyer’s questions in the order they arise: what is this, what does it really look like, how much, when does it arrive, is my option available. Price, stock and delivery must be visible on the page, and Product structured data should tell Google the same things. Find the pages that lose buyers by comparing view_item and add_to_cart in GA4.

Someone clicks an ad and lands on your backpack page. The photo is lovely, but the size of the bag isn’t clear. To see the price they have to pick a colour. To find out when it will arrive they have to add it to the basket and walk through to the payment step. A buyer left with three unanswered questions rarely asks a fourth; they close the tab. The ad budget is wasted by what the page did.

The short answer to how an e-commerce product page should look is this: it should answer the buyer’s questions in the order they come to mind, without making them search. This article shows how to build a product page in your own shop in that order, and then how to find which page loses buyers. Improving a marketplace listing is a separate job; we covered the Trendyol one in how to improve a marketplace listing. If you haven’t built the shop yet, start with how to set up an online shop.

Which questions the page answers, and in what order

Instead of seeing the product page as a design area, think of it as a sequence of the buyer’s questions. Someone looking at a product first works out what they are looking at, then how it looks, then what it costs and when it will reach them, and then whether their own option exists. The description and reviews are read after those, to firm up the decision.

The seven parts of a product page and the buyer question each one answers Product name Is this the product I wanted? Photos What does it really look like? Price, delivery, stock How much, and by when? Variant choice Is my size and colour here? Add to basket Can I buy it now? Description Are my questions answered? Reviews What happened to other buyers? The seven parts of a product page and the buyer question each one answers Product name Is this the product I wanted? Photos What does it really look like? Price, delivery, stock How much, and by when? Variant choice Is my size and colour here? Add to basket Can I buy it now? Description Are my questions answered? Reviews What happened to other buyers?
Figure: A product page answers the buyer’s questions in turn: name, photos, price and delivery information, variant choice, add to basket, description and reviews.

The steps below take these seven parts in turn. Each ends with a check question; if the answer is “no”, that is where to fix.

1. Title: identify the product at a glance

The title should carry the brand, the type of product and the feature that sets it apart: “Waterproof 25-litre laptop backpack”, for example. The sturdiest title, for search engines and buyers alike, is built from the words a person would type when looking for that product in their own sentence. Have one main heading (H1) on the page and put the product name in it. Don’t stuff it with keywords; the long title that works on a marketplace erodes trust in your own shop.

Check question: could someone who reads only the title say what the product is?

2. Photos: answer the questions with images

Because the buyer can’t touch the product, the photo stands in for the hand in a shop. Make sure of the following:

  • The first photo shows the product clearly on a plain background; Google also says it prefers pictures that clearly show the product, against a white background for example.
  • After that come different angles, close-ups of details and one shot of the product in use.
  • If size is confusing (bags, furniture, jewellery), show the product next to a person or a familiar object.
  • Give every colour or model option its own photo, and change the image when the option changes.
  • Make the files light for mobile screens and write descriptive alt text. For speed, see why a fast site sells more.

Check question: is the “what does it look like” question customer service hears most often answered in the photos?

3. Bring price, delivery and returns forward

What bothers buyers most is information that affects the decision showing up late. If the delivery charge, the estimated delivery time and the returns terms first appear at the payment step, the buyer feels misled. Put these next to the add-to-basket button, short and clear:

  • The current price; if there is a discount, the crossed-out old price must be real.
  • The delivery charge or the free-delivery condition, and the estimated delivery time.
  • A one-sentence summary of returns and exchanges, linking to the full terms.

Check question: could someone who opens the page say, without adding to the basket, what they will pay in total and when the product will arrive? Information that appears late is also the source of the “late-appearing cost” problem described in how to reduce cart abandonment.

4. Variants and stock: easy to choose, honest about status

Size, colour or capacity selection is where product pages go wrong most often.

  1. Show the options as visible buttons or colour swatches rather than burying them in a drop-down.
  2. If an option is out of stock, show that at the moment of choosing, on the option itself; the buyer shouldn’t find out after adding it to the basket.
  3. Open the size chart from a link next to the choice, on the same page.
  4. Generate messages such as “only a few left” from real stock only. If the stock count doesn’t come automatically from your shop system, don’t write the message at all.
  5. Don’t delete the page of a sold-out product; leave an “out of stock” status and links to similar products. The page’s address and history are valuable.

According to Google’s guidelines, if each variant has its own address and is identified separately, marking the variants up as a product group helps Google understand which products are versions of the same product. We deal with that in the structured data step below.

5. Write the description around the buyer’s questions

The description is there to answer the questions the buyer wanted to ask but couldn’t, not to copy the maker’s feature list. Before writing, go through customer messages, order notes and return reasons and pull out the five questions asked most often. Then build the description in this order:

  1. In the first two sentences, who and what the product is for.
  2. The feature list: size, material, weight, compatibility, the facts buyers use to compare, in short bullet points.
  3. Use, care and what is in the box.
  4. Questions specific to this product: “Is it washable?”, “Which models is it compatible with?”

Write the text again for every product. If many sites use the same manufacturer description, your page adds nothing.

Check question: are the five questions customer service gets most often answered in the description?

6. Reviews: real, visible and answered

The review section shouldn’t be just a star average: the number of reviews, the spread of ratings and the details buyers write are read when deciding. Don’t show only the positive ones; a short, calm reply to a negative review builds more trust than a spotless page. Getting fake reviews written or bought is an ethical problem, and Google also treats fake reviews in structured data as a breach of its guidelines.

For new products with no reviews yet, don’t fill the gap with fakes. Add a review request to the post-order email and strengthen the description and photos until reviews arrive. We cover the timing and wording of the request in our customer reviews guide.

7. Product structured data: what Google asks for

To give Google your product page’s information in machine-readable form you use Product structured data (see structured data in the glossary). Google distinguishes two kinds: product snippets for pages where the product can’t be bought, and merchant listings for pages where people can buy the product from you. A product page in your own shop is the second.

The table below summarises which Product property in Google’s documentation matches what you show on the page, and whether it is required or recommended.

What you show on the page Product property Status at Google
Product name name Required
Product photos image Required
Current price and currency offers: price, priceCurrency Required (price must be above zero)
Stock status offers: availability Recommended
Delivery charge and time offers: shippingDetails Recommended
Returns terms hasMerchantReturnPolicy Recommended
Brand, barcode, stock code brand, gtin, sku Recommended
Star average aggregateRating Recommended

From Google’s guidelines, keep these in mind when you use these properties:

  • The information you mark up must be visible to readers on the page. Writing a price, stock level or review into structured data that isn’t on the page breaks the guidelines.
  • The page should focus on a single product (or variants of the same product). Don’t mark up a category page as a Product.
  • If you sell in more than one currency, use a separate address for each currency.
  • Where possible, put the data in the page’s initial HTML; markup generated later with JavaScript can make crawling less frequent for fast-changing information such as price and stock.
  • For variants, link each one with a ProductGroup and give every variant a unique identifier and address.
  • To validate, use the Rich Results Test; for the live page, use the URL Inspection tool in Search Console.

Remember that correct markup does not guarantee that Google will show a rich result; it only makes the page eligible. For the technical audit of structured data, see the relevant item in the technical SEO checklist.

8. Which page loses buyers: measure

Once the page is built, the answer to “is it good?” shouldn’t be your opinion. GA4’s e-commerce events show it product by product: according to Google’s documentation a view_item event is sent whenever an item’s details are viewed and an add_to_cart event when an item is added to the basket. If that isn’t set up yet, start with the e-commerce section of the GA4 setup checklist.

  1. Put view_item and add_to_cart counts side by side for each product. Product pages that are viewed a lot but added rarely are your shortlist.
  2. Split those pages by device. For a page that does well on desktop and badly on mobile, the cause is often visibility: the button or price sits below the first screen.
  3. Look for the cause using the seven questions above: missing photo, late delivery information, sold-out option, empty description?
  4. Change one thing at a time and compare equal-length periods before and after. Allow for things like season and campaigns.
  5. People who reach the payment step and leave there are a sign of a different problem; for them, move on to the guide on reducing cart abandonment.

To work out the rate you can use the conversion rate calculator. Compare your own products with each other and with your own history, not with other sites’ averages.

Common mistakes

  • Hiding the price or the delivery charge until an option is chosen.
  • Using one photo for every colour.
  • Pasting the manufacturer’s description as it is.
  • Not showing an out-of-stock option until the buyer has added it to the basket.
  • Writing a review rating or stock level into structured data that isn’t visible on the page.
  • Marking up a category page as a Product.
  • Publishing the product page without trying it on mobile.
  • Leaving the add-to-basket button below a long description.

Common questions

How many photos should a product page have?

There is no fixed number; the measure is whether they answer the buyer’s questions. One clear main photo, different angles, a detail close-up and a shot in use is a sound start for most products. Give every option its own photo. We cover the shot list and file preparation in our product photo guide.

Is it compulsory to add Product structured data to a product page?

No, it isn’t compulsory, but it is one of the ways Google can show price, stock and delivery in search results. The required properties are the name, an image and an offer with a price and currency; the others are recommended. Display is not guaranteed.

Should price and delivery information be on the product page or in the basket?

On the product page, near the add-to-basket button. If the exact amount depends on the delivery address, give the estimated time and the free-delivery condition and say where the exact amount will appear.

Something to do today: open the pages of your three most advertised products on your phone. Without scrolling, can you see the price, the delivery time and whether the options are in stock? Every piece of information you can’t see is a place where the buyer’s question goes unanswered. Make a note, fix the most critical one, and a week later look again at that page’s view_item and add_to_cart counts in GA4.

The product catalogue and its content are within the scope of our e-commerce service.

Sources

This article is general information, not legal, financial or technical advice. Platforms, their rules and the law change over time, so some details may have changed since 11 November 2026 or contain small errors. Before you make a decision for your business, check the current official sources or write to us.

Tell us about
your project.

Fill in the form or write to us directly, and we will agree on a day to talk.

Your first meeting is with Deniz Sezer, founder of Detmore.

First meeting free · Reply within one working day · Written proposal in 2 to 3 days · NDA ready

What do you need? pick as many as you like

Name, email and phone are required.

Contact

We reply within one working day.