What is a PDP (product detail page) in ecommerce?

PDP is an acronym you will read in an analytics report, in an agency proposal or in your store theme's documentation, and it names something you already know: the product page, the page devoted to a single product, with its price and its buy button. What that page should carry, field by field, is in the product page entry. Here is what the acronym adds: where it comes from, where you will find it, and how it differs from its counterpart, the PLP (product listing page). When someone proposes to "improve the PDP", ask whether they mean one page or the template all of them share: the budget and the risk are nothing alike.

What PDP means and where it is used

The page that Schema.org describes with the Product type, defined as any offered product or service,⁠^{[1]Schema.org. Product} has a long name, product detail page, and a short one, PDP. Most store owners just say product page, and the acronym lives with teams that work with tools and documentation built around it. It shows up mainly in three places.

In analytics. Google Analytics 4 measures ecommerce with events, and two of them separate exactly these two pages: view_item is sent every time someone views an item's detail screen, and view_item_list, when they are shown a list of results.⁠^{[2]Google Analytics, developer documentation. Measure ecommerce} Between the two comes select_item, sent when that person picks an item from the list, and then add_to_cart, when they add it to the cart.⁠^{[2]Google Analytics, developer documentation. Measure ecommerce} In a purchase funnel, the PDP is the step between seeing a list and adding to cart, and it is the page behind metrics like "PDP views" or "PDP conversion".

In templates. A store does not design each product page separately: it generates them from a template. In Shopify themes, the product template is the one that renders the product page, with its images and content and a form for the customer to pick a variant and add it to the cart.⁠^{[3]Shopify.dev. product (template)} The collection template renders the page that lists all the products in a collection, with filters, sorting and pagination.⁠^{[4]Shopify.dev. collection (template)} So "changing the PDP" can mean one page or all of them at once: a change to the template reaches every page that uses it.

In Google's documentation. Google does not need the acronym, but it does need the distinction. Its product results accept only pages centered on a single product, or on several variants of the same product, and a page that lists products, such as "shoes from our store", does not count.⁠^{[5]Google Search Central. Merchant listing (Product, Offer) structured data} In addition, only pages where the product can be bought are eligible for merchant listings.⁠^{[5]Google Search Central. Merchant listing (Product, Offer) structured data} In its guide to ecommerce site structure, the natural path runs from the menu to the categories, from the categories to the subcategories and from there to every product page.⁠^{[6]Google Search Central. Help Google understand your ecommerce site structure}

In a store

A fictional example: an outdoor gear store on Shopify and four of its pages, classified by the same criteria analytics and Google use.

The second row is the one that raises the most questions. A shoe with eighteen size and color combinations is still a single PDP, because Google accepts in its product results pages for one product with several variants.⁠^{[5]Google Search Central. Merchant listing (Product, Offer) structured data} What changes is the markup, which has to say which product variants exist and which one each is. The fourth row matters too: a guide can talk about a product and link to it, but it is not a PDP, because it is not the page where you buy.

How to check it

1. Open a product page and a category page on your store and note, for each, which theme template generates it. In Shopify, the product and collection templates are different ones.⁠^{[3]Shopify.dev. product (template)}⁠^{[4]Shopify.dev. collection (template)}
2. Look in Google Analytics 4 at which event is recorded when each opens. The product page should fire view_item and the category should fire view_item_list; if they are swapped, the PDP reports do not measure what they say.⁠^{[2]Google Analytics, developer documentation. Measure ecommerce}
3. Look for the Product block in the product page's code and confirm it does not appear on the category page as if it were a product: Google's product results accept only pages for one product or its variants.⁠^{[5]Google Search Central. Merchant listing (Product, Offer) structured data}
4. Check that you can reach each product page from the category through a normal link. Google recommends linking from categories to all product pages and warns that otherwise Googlebot may not find all your products by crawling alone.⁠^{[6]Google Search Central. Help Google understand your ecommerce site structure}

Related concept: PLP

The PLP is the page that lists several products, such as a category, a collection or the internal search results, and links to each one's PDP. In analytics they are told apart by the event (view_item_list versus view_item),⁠^{[2]Google Analytics, developer documentation. Measure ecommerce} in a Shopify theme by the template,⁠^{[4]Shopify.dev. collection (template)} and in Google by the markup: product markup goes on the PDP and not on the PLP.⁠^{[5]Google Search Central. Merchant listing (Product, Offer) structured data} The PLP helps people choose; the PDP closes the sale, and a store needs both well linked to each other.

To keep going, the catalog and entities reading path lays out the rest of the terms, and the guide to auditing a product page's markup breaks it down into steps.