In the category page post I made the case that categories are the highest-leverage template on a store, and the practical split I gave was to optimise categories to be found and product pages to be chosen. That's still the right order of work. But "chosen" undersells what a good product template does in search, because product pages fight a contest of their own, the long tail of specific, late-stage queries that no category can match. This post is what I actually do to the product template in ecommerce SEO engagements, once the category work is under way.
The template framing matters as much here as it did for categories. You won't hand-optimise eight hundred product pages, and you don't need to. Most of what follows is a fix to the template or the data feeding it, applied once and multiplied across the catalogue, with hand-written effort reserved for the products that earn it.
The searches product pages win
Category queries are broad and product queries are precise. Someone typing "walking boots" wants a range to browse, and someone typing a specific brand and model name, or "in size 11", or "spare filter for", has finished browsing and is choosing where to buy. The volumes on these queries are individually tiny and collectively significant, and the intent is about as close to a purchase as search traffic gets.
That precision is also why the work is different. A category page is built around one query you chose. A product page matches whatever specific phrasing the buyer brings, which means its job is to carry the product's real name, its distinguishing attributes, and the details a buyer checks before paying, in crawlable text rather than locked inside an image or a tab that never renders.
Titles that match how people search for the product
The title tag fix is the cheapest one on the template. The default on most platforms is the product name as entered in the admin, which is fine when the product name is what people search and useless when it's an internal naming convention. "SKU-4402 Classic II" tells Google nothing. "Men's Classic II Leather Walking Boot" matches the query.
The pattern I set is product name, then the one or two attributes that disambiguate it (the material, the fit, the model year, whatever buyers actually specify), then the brand. Front-loaded, no keyword stuffing, and driven by the product data so it applies catalogue-wide without anyone editing titles by hand.
Descriptions, and the manufacturer copy problem
The standard failure on product pages is the pasted manufacturer description, the same paragraph that appears word for word on every other retailer stocking the item. It's worth flagging that this isn't a penalty risk, it's a relevance problem. When fifty stores publish identical text, Google picks one or two to rank, usually the biggest, and a smaller store competing with borrowed words has given up its only editorial advantage.
The answer isn't to rewrite eight hundred descriptions next week. Rank the catalogue by revenue and search opportunity, rewrite the top slice properly, and let the rest wait their turn. A proper rewrite is written for the buyer's decision, not the crawler: what it's made of, how it fits or fails to, what it's compatible with, what's in the box, and the question every returns team wishes had been answered on the page. Two hundred honest words beat eight hundred padded ones.
Structured data is where product pages earn their rich results
Product pages have a search feature categories don't get, the merchant listing treatment, price, availability and review stars shown directly in results. Google's requirements for it are specific: the page must be one where a shopper can actually buy, and the markup needs a name, an image, and an offer carrying the price, the currency, and availability. Get that right across the template and every product in the catalogue becomes eligible at once.
Most modern platforms output Product schema by default, so the practical work is usually checking rather than building. The recurring fault I find in audits is duplication, a theme outputting one block of Product markup and a review app outputting another, with conflicting values in each. Search Console's merchant listings report shows what Google can actually read, and it's the first place I look. On Shopify the app stack is the usual culprit, which is a pattern I've covered in the Shopify SEO guide.
Variants, and one product wearing five URLs
Every store with variants faces the same question, one page with a size picker or separate pages per variant. Search demand answers it. If people search "in green" or by capacity, and the SERP shows retailers ranking variant pages, splitting can be justified. If they don't, separate variant URLs are just duplicate pages splitting their own authority, and they belong canonicalised into one.
The same consolidation logic applies to duplicate product URLs generally. Platforms mint them freely, session parameters, collection-scoped paths, tracking suffixes, and every duplicate collects internal links that should be concentrating on one canonical page. This sits alongside faceted navigation in the family of ecommerce problems that quietly cap everything else, and my technical SEO checklist covers the crawl and indexation side in full.
Out of stock, discontinued, seasonal
Product pages die more often than any other template, and stores rarely have a policy for it. The default outcomes are bad in both directions, dead pages returning 404s and losing whatever equity they'd earned, or zombie pages selling nothing and clogging the index. The right move depends on why the product went away.
| Situation | What to do | Why |
|---|---|---|
| Out of stock, coming back | Keep the page live, mark it out of stock, show a restock date or notify option | The page keeps its rankings and the buyer gets an honest answer |
| Discontinued, direct successor exists | 301 redirect to the successor | Passes the old page's equity to the page that can actually convert |
| Discontinued, no replacement | Redirect to the closest category, or let it 410 if it never earned links or traffic | A category is a useful landing; redirecting everything to the homepage is not |
| Seasonal | Keep the page live all year | Rebuilding each season starts the ranking clock from zero every time |
The one firm rule is that the decision is made deliberately, per situation, rather than left to whatever the platform does by default.
Reviews do quiet double duty
Customer reviews are the cheapest content a product page can acquire. They're unique text on a template otherwise prone to duplication, they refresh pages that would never otherwise change, they supply the ratings that feed the review stars in results, and customers phrase things in the exact long-tail language other buyers search. A review section that renders as crawlable text, rather than inside a widget Google can't read, is one of the better returns on the template. Soliciting them honestly, and replying to the bad ones, is retail work rather than SEO work, but the SEO benefit is real.
A product page needs a route in
Product pages sit at the bottom of the site's hierarchy, which means they rank on the authority the structure passes down to them. The category page is the primary route, one more reason the category work comes first, supported by related-product links that connect the long tail sideways. The failure case is the orphan, a product removed from its collections but still live, reachable only through the sitemap. Orphaned products are among the most common finds in my audits, and a page with no internal links is a page the store has already given up on, whether anyone decided that or not.
Product page SEO FAQs
How long should a product description be?
Long enough to answer what a buyer checks before purchasing, which for most products is 150 to 300 words. Word count targets produce padding, and padding helps nobody. A short description that covers materials, sizing, compatibility and the common pre-sales question outranks a long one that says nothing, because it earns the engagement and the conversions that a ranking has to be built on.
Do I need unique descriptions for every product?
Eventually, ideally, but not next week. Prioritise by revenue and by search opportunity, rewrite the products that matter, and accept manufacturer copy on the long tail until each product's turn comes. A store that rewrites its top hundred sellers properly gets most of the available benefit.
Should out-of-stock product pages be deleted?
Not if the product is coming back, keep the page live and marked out of stock so it holds its rankings. Deletion, or rather a redirect or a deliberate 410, is for discontinued products, and the choice between them depends on whether a genuine successor exists. The mistake to avoid is bulk-redirecting every dead product to the homepage, which Google treats as a soft 404 and buyers experience as a dead end.
Do reviews on product pages help SEO?
Yes, on several fronts at once. They add unique, regularly refreshed text to the page, they supply the rating data that makes review stars possible in search results, and they capture the natural phrasing of long-tail queries. They need to render as crawlable text on the page rather than inside a script-only widget, which is worth checking before assuming the benefit is being collected.
Want the whole catalogue working in search?
Tell me what you're working on and what you're trying to achieve, and I'll give you an honest view of whether I can help and what it would take.
Get in touch