Ecommerce product page SEO in 2026 is no longer one job. A product detail page (PDP) now has to earn visibility on three separate surfaces: classic organic results, merchant and Shopping listings, and AI-generated answers, and each one reads your page differently. The brands winning right now are the ones that stopped treating the PDP as a single asset and started treating it as a hub with supporting content around it.
Key Takeaways
- A PDP competes on three surfaces simultaneously: organic blue links, Shopping/merchant listings, and AI Overviews. Each rewards different signals.
- Organic wants crawlable unique copy and internal links. Shopping wants clean, complete structured product data. AI Overviews want factual, extractable, attribute-level answers.
- Supporting content, size guides, care instructions, shipping and return policy pages, FAQ pages, accounts for a large share of what AI systems actually cite. The PDP alone rarely wins the citation.
- For Indian D2C, COD availability and return policy are trust surfaces, not footer links. Surface them as structured, crawlable content.
- Rupee pricing, GST-inclusive display and delivery timelines belong in your structured data, not just in your theme's HTML.
- Schema earns rich-result eligibility and better click-through. It is not a direct ranking factor. Treat it as a presentation lever.
- The marketplace-vs-own-site tension is a real strategic fork for Indian brands, and it changes which surface you should prioritise.
One page, three audiences: the crawler, the merchant feed, and the answer engine.
Why "Product Page SEO" Stopped Being One Thing
For most of the last decade, PDP optimisation meant one checklist: unique title, unique description, decent images, some reviews, Product schema. You optimised for one result type and hoped.
That model broke for two reasons. First, Google's Shopping surfaces became a parallel ranking system driven largely by feed and structured data quality rather than page content. Second, AI-generated answers started intercepting exactly the queries that used to send high-intent traffic to PDPs: "is X good for Y", "X vs Y", "best X under ₹3,000".
AI Overviews now appear on roughly 14% of shopping-intent queries and that share is rising sharply. That is not a fringe number when your entire acquisition model depends on non-brand product discovery.
The Practitioner's Reframe
Stop asking "how do I rank this page?" Start asking "which of the three surfaces can this SKU realistically win, and what does that surface need?"
A ₹499 phone case is not going to win an AI Overview citation. A ₹14,000 mechanical keyboard with a genuine specification comparison absolutely can.
Surface One: Organic Search
Organic still pays the bills for most Indian D2C brands, particularly on long-tail SKU and category-modifier queries.
What Actually Moves Organic PDP Rankings
- Genuinely unique on-page copy. Manufacturer-supplied descriptions used verbatim across fifty retailers give you nothing. Write 150-300 words that only your brand could have written: how it fits, who it's wrong for, what changed in this version.
- Internal linking depth. PDPs that sit four clicks from the homepage with no contextual inbound links from blog or category content underperform. Link from guides into PDPs with descriptive anchors.
- Indexation hygiene. Faceted navigation on Indian Shopify and WooCommerce stores routinely generates thousands of crawlable colour/size permutations. Canonicalise properly and keep parameter URLs out of the index.
- Core Web Vitals. LCP under 2.5 seconds, INP under 200 milliseconds, CLS under 0.1: all measured at the 75th percentile of real users. On Indian mobile networks the LCP threshold is the one that bites, and hero-image weight is almost always the culprit. Google's own guidance on Core Web Vitals is the reference to work from.
The Thin-PDP Trap
If your catalogue has 4,000 SKUs and 3,800 of them have two lines of copy, you do not have a 4,000-page site. You have a 200-page site with 3,800 liabilities. Prune, consolidate variants onto parent pages, or noindex the tail. I have seen category-level ranking improve simply by removing thin variant pages from the index.
Surface Two: Merchant and Shopping Listings
Shopping listings are a data problem, not a copywriting problem. The feed is the product.
Feed Quality Beats Page Quality Here
The signals that matter: complete GTIN/MPN where applicable, accurate availability, accurate price including currency, shipping and return_policy attributes, and high-resolution images on clean backgrounds. Missing or stale availability is the single most common reason Indian merchants get suppressed.
Rupee Pricing and GST in Structured Data
This is where Indian stores consistently get it wrong. Your theme displays "₹2,499 (incl. GST)" but your Product schema emits "price": "2499" with no priceCurrency, or emits an ex-GST figure that mismatches the visible price. Price mismatch between structured data and rendered page is a hard disqualifier for rich results.
Get these right:
priceCurrency: "INR"always, explicitly.- The
pricevalue must match the price a user actually sees and pays. If you display GST-inclusive, emit GST-inclusive. - Use
priceValidUntilon time-bound offers so you don't get flagged as stale. - Emit
availabilityaccurately,InStock,OutOfStock,PreOrder, and keep it synced with real inventory.
The Schema.org Product vocabulary and Google's product structured data documentation are the two sources worth reading end to end. Everything else is commentary.
Schema Is a Presentation Lever, Not a Ranking Lever
Say it plainly, because agencies keep selling it wrong: marking up your PDP does not make Google rank it higher. It makes it eligible for richer presentation, star ratings, price, availability in the result snippet, which lifts click-through rate. That lift is real and worth chasing. The direct ranking boost is not.
Surface Three: AI Overviews and Answer Engines
This is the surface most Indian brands are ignoring, and it's the one changing fastest.
The citation rarely comes from the PDP. It comes from the page that answers the question around the product.
The Supporting-Content Insight
Here is the finding that reorganised how I approach ecommerce content: when you look at what AI systems actually cite for product-intent queries, a large share of cited URLs are not product pages at all. They are size guides, materials and care pages, comparison articles, shipping and returns policies, and FAQ hubs.
That makes sense mechanically. An answer engine responding to "will this jacket work for Bangalore winters" needs prose that discusses temperature ranges and fabric weight. Your PDP says "premium fleece, unisex fit." Your fabric guide says the thing that gets cited.
What to Build Around Every Significant PDP
- A size and fit guide with actual measurements in cm and a "runs small/true/large" statement.
- A materials and care page written as prose, not a spec table alone.
- A shipping and delivery page with real timelines by region, metro vs Tier-2 vs Tier-3.
- A returns and refunds page in plain language with the actual window, the actual process, and who pays return shipping.
- A comparison page for any SKU where buyers genuinely cross-shop.
Link all of these bidirectionally with the PDP. That cluster is your AI visibility asset.
Write for Extraction
Answer engines extract statements, not vibes. "Machine washable at 30°C; do not tumble dry" is extractable. "Easy care for the modern wardrobe" is not. Lead paragraphs and section openers should state the fact before the flourish.
The India Wedge: COD and Returns as Trust Surfaces
Every article on this topic is written for a US buyer with a credit card and a two-day Prime expectation. Indian purchase behaviour is different, and it changes what your PDP needs to say.
Cash on Delivery Is a Ranking-Adjacent Signal
COD availability is one of the highest-weight conversion factors for first-time buyers from Tier-2 and Tier-3 cities. It is also increasingly something buyers ask about, including to AI assistants. "Does [brand] offer cash on delivery" is a real query with real volume.
Put COD availability on the PDP as crawlable text (not just a badge image), and give it a dedicated policy page. Same for pincode-level serviceability if you can express it in prose ranges.
Return Policy as Content, Not Legalese
A returns page written by a lawyer converts nobody and gets cited by nothing. Write it as a customer would ask it: "Can I return this if it doesn't fit?" "How many days do I have?" "Do I pay for return pickup?" Then answer in one sentence each, with the FAQPage markup on top.
This is the single highest-ROI content asset most Indian D2C brands have never bothered to write properly.
The D2C vs Marketplace Tension
Most Indian D2C brands sell on their own site and on Amazon, Flipkart and Meesho. That creates a real conflict: the marketplace listing often outranks your own PDP for your own product name, because the marketplace has domain authority you will never match.
You have three honest options:
- Concede the SKU query, own the category and problem queries. Let Amazon rank for "brand X model Y"; you rank for "best Y for Z use case" and capture the buyer earlier.
- Differentiate the own-site offer, bundles, colours, warranty terms that don't exist on the marketplace, so the own-site PDP is a genuinely different product page.
- Compete head-on with content depth the marketplace listing structurally cannot have: video, guides, real reviews with photos, comparison tools.
Option 1 is right for most brands under ₹10 crore revenue. Option 3 is where I'd spend budget above that.
The Priority Matrix: Effort vs Impact Across Three Surfaces
This is the working document. Score each tactic on effort, then on impact per surface (High / Medium / Low / None). Do the high-impact-low-effort row first, always.
| Tactic | Effort | Organic | Shopping | AI Overviews | Do it when |
|---|---|---|---|---|---|
| Unique 200-word PDP copy | Medium | High | Low | Medium | Always, top 20% of SKUs first |
| Complete Product schema with INR + GST-accurate price | Low | Low | High | Medium | Immediately, sitewide |
| Fix availability sync in feed | Low | None | High | Low | Immediately |
| Size/fit guide per category | Medium | Medium | None | High | Before scaling ad spend |
| Returns + COD policy pages with FAQ markup | Low | Medium | Low | High | Immediately, highest ROI |
| Review collection with photos | High | Medium | High | Medium | Ongoing, always on |
| LCP optimisation on PDP template | Medium | High | Low | None | If mobile LCP > 2.5s |
| Comparison pages for cross-shopped SKUs | High | High | None | High | Top 10 SKUs only |
| Faceted-nav indexation cleanup | Medium | High | None | None | If index bloat > 3x SKU count |
| Video on PDP | High | Low | Medium | Low | After the above |
| Pruning thin variant pages | Low | High | None | None | If catalogue > 1,000 SKUs |
| Structured shipping timelines by region | Low | Low | Medium | High | Immediately |
Read the pattern: the cheapest wins, schema accuracy, policy pages, availability sync, regional shipping data, disproportionately serve Shopping and AI surfaces. Most Indian teams spend their effort on the expensive organic-only column instead.
Measuring All Three Surfaces
You cannot manage what you don't separate.
Organic
Search Console, filtered to PDP URL patterns. Track impressions and clicks separately, impression growth with flat clicks usually means you gained visibility on queries you don't deserve.
Shopping
Merchant Center diagnostics for disapprovals and warnings. Track the suppressed item count as a health metric, not just approved items.
AI Overviews
This is genuinely harder. Practical approach: build a tracked list of 30-50 buying-intent questions in your category, check them manually or with a rank tracker that captures AI Overview presence, and record whether you're cited and which URL got cited. Do it monthly. You are looking for direction, not precision.
For ongoing coverage of how these surfaces evolve, Search Engine Land and Search Engine Journal remain the two publications worth actually reading.
Three surfaces, three measurement systems. Reporting them as one number hides everything useful.
A 90-Day Sequence That Works
Days 1-30: Fix the data layer. Audit Product schema across templates. Correct INR currency, GST-inclusive price parity, availability sync. Clean up faceted indexation. Write the returns, COD and shipping policy pages with FAQ markup.
Days 31-60: Build the supporting cluster. Size guides, materials pages, and comparison pages for your top 10 revenue SKUs. Interlink with the PDPs.
Days 61-90, Deepen the PDPs. Rewrite copy for the top 20% of SKUs. Fix LCP on the PDP template. Start systematic review collection with photo prompts.
Then measure, and repeat with the next tier of SKUs. The mistake is trying to do all 4,000 pages at once. Nobody has ever finished that project.
Frequently Asked Questions
Does adding Product schema improve my rankings?
No, not directly. Schema makes your page eligible for rich results, price, availability, star ratings in the snippet, which typically improves click-through rate. That is a real and worthwhile gain, but it is a presentation and CTR lever, not a ranking factor.
Should I show GST-inclusive or GST-exclusive prices in structured data?
Whatever the customer actually sees and pays on the page. The rule that matters is parity: the price in your structured data must match the rendered price. Mismatches get rich results suppressed.
How many words should a product description be?
There is no threshold. The test is whether the copy contains information that exists nowhere else: fit notes, use-case guidance, honest limitations. 150 unique words beats 600 words of manufacturer boilerplate every time.
Why is my Amazon listing outranking my own product page?
Marketplace domains carry authority your store cannot match on brand-plus-model queries. Rather than fighting that directly, target the earlier-funnel category and use-case queries where content depth wins, and differentiate your own-site offer so the pages aren't competing for identical intent.
Do AI Overviews send meaningful traffic?
Less traffic than a blue link, but the click that does come through is high-intent. More importantly, being the cited source shapes the buyer's shortlist before they ever click anything. Treat it as brand positioning with a traffic side-effect.
What supporting content matters most for AI visibility?
Returns and shipping policies, size and fit guides, and honest comparison content. These get cited far more often than PDPs because they contain the prose-level factual detail answer engines need to extract.
Is COD worth mentioning on the product page for SEO?
Yes: as crawlable text, not a badge image. COD availability is a genuine query intent in India and a strong trust signal for first-time buyers outside metros. A dedicated policy page compounds the benefit.
How do I stop faceted navigation from bloating my index?
Canonicalise filtered URLs to the parent category, block parameter combinations in robots.txt where crawl budget is a concern, and only allow indexation for facet combinations with genuine standalone search demand: usually colour and a handful of size or material facets, nothing more.
Should a small Indian D2C brand invest in Shopping feed optimisation or organic content first?
Feed and schema accuracy, because it's low effort with high Shopping impact and it's a prerequisite for everything else. Content investment only pays once the data layer is clean.
How often should I re-audit product page SEO?
Structured data and feed health monthly: these break silently when themes or apps update. Content depth quarterly, working through SKUs by revenue contribution.
If you're running an Indian D2C or edtech brand and your product pages are stuck on one surface while the other two go unclaimed, that's usually a sequencing problem rather than an effort problem. I write about organic growth for Indian brands at younusfardeen.com: have a look, and get in touch if you want a second pair of eyes on your setup.