How a PDP works
PDP stands for product detail page: the page for one purchasable item. Title, images, price, availability, variants, description, specifications, delivery information, reviews and the add-to-cart button all live here. In analytics and in agency conversation it is almost always shortened to PDP, and its sibling is the listing page that sends traffic to it.
Technically it is the page most likely to carry Product structured data, so a search engine can read price and availability without interpreting the layout. It is also the page a shopping feed points at, which means the price and stock shown on the page and the values sent in the feed have to agree or the listing is disapproved.
Why PDPs matter
It is the last page before the money. Every other page on an ecommerce site exists to deliver someone here, so a weak product page wastes all the traffic that reaches it, paid and organic alike. Small changes to the images, the delivery promise or the way variants are chosen move the conversion rate across the whole catalogue at once.
It is also where long, specific searches land — a model number, a size, a colour, a brand plus a city. Those searches are individually small but numerous together, and they convert well because the shopper has already decided what they want and is only choosing where to buy it.
Where PDPs go wrong
Manufacturer copy pasted across every retailer selling the item is the classic problem. Nothing on the page is yours, so there is no reason for a search engine to prefer your version of it. Thin content is the same fault in another form: a title, one image and a price is not a page anyone can buy from with confidence.
The other recurring faults are structural. Each size or colour gets its own address with almost identical content; a discontinued item is deleted and returns a 404 while people are still searching for it; the feed price drifts from the page price and Shopping listings quietly stop showing. All three are avoidable with rules set once and applied by template.
Getting it right
Write something on each page that only you could write: what the product is genuinely good for, what it does not suit, sizing guidance, what is in the box, delivery area, warranty and after-sales terms. For a retailer in Nepal those local details answer real hesitations, and no competitor’s copied description covers them.
Keep one canonical page per real product and treat colours and sizes as variants of it rather than separate pages. Mark the page up with Product structured data that matches what a visitor can see, and decide in advance what happens to the URL when the item sells out. Template-level decisions like these sit inside ecommerce SEO rather than being made product by product.