Product Page SEO: A Field-Tested Checklist
The six things every ranking product page gets right: titles, original descriptions, live structured data, images, reviews, and internal links.
A product page that ranks and converts needs six things done correctly: a unique title and H1 built around the actual product name and its distinguishing attribute, a description written for the specific SKU rather than copied from the manufacturer, valid Product structured data with live price and availability, fast-loading original images with descriptive alt text, genuine review content where it exists, and internal links back to the category and related products it belongs with. Miss any one of these and the page either fails to rank, fails to earn a rich result, or ranks and still doesn’t convert. This is the field-tested checklist, in the order that actually moves the needle.
Key takeaway
- Title tags and H1s should include the exact product name plus the one attribute a shopper searches by — size, color, model number, or material.
- Product structured data must include price, priceCurrency, and availability rendered in the server-side HTML, not injected by JavaScript after load.
- A copied manufacturer description won’t get outright penalised, but it competes weakly against pages Google judges more complete and original.
- Reviews, genuine stock status, and fast page load are conversion factors that increasingly double as ranking factors through engagement and rich-result eligibility.
Why most product pages underperform before you even touch content
The most common failure isn’t bad copy — it’s a templated title tag that’s identical in structure across ten thousand SKUs, with nothing to differentiate one product from a near-identical variant three clicks away. “Men’s Running Shoe — Brand Name” repeated across twelve colorways gives Google no signal about which page should rank for which specific query. Fix the differentiation problem first: work the attribute that actually matters to search intent — size, color, capacity, model number — into the title, H1, and URL slug before spending any effort on the description itself.
Title tags, H1s, and URLs that actually differentiate
Keep the title tag under roughly 60 characters where possible, lead with the product name, and follow with the one differentiator a shopper is likely to search alongside it. The H1 can be slightly more natural and doesn’t need to match the title tag word for word, but it should still contain the product name plainly — don’t get clever with a marketing tagline as the H1 and bury the actual product name in body copy. URLs should be short, human-readable, and stable: changing a product’s slug after it’s earned rankings and backlinks is one of the more avoidable ways to lose organic traffic on a page that was already working.
| Checklist item | What “done right” looks like | Most common failure |
|---|---|---|
| Title tag | Product name + key differentiator, under ~60 characters, unique per SKU | Templated title identical across dozens of near-duplicate variants |
| Product description | Original copy written for this specific SKU, 150–300 words | Manufacturer description pasted verbatim, identical to hundreds of other retailers |
| Product structured data | Price, priceCurrency, availability rendered server-side, kept current | Schema present but stale — shows “in stock” on a sold-out item for weeks |
| Images | Multiple original angles, compressed, descriptive file names and alt text | Single manufacturer stock photo, generic alt text like “product1.jpg” |
| Reviews | Genuine customer reviews displayed with valid Review/AggregateRating schema | No reviews at all, or review schema present with no visible reviews on the page |
| Internal links | Breadcrumb back to category, links to 3–6 genuinely related products | Orphaned product page reachable only through search or a sitewide footer link |
Product descriptions: write for the SKU, not the catalog
Copying the manufacturer’s description saves time, and Google has been explicit that doing so doesn’t trigger a duplicate content penalty on its own. The real cost shows up differently: when your page and fifty other retailers all carry the identical paragraph, Google’s systems pick one representative version to show for that content, and it’s rarely the smallest or newest domain in the group. A description written specifically for your store — how this product fits into your catalog, what makes it different from the variant next to it, practical details a generic manufacturer blurb skips — gives the page an actual chance to be treated as unique. This doesn’t need to be long. 150 to 300 words is enough for most products, with shorter 50–100 word summaries acceptable for simple, low-consideration items. We cover this in more depth in writing product descriptions that rank and sell.
Structured data: the part that gets skipped and then goes stale
Google’s Product structured data requirements are specific: price, priceCurrency, and availability need to be present, accurate, and rendered in the HTML the server returns — not added by client-side JavaScript after the page loads. This is the single most common reason product pages lose rich-result eligibility. A store implements schema correctly at launch, then the inventory system updates stock status through a JavaScript layer that never touches the underlying markup, and six months later half the catalog shows “in stock” schema on products that sold out weeks ago. Google treats that mismatch as unreliable data and can quietly stop showing the rich result at all. Reviews compound this: AggregateRating markup with no actual reviews visible on the page is a mismatch Google’s systems are built to catch.
Server-rendered or it doesn’t count
Google’s structured data documentation is explicit that Product markup generated only by JavaScript after page load is unreliable for eligibility — price and availability fields in particular need to exist in the HTML the server returns.
Source — Google Search Central, Product structured data documentation
Images, load speed, and the things shoppers actually judge you on
Product pages are frequently the heaviest page type on an ecommerce site, loaded with multiple high-resolution images, review widgets, upsell carousels, and third-party scripts for reviews or chat. Every one of those is a candidate for slowing down the page’s largest contentful paint, which affects both rankings and, more directly, whether a shopper waits around for the page to finish loading. Compress images without visibly degrading quality, lazy-load everything below the fold except the primary product image, and audit third-party scripts on your highest-traffic product pages at least twice a year — they accumulate faster than anyone remembers to remove them.
- Confirm price and availability schema render in page source (view-source, not just the rendered DOM) and match what’s actually in stock.
- Check the title tag and H1 against three near-identical variant pages to confirm they’re genuinely differentiated.
- Rewrite any description copied verbatim from a manufacturer feed, starting with your highest-traffic SKUs.
- Confirm the primary product image loads with high priority and everything else is lazy-loaded.
- Add or verify breadcrumb schema and at least three genuine related-product internal links.
Internal links: the difference between a page that ranks and one that doesn’t
A product page with no inbound internal links beyond a sitewide footer mention is functionally invisible to Google’s crawler in terms of priority — it gets discovered eventually, but it’s treated as low-importance relative to pages that are actually linked from category listings, related-product modules, and breadcrumbs. This matters more for out-of-stock and seasonal products, which lose their internal links first when navigation gets pruned; see our guide on handling out-of-stock and discontinued products for how to manage that without losing the page’s accumulated authority. Structured internal linking, done consistently across a catalog, does more for average product-page rankings than any individual on-page tweak.
Frequently asked questions
Does a copied manufacturer description hurt product page rankings?
It doesn’t trigger a duplicate content penalty, but it competes weakly. When many retailers carry the identical paragraph, Google’s systems pick one representative version to surface, and a page with only copied copy has little to differentiate it from that competition.
What structured data does a product page actually need?
At minimum: price, priceCurrency, and availability, rendered in the server-side HTML rather than added by JavaScript. Add AggregateRating and Review markup only if genuine reviews are visible on the page — mismatched schema can disqualify the page from rich results.
How long should a product description be?
Most well-optimised product descriptions run 150 to 300 words, written specifically for that SKU. Simple, low-consideration products can work with a shorter 50 to 100 word summary as long as it’s original rather than copied from a feed.
Why do product page rankings drop after a URL change?
Changing a product’s slug resets the accumulated signal tied to that exact URL, even with a 301 redirect in place — redirects preserve most link equity but rarely all of it, and rankings typically take time to recover. Keep product URLs stable once they’re indexed and earning traffic.
Should every product variant have its own URL?
It depends on whether the variant has independent search demand — a different color with real search volume usually deserves its own URL, while a minor size variant often doesn’t. This gets its own dedicated treatment; the short version is: separate URLs for variants people actually search by name.
The bottom line
Product page SEO isn’t one big lever — it’s six smaller ones that all need to be correct at once: differentiated titles, original descriptions, accurate server-rendered structured data, fast-loading original images, genuine reviews, and deliberate internal links back to the category page above it. None of these are difficult individually. What’s difficult is doing all six consistently across a catalog of thousands of SKUs, which is exactly where most stores fall short and where the opportunity sits for anyone willing to fix it systematically, as laid out in our full ecommerce SEO guide.
Want your product catalog audited against this checklist? See our ecommerce SEO plans.
