Should you really create a page for each product variant or focus on consolidated pages?

Why is Google bringing up this topic now?

E-commerce sites often create hundreds of product pages for nearly identical variants — colors, sizes, slightly different formats. This approach might seem logical to cover all possible queries, but it generates duplicate or nearly duplicate content on a large scale.

The problem — Google has to crawl, index, and evaluate all these pages despite the little differentiated value they bring. The result: dilution of internal PageRank, cannibalization of rankings, and wasted crawl budget on secondary URLs instead of focusing on strategic pages.

What does 'balancing specificity and resource conservation' mean?

Mueller points out a classic dilemma. On one hand, creating a page for each variant allows you to capture ultra-specific long-tail queries (“blue running shoe size 42 women”). On the other hand, multiplying pages fragments SEO signals — backlinks, anchors, user engagement — and complicates site hierarchy.

The balancing act must be done on a case-by-case basis. If a variant generates significant search volume or a distinct buying journey, it likely deserves its own page. Otherwise, consolidating multiple variants onto a pivot page with dynamic filters or selectable options is often more cost-effective.

How do you assess if a product 'deserves' its own page?

The first question: is there a measurable search volume for that specific variant? If no one is searching for “red short-sleeve V-neck organic cotton t-shirt,” creating a dedicated page is pointless. Second criterion: can the content be substantially differentiated? If the only variable is color or size, the descriptive text will inevitably be duplicated.

The third point — user behavior. If visitors convert better on granular product pages because they find exactly what they are looking for without filters, then the UX justifies having multiple pages. But beware: poor UX (labyrinthine navigation, orphan pages) negates this benefit.

• Search volume: check in Google Search Console or a keyword tool if the variant generates impressions.
• Content differentiation: can we write 300 unique and relevant words for this variant?
• Search intent: does the query require a specific answer or is a catalog page with filters sufficient?
• Conversion and engagement: analyze GA4/CRO metrics to see if granular pages outperform grouped pages.
• Crawl budget: sites with more than 10,000 URLs must prioritize — Google will not crawl everything daily.

Is this recommendation consistent with what's observed in the field?

Yes — but with important sector nuances. Large e-commerce sites that have consolidated their product pages (Amazon, Zalando) heavily utilize dynamic filters and canonical URLs to prevent an explosion of indexable pages. Their internal PageRank focuses on robust parent pages that rank for generic and mid-tail queries.

In contrast, niche sites (luxury watches, auto spare parts) maintain ultra-specific pages because their audiences seek exact references and each variant has a unique data sheet. In these cases, granularity is an asset — provided that each page has original content and a good reason to be indexed.

What nuances need to be added to this statement?

Mueller remains deliberately vague on quantitative thresholds. How many product pages is 'too many'? No number. From what monthly search volume does a variant justify its page? [To be verified] — Google does not provide a clear metric.

Another ambiguity: the notion of 'resource conservation'. Are we only talking about crawl budget, or also editorial capacity (writing unique content for 5,000 variants is unrealistic for 90% of sites)? And what to do when variants are generated automatically by a PIM or ERP? Does Google expect us to massively deindex, canonicalize, or block in robots.txt?

Finally, this recommendation ignores a common case: product pages created for legal or regulatory reasons (labeling, traceability, product GDPR compliance). Even if they have no SEO volume, they must exist — and there, the SEO/compliance balancing act becomes complex.

In what cases does this rule not apply?

Marketplaces and aggregators are a blatant counter-example. A site like Cdiscount or Fnac.com lists thousands of merchants selling the same product with minor variations (new/used condition, different seller). Creating a page for each offer would be absurd — but the opposite (a single generic product page) would kill price comparison and UX.

Another exception: sites whose model relies on SEO long-tail (comparators, affiliate blogs). Their strategy is precisely to multiply pages to cover as many ultra-specific queries as possible, even at low volume. For them, consolidating would be counterproductive — as long as the content remains unique and the crawl budget follows.

What concrete steps should be taken to audit product pages?

Start by exporting from Google Search Console all indexed product pages and their performance (impressions, clicks, CTR, average position). Isolate those generating less than 10 impressions per month — these are candidates for consolidation or deindexation.

Next, cross-reference with your analytics data: bounce rate, session duration, conversion rate. A product page with 500 SEO impressions but 0 conversion and 90% bounce rate is a clear signal of low relevance. Either the content does not meet the intent, or the page is orphaned in your hierarchy.

What mistakes should be avoided during consolidation?

Never delete product pages without proper 301 redirects. Many e-commerce sites redirect all deleted variants to the homepage — this is a soft 404 in disguise that loses equity from those URLs. The best practice: redirect to the semantically closest consolidated product page.

Second pitfall: cannibalizing in the attempt to consolidate. If you group 5 variants onto a parent page, but Google continues to index the 5 individual URLs (because they remain crawlable and non-canonicalized), you create an indexation conflict. The result: no URL ranks properly. Use canonical tags, and if necessary, noindex on secondary variants.

How can you verify that the chosen strategy is working?

Set up position tracking for key queries by product segment. If you consolidate, parent pages should gain visibility on generic and mid-tail queries within 4 to 8 weeks after going live. If they stagnate or decline, it may be that the consolidation sacrificed too much SEO signal.

Also monitor the crawl budget in Search Console (crawling statistics). After consolidation, the number of pages crawled daily should decrease, but the rate of crawled/indexed pages should remain stable or increase. If Google crawls less but proportionally indexes more, that’s a good sign — you’ve eliminated noise.

• Export product pages with less than 10 impressions/month from GSC
• Analyze conversion rates and engagement per product page in GA4
• Identify clusters of variants sharing 80% identical content
• Map out 301 redirects before any URL deletion
• Implement canonicals on secondary variants if they remain accessible
• Track changes in positions and crawl budget post-consolidation for 3 months