Ecommerce SEO
Product pages live a double life: the long tail's landing spot for "[exact product] + [modifier]" searches, and the conversion floor where every upstream ranking gets cashed or wasted. Optimising them is mostly a template job — decisions made once, multiplied across the catalogue — plus an editorial investment reserved for the products that earn it. Here's the field guide: the template layer, the content layer, and the triage that decides which SKUs get the hours.
The template layer (fix once, win everywhere)
- Title pattern: [Product Name] – [Key Attribute] | [Brand] — the product's actual search identity front-loaded, boilerplate trimmed per the CTR findings. Attribute choice matters: the spec buyers search by (size, material, compatibility) belongs in the pattern.
- Product schema, complete and live: price, availability, ratings pulled from real data — the stars-and-price SERP treatment is the template layer's biggest single CTR lever.
- The variant decision: one canonical page per product with variants as options (default, correct for most) versus separate URLs per variant (only when variants have distinct search demand — "red X" as a real query) — the duplication rules applied at template level.
- Image discipline: multiple angles, compressed, alt-texted with the product identity — product images rank in image search and feed Shopping surfaces.
- The trust furniture in-template: reviews rendered (indexable text, not JS-only widgets), shipping/returns visible, stock status honest — conversion inputs that double as content uniqueness.
- Internal links beyond the grid: breadcrumbs (with markup), related products chosen by genuine relation, and — the underused one — links from relevant guide content into the product, per the routing strategy.
The content layer (where the triage applies)
Manufacturer boilerplate is the default and the problem — the same paragraphs on fifty competing stores, per the sameness rules. The fix is real description writing: what it's for, who it fits, honest trade-offs, the questions buyers actually ask (mine support tickets and reviews for them — FAQ blocks on product pages are snippet bait with buying intent). But writing 5,000 descriptions is a misallocation, so triage per the case study's 80-of-800 rule: unique editorial for the revenue head (top sellers, high-margin, high-search SKUs), enhanced-template treatment for the middle (attribute-driven generated text plus reviews doing the uniqueness work), and structural-only for the long tail — canonical hygiene, schema, and a strong category above them carrying the ranking load.
The measurement that keeps it honest
Product-page SEO reports on two lines, per the chain: long-tail entry (product-page organic sessions and their query breadth in Search Console — the template layer's scoreboard) and revenue per organic session on product pages (the content layer's). The classic diagnostic split: impressions without clicks → title/schema problem; clicks without conversions → content/trust problem; neither → the category above is weak, and the fix lives one level up.
Frequently asked questions
How long should product descriptions be?
As long as a real buying decision needs — a commodity cable wants specs and compatibility in a hundred words; a premium jacket wants materials, fit and care in four hundred. The word-count question is the wrong frame here as everywhere; the coverage question (would a knowledgeable friend's answer be complete?) is the right one.
Should out-of-stock or discontinued products keep their pages?
Policy question with a full guide of its own — short version: temporary outages keep the page live and honest; permanent removals redirect to the successor or category; never mass-404 URLs that hold rankings and links.
Can product pages earn links at all?
Rarely directly (the indirection doctrine exists for a reason) — exceptions being genuinely novel products that get press and the comparison-format pages that straddle content and commerce. For everything else: the guides earn, the architecture routes, the products cash — with the earning side scalable through real publisher placements (ours).