Ecommerce Website Developer

JournalAbout 2 min read

Should product variants have their own URLs?

It depends on whether people search for the variant, and whether the variant page would be worth reading when they arrive.

Written by

Javed IqbalApproved contributor

Contributed by

Nazir AbbasApproved contributor

Published

Abstract measured panel in the brand colours

Key takeaways

  • Two tests: distinct search demand, and distinct content
  • Size and specification often pass both; colour often fails the second
  • Variants without a page use a parameter, canonical to the clean parent URL
  • Internal links should point at the clean URL, not the parameterised one
  • Shared pages describe a price range, not a single fixed price
  • Compare indexable product URLs against actual product count

A product in six colours and five sizes is thirty combinations. Give each one an indexable URL and you have turned one product into thirty near-identical pages. Give none of them a URL and you may be invisible for the searches that actually convert.

The right answer sits between the two and depends on demand.

The test

A variant deserves its own indexable page when both of these are true:

  1. People search for the variant specifically, not just the parent product
  2. The resulting page would say something the parent page does not

Colour frequently passes the first test and fails the second. Someone searching for a specific colour of a well known product is a real search, but if the variant page is the parent page with one word changed, it is a duplicate with a keyword in the title.

Where variants usually earn a page

  • Size or capacity when it changes what the product is for. A 2TB drive and a 256GB drive are different purchases.
  • Model or specification within a product family, where the specification table genuinely differs.
  • Material or finish in categories where that is the primary buying decision, such as flooring or worktops.

Where they usually do not

  • Colour on clothing, unless the colour has its own established demand
  • Quantity or pack size, which belongs as an option on one page
  • Anything where the only difference is a single attribute value in an otherwise identical page

Handling the ones that do not get a page

Use a parameter on the parent product, with the canonical pointing at the clean parent URL.

  • /product/widget is the canonical page
  • /product/widget?colour=blue renders the blue variant selected, canonical to /product/widget
  • Internal links point at the clean URL, not the parameterised one

That way a customer can share a link to the exact variant, and a search engine consolidates the signals onto one page.

The structured data question

If variants share one page, the structured data should describe the product with its price range, not pretend to be a single fixed price. If a variant has its own page, that page describes that variant.

Check what you have

Crawl your product section and count distinct indexable URLs against your actual product count. If the first number is several times the second, variants are generating pages nobody asked for, and that crawl budget is coming from somewhere.

Frequently asked

Questions readers ask

Should product variants have separate URLs?

Only when the variant has its own search demand and the page would contain something the parent page does not. Size and specification often qualify. Colour on clothing usually does not, and giving every colour a page creates near-duplicates.

How do I handle canonical tags for variants?

Variants without their own page render on a parameterised URL with the canonical pointing at the clean parent address. That lets a customer share a link to the exact variant while search engines consolidate signals onto one page.

What structured data should a variant page use?

Describe what is actually visible. If variants share one page, describe the product with its price range rather than a single fixed price. Never emit a price or availability that a customer cannot see on that page.

About the authors

Javed Iqbal

Written by

Javed IqbalApproved contributor

SEO Specialist & Co-Founder

Leads search, with more than five years in ecommerce and technical SEO for businesses in the UK, the US and the UAE.

Nazir Abbas

Contributed by

Nazir AbbasApproved contributor

Web Developer & Co-Founder

Builds and maintains ecommerce sites in React, Next.js and WordPress, and handles the technical side of search.

Editorial process: every article is written by one of the two co-founders and reviewed by the other before publication. Technical claims are checked against how the systems actually behave, and anything we cannot evidence is left out rather than asserted.

Related reading