A product page has one job before it has any other: let someone recognise the right pair, choose the right size and understand what happens after they pay. Search performance follows from that. Ranking depends on a coherent whole — the information you publish, the internal links around it, the images, the availability data and how the page behaves on a phone. Title tags and meta descriptions are part of the work, not a substitute for it.
Footwear makes the problem easy to see. Two models can look identical in a thumbnail and differ in width, upper material, sole construction and intended use. A buyer who cannot tell them apart either leaves or orders the wrong size and sends it back.
What follows applies to a catalogue rather than a single page. It assumes you have real product data, and that you are prepared to say what you do not know instead of filling the gap with adjectives.
Give categories and product pages separate jobs
A category page helps someone compare several products that answer the same need. A product page describes one model, or one variant, that the visitor is considering buying. That distinction drives your headings, copy and links: the category explains how to choose, the product pages carry the specifications.
Repeating a word such as trainers or boots across many titles does not prove cannibalisation. Check instead whether several pages answer the same intent with no clear difference, and which of them Google shows for the queries that matter. Model names, use cases and materials should make the difference obvious to a reader, not only to a crawler.
Link every product page to a relevant category and to the resources a buyer needs, starting with the size guide. Avoid hiding the catalogue behind an internal search box or an awkward filter. Related-product links should point at a genuine alternative — same use, different colour, different last — not at whatever a plugin suggests. A technical SEO audit surfaces these structural gaps faster than reading templates one by one.
Write a precise title and a description you can defend
Build the title from the product identity and the attributes that let someone recognise it. One workable pattern, filled in with accurate data, is: Trainers [model] [colour] – [brand]. Add a material or a use case when it is a useful distinction, not when it is another keyword you would like to rank for.
Google's guidance on title links asks for descriptive, concise wording. No universal character limit guarantees a title is shown in full: the result can be truncated or rewritten. The product name on the page and the title used in search should tell the same story.
The meta description summarises what makes this page worth opening: the model, the sizing information, the fact that delivery terms are available. Only include a price, a lead time or a rating if the figure is accurate and maintained. A stale description is worse than a plain one.
Google's documentation on snippets explains that it may use page content instead of your meta description, depending on the query. The description has to stay consistent with what the buyer will find, without invented urgency or an advantage that does not exist.
Answer the questions that decide the purchase
Put the essential facts next to the variant selector and the buy button: name, applicable price, availability, sizes and delivery terms. Everything that needs explaining can come below.
| Section | What to verify |
|---|---|
| Size and fit | Chart specific to the model or range, measuring method, width where it is known |
| Composition | Materials of each part, as supplied by the manufacturer |
| Use | Conditions the shoe suits, documented limits, recommended care |
| Manufacturing | Stages and places you can actually document, without confusing design with assembly |
| Commitments | The exact scope of any label or scheme, the evidence, and which products it covers |
| After the purchase | Delivery, exchange, returns, contact route and the terms that apply |
An adjective such as responsible tells a buyer nothing they can verify about a material or a certification. Do not extend a label held by one range, or one supplier, to the whole catalogue. State the concrete fact, its scope and where it can be checked. That precision beats a run of qualifiers.
Length follows from the information needed. Google's guidance on helpful content sets no word quota. A clear page, supported by a shared size guide and sensible internal links, avoids repeating the same long passage on every model. Across a large catalogue, it helps to settle the content structure once rather than improvising per product.
Show the product with images that do real work
Plan the views a buyer needs to understand shape, detail, sole and colour. A worn shot helps with proportions. Make sure the images match the selected variant, and that you have the right to use every photograph you publish.
Alternative text should describe the useful information in the image — the view and the colour, when those details matter. It is not a place to stack keywords. Decorative images should be marked as such, and swatches and size buttons need an accessible name that describes what they do.
Match dimensions and compression to how the image is displayed, then look at the result. A single weight limit does not suit every use: a detailed zoom and a thumbnail have different needs. The main image visible on load should not be delayed by template-wide lazy loading.
Handle variants without blanket rules
A colour or a size can be selected on a single page or served from its own URL. The right choice depends on your catalogue and what the platform supports. Google describes several configurations in its recommendations on ecommerce URL structure and in its documentation on product variants.
Check that a link to a variant really opens the combination it promises, with the matching image, price and stock. A stable URL makes that check possible. Then set canonical URLs in line with the architecture you chose and the data the shop holds.
Applying noindex to every variant is not a strategy, and neither is creating a standalone page for every combination. Start with a few representative cases: a simple model, one with several colours, a size that is out of stock, a product that has been withdrawn. Watch how they behave before you generalise.
Describe the product to search engines with accurate structured data
Markup helps Google interpret the product and its offers. Product structured data can contribute to eligibility for certain enhanced presentations. Eligible is not the same as shown: markup does not guarantee that a price or a star rating appears.
Generate the markup from the data you maintain in the catalogue — name, image, price, currency and availability. Reviews and their average should only be added when they match genuine reviews shown on the page. A sample snippet containing a placeholder rating must never become a published one.
Check that the page, the markup and any merchant feed agree. Test variants and out-of-stock states too: an extension can produce markup that is technically valid but wrong, because it picks up the wrong price or keeps an old availability value.
Check performance and the mobile journey
Measure several representative product pages, and look at field data from real users where it exists. The Core Web Vitals are LCP, INP and CLS. The quality thresholds are at most 2.5 seconds, 200 milliseconds and 0.1, assessed at the 75th percentile of visits for field assessment. INP replaced FID in that set.
Those thresholds do not let you calculate a universal revenue loss per second. Use them to locate problems, then test the journey yourself: selecting a size, adding to basket, completing the order. Check keyboard access, zoom, error messages and any overlay that hides an action on a small screen. Work on page speed where the measurement points, not where it is easiest.
Basket functions and stock data often need special handling. Check they are still fresh after any change to caching rules: a page that loads quickly but shows yesterday's availability has not been improved.
Measure improvements without confusing the causes
Choose a priority group of product pages based on demand, stock, margin and known problems. Record the starting state and note every change. Organic clicks tell you about access from Google; add-to-basket events, purchases and return requests tell you about later stages.
Compare comparable periods, and document promotions, restocks and price changes as you go. If sales rise during a discount, the effect cannot be credited to a new title. Look at results by model or family rather than an average that mixes available products with sold-out ones. What you will measure, and against what baseline, belongs in the scoping stage rather than after the fact.
Worked this way, the catalogue improves in steps: more precise information, an easier choice, a technical description that matches reality. The next batch of product pages reuses the structure you have validated.
Common questions
Do I need 800 words on a product page to sell shoes?
No. You need the information required to choose: size, composition, use, photographs and purchase terms. A shared size guide can carry part of it. Google publishes no preferred word count, and padding rarely helps anyone decide.
Can the same word appear in the titles of several products?
Yes, if it is the accurate term. What matters is that each title identifies the model and its useful differences. Repeating a category word does not on its own show that your pages compete.
Should every colour variant be kept out of Google?
No. Settle the catalogue architecture, the internal links and the canonical URLs first. Variants can have their own URLs or be selected on one page. Test how a few behave before applying a rule shop-wide.
Does Product markup make star ratings appear automatically?
No. It contributes to eligibility when the data and the rules are respected. Ratings must correspond to genuine reviews of the right product. Google then decides how, or whether, to present the result.
Which metric replaced FID in the Core Web Vitals?
INP, which measures how responsive interactions are, replaced FID. The other two are LCP for the largest content element loading and CLS for visual stability. Complete those measurements with a real test of the purchase journey on a phone.
Can I add a certification to every product description?
Only if its scope genuinely covers the products concerned and you hold evidence you can show. A certification held by a supplier, a material or a single range should not be extended to the whole catalogue.