Guide
Ecommerce CRO audit
A page-by-page review of an online store, from collection page to checkout.
Ecommerce conversion
Product page optimization: how to get more shoppers to add to cart
Product page optimization is the work of finding why shoppers look at a product and leave, then fixing the page so more of them add to cart and buy. This guide covers the elements that decide a sale, how to find the problems on your own pages, and how to fix and test them in the right order.
Short answer
Product page optimization is improving an ecommerce product page so more viewers add to cart and buy. Start with what blocks a purchase (broken selectors, a hidden add to cart button, unclear delivery costs, a poor phone layout), then answer the questions shoppers ask before buying, then test the changes whose effect is uncertain.
- Fix what blocks a purchase before anything that only persuades: selectors, the add to cart button, delivery costs and the phone layout.
- Your own data shows where to start: product views to add to cart, split by device, source and product.
- Answer the questions shoppers ask in chat, reviews and returns on the page itself, near the price and the button.
- Test changes whose effect is uncertain only when your traffic can reach the sample size in a few weeks.
- Keep price, stock, variants and delivery in the page HTML and Product structured data so AI agents can read them too.
What is product page optimization?
Product page optimization is the process of improving an online store's product pages so that more of the shoppers who view a product add it to their cart and go on to buy. It covers everything a shopper uses to decide: photos, price, description, variant selectors, the add to cart button, reviews, delivery and returns details, speed and the phone layout.
The product page is where most buying decisions in a store are made. Home and collection pages send people there; the cart and checkout only finish what the product page started. A shopper who leaves a product page without adding to cart rarely shows up in a checkout report, which is why product page problems are easy to miss and expensive to leave alone.
The work has three parts, and this guide follows them in order. First, find where your product pages lose shoppers and why, from your own data. Second, fix the elements that block or slow a purchase, then the ones that leave questions unanswered. Third, test the changes whose effect you cannot predict, and build the winners into your theme.
One note on the phrase: if you searched for it as an app developer, you may be looking for Apple's App Store feature of the same name, which tests icons and screenshots on an App Store listing. Apple documents it on its Product Page Optimization page. This guide is about ecommerce product pages.
Why product page optimization matters for an online store
Product page optimization matters because the product page is where interest turns into an add to cart. Ads, search and email can bring the right people to a product, but if the page leaves their questions unanswered, hides the button or loads slowly on a phone, that traffic is paid for and lost. A better page makes every visit worth more.
It also tends to be the page type with the most reach inside a store. Most stores run every product on one template, so a fix to the template applies to the whole catalog at once. A clearer delivery line or a better variant selector, built once, appears on every product.
Finally, product pages are where trust is decided. A shopper who has never heard of your store is asking whether the product is what it looks like, whether it will arrive when they need it and what happens if it does not fit. The answers belong on the product page, not three clicks away in a policy page.
How to find what is wrong with your product pages
To find what is wrong with your product pages, start with your analytics: the share of product page sessions that add to cart, split by device, traffic source and product. Then watch session recordings of shoppers who left, read the questions customers ask before buying, and place a test order on your own phone. The data tells you where; the research tells you why.
Do not start from a list of best practices. A list tells you what other stores fixed. Your data tells you what your shoppers are stuck on, and that is the only list worth working through.
| Source | What to look at | What it tells you |
|---|---|---|
| Analytics funnel | Product views to add to cart, by device, source and product | Which products, devices and traffic sources lose the most shoppers |
| Session recordings | Sessions on product pages that ended without an add to cart | Where people hesitate, scroll back, tap things that are not links, or give up on a selector |
| Heatmaps and scroll maps | How far down people scroll and what they tap on the phone layout | Whether shoppers ever reach the reviews, delivery details or description |
| Customer questions | Live chat logs, support emails, product Q&A | The questions the page does not answer, in the shopper's own words |
| Reviews and returns | Return reasons, complaints in reviews | Where the page set the wrong expectation about size, color or quality |
| On-page poll | One question to shoppers about to leave: "What stopped you from buying today?" | Objections you would not guess from numbers alone |
| Your own test order | Buy a product on your own phone, on mobile data | Slow loading, broken selectors and surprise costs you stopped noticing |
Compare products with each other, not with an average
The most useful comparison is inside your own store. Sort products by views and look at their add to cart rates side by side. A product with plenty of views and a low add to cart rate compared with similar products is a page problem worth opening. Industry averages mix stores with different prices, audiences and traffic, so they tell you very little about yours.
Split by device before you conclude anything
A product page can work well on a laptop and badly on a phone, and a combined number hides it. If the phone add to cart rate is far below desktop on the same products, start with the phone layout: the button position, the photo gallery, the selectors and how much scrolling it takes to reach the price.
Check the tracking first
Before you trust any of this, confirm that your add to cart and purchase events match real orders. A missing event on one theme section or a double-counted button makes a healthy page look broken, or the other way around.
The 12 elements of a product page that decide a sale
The elements that decide whether a shopper buys are the product title and price, the photos, the variant selectors, the add to cart button, delivery and returns details, the description, reviews, trust signals, size or fit help, stock status, related products and page speed. Each one either answers a question the shopper has or gets in the way of buying.
| Element | Shopper's question | What to check |
|---|---|---|
| Title and price | What is it, and what does it cost? | A plain product name, the price visible without scrolling on a phone, sale prices shown honestly |
| Photos and video | Is it what I think it is? | Every side, close-ups of materials, the product in use, scale next to something familiar, fast to load |
| Variant selectors | Can I get the one I want? | Clear labels, swatches for colors, unavailable options marked, photos that change with the choice |
| Add to cart button | How do I buy it? | One clear primary button, easy to reach with a thumb, a visible confirmation after tapping |
| Delivery and returns | When will it arrive, what will it cost, and can I send it back? | Delivery cost and time near the price, the returns rule in one line, a link to the full policy |
| Description | Will it do what I need? | Benefits first, then specifications in a scannable list; answers to the questions customers actually ask |
| Reviews | What do other buyers think? | Easy to find, recent, with photos where possible, including the negative ones |
| Trust signals | Is this store safe to buy from? | Payment options, contact details, the business behind the store; real badges only |
| Size and fit help | Will it fit, or will it fit my space? | A size guide on the page, dimensions in units your buyers use, fit notes from reviews |
| Stock status | Can I get it now? | Accurate stock, back-in-stock alerts for sold-out variants; no fake scarcity |
| Related products | Is there a better match, or something I also need? | Recommendations that help the choice, placed so they do not compete with the add to cart button |
| Speed | (Not asked, but felt) | Fast first view on a phone over mobile data; heavy apps and scripts removed or delayed |
What should be above the fold on a product page?
Above the fold on a product page, a shopper should see the product name, a clear main photo, the price, the variant choices and the add to cart button. On a phone that space is small, so the delivery line and a short review summary usually sit just below. Anything that pushes the price or the button out of the first screen needs a strong reason.
On a phone, the most common problem is a photo gallery that fills the whole first screen, so the shopper has to scroll past it to find out what the product costs. Try a slightly shorter gallery with swipe, and put the title and price directly under it.
On desktop, the usual layout of photos on the left and buying details on the right works because shoppers expect it. Keep the buying column focused: name, price, review summary, selectors, button, delivery line. Move long descriptions, specifications and brand stories below.
A sticky add to cart bar
Once a shopper scrolls down to read the description or reviews, the button scrolls away. A sticky add to cart bar keeps the button in reach. Convertica has tested this on client stores: see the sticky CTA case study and the product page redesign case study for what was changed, how it was measured and the result on those stores. A result on one store is a reason to test the idea on yours, not a promise.
How to improve product photos, selectors and descriptions
To improve product photos, show what a shopper would check by hand: every side, the materials up close, the product in use and its size. To improve selectors, label every option clearly, use swatches for colors and change the photo when a variant is picked. To improve descriptions, lead with what the product does for the buyer and answer the questions customers ask.
Photos answer questions before copy does
Most shoppers look at the photos before they read anything. Go through your chat logs and return reasons and ask, for each recurring question, whether a photo could answer it. "How big is it?" is a photo of the product in a hand or on a shelf. "What does the back look like?" is a photo of the back. "Is the fabric thick?" is a close-up. Keep the files light: large images are one of the most common reasons product pages load slowly on phones.
Variant selectors are where purchases quietly fail
A shopper who cannot work out which option to pick, or who picks a color and still sees a photo of a different one, often leaves without saying why. Check that every option has a clear label, that colors use swatches rather than a dropdown of names, that sold-out options are marked before they are picked and that the button explains what is missing if nothing is selected. Convertica's variant selector case study shows one store's redesign and how it was tested.
Descriptions that help a decision
Write the description for the shopper who is nearly convinced and has one more question. Start with two or three sentences on what the product does for them, then a scannable list of specifications: materials, dimensions, care, what is in the box, compatibility. Use the words customers use in reviews and chat, not the words in the supplier's catalog. If a manufacturer's description is copied on dozens of other stores, rewriting it helps both the shopper and search.
- Lead with the use. What problem does it solve, and for whom?
- List the specifications. Dimensions, materials, weight, care, compatibility.
- Answer known objections. Fit, durability, setup, what happens if it does not suit.
- Cut the filler. Phrases like "premium quality" say nothing a shopper can check.
How to show delivery, returns and reviews on a product page
Show delivery cost and timing in one line near the price, the returns rule in one line below it, and a link to the full policy. Place a short review summary near the product name and the full reviews close enough that a phone shopper reaches them without scrolling past a long description. Surprise costs at checkout start on a product page that left them out.
Delivery and returns belong next to the price
A shopper adding something to a cart is already asking what the total will be and when it will arrive. If the answer is only in the footer or at checkout, some will leave to find out elsewhere. One line such as "Free delivery over a set amount, usually 2 to 4 business days" (with your real terms) and one line on returns does more than a full policy page nobody opens. Convertica's free shipping badge case study tested where a store showed its free shipping offer.
Reviews: placement matters as much as having them
Reviews only help if shoppers see them. On many themes they sit below a long description, related products and a footer banner, which on a phone can be a very long scroll. Check your scroll map: if most phone shoppers never reach the reviews, move them up. The reviews section case study shows a store that tested exactly that.
Trust signals that are true
Show the payment methods you accept, a real way to contact you and who runs the store. Use only badges you have earned. A made-up "secure checkout" seal or a countdown timer that resets on every visit can lift a test briefly and cost you the shoppers who notice.
How to optimize a product page in 8 steps
To optimize a product page, check your tracking, find the products and devices losing the most shoppers, research why with recordings and customer questions, fix anything that blocks a purchase, answer the open questions on the page, speed it up, test the uncertain changes, and build what works into your theme. Work on the template so the fix reaches every product.
-
Check that your tracking matches your orders
Compare add to cart and purchase events in your analytics with orders in your store platform for the same period. If they disagree by a lot, fix the tracking before you judge any page.
-
Find the products and devices losing the most shoppers
Build a simple table: product views, adds to cart and add to cart rate, per product and per device. Start with high-traffic products whose rate is low compared with similar products, and with any large gap between phone and desktop.
-
Research why, from your own shoppers
Watch recordings of sessions on those pages that ended without an add to cart. Read chat logs, product questions and return reasons. Run a one-question exit poll. Write down every problem with the evidence beside it.
-
Fix anything that blocks a purchase
Broken or confusing selectors, a button that is hard to find or tap, an error with no explanation, a price or delivery cost that only appears at checkout. These are bugs, not ideas to test. Fix them and move on.
-
Answer the open questions on the page
Take the questions from step 3 and answer each one where shoppers look: a photo, a line near the price, a size guide, a specification, a review filter. Put the answer near the moment the question comes up.
-
Make the page fast on a phone
Compress and resize images, remove apps you no longer use, and delay scripts that are not needed for the first view. Test on a mid-range phone over mobile data, not on office Wi-Fi.
-
Test the changes whose effect is uncertain
Layout changes, photo order, review placement and new sections can help or hurt. If your traffic can reach the sample size a test needs within a few weeks, run an A/B test. If not, make the change, watch the numbers and be ready to undo it.
-
Build what works into the theme
A winning variant left running in a testing tool slows the page and may not be visible to everyone. Build it into the template so it applies to every product, then pick the next problem from your list.
How to A/B test product page changes
To A/B test a product page change, write a hypothesis based on your research, choose one main metric (usually revenue per visitor or orders per visitor), calculate the sample size before launch, run the test across full weeks on the product template, and only act on a result that reaches the sample you planned. Test the template, not one product, so the test gets enough traffic.
Add to cart rate is tempting as the main metric because it moves quickly, but a change can raise adds to cart and still lower orders: a bigger button that sends more undecided shoppers to the cart, for example. Track add to cart as a supporting metric and judge the test on orders or revenue per visitor.
Most stores cannot test small tweaks. The smaller the change you want to detect, the more visitors a test needs: halving the lift you want to detect roughly quadruples the sample. If the A/B test sample size calculator says your test needs months, test a bolder change or ship the fix without a test.
- Good candidates for a test: moving reviews up, a new photo order, a sticky add to cart bar, a different layout for the buying column.
- Usually not worth testing: fixing a broken selector, adding a missing delivery cost, correcting wrong specifications.
- Hard to test on a small store: button color, small copy changes, font tweaks.
Agent readiness
Can AI shopping assistants read your product pages?
Some AI assistants now read store pages on a shopper's behalf, to compare products or check a price. What they can read depends on what is in the page HTML.
PERSON VIEW
Product page
Linen duvet cover
In stock. Free delivery, 2 to 4 business days.
Illustrative example
AGENT VIEW (PAGE HTML)
- name
- Linen duvet cover
- PASS
- offers.price
- null
- LOADED BY SCRIPT
- offers.availability
- null
- NOT IN HTML
- shippingDetails
- null
- NOT IN HTML
Illustrative example: the price, stock status and delivery line are added by scripts after the page loads. A person sees them. An agent reading only the page HTML does not.
An AI assistant that reads a product page usually works from the HTML the server sends and any structured data on the page. Some do not run JavaScript. If your price, stock status, variants or delivery details appear only after a script runs, an assistant may not see them, and it cannot pass them on to the person who asked.
- Keep price, stock, variant names and delivery details in the page HTML.
- Add Product structured data with offers, availability and, where you can, shipping and return details. Check it with the schema markup validator.
- Check that your robots.txt does not block the AI crawlers you want to read your store.
- Treat this as a new area: nobody has years of data on it, so check what is readable and adjust.
Convertica's free audit includes an AI visibility and agent readiness check that reads these things on your page; the AI visibility checker leads with it. It reads your page and site files. It does not ask any AI assistant about your store.
Common product page optimization mistakes
The most common product page optimization mistakes are copying another store's page instead of studying your own shoppers, judging changes on desktop only, hiding delivery costs until checkout, adding apps until the page is slow, using fake urgency, and testing tiny tweaks the store does not have the traffic to measure. Each one wastes effort or costs trust.
- Copying a big brand's page. Their shoppers already trust them. Yours may need more reassurance, not less.
- Reviewing on a laptop only. Open every change on a phone first, because that is where most problems hide.
- Hiding costs. Delivery fees that appear at checkout make shoppers distrust the price they saw.
- Stacking apps. Each review widget, popup and badge app adds scripts. Remove what you do not use.
- Fake scarcity. "Only 2 left" on every product, or timers that reset, will be noticed.
- Burying the button. Long descriptions and banners above the add to cart button on a phone.
- Testing tweaks. A button color test on a small store rarely reaches a reliable answer.
- Fixing one product. Most problems live in the template. Fix it once, for the whole catalog.
Product page optimization checklist
Use this product page optimization checklist on your best-selling product, on a phone first and then on desktop. Every item is a yes or no question. Anything you answer no is a candidate for your list, and the evidence from your own research decides which one comes first.
- Can I see the name, price and add to cart button without scrolling on a phone?
- Do the photos show every side, the materials, the product in use and its size?
- Does the main photo change when I pick a color or variant?
- Are sold-out options marked before I pick them?
- Does the button tell me what is missing if I have not chosen an option?
- Is the delivery cost and time stated near the price?
- Is the returns rule stated in one line on the page?
- Can I reach the reviews on a phone without a long scroll?
- Does the description answer the questions customers ask in chat?
- Is there a size guide or dimensions in the units my buyers use?
- Does the page load quickly on a phone over mobile data?
- Are price, stock and delivery in the page HTML and in Product structured data?
- Is every badge, timer and stock count true?
Audit and rebuilds
Where Convertica fits
Convertica has run conversion research and A/B tests on client stores since 2017. Today it starts with a free CRO audit: enter a product page and see an overall score, eight check scores and three fixes. The full report lists every finding with how to fix it, and if you would rather not build the fixes yourself, Convertica's team can rebuild that one page with every fix the audit found, whatever platform it runs on.
Related
More on ecommerce conversion
Guide
Shopping cart optimization
Keep the cart from losing the shoppers your product page won.
Guide
Ecommerce key metrics
Revenue per visitor, add to cart rate and the other numbers worth watching.
Questions about product page optimization
What is product page optimization?
Product page optimization is the process of improving an ecommerce product page so more of the shoppers who view it add the product to their cart and complete the order. It covers the photos, price, description, variant selectors, add to cart button, reviews, delivery and returns information, page speed and how the page reads on a phone.
What should I fix first on a product page?
Fix whatever stops shoppers from buying at all before anything that only persuades: a broken variant selector, a hidden or slow add to cart button, missing delivery costs, or a page that is hard to use on a phone. Then work on the questions shoppers ask before buying, such as size, fit, materials, delivery time and returns.
How do I know if my product pages are underperforming?
Compare your own numbers, not an industry average. Look at the share of product page sessions that add to cart, split by device, traffic source and product. A product with plenty of views and few adds to cart, or a large gap between desktop and mobile, shows you where to look first.
Do product page changes need an A/B test?
Clear fixes, such as a broken selector or a missing shipping cost, can go straight live. Changes where the effect is uncertain, such as a new layout, a different photo order or moving reviews, are worth testing if your traffic can reach the sample a test needs in a few weeks. On a small store, ship the change and watch your numbers.
How many product photos should a product page have?
There is no fixed number. Show enough photos to answer what a shopper would check in a store: the product from every side, close-ups of materials and details, the product in use, and its size next to something familiar. If customers keep asking a question a photo could answer, add that photo.
Is product page optimization the same as Apple's Product Page Optimization?
No. Apple's Product Page Optimization is an App Store Connect feature that lets app developers test different icons, screenshots and preview videos on their App Store listing. Ecommerce product page optimization is about the product pages of an online store, and this guide covers that meaning.
Does product page SEO conflict with conversion optimization?
Rarely. The things that help a product page rank, such as a clear product title, a useful description, unique photos, structured data and fast loading, also help shoppers decide. The conflict usually comes from stuffing keywords into copy, which makes the page harder to read and does not help either goal.
How do AI shopping assistants read product pages?
AI assistants and agents that read a store's pages usually work from the page HTML and its structured data, and some do not run JavaScript. If the price, stock status, variants or delivery details appear only after a script runs, an agent may miss them. Keep those facts in the HTML and in Product structured data.
