‘What every product page should contain’ checklists are easy to complete and almost useless in practice. A name, photos, price, availability, add-to-cart button, and reviews—every store has these today. The problem starts one level deeper: a specific product is missing one piece of information without which the customer cannot make a decision. No universal checklist will identify it for you. But you can discover it in questions your customers have already asked and in the way they behave on the page.
Customer questions are a ready-made list of gaps
Every question someone asks you about a product is a signal that the answer was either absent from the page or placed somewhere the customer did not reach. One question is an isolated case. The same question asked five times in a month is a gap in the description that costs your support team time with every subsequent customer—and costs you sales when visitors choose not to ask.
The greatest advantage of this source is that you do not need to start anything from scratch. Chat conversations, tickets, callback requests, and form messages already exist. You only need to read them from one perspective: what did the customer want to know about the product?
- Collect material from a single period.Take conversations and tickets from the past thirty days. A shorter period will provide too few repetitions; a longer one will overwhelm you with issues you have already resolved.
- Filter out anything unrelated to the product.Set aside questions about order status, payment, or complaints. Keep only pre-purchase questions about the product itself.
- Record the URL where the question was asked.In Meetlead, the operator can see which page the visitor is on, while the customer journey shows the URLs they visited. This links the question to a specific product page rather than a general impression.
- Group by information, not phrasing.‘Will it fit the 2021 model?’, ‘I have an older version—will it work?’, and ‘What are the requirements?’ are all one question about compatibility.
- Count repetitions and rank the groups.A group with five occurrences takes precedence over five groups with one occurrence each. Start at the top of the list, not with the question that annoys you most.
- Decide where the answer belongs.Not every answer belongs in the description. Some should be a photo caption, some a specifications table, and some a sentence beside the buy button.
The same material is useful when building a knowledge base and website FAQ, but do not conflate the two. An answer about compatibility hidden in a separate FAQ tab will not help someone on the product page with their finger poised over the buy button. Information specific to that one product belongs in its product description.
Before rewriting your descriptions, read your last thirty conversations with one question in mind: what could the customer not find on the page? See how Meetlead brings chat, callback requests, and tickets together—along with the URL where the question was asked.
For these questions to reach you at all, someone must be available during the hours when people shop. We discuss the conditions for effective store chat separately in our guide to live chat for online stores.
Common gaps, industry by industry
Gaps recur within an industry, although every store believes it has already covered them. The table below is not a substitute for your list of questions. It is there to help you check whether you have overlooked something obvious to a customer but invisible to someone who knows the catalog by heart. We break down the first row, the size question, step by step in our guide to answering size questions in a clothing store.
Scroll the table sideways to see all columns.
| Customer question | What is missing | Where to add it |
|---|---|---|
| Which size should I choose for my measurements? | A size chart based on body measurements, not garment measurements | An expandable section beside the size selector |
| Will this fit my model? | A list of compatible devices or versions | The specifications block, above the marketing description |
| What are the dimensions when folded and unfolded? | Complete dimensions, not just the package size | A specifications table plus an annotated drawing |
| What exactly is included? | A list of what is and is not included | A bulleted list directly below the price |
| How much does it weigh, and can I carry it in myself? | The weight and delivery method for a bulky item | The delivery section on the product page, not in the terms |
| Does the photo show the true color? | A photo of the variant the customer selected | A gallery that changes with the selected variant |
| How long will this specific product take to ship? | A dispatch estimate for this item, not a general statement | A line beside the add-to-cart button |
| What if it does not fit? | A one-sentence summary of the return policy | Below the buy button, not in the footer |
In most cases, the information exists somewhere in the store—in the terms, on the delivery page, or under a help tab. It is missing from the place where the decision is made. This is a content placement problem rather than an editorial one, which is why the ‘where to add it’ column can matter more than the middle column.
Meetlead is not an ecommerce platform and does not edit product pages. It helps you determine what they are missing—you make the changes in your own store.
Return terms are another recurring gap—questions about them usually mean that the information is buried too deeply. We examine this in our article about return policies and purchase decisions.
When the ordered and received variants differ, use the guide: Wrong item received: verify an order mix-up without repeat questions.
Scroll maps: where attention ends on a long product page
Adding to a description only makes sense if visitors will see the new content. Product pages grow over the years as recommended sections, banners, reviews, and related products are added, until information placed at the end falls out of reach. A scroll map shows this clearly: how far most visitors get and where traffic all but disappears.
- Reach boundaryThe point reached by most visits. Everything below it is content for a minority—and should be treated that way when you plan the page.
- Sharp dropA sudden change in reach at a single point usually signals an element that looks like the end of the page, such as a wide banner, a frame, or empty space.
- Difference between phone and desktopThe same page has a different boundary on each device. On a phone, the specifications section can end up several screens too far down.
- Drop-off before the buttonIf attention ends immediately above the buy button, check what sits directly above it and whether it draws the eye away.
Meetlead maps are collected separately by URL and device type, so you review a product page twice—once on mobile and once on desktop. We describe the principles and common interpretation errors in our guide to reading heatmaps. One additional rule applies to product pages: do not compare a map for a bestseller with one for a product that receives only a dozen visits a month.
The conclusion from this kind of analysis is rarely ‘add more’. Much more often, it is ‘move it higher’. The answer to the most common question should appear above the reach boundary, not beside a section that only one visitor in ten sees.
Before adding another paragraph, see whether anyone scrolls that far. See how Meetlead's scroll and click maps work—separately for phone and desktop, for every URL.
Photos and variants: what recordings reveal
The gallery and variant selector are where a product page most often diverges from what the store planned and what the customer actually does. A click map reveals the pattern, but only a session recording puts events in sequence and lets you see exactly where the decision stalled.
- Arrival from search
A visitor lands on the mobile product page and pauses at the first photo.
- Enlarging the photo
Two clicks on the photo and an attempt to zoom in on a detail. The preview opens at a resolution that reveals nothing more.
- Switching variants
The visitor selects a different color. The gallery does not update, so they return to the previous variant and switch again.
- A quick scroll down
They pass through the description without stopping, reach the reviews, and return to the top of the page.
- Leaving without adding to the cart
The session ends on the product page. Later that day, someone asks in chat about the color's true shade.
This sequence is worth more than ten team opinions because it points to a specific cause: the customer could not see the product in the selected variant. The fix in the store is inexpensive—a photo assigned to the variant and a useful preview.
- Watch five recordings from one product page and one device type only.
- Check whether anyone clicks non-clickable elements, such as variant labels, icons, or captions below the photo.
- Look for returns to the gallery after switching a variant.
- Count how many people reach the specifications table at all.
- See whether the customer scrolls through the description or jumps straight to the reviews.
- Record every point where cursor or finger movement pauses for more than a few seconds.
Show the price and additional costs early enough
Price is usually the one piece of information that is never missing from a product page. What is missing is everything added to it. A customer who learns the full cost only in the cart does not judge the offer as more expensive—they judge it as dishonest, and that is much harder to repair.
Scroll the table sideways to see all columns.
| Information | When the customer looks for it | Consequence of showing it too late |
|---|---|---|
| Delivery cost for this product | While comparing offers, on the product page | A return to search without adding the item to the cart |
| Free-delivery threshold | Immediately after seeing the price | A missed opportunity to increase the order value |
| Surcharge for carrying in or assembly | For bulky products | Abandonment at the final purchase step |
| Fulfillment time for this item | Before the decision, especially for gifts | A question in chat or a silent exit |
| Per-item price for sets | When comparing it with a competing offer | The impression that the offer costs more than it does |
If this information appears only in the cart, you will see part of the problem not on the product page but along the purchase journey. We describe a method for breaking abandonment down by stage in our article about abandoned carts—there, you look for the cause at checkout; here, you check whether all the information was available earlier.
There is also a layer that cannot be covered by a single sentence about returns: the credibility of the store as a whole. We compare the elements that strengthen it with those that damage it in our article on building trust on a website. On the product page, it is enough to ensure that the most important ones are visible near the buy button.
Show us one product page that attracts the most questions. Schedule your implementation—we will configure maps, recordings, and conversations so you can see where the purchase decision stalls.
Review product pages monthly instead of fixing them once
Rewriting descriptions once produces results for a quarter. Then new products arrive, variants change, a supplier changes the packaging, and the questions return. A short routine therefore works better than one large project a year.
- Review conversations and tickets for product questions once a month.
- Choose the three product pages with the most recurring questions, not all of them at once.
- For each one, check the scroll map separately on mobile and desktop.
- Watch five recordings from each selected page and record the common themes.
- Make one change per page so that you can attribute its effect.
- After a month, count whether questions about the same issue have disappeared.
- Add new products to the review only after collecting the first questions.
The penultimate item on the list is the most reliable measure. Sales of a single product depend on too many factors to attribute growth to one improvement in its description. The disappearance of a specific question after you add a specific piece of information is direct evidence—and it appears sooner.
It is also worth watching the direction of your changes. A product page should not be exhaustive documentation. It should answer the questions customers actually ask, in the order they ask them.
