Online Store Product Card Optimization
TL;DR Why are product pages worth optimizing? Many stores focus on the home page and categories and leave product pages to the template. That costs them long-tail traffic: searches for a specific model, colour, size or material. Someone who lands on exactly the product they searched for is much more likely to buy. Product pages […]
TL;DR
- Product pages win long-tail searches for specific models, colours and sizes, and those visitors are close to buying.
- Give every product a unique name (H1), title tag and description written from real attributes and buyer questions, not the manufacturer’s copy.
- Add Product structured data with price, availability, ratings, shipping and returns, and keep Merchant Center data consistent with the page.
- Group variants (colour, size) properly, keep out-of-stock pages live, and redirect discontinued ones to the closest replacement.
- Make sure every product is linked from a category and has fast, well-described images.
Why are product pages worth optimizing?
Many stores focus on the home page and categories and leave product pages to the template. That costs them long-tail traffic: searches for a specific model, colour, size or material. Someone who lands on exactly the product they searched for is much more likely to buy. Product pages also feed Google Shopping, image search and AI shopping answers, which pull prices, availability and attributes straight from the page and your product feed.
The common problem is copy imported from the manufacturer or wholesaler: the same text appears in hundreds of stores. Google won’t penalise you for it, but it picks one version to show (Google), and it has no reason to pick yours. Unique details, photos, reviews and answers are what make your page the one worth showing.
Make your brand visible – from Google to AI chatbots.
What should a product page checklist include?
| Element | Best practice | Common mistake |
|---|---|---|
| URL | Short, readable, words separated by hyphens; stable when the product changes category | IDs and parameters only (?p=384729), underscores |
| Product name (H1) | Type + key attributes: brand, model, colour, material | Ten products all called “Women’s pumps” |
| Title tag | Product name first, then brand or store | Same title as the category, or keyword lists |
| Meta description | Benefit + offer (delivery, returns), unique per product | Empty or copied from the manufacturer |
| Description | Answers buyer questions: fit, use, care, compatibility | Manufacturer copy, one block of text |
| Attributes | Structured table: size, material, dimensions, GTIN | Attributes hidden in images or only in JS tabs |
| Images | Several unique photos, descriptive alt and file names, WebP/AVIF | One supplier photo, lazy-loaded main image |
| Reviews | Reviews and Q&A on the page, in HTML | Reviews only in a third-party widget loaded by JS |
| Structured data | Product + Offer with price, availability, shipping, returns | Price in markup different from the page |
| Variants | ProductGroup with variants; one indexable URL per variant or one page with all | Duplicate pages per size with no canonical |
| Internal links | Category, breadcrumbs, related products | Orphaned products with no links |
| Availability | Out of stock: keep page live; discontinued: 301 to closest product | 404 for temporarily unavailable products |
How should you build product URLs?
Keep URLs short, readable and stable. Use words separated by hyphens rather than underscores, and avoid long chains of IDs and parameters (Google). Leaving the category out of product URLs means the address doesn’t change when the product moves to another category, so you avoid redirects.
| Example | |
|---|---|
| Not user-friendly | example.com/?p=384729_kjwbx_%_192_html |
| Better | example.com/red-leather-ankle-boots-rb-2041 |
How do you write unique product names and titles?
When many products share the same type, their names often end up identical. Build each name from the attributes shoppers search for: type, colour, material, heel height, brand or model. This makes names unique and matches long-tail searches. Mark the product name as the page’s H1. Check for duplicate titles regularly with a crawler (technical SEO tools) or a PIM export.
| Generic name | Optimized name | Keyword | Monthly searches (US, Mangools, 12-month average, Nov 2026) |
|---|---|---|---|
| Women’s boots | Women’s High Heel Leather Boots | women’s high heel boots | 3,000 |
| Women’s boots | Red Women’s Ankle Boots with Block Heel | red ankle boots women | 830 |
| Women’s boots | Women’s Suede Chelsea Boots, Black | black chelsea boots women | 4,900 |
In the title tag, put the product name first, then the brand or store name. Google often rewrites titles and descriptions that don’t describe the page well (Google). Use the meta description to give a reason to click (free delivery, returns, a real promotion); it affects clicks, not rankings.

