Product Page SEO: How to Rank a Catalogue, Not Just One Page

I sit down with a store owner, open Search Console, filter the pages report to /product/, and we usually see the same picture. Nine hundred product pages on the site. Around forty of them have ever been shown to a human being.

That shop did not have a content problem. It had one page nobody had told what to rank for, repeated nine hundred times.

Most guides to product page SEO hand you a list of seventeen things to do to a product page. That list is fine, right until you own a catalogue. Nobody hand edits nine hundred pages, and nobody should. The useful questions are which pages deserve a person, what the template does for everything else, and what Google now needs in the code before your price and your stock appear in the result.

Here is the process I use, in the order I use it.

What does a product page need to rank?

A product page ranks when it answers a shopping query better than the other results: a title that matches how buyers name the thing, a description written for your store instead of copied from the supplier, images with real alt text, visible price and availability backed by structured data, and reviews from people who bought it.

That is the checklist part. It is also the easy part.

The harder truth is that the ceiling is usually not the page, it is the query. If four hundred other retailers list the same item, the search result is a fight between marketplaces, and your copy of the manufacturer paragraph will not win it. You need a page that says something the supplier PDF never said.

Which keyword should a product page target?

Product pages win specific queries and category pages win broad ones. A single item page should target the way a buyer names that exact item, usually brand plus model plus one attribute. The phrase that describes the whole class belongs to the category page sitting above it.

The most expensive mistake I see is a shop aiming its best product page at the category term, then wondering for six months why it sits on page four. Google is showing a list for that query. You handed it one item.

How do you fix product descriptions across a big catalogue?

You do not fix them all. Rank the catalogue by revenue and by impressions, rewrite the top slice by hand, and let the template carry the tail.

Open the Search Console pages report, filter to your product URL pattern, sort by impressions and export it. Cross that list against your best selling products from the last year. The overlap is your work list, and in most stores it runs to twenty or fifty pages rather than the whole catalogue.

When you do rewrite, add what the supplier never wrote. How it sizes against the brand next to it. What is actually in the box. The question your customer service team answers eleven times a week. And the honest line about who should buy something else, which does more for conversion than any adjective. That work is the core of what our team does inside a store, and it is why ecommerce SEO is mostly editorial work rather than technical tinkering.

What should the template handle for everything else?

Anything that can be generated from product data belongs in the template, so the tail of your catalogue gets a competent page without a person touching it.

A title formula that holds up across thousands of products: brand, model, the attribute people search by, then your store name, kept near sixty characters so Google shows it whole. Breadcrumbs with markup, so the result carries the category path. A specifications block rendered as plain text. Image file names and alt text built from the product attributes you already store. Related product modules that link sideways across the catalogue.

One rule I would enforce without exception: no product page exists without a link from a category page. Orphan products are everywhere in stores that push stock straight from an ERP, and a page nothing links to is a page Google rarely comes back to.

What structured data do product pages need?

Product markup, and which flavour you need depends on whether someone can buy on the page. Google documents two treatments. Product snippets lean on review information and suit editorial pages where nothing is for sale. Merchant listings cover purchasable items and open up apparel sizing, shipping detail and return policy inside the result.

Give it price, currency, availability and condition. Then add the parts most stores skip. Google’s guidance asks for the return policy, any fees involved and how many days a customer has to send something back, and it lets you declare those policies once at organisation level rather than on every page.

Validate with the Rich Results Test, then watch the merchant listings report in Search Console. Markup that disagrees with the visible page gets you flagged rather than rewarded, and the usual culprit is a price in the code that no longer matches the price on screen after a sale ends.

How do you handle variants, stock outs and discontinued products?

One indexable page for each thing a person actually searches for. Everything else consolidates.

For variants, the test is whether buyers type the attribute. In fashion they type the colour, so a colour URL can earn its own place. In most other categories they do not, and those variant URLs should carry a canonical pointing at the main product page instead of splitting the same signals twelve ways.

For products that go out of stock, keep the page live, set availability to OutOfStock in the markup, and put alternatives high on the page. When a product is gone for good, redirect it to whatever replaced it, or to its category if nothing did. Sending every dead product to the home page is the lazy option, and Google mostly treats it as a soft 404.

Do product pages show up in AI answers?

Sometimes, though rarely on their own. When ChatGPT or an AI Overview recommends a specific product, it tends to lean on the material around the purchase: comparison pages, buying guides, size charts, and what reviewers said. The store that gets named is the one with a real ecosystem around the decision, not the one with the prettiest add to cart button.

Two practical things follow from that. Keep specifications as genuine HTML text, because a spec table hidden behind a tab that only renders after a click is invisible to a lot of what reads your page. And keep the product name identical across your site, your Merchant Center feed and any marketplace listing, so a machine reading all three can tell they describe the same object.

What changes when you sell into more than one country?

Each market needs its own product URL, its own hreflang set, its own currency and its own delivery and returns information. Skip that and the right page for the wrong market outranks the one you meant to show.

Plenty of Spanish stores translate the description into French, publish it, and stop. No hreflang between the versions, delivery times written for a customer in Madrid, and a returns address the French buyer will never use. The page ranks badly and converts worse, and it is normally the first thing we unpick in an international SEO project.

Where I would start this week

Open Search Console tomorrow morning, filter to your product pages and sort by impressions. The twenty pages at the top are where a week of writing pays for itself, and you will probably find two or three sitting in position eleven that move with an afternoon of work.

I am Armen, an SEO consultant in Barcelona, and I run ACERO Digital with a team who spend most of their week inside catalogues like yours. If you would rather have someone tell you which twenty pages matter before you spend the week, get in touch and send me the URL of your store.