November 13, 202610 min read
What is a PDP? Product detail pages in ecommerce, explained
In ecommerce, PDP stands for product detail page: the page on your store that shows one product and lets a shopper buy it. The same letters mean something else in other fields, like Medicare prescription drug plans and personal development plans at work, so if you landed here for one of those, this isn't the page you want.
This guide covers what a PDP is, how it differs from a product listing page, what a good one includes, and what AI shopping agents read when they look at one. It's about the product pages on your own store. If you already know all that and want to raise the conversion rate on the pages you have, go to our guide to PDP optimization.
What is a PDP?
A product detail page is the page for a single product. It's sometimes called a product page or a product display page, and the job is the same under any name: give a shopper everything they need to decide, then let them buy. A typical PDP has the product's name, photos and video, a description, the price, options like size and color, reviews, shipping and returns details, and an add-to-cart button.
One product usually gets one PDP, even when it comes in a dozen sizes and colors. The shopper picks a variant on the page, and the photos, price, and stock status change to match.
Your store's PDPs vs. marketplace listings
A lot of advice about PDPs is written for marketplace listings, like a product's page on Amazon or a retailer's site. Those are PDPs too, but the marketplace controls the layout, the reviews, and the buy button, and brands compete on the content they're allowed to submit. On your own store you control the whole page, down to what happens when a shopper has a question.
PDP vs. PLP
A product listing page (PLP) is the page that shows many products at once, like a category page, a collection, or a set of search results. Shoppers use a PLP to narrow their options, and they use a PDP to decide on one. The two work as a pair: a shopper filters a PLP down to a few candidates, opens a PDP for each, and buys from one of them.
PLP (product listing page) | PDP (product detail page) | |
|---|---|---|
What it shows | Many products in a grid or list | One product in full detail |
The shopper's job | Browse, filter, and compare | Decide whether to buy this one |
Main action | Click through to a PDP | Add to cart |
Number to watch | Clicks through to product pages | Add-to-cart rate and purchases |
A PLP is where product discovery happens, and the PDP is where it ends in a purchase or a lost sale.
Why the PDP does so much of the selling
Shoppers often skip your homepage entirely. A search result, a social post, an ad, or a link in an email drops them straight onto a product page, and that page has to introduce the product and close the sale on its own.
Most stores have room to improve here. In Baymard Institute's product page benchmark, 52% of desktop sites, 62% of mobile sites, and 64% of apps rate "mediocre" or worse on product page usability.
What a good PDP has
Every element on a product page exists to answer a question the shopper has before they'll buy. Thinking about elements that way tells you what each one needs to do, and it makes the gaps on your own pages easier to see.
What is it, and is it for me?
The first screen has to confirm the shopper is in the right place. A clear product name, a sentence on what it does or who it's for, and a strong main image do most of this work.
Photos carry more than you'd expect, because they stand in for picking the product up. Show it from every angle, on a person when it's something worn, and next to something familiar so the shopper can judge its size. Baymard found that 37% of benchmarked sites don't include images that show a product's scale.
Will it fit or work for me?
For apparel and footwear the question is about sizing, and the answer is a size chart, notes on how the item runs, and fit details from reviews. For electronics and home goods it's compatibility and dimensions. For beauty and food it's ingredients.
Put the answer right next to the choice the shopper is making. A size guide belongs beside the size selector. Baymard recommends button-style size selectors over drop-down menus, and 57% of the sites it benchmarked still don't use them.
What will it cost, and when will it arrive?
Shoppers want the total cost and an arrival date before they commit. The price alone often isn't enough, because shipping and taxes change the number. Baymard found that 67% of benchmarked sites don't show an estimated total order cost near the buy section.
A delivery estimate works best as a date ("arrives by Thursday") and sits near the add-to-cart button, where the decision happens.
What if it's wrong?
A short summary of your returns and exchange policy near the price takes the risk out of the decision, with a link to the full policy for shoppers who want details. Of the sites Baymard benchmarked, 44% don't link to their return policy from the product page at all.
Do people like it?
Reviews and ratings do what your copy can't, because they come from someone who bought it. Customer photos help even more, and they're most useful when shoppers can browse all of them in one place, which 63% of the sites Baymard benchmarked don't allow. It's also worth replying to negative reviews, since a calm, specific reply shows the next shopper what happens when something goes wrong. Baymard found 89% of sites don't.
How do I buy it?
One clear add-to-cart button, close to the price and the options, with nothing competing for attention. On mobile, keep the button within reach as the shopper scrolls, so they don't have to scroll back up to buy.
The questions a PDP can't answer on its own
A good PDP answers the questions most shoppers have. Some questions depend on who's asking, though, and no amount of copy covers them for everyone. Will this jacket fit like the one the shopper bought from you last fall? Will it reach their address before a trip on Saturday? Can they exchange the pair they ordered last month for this one?
Those shoppers either find someone who can answer or they leave. A live answer on the page, from customer experience AI or a person, keeps the sale going.
Gladly Agentic Commerce answers the sizing and fit questions that stall a purchase, and it draws on each customer's full history, including their sizes and past purchases, so its answer can account for what they've bought before. It can offer help when a shopper lingers on a page or looks ready to leave. Shoppers can check out inside the conversation without being sent somewhere else, and for a big purchase, a person on your team is one tap away.
Those conversations also show you what your pages are missing. Our PDP optimization guide walks through how to tag a month of pre-purchase questions by product and topic and turn the top ones into page fixes.
Try Gladly AI right here
Shoppers asking questions your PDP can't answer? Ask Gladly AI.
Get a practical answer in seconds, from AI built for retail.
What AI shopping agents read on a PDP
Not every shopper reaches your PDP in a browser anymore. More of them ask an AI assistant like ChatGPT to find and compare products for them, and some of those assistants can complete the purchase. That's agentic commerce, and it changes who reads your product pages. An AI agent reads the product data behind the page, so your layout and lifestyle photos do little for it.
That data comes from two places. The first is structured data in the page's code. Google's product structured data lets a merchant mark up price, availability, shipping, and return policy so Google can show them in search, and Google recommends pairing that markup with a Merchant Center feed. The second is a product feed sent straight to the AI platform. OpenAI publishes a product feed specification for merchants who want their products discoverable in ChatGPT, with basics like title, description, brand, image, availability, and price.
A few habits make a PDP easier for an agent to read and recommend:
Write attributes as text. A material, a measurement, or a care instruction that only appears inside an image is invisible to an agent.
Keep the page and the feed in sync. If the page says a product is in stock and the feed says it isn't, an agent can't trust either one.
Answer the common questions on the page. Fit notes, compatibility, and what's in the box give an agent something specific to repeat to a shopper.
Who owns the PDP
A product page usually has several owners, which is part of why it's hard to improve. Merchandising or the ecommerce team typically owns the product content: names, descriptions, photos, and pricing. Design and development own the template every product shares. Marketing or SEO handles the title tags, descriptions, and structured data that bring shoppers in, and whoever runs your product data or feeds keeps the information consistent across channels.
Your customer experience team sees something none of those teams do: every question a shopper asked because the page didn't answer it. Get that list into the hands of whoever writes the product content, and the next version of the page answers more of it.
Next step: improve the PDPs you have
Once you know what a PDP is and what a good one includes, the work is finding which of your pages fall short and fixing them in order. Our PDP optimization guide covers that process, from finding where shoppers stall to measuring PDP conversion rate, and our ecommerce conversion rate optimization framework shows how to sequence tests across the rest of your site.
