E-commerce Product Page SEO

Product pages are where e-commerce SEO is won or lost, and they are usually the least optimised pages on the store. Most shops pour effort into the homepage and category pages, then publish four hundred product pages with the manufacturer's description pasted in.

Those product pages are the ones matching what people actually search.

Start with the title tag

Product page titles are frequently just the product name, which wastes the most valuable ranking real estate you have.

A structure that works:

[Product Name] – [Key Attribute] | [Brand or Store]

Real examples:

• Weak: Product 4839
• Better: Blue Running Shoes
• Good: Nike Pegasus 41 Running Shoes – Men's Blue | StoreName

Include what people search: brand, model, key attribute, and the product category. Keep it under 60 characters where you can.

Write your own product descriptions

Manufacturer descriptions are duplicated across every retailer selling that product. Google has to choose which copy to rank, and it will not choose the smallest store.

What a good description covers:

• What problem it solves, in the customer's language.
• Specifications, in a scannable format.
• What is in the box.
• Sizing, fit or compatibility.
• The questions your support team keeps answering.

Aim for 300+ words on products that matter. For a catalogue of thousands, prioritise your top 20% by revenue — the rest can wait.

That last point is worth dwelling on. Your support inbox is a keyword research tool. The questions customers ask before buying are, almost word for word, what they typed into Google beforehand.

Product schema is not optional

Structured data is what produces the price, availability and star rating in search results. Those rich snippets meaningfully change click-through rate.

Minimum viable Product schema:

{
  "@context": "https://schema.org",
  "@type": "Product",
  "name": "Nike Pegasus 41 Running Shoes",
  "image": ["https://example.com/pegasus-41.jpg"],
  "description": "Your own product description here.",
  "sku": "NP41-BLU-42",
  "brand": { "@type": "Brand", "name": "Nike" },
  "offers": {
    "@type": "Offer",
    "url": "https://example.com/pegasus-41",
    "priceCurrency": "USD",
    "price": "129.99",
    "availability": "https://schema.org/InStock"
  },
  "aggregateRating": {
    "@type": "AggregateRating",
    "ratingValue": "4.6",
    "reviewCount": "89"
  }
}

Two rules: the price and availability in your schema must match what is on the page, and only include aggregateRating if you genuinely have reviews. Mismatches and invented ratings get manual actions.

Handling variants without creating duplicates

This is the most common structural mistake in e-commerce SEO. One shirt in six colours and five sizes can generate thirty near-identical URLs.

Three approaches:

1. One page, variants selected on-page. Simplest, avoids duplication entirely. Best when people search the product, not the variant.
2. Separate pages with canonicals to a main version. Use when variants have genuinely different content, but you want ranking consolidated.
3. Separate indexable pages per variant. Only when people actually search for the specific variant — "red Nike Pegasus 41" has real volume; "size 9.5" does not.

Whichever you pick, ensure filter and sort parameters (?color=blue&sort=price) are not generating indexable duplicates. Canonical them to the clean category URL.

Images

Product images are both a conversion factor and a traffic source through Google Images.

• Descriptive filenames — nike-pegasus-41-blue.jpg, not IMG_4839.jpg.
• Alt text describing the product — "Nike Pegasus 41 running shoe in blue, side view".
• Compressed and served as WebP. Product galleries are usually the heaviest thing on the page.
• Explicit width and height to prevent layout shift.
• Lazy-load gallery images, but never the main product image — that is your LCP element.

Out of stock and discontinued products

Deleting a product page throws away every link and ranking it accumulated.

• Temporarily out of stock: keep the page live, set schema availability to OutOfStock, show an expected date, and offer a back-in-stock notification.
• Permanently discontinued with a successor: 301 redirect to the replacement.
• Discontinued with no successor: keep it live if it has traffic or links, with clear alternatives shown. Only 410 it if it has neither.

Never redirect everything to the homepage. Google treats that as a soft 404 and it helps nobody.

Reviews

Reviews add unique content to every product page automatically, in the exact language customers use. They also feed aggregateRating schema.

Ask for them systematically — an automated email seven to fourteen days after delivery. Publish the negative ones too; a product with only five-star reviews reads as fake, and the response to a critical review is often more persuasive than the praise.

Technical checklist for stores

• Product pages reachable within three clicks of the homepage.
• Category pages have unique intro copy, not just a product grid.
• Breadcrumbs implemented, with BreadcrumbList schema.
• Pagination handled properly, not blocking crawl of deep products.
• Internal search result pages set to noindex.
• XML sitemap includes all live product URLs and excludes out-of-stock discontinued ones.
• Mobile page speed passing — most e-commerce traffic is mobile.
• Checkout and cart pages noindex.

Where to start with a large catalogue

If you have thousands of products, do not attempt all of them.

1. Identify your top 20% by revenue.
2. Write original descriptions for those first.
3. Fix schema across the whole store — that part is templated and scales for free.
4. Fix faceted navigation and crawl waste — also a one-time structural fix.
5. Work down the catalogue by revenue over time.

Steps 3 and 4 are template-level changes that improve every page at once. Do them before the manual content work.

If you are building or migrating a store, this is part of what our e-commerce development and SEO services cover.