Product detail page(PDP)

Long definition

The PDP is the unit of inventory in SEO terms. Every other page in an ecommerce architecture exists to feed the PDP traffic and authority — the home links to PLPs, PLPs link to PDPs, the PDP closes the deal.

Title patterns. The reliable structure for high-intent product queries is Brand + Product Name + Key Attribute. "Sony WH-1000XM5 Wireless Noise-Cancelling Headphones" beats "Premium Headphones — Buy Now" by a wide margin in CTR studies. For long-tail variants, append the differentiator: ... — Black, 30hr Battery. Don't stuff. Don't repeat the brand twice. The H1 can match the title or trim the brand suffix; what matters is consistency with the schema's name field.

Above the fold. The first viewport carries the load-bearing decision elements: gallery, price, availability, primary CTA, and one trust signal (review count or shipping promise). Every additional element pushed above the fold pushes the buy button down. The classic mistake is stuffing reviews, related products, or banner promos there — they belong below the fold. A PDP that loses the buy button on a 13-inch laptop loses conversions at the same rate as any other commerce conversion failure.

Schema. Every PDP carries schema.org/Product as JSON-LD: name, image, description, brand, sku, gtin13, offers (with price, priceCurrency, availability, priceValidUntil), and aggregateRating plus individual review nodes when reviews exist on the page. See product-schema for the field-by-field breakdown.

Internal linking from PLPs. Each PDP should be reachable from at least one PLP, ideally with a descriptive anchor (the product name, not "view product"). Featured / best-seller blocks on the home or category pages funnel link equity to the most strategic PDPs. Orphan PDPs — reachable only via on-site search — get crawled rarely and rank poorly.

Common misconceptions

• "Every variant needs its own PDP." Not since hasVariant shipped in October 2023. A single canonical PDP with ProductGroup can host all SKUs without fragmenting backlink authority. See product-variant-seo.
• "Long descriptions are always better." A wall of text below the fold doesn't help if the load-bearing facts (size chart, materials, return policy) are buried. Information hierarchy beats length.
• "Reviews live on a separate review page." Reviews on a separate URL forfeit eligibility for the PDP's aggregateRating rich result. They must be on the same URL as the buy button.
• "PDP H1 should match the search query exactly." The H1 should match the product, not whatever query you're chasing. Query-stuffed H1s read like spam to both users and quality systems.