Product Seo
Opener + Author Info
These tactics work for individual product pages when you have fewer than 500 SKUs. Crawl budget and faceted navigation issues need different treatment when you have 500+ products or dynamic filtering on category pages.
By Niraj Raut | 11 min read
H2–1: Why Most Product Pages Don’t Rank (And How to Fix It)
Thousands of ecommerce sites have thousands of product pages. Only a fraction rank. Here’s why most fail:
Reason #1: Duplicate or Thin Descriptions Most product pages copy the manufacturer’s description word-for-word. Google sees identical text across 50 reseller sites. Your page isn’t unique, so it doesn’t rank. You need a unique, helpful description that adds value beyond the brand’s version.
Reason #2: Generic Title Tags A title tag like “Blue Running Shoes | BrandName” doesn’t rank because thousands of sites use the same title. You need specificity: “ASICS GEL-Kayano 29 Blue Men’s Running Shoes | Lightweight Cushioned | Breathable.”
Reason #3: Missing or Poor Image Alt Text Google can’t “see” images. It reads the alt text. If your alt text says “product-1.jpg” or “shoe,” Google learns nothing. Descriptive alt text like “ASICS GEL-Kayano 29 blue men’s running shoe with mesh upper and gel cushioning” helps ranking and accessibility.
Reason #4: No Product Schema Without Product schema (price, availability, rating), Google treats your page like any other page. With it, you unlock rich snippets: ratings, price, in-stock status, and reviews appear directly in search results. Rich snippets get 25–30% higher click-through rate.
Reason #5: Poor Internal Linking Each product page should link back to its category and to related products. If a product page has zero internal links, it’s orphaned. Google crawls it less frequently, and users can’t discover related products. You’re leaving conversions on the table.
H2–2: Product Title Tag Formula: Write for Humans and Google
Your title tag is the #1 on-page ranking factor for a product page. It’s also the first thing searchers see in search results. Write it for both.
Formula: [Primary Keyword] | [Differentiator] | [Brand/Store Name]
Examples:
| Product | Formula Application | Title Tag | ||||
|---|---|---|---|---|---|---|
| Running shoes | [Shoe type + brand] | [Key feature] | [Store] | “ASICS GEL-Kayano 29 Men’s Running Shoes | Lightweight Cushioned | ShoesPlus” |
| Laptop bag | [Product + material] | [Use case] | [Brand] | “Waterproof Laptop Backpack | 17-inch | TravelGear” |
| Coffee maker | [Type + capacity] | [Feature] | [Brand] | “Programmable Coffee Maker 12-Cup | Auto-Brew Timer | HomeGoods” |
| Phone case | [Compatibility + material] | [Protection] | [Brand] | “iPhone 15 Pro Max Case | Drop-Proof to 10ft | CaseShield” |
Best practices:
- Keep it under 60 characters (Google truncates longer titles).
- Put the primary keyword early (within the first 30 characters).
- Include a differentiator (what makes this product unique).
- Avoid keyword stuffing (one iteration of the keyword is enough).
- Make it readable (use pipes or dashes to separate sections; avoid symbols).
Common mistakes:
- “Blue Running Shoes” (too generic; no brand or differentiator)
- “ASICS GEL-Kayano 29 Blue Lightweight Cushioned Breathable Durable Running Shoes for Men” (too long; truncated in search)
- “ASICS ASICS GEL-Kayano GEL-Kayano Running Shoes” (keyword stuffing; looks spammy)
H2–3: Unique Product Descriptions: Length, Keywords, and Structure
Google favors unique, helpful descriptions. Here’s how to write them.
Length: Aim for 150–250 words per product description. This is long enough to be ranking-competitive but short enough that customers read it before making a purchase decision. Shorter descriptions (50–100 words) rarely rank.
Structure:
Paragraph 1 (30–40 words): Answer “What is this product?” Example: “The ASICS GEL-Kayano 29 is a premium men’s running shoe designed for distance runners who need stability, cushioning, and durability. It combines gel technology with engineered mesh for breathability.”
Paragraph 2 (50–70 words): Why does it matter? Example: “Long-distance running puts stress on your feet and joints. A poorly cushioned shoe leads to injury and discomfort. The GEL-Kayano 29 reduces impact through dual gel cushioning and a reinforced midfoot, letting you run longer without pain.”
Paragraph 3 (50–70 words): Key features and benefits Example: “Features: lightweight engineered mesh upper, dual-layer gel cushioning, reinforced midfoot support, reflective elements for night visibility. Benefits: reduces fatigue, prevents common running injuries (shin splints, plantar fasciitis), improves pace and endurance.”
Paragraph 4 (optional, 30–40 words): Call to action or sizing note Example: “True to size. Recommended for neutral to underpronated runners. Free returns within 30 days if not satisfied.”
Keyword placement: Include your primary keyword (e.g., “ASICS GEL-Kayano 29 men’s running shoes”) once in the first paragraph. Include 2–3 keyword variations naturally throughout (e.g., “lightweight running shoe,” “cushioned men’s shoes”). Don’t force keywords; write for humans first.
H2–4: Image Alt Text: The Overlooked Ranking Factor
Alt text serves two purposes: (1) it helps visually impaired users understand the image via screen readers, and (2) it signals to Google what the image shows, helping your page rank for visual search queries.
Alt text best practices:
Good alt text:
- “ASICS GEL-Kayano 29 blue men’s running shoe, side view showing mesh upper and gel cushioning”
- “Coffee maker 12-cup programmable with auto-brew timer, stainless steel, black display panel”
- “Waterproof laptop backpack 17-inch, black, with multiple compartments and USB port”
Bad alt text:
- “product-1.jpg” (not descriptive)
- “shoe” (too vague)
- “ASICS GEL-Kayano 29 men’s running shoes blue lightweight cushioned breathable durable reflective” (keyword stuffing)
- “” (empty)
Formula for product alt text: [Product name] [color] [material/type] [angle/feature]
Apply to all product images:
- Hero/main product image (side view, full shoe)
- Detail images (sole, upper, heel)
- Lifestyle images (shoe on foot, runner wearing shoe)
- Comparison images (shoe next to competitor model)
H2–5: Product Schema and Rich Snippets: The Technical Edge
Product schema is structured data that tells Google exactly what your product is, how much it costs, if it’s in stock, what customers rate it, and more.
Schema fields to include (minimum):
| Field | Example | Why It Matters |
|---|---|---|
| Name | “ASICS GEL-Kayano 29 Men’s Running Shoes” | Identifies the product |
| Description | Long product description | Provides context |
| Image | URL to product image | Displays in search results |
| Brand | “ASICS” | Shows manufacturer |
| Offer.Price | “150.00” | Shows cost |
| Offer.Availability | “InStock” | Shows if available (affects rich snippets) |
| Offer.PriceCurrency | “USD” | Specifies currency |
| AggregateRating.ratingValue | “4.5” | Shows star rating (4.5 out of 5) |
| AggregateRating.ratingCount | “238” | Shows number of reviews |
| AggregateRating.bestRating | “5” | Sets scale (out of 5) |
| ProductCollection (if variants exist) | Array of color/size variants | Handles variants properly |
Implementation (JSON-LD example):
{
"@context": "https://schema.org",
"@type": "Product",
"name": "ASICS GEL-Kayano 29 Men's Running Shoes",
"description": "Premium men's running shoe with dual-layer gel cushioning and engineered mesh upper...",
"image": "https://example.com/images/asics-kayano-blue-hero.webp",
"brand": {
"@type": "Brand",
"name": "ASICS"
},
"offers": {
"@type": "Offer",
"price": "150.00",
"priceCurrency": "USD",
"availability": "https://schema.org/InStock",
"seller": {
"@type": "Organization",
"name": "Your Store Name"
}
},
"aggregateRating": {
"@type": "AggregateRating",
"ratingValue": "4.5",
"ratingCount": "238",
"bestRating": "5",
"worstRating": "1"
}
}
Validate with Google’s Rich Results Test before publishing. Errors prevent rich snippets from showing.
H2–6: Frequently Asked Questions
Q1: How do I handle product variants (color, size) without creating duplicate content?
A: Use canonical tags to point all variants to a primary version, or use variant schema (color, size as structured data properties). Don’t create separate URL for each combination. Example: /asics-kayano-blue-9.5 and /asics-kayano-blue-10 should share a canonical tag pointing to /asics-kayano-blue. Alternatively, use URL parameters (?color=blue&size=9.5) and parameter handling in Google Search Console to tell Google they’re the same product.
Q2: Should I use the manufacturer’s description or write my own?
A: Write your own, or modify the manufacturer’s. Thousands of retailers copy the exact same description. Google penalizes near-duplicate content. Add value: include sizing advice, care instructions, or customer questions your store hears. Make it unique to your store.
Q3: How often should I update product descriptions?
A: Update when you get new customer questions in your email or reviews. Update if the product gets a new variant or feature. Update every 6–12 months if nothing changes (freshness signals help ranking). Don’t update just for the sake of it; Google’s crawlers will detect thin changes.
Q4: Do I need to include price in the description, or is schema enough?
A: Schema is enough technically, but mentioning price in the description can help with CTR and conversion. If you mention it, keep it in the last paragraph so it doesn’t distract. Don’t mention competitor prices (focuses searcher attention elsewhere).
Q5: How do I optimize product pages for mobile?
A: Title tag and description are identical on mobile. Alt text is read the same way. Focus on: (1) mobile-friendly image size (load fast, high quality), (2) quick specification access (don’t make users scroll 5 paragraphs to see size/color options), (3) fast “add to cart” button (visible above the fold).
Q6: What if my product page competes against marketplace listings (Amazon, eBay)?
A: You can’t outrank marketplace listings on your product name (e.g., “ASICS GEL-Kayano 29”). Instead, rank on use-case and comparison queries: “best running shoes for flat feet,” “ASICS vs New Balance for distance running.” Write content that educates, not content that competes on product listings.
Choose Your Path
Option 1: DIY Product Page Audit You have 100–300 products and 3–5 hours. Use the checklist above. Audit your top 50 products (by traffic), fix title tags and descriptions, and add schema. See ranking improvements in 4–8 weeks.
Option 2: Optimize with a Template You want a repeatable process. Build a title tag template and description structure. Train your product team to follow it. Test on 10 products first. Once you validate improvements, scale to all products.
Option 3: Hire for Bulk Optimization You have 500+ products and limited internal resources. An agency or freelancer can audit, write descriptions, implement schema, and internal linking at scale. Cost: $2,000–$10,000 depending on product count.
Three-Part Close
Individual product pages are your revenue engine. A product that ranks position 1 instead of position 2 can generate 2–3x more organic traffic. Multiply that across 100 products and the cumulative impact is enormous.
The tactics in this guide—unique descriptions, proper schema, good alt text, strong internal linking—are the same tactics every ecommerce site should use. Yet most don’t, because they copy-paste manufacturer descriptions and call it done. That’s your competitive advantage.
Start with your top 20 products by revenue. Optimize their title tags, descriptions, and schema. Test for 4–8 weeks. Once you see ranking improvements, scale the process to your next 100 products.
Need help auditing your product pages or training your team on the process? Reach out to Niraj Raut at nirajraut.com.np. He works with ecommerce teams weekly to scale product page optimization across hundreds of SKUs.