Variant URLs: when they deserve to be indexed

Variant URLs: when they deserve to be indexed

Written by

in

TL;DR

A shirt in six colours and five sizes is thirty combinations. Whether each gets a URL is a decision most stores never make, so the platform makes it and everybody finds out during a crawl. One indexable product page is right for most catalogues, and I would need a specific reason to depart from it.

A shirt in six colours and five sizes is thirty combinations. Whether each of those gets a URL, and whether those URLs get indexed, is a decision most stores never make. The platform makes it and everyone finds out during a crawl.

The default answer

One indexable product page, variants selected on it. That is right for most catalogues and I would need a specific reason to depart from it.

The reasoning is simple: thirty near-identical pages compete with each other, split whatever links the product earns, and none of them is stronger than the single page would have been. You have divided one asset into thirty fractions.

Most platforms handle this correctly by default, with variant URLs carrying a canonical to the parent product. HTTP Archive’s 2025 Web Almanac found a canonical tag on only 67% of mobile pages, meaning a third of the web has none, so a platform that ships one on a duplication pattern it created is doing better than most. Check yours survived the theme and move on.

When a variant genuinely deserves its own page

Three tests. It needs all three, not one.

People search for the variant specifically. Not the product. The variant. “Black leather office chair” is a search. “Office chair, colour black” is a filter. The difference is whether the attribute is how people name the thing they want.

The variant has meaningfully different content. Different images, different specification, different price, different use case. If the only difference is one word in a dropdown, it is not a page.

You would back it with internal links. The usual test. If you would not link to it from the category, you do not believe it can rank, and it should not be indexable.

In practice this passes for one attribute at most, usually colour on fashion or capacity on electronics, and never for size, quantity or packaging.

Scale makes the arithmetic unforgiving. The 2025 Web Almanac found ecommerce on 19.2% of mobile sites, and on a catalogue of any size a permissive variant setting is the fastest URL multiplier available: six colours by five sizes on a thousand products is thirty thousand pages that nobody wrote and nobody will read.

The case people get wrong in the other direction

Worth flagging because over-consolidating is also a mistake.

Some catalogues sell things where the variant is the product. Car parts by vehicle fitment. Printer cartridges by model. Filters by dimension. Here the variant is exactly what the customer searches, the compatibility is the whole purchase decision, and collapsing them into one page with a dropdown makes the site invisible for the only queries that matter.

The test still holds. People search the variant specifically, the content genuinely differs, you would link to it. It just passes for every variant rather than none. Recognising which kind of catalogue you have is the actual judgement, and it is not a rule you can apply from outside the business.

What to check

  • Do variant URLs exist at all? Some platforms use parameters, some use paths, some render entirely client-side with no URL. All three are fine and they need different handling.
  • Is the canonical intact? Raw source, not the inspector. A canonical injected after JavaScript runs is conditional.
  • Which URL do your internal links point at? If the category grid links to a variant URL rather than the parent, every internal link on the site is voting for a page you have declared non-canonical.
  • Are variants in the sitemap? If they are canonicalised away, they should not be, because you are submitting pages you have told Google to ignore.

Why this belongs in the thin content conversation

Thirty variant pages with one word different is the purest example of thin at scale, and it is not a writing problem. Nobody wrote them. The fix is a decision, not four hundred descriptions, which is the same answer as almost everything else in a large catalogue.

The short version

  1. Default: one indexable product page. Thirty fractions beat nothing.
  2. Most platforms canonicalise variants correctly. Check yours survived the theme.
  3. Three tests to index one: searched specifically, genuinely different, worth linking to.
  4. Usually passes for one attribute at most, and never for size or quantity.
  5. Fitment catalogues are the exception, because there the variant is the product.
  6. Check what your internal links point at. Often the non-canonical version.
  7. Canonicalised variants do not belong in the sitemap.

If a site should be ranking and it isn’t, that’s the work I do. Ecommerce SEO covers variants, facets and the URLs a catalogue makes for you. If you’re not sure which of several plausible problems is costing you, that’s what an SEO audit is for.

Headshot of Mehul Dedhia, SEO consultant

Written by Mehul Dedhia

I’ve been doing SEO for about fifteen years. Most of my work isn’t building new websites. It’s figuring out why sites that should rank don’t. Local businesses, ecommerce and Shopify brands, affiliate sites, small brands and enterprise. If a site is stuck or has lost rankings, that’s usually where I come in.

Connect with me on LinkedIn