PDP vs PLP: The Difference, and Which One Should Rank

Last updated: October 15, 2026

A PLP (product listing page) shows many products so a shopper can compare and narrow down. A PDP (product detail page) shows one product in full so a shopper can decide to buy. On Shopify, a PLP is a collection page at /collections/... and a PDP is a product page at /products/....

That part is simple. The part that costs stores money is the next question: which of the two should rank for a given search, and what happens when both try.

New to the terms? Start with What is a PDP in ecommerce.

The difference at a glance

	PLP (product listing page)	PDP (product detail page)
Products shown	Many	One
Also called	Collection, category, catalogue page	Product page, product display page
Shopper intent	"What are my options?"	"Should I buy this one?"
Shopify URL	/collections/running-shoes	/products/nimbus-26
Shopify template	collection.liquid	product.liquid
Typical search	"running shoes for flat feet"	"asics nimbus 26 mens size 10"
Search volume profile	Higher volume, broader	Lower volume, long tail, higher intent
Primary job	Narrow the choice	Remove doubt and close
Key elements	Filters, sorting, thumbnails, price	Images, variants, add-to-cart, proof
Conversion rate	Lower (browsing)	Higher (deciding)

Which page should rank for what

This is the decision that actually matters, and the rule is intent-based.

PLPs should rank for category and modifier searches. Anything plural, anything with a qualifier, anything where the shopper has not chosen yet:

• "running shoes"
• "waterproof hiking boots"
• "gold hoop earrings under £50"

The shopper wants a set to choose from. Landing them on one product is a mismatch: they bounce back to Google to see the alternatives.

PDPs should rank for product and model searches. Anything naming a specific item:

• "asics gel-nimbus 26"
• "nimbus 26 womens size 7 black"
• brand + model + variant combinations

The shopper has already chosen. Landing them on a collection page makes them search again inside your site, and a meaningful share will not.

The grey zone is single-product categories. If you sell one hero product, the PDP and the category are effectively the same thing, so consolidate rather than maintain both.

When they cannibalise each other

Cannibalisation happens when both page types compete for the same query and Google cannot decide which to serve. The symptoms are recognisable:

• A query's ranking URL flips between a collection and a product page week to week
• Both pages sit on page 2–3 when one of them alone could reach page 1
• Impressions are healthy and clicks are not, because neither page is a confident match

In Google Search Console, filter by query and look at the Pages tab. If two URLs trade positions for the same term, that is the signal.

The fix is not to delete one. It is to make the intent split explicit:

1. Decide which page type owns the query, by the rule above.
2. Give the losing page a different, narrower target, or deindex it if it serves no search purpose.
3. Internally link from the losing page to the winner with exact-match anchor text.
4. Make sure titles do not overlap. If the collection is "Running Shoes" and a product is "Running Shoe - Nimbus 26", the overlap is doing damage.

How each page earns its ranking

The two page types rank through completely different mechanisms, and treating them the same is why most stores underperform on one of them.

PLPs rank on:

• Category-level copy that actually says something (not 400 words of filler below the grid)
• Internal linking depth: how many places point to this collection
• Filter and facet handling that does not create thousands of thin duplicate URLs
• Clear, stable URL structure

PDPs rank on:

• Unique product copy: manufacturer descriptions used verbatim are duplicate content
• Structured data: Product schema with price, availability, reviews
• Review volume and recency
• Image optimisation and alt text
• Internal links from relevant collections and content

The most common technical mistake on PLPs is letting every filter combination generate a crawlable URL. The most common mistake on PDPs is shipping the supplier's description unchanged across every store that sells the same item.

For the conversion side of the product page, see our Shopify PDP optimization guide.

On Shopify specifically

	PLP	PDP
Template	collection.liquid / collection.json	product.liquid / product.json
URL	/collections/<handle>	/products/<handle>
Duplicate risk	/collections/x/products/y nested URLs	Variant URLs with ?variant=
Schema	ItemList / BreadcrumbList	Product + Offer + AggregateRating

Two Shopify-specific traps:

Nested product URLs. Shopify can serve the same product at /products/nimbus-26 and /collections/running/products/nimbus-26. Canonical tags should always point to the clean /products/ version. Most themes handle this, but it is worth verifying rather than assuming.

Tag-based filter pages. Collection filtering via tags can generate large numbers of near-identical URLs. These should not be indexable unless a specific filtered view has real search demand behind it: "mens running shoes" might; "running shoes sorted by price ascending" does not.

Frequently Asked Questions

What does PLP stand for?

PLP stands for product listing page: a page showing multiple products, such as a category or collection page. It is the counterpart to the PDP, or product detail page.

Should a PLP or a PDP rank for a category keyword?

A PLP. Category searches like "running shoes" are comparison searches: the shopper wants options. Serving a single product page to that query is an intent mismatch and usually results in a bounce back to the results page.

Can a PDP rank for broad keywords?

Occasionally, for very strong brands or genuinely unique products with no category to sit in. For most stores it is not worth pursuing: the PLP will serve that intent better and convert the resulting traffic more reliably.

How do I know if my PLP and PDP are cannibalising?

In Google Search Console, filter to the query and open the Pages tab. If two URLs alternate positions for the same term across weeks, they are competing. Decide which page owns the intent and redirect the other's targeting.

Do PLPs and PDPs need different schema?

Yes. PLPs use ItemList and BreadcrumbList. PDPs use Product with Offer and, where reviews exist, AggregateRating. Applying Product schema to a listing page is a common error and does not produce product rich results.