Most Indian D2C stores I look at have forty blog posts and eleven collection pages. The blog has a writer, a calendar and a monthly review call. The collection pages have whatever the theme shipped with, plus a filter menu nobody has touched since launch.
That ratio is backwards. It is the most expensive habit in Indian e-commerce SEO, and it is expensive precisely because it feels productive.
This guide ranks store page types by how much revenue they actually carry, and says plainly which ones deserve developer hours and which ones do not.
Is e-commerce SEO worth the engineering time, or is it theory that will not move sales?
It is worth the engineering time for roughly three page types, and it is theory for most of the rest.
That is the honest version of the answer. E-commerce SEO has a concentrated return, not a spread one. A store doing a few hundred to a few thousand orders a month does not need a sitewide overhaul. It needs its collection templates, its faceted URL handling and its product markup fixed — and then it needs to stop.
The reason the doubt exists at all is that most SEO proposals bundle those three things with twenty low-value items, so the whole package looks like a six-month engineering commitment for an uncertain outcome. Priced as a bundle, the scepticism is correct. Priced as three fixes, it is usually the cheapest demand channel a D2C brand has, because the traffic it captures is already in buying mode.
The test I would apply before approving any sprint: does this change affect a page a shopper can buy from, or reach a buyable page in one click? If no, it goes to the bottom of the list, whatever the tool says.
Why do Indian D2C stores over-invest in blogs and starve collection pages?
A blog post is a decision one person can make on a Tuesday. It goes live the same week. It produces a URL, a word count and a line in a report. Nothing about the theme changes, no staging environment is involved, and nobody has to test a checkout after it ships.
A collection page is the opposite. Changing how filters generate URLs, how many products render before pagination kicks in, or how the intro copy sits in the template means touching the theme. That means a developer, a staging build and a release window. So it waits.
The budget follows the path of least resistance rather than the path of most revenue. Over a year, that produces a store with strong coverage of “how to style a kurta” and no coverage of “cotton kurta set for women” — which is the query with a card in someone’s hand behind it.
Google’s own documentation is unusually direct about why this matters. In its guidance on ecommerce site structure, it states that “if category pages don’t include direct links to all products in a category, Googlebot might not find all of your products by crawling alone.” Collection pages are not a nice-to-have layer on top of the catalogue. They are the crawl path to the catalogue.
Which page types actually carry revenue?
Here is the ranking I work from. It is ordered by revenue contribution per unit of effort, which is a different ordering from traffic volume — and that difference is the whole point.
| Page type | What the shopper is doing when they land | Why it does or does not make money | What building it properly costs you | Build order |
|---|---|---|---|---|
| Collection / category pages | Comparing options inside a category they have already chosen | Highest intent that still has choice left in it; one page can carry an entire product line | Developer time on the template, plus a copywriter for the intro block | 1 |
| Filtered sub-collections (colour, size, price band, occasion) | Narrowing to a specific want: “black cotton kurta under ₹1500” | Captures long-tail commercial queries no single product page can rank for | Developer time on URL rules and index/noindex logic — the hardest item on this list | 2 |
| Product detail pages (PDPs) | Deciding on one specific item | Converts best of any page type, but each one ranks for a narrow query set | Structured data, unique descriptions, real images; scales with catalogue size | 3 |
| Buying guides and comparison pages | Choosing between options before they trust a brand | The only blog format that reliably earns revenue, because it links directly to collections and PDPs | Writer time plus honest product knowledge; no developer needed | 4 |
| Brand, offer and “buy online” pages | Looking for you specifically, or for a live offer | Cheap to make, converts well, but demand is capped by how many people already know you | An afternoon each | 5 |
| Trust pages (size guide, shipping, returns, care) | Removing the last objection before checkout | Rarely ranks, frequently decides the sale; also feeds AI answers about your policies | A day of writing, once | 6 |
| Top-of-funnel blog posts | Reading, not buying | Generates sessions and almost no orders; useful mainly as internal links into commercial pages | Ongoing writer cost, forever | 7 |
Read the table as a sequence, not a menu. Rows 1 to 3 are where engineering time goes. Rows 4 to 6 are where writing time goes. Row 7 is where most Indian D2C content budgets currently sit.
What does a collection page need before it earns anything?
Every product reachable by a crawler. Not by a “Load more” button. Google is explicit that its crawlers “don’t ‘click’ buttons and generally don’t trigger JavaScript functions that require user actions.” If your collection loads products on scroll or on click, paginate with real <a href> links behind it, and give each page in the sequence its own URL. Google’s pagination guidance also warns against using URL fragments after a # for page numbers.
A URL rule for filters that you decided on purpose. Google’s ecommerce URL guidance asks you to “minimize the number of alternative URLs that return the same content” and to use ?key=value parameters rather than bare values. The practical decision is which filtered views you want indexed. Colour and category combinations that people actually search for — yes. Sort order, page-size and session parameters — never.
Copy that answers the buying question, not the SEO brief. A collection page intro should tell a shopper what is in this collection, what the range covers, and how to choose. Two hundred useful words above the grid beats eight hundred words hidden below the fold, and it is the text an AI answer engine can lift cleanly when someone asks what to look for in this category.
Internal links from the pages that already have authority. Your homepage, your buying guides, your best-performing posts. Google notes that “the more links a page has to it within a site, the higher the relative importance of the page to other pages on your site.” Most stores point all their internal links at blog posts. Point them at collections instead.
This is also the point where content work and commercial pages stop being separate projects. If you are planning a calendar, plan it as content that feeds your collection and product pages rather than as a standalone blog.
Do product pages still matter once collections rank?
Product pages are no longer just ranking assets. They are the data source for Google’s shopping surfaces. Google’s structured data documentation splits product markup into two classes: merchant listings, for “pages where customers can purchase products from you,” and product snippets, for “product pages where people can’t directly purchase the product.” Adding the merchant listing properties makes a page eligible for both.
For an Indian D2C store, this is the highest-leverage markup work available, and it is genuinely engineering work — price, availability, shipping and return details have to come from live data, not a hardcoded block. Get it wrong and the markup is worse than absent, because it is wrong in public.
Two practical notes. First, variants: if you sell one shirt in six colours, decide whether those are separate URLs or one URL with parameters, and mark them up consistently. Second, descriptions: a manufacturer description copied across your site, three marketplaces and two resellers gives Google no reason to prefer your version.
Where do blogs actually earn their place?
A buying guide that genuinely helps someone choose — fabric weights for Indian summers, how sizing runs across brands, what to check before buying a mattress online — earns its place three ways. It ranks for research queries. It passes internal link equity to the collections it references. And it gives an AI answer engine something quotable that names your brand.
A post written to hit a keyword volume target does none of that. It sits in the index, adds a line to the monthly report, and sends its traffic straight back out.
The filter is simple: if a post cannot link naturally to a collection or product page, it probably should not exist on a store’s domain. If you want the full picture of how this sits alongside technical and local work, my services for e-commerce and D2C brands lay out the sequence.
What should the first 90 days of engineering time go to?
Month one: fix crawl access to the catalogue. Audit whether every product is reachable through collection links, replace JavaScript-only loading with paginated <a href> links, and submit a clean product sitemap or Merchant Center feed as a backstop.
Month two: decide the filter URL policy and implement it. Which filtered views get indexed, which get parameters excluded, which get canonicalised. This is the item most stores skip, and it is the one that separates a store with twelve ranking pages from one with two hundred.
Month three: product markup and collection copy. Merchant listing properties on every PDP, driven by live data, and a written intro on every collection that a shopper would actually read.
How do you know it is working before revenue moves?
Watch leading indicators against your own baseline, not against a published benchmark.
The useful ones sit in Search Console: how many collection URLs are indexed versus submitted, whether the Merchant listings report shows valid items and how that count moves after markup ships, and whether impressions on category-level queries are rising even before clicks do. In analytics, segment landing pages by template — collection, product, blog — and look at revenue per session for each.
That last number usually settles the argument on its own. When a store sees what a collection session is worth against what a blog session is worth, the budget conversation stops being theoretical.
I would avoid industry-average uplift figures entirely. Conversion rates and traffic mixes vary so much across Indian D2C categories that a published average tells you nothing about your store, and any agency quoting one as a forecast is selling, not measuring.
Want Better eCommerce SEO in India?
Optimize key pages, improve search visibility, and attract more potential customers.
Contact us today. No obligation. Contact us today.Frequently asked questions
Should I stop blogging completely?
No. Shift the mix. Buying guides and comparison pieces that link into collections stay. Keyword-volume posts that link nowhere commercial can stop, and the freed budget moves to collection copy and product descriptions.
How many collection pages should a store have?
As many as there are distinct things people search for and you actually stock. A store with 300 SKUs might justify 25 to 40 collection and sub-collection pages. Creating collections for combinations you cannot fill leaves shoppers on an empty grid, which is worse than not ranking.
Do I need a developer, or can my Shopify or WooCommerce theme handle this?
Themes handle the basics — collection templates and pagination usually exist out of the box. Filter URL rules, index control on faceted views and live-data product markup need a developer in almost every case.
Is this different for a marketplace-first brand selling mainly on Amazon or Flipkart?
The page types rank the same way, but the economics change. If most of your volume is on marketplaces, your own site’s collection pages compete with your own marketplace listings. Decide which one you want ranking for your brand plus category terms before investing in both.
How long before collection page work shows up in sales?
Long enough that you should measure indexation and impressions first. Crawling and reindexing a changed template is not instant, and seasonal demand swings in Indian categories can mask the effect for a full cycle.
If you want this sequenced against your own catalogue rather than a generic list, my SEO services for e-commerce brands start with exactly this audit: which page types you have, which ones carry revenue, and what the first ninety days of developer time should buy.