What should a product description include?
Write descriptions for your key products first if the catalogue is large: bestsellers, seasonal products and those with the highest margin. Then work through the rest by template. A good description:
- repeats the product name naturally and covers related searches (colour, material, style, occasion, brand);
- answers the questions buyers ask: fit and sizing, how it feels, what it goes with, how to care for it;
- is split into short blocks with H2 or H3 subheadings, such as “Fit and sizing” or “Materials and care”;
- puts specifications in a table, not in a paragraph;
- is in the HTML of the page, not loaded only after a click on a JavaScript tab.
There is no ideal length; write as much as the product needs (Google). AI shopping assistants read the same descriptions and compare products by their attributes, so be specific. More on writing for them: product descriptions ready for AI search.
Which structured data does a product page need?
Product structured data makes the page eligible for product rich results (price, availability, ratings) and Merchant listings in Shopping (Google, Google). Include shipping and return policy, and GTIN where you have it. For products sold in several colours or sizes, use ProductGroup with variants (Google). Keep the data identical to what’s visible on the page and to your Merchant Center feed (Google). More types worth using: structured data for SEO.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Product",
"name": "Red Leather Ankle Boots with Block Heel",
"sku": "RB-2041-38",
"gtin13": "5901234123457",
"brand": { "@type": "Brand", "name": "Your Store" },
"image": ["https://example.com/img/red-leather-ankle-boots-1.webp"],
"description": "Red leather ankle boots with a 5 cm block heel and side zip.",
"color": "Red",
"material": "Leather",
"aggregateRating": { "@type": "AggregateRating", "ratingValue": "4.6", "reviewCount": "87" },
"offers": {
"@type": "Offer",
"url": "https://example.com/red-leather-ankle-boots-rb-2041",
"price": "349.00",
"priceCurrency": "PLN",
"availability": "https://schema.org/InStock",
"itemCondition": "https://schema.org/NewCondition",
"shippingDetails": { "@type": "OfferShippingDetails",
"shippingRate": { "@type": "MonetaryAmount", "value": "0", "currency": "PLN" },
"shippingDestination": { "@type": "DefinedRegion", "addressCountry": "PL" } },
"hasMerchantReturnPolicy": { "@type": "MerchantReturnPolicy",
"applicableCountry": "PL",
"returnPolicyCategory": "https://schema.org/MerchantReturnFiniteReturnWindow",
"merchantReturnDays": 30 }
}
}
</script>
Test the markup in the Rich Results Test and monitor the Product snippets and Merchant listings reports in Search Console. Google doesn’t guarantee rich results even when the markup is valid.
Let your customers find you, wherever they look.
Why do reviews matter on product pages?
Reviews add fresh, unique content in the words customers use, help others decide, and can show as star ratings in results. Make sure reviews are in the page’s HTML, not only in a widget loaded later, and reply to questions. Ask for reviews after delivery, and never write or filter them yourself.
How do you optimize product images?
- Alt text for every photo, describing what it shows: “red leather ankle boots with block heel, side view”.
- Descriptive file names with hyphens, numbered for multiple photos: red-leather-ankle-boots-1.webp, red-leather-ankle-boots-2.webp.
- Unique photos (on a model, details, in use) instead of only the supplier’s packshots; add video or 360° views for key products.
- Speed: modern formats (WebP, AVIF), correct sizes, and don’t lazy-load the main image, which is usually the page’s LCP element (web.dev).
Google treats the file name as a light hint; alt text, the surrounding content and image quality matter more (Google).
How should product pages be linked internally?
Every product needs at least one link from a category. Products left without a category become orphaned pages that crawlers struggle to find. Crawl the store regularly, compare the list with your product feed or sitemap and fix orphans (indexing problems). Add related-product modules (“Customers also bought”, “More from this category”) as plain HTML links so they help crawlers too.
Use breadcrumbs with BreadcrumbList structured data. Since January 2025 Google no longer shows breadcrumbs in mobile results, only on desktop (Google), but they still help users and crawlers understand the site structure.

What should you do with out-of-stock and discontinued products?
| Situation | What to do | Why |
|---|---|---|
| Temporarily out of stock | Keep the page live, mark availability as OutOfStock, show the restock date and alternatives | Keeps rankings and links; avoids soft 404s |
| Discontinued, close replacement | 301 redirect to the replacement or its category | Passes signals to a relevant page |
| Discontinued, no replacement | Keep with alternatives if it still gets traffic and links; otherwise 404 or 410 | Avoids redirects to irrelevant pages |
| Seasonal product returning next year | Keep the same URL and update it | Builds history over seasons |
FAQ
Can I use the manufacturer’s product descriptions?
You can, and you won’t be penalised, but many other stores have the same text. Rewrite descriptions for your key products and add unique details, photos and reviews.
How long should a product description be?
As long as the product needs. Simple products can have a short description with a specification table; technical or expensive ones need more detail.
Should product URLs include the category?
It’s better not to. Without the category, the URL doesn’t change when the product moves, so you don’t need redirects.
Should each colour or size have its own URL?
Give a variant its own URL only if people search for it separately (often colour, rarely size). Group variants with ProductGroup structured data and use canonical tags where pages duplicate each other.
Do product rich results improve rankings?
No. They can make your result more visible and clickable, but they don’t change positions.
Sources
- Google Search Central: Ecommerce SEO
- Google Search Central: URL structure best practices
- Google Search Central: Consolidate duplicate URLs
- Google Search Central: Title links and Snippets
- Google Search Central: Product snippet, Merchant listing and Product variants structured data
- Google Search Central: Image SEO best practices
- Google Search Central Blog: Simplifying the visible URL element on mobile search results
- web.dev: The performance effects of too much lazy loading
- Google Merchant Center: Product data specification
About the author: This article was prepared by the Insightland SEO and GEO team. Insightland is a Wrocław-based agency, part of the Hexe Capital Tech Hub, that connects business, tech and data: SEO and GEO, performance marketing, UX and analytics, and SEO and AI training. Contact us.