Product Page SEO

A product page (PDP) is the URL that should rank when someone wants that item, not “a type of item.” Category pages handle the type. If you mix those jobs, both URLs compete and neither converts cleanly.

Keyword mapping is covered in E-Commerce Keyword Research. This article is what goes on the PDP itself.

Title, meta, and first screen

The title tag should name the product the way a shopper searches: brand, model, a distinguishing attribute (size, color, pack). It is not a marketing headline. Check length and overlap with the meta title preview and how it looks in results with the SERP snippet preview.

On-page H1 should match the product, not a different promotional name. Price, availability, and primary image belong in the first viewport. SEO that hides stock until scroll is conversion work wearing a ranking costume.

Meta description is a pitch for the click, not a ranking lever. Include a fact (capacity, material, what’s included) and a differentiator you can keep true (cut-off time, bundle). Do not promise rankings or delivery you do not operate.

Copy that is unique to the SKU—and to variants

Manufacturer PDFs are written once. If you paste them, you are one of many identical pages.

Minimum unique layer:

• What is in the box (cables, spare parts, manuals).
• Compatibility you have verified, not a slogan.
• Who it is not for (saves returns).
• Shipping and return facts that apply to this SKU (hazmat, made to order).

The word counter tells you whether the template rendered empty. It does not tell you the page is “optimized.” A 120-word spec-led description that is true beats 800 words of interchangeable adjectives.

Variants. If navy and red are the same copy and the same lifestyle photo, one canonical URL with a selector is usually cleaner. If navy is a different SKU people search by color name, give navy its own URL, image, and title—and canonical logic that does not point all colors at a default that never matches the query. Technical SEO covers canonicals; the merchandising choice is yours.

Out-of-stock: keep the URL if you will replenish; show status and a substitute. Deleting URLs every time a size sells out creates 404 churn.

Specs as the ranking and conversion body

Search engines and shoppers both use structured facts. A table is not decoration.

Field	Why it belongs on the PDP
Dimensions / weight	Shipping cost, fit, “will it fit my bag”
Materials / ingredients	Allergens, durability, compliance
What’s included	Reduces “missing parts” tickets
Warranty / support path	Trust without fake review stars
SKU / MPN	Model queries and feed quality

Mark those facts up only if they are visible—see E-Commerce Schema Markup. Do not invent ratings.

Amazon’s listing fields are a different surface with different rules; do not copy Amazon backend-term tricks onto your own site. For the marketplace, use Amazon Product Listing Optimization.

Internal links that a crawler can use

From the PDP:

• Breadcrumb to the primary collection (the one in your IA, not five overlapping crumbs).
• HTML links to 2–5 related in-stock products (not a JS widget that never renders in the initial HTML).
• A link to a fit or care guide if that content exists.

Internal linking for online stores explains orphan SKUs. A product that is only reachable from site search is weakly crawled.

Do not stuff the description with links to every category you sell. One clear parent is enough.

Indexation checklist

• One canonical URL per product you want in the index.
• Variants: index only when unique; otherwise rel=canonical to the parent and keep robots consistent.
• Sitemap includes canonical PDPs, not every parameter combination.
• Thin or duplicate SKUs (same product, new URL for a sale price) should not all be indexable.

Title templates that stay true

A workable pattern: Brand + Product type + distinguishing spec. Example shape: “Acme 500ml insulated bottle — navy.” Swap navy for the variant you index. Do not append “best,” “cheap,” or a year unless the product actually changes by year.

When the manufacturer name is the query, put it first. When the generic type is the query, the collection should rank—not twenty PDPs with the same type in the title (keyword research).

Sale price in the title (“20% off”) goes stale. Put promos in the visible badge and keep the title identifying.

Out of stock, bundles, and sets

OOS PDPs can still rank for the model query. Show status, a restock hint if honest, and HTML links to in-stock substitutes. Redirecting every OOS URL to the collection deletes the query match.

Bundles need their own URL if people search the bundle name; otherwise they confuse the parent SKU’s specs. Sets should list contents so schema and shoppers agree (schema markup).

User-generated Q&A belongs on the PDP only if you moderate it. Unreviewed answers become return reasons and, if marked up, a schema honesty problem.

Platform notes: Shopify SEO Fundamentals (duplicate product URLs, collections) and WooCommerce SEO Fundamentals (permalinks, plugin canonicals).

The longer template and merchandising pass is the e-commerce product page guide. Pair it with the e-commerce SEO guide. A PDP is SEO-complete when a crawler can find it, a shopper can identify the SKU in the title, and the body is not a clone of the manufacturer’s page.