Product Variants SEO: Should Each Variant Get Its Own URL?

This guide answers the main product variants seo question every store faces: should each colour, size or material get its own URL, and how do you tell Google that those variants belong to one product?

Should product variants have separate URLs?

Yes, each variant should be reachable at its own distinct URL, but that does not mean each variant needs its own indexable page. These are two separate decisions, and mixing them up is the source of most variant problems I see in store audits.

Google’s guidance on ecommerce URL structure suggests giving each variant its own URL, either as a path segment such as /t-shirt/green or as a query parameter such as /t-shirt?color=green. It adds that if variants use optional query parameters, the canonical URL should leave the parameter out. Google’s product variant structured data guide goes further: the site must be able to preselect each variant directly with a distinct URL, showing the right image, price and availability.

So the practical answer looks like this:

• Distinct URL per variant: yes, so shoppers can share and land on the exact option, and so Google can match variants to offers.
• Indexable page per variant: only when a variant has its own search demand and its own useful content.
• Everything else: canonicalise variant URLs to the main product page.

One more point from Google’s variant guide matters for how the page behaves: when a shopper lands on a variant URL, the page should show that variant already selected, with the correct image, price and availability, and allow it to be added to the cart. A variant URL that loads the default colour and makes the visitor choose again is a poor experience and sends mixed signals to anyone checking the page.

Do color and size variants cause duplicate content?

Colour and size variants cause duplicate content only when each variant is published as a separate indexable page with nearly the same text, images and title. Ten size pages for one jacket, each with the same description, give Google ten candidates for one search and no reason to prefer any of them.

Size variants almost never deserve separate indexable pages, because nobody searches for “this jacket in size 38” as a distinct product. Colour is different in some categories. People do search for “black leather sofa” or “white running shoes”, and a colour can change the main photo, the style and even the price.

A simple test I use with clients is to ask three questions about each variant attribute:

1. Do people search for this attribute together with the product type? Check your keyword tool or Search Console queries.
2. Does the variant look clearly different in photos?
3. Can you write content that is genuinely specific to this variant?

Two or three yes answers point to a separate indexable page. Zero or one point to a single page with variant selectors.

Single page or one page per variant: which is better?

A single product page with selectable variants suits most stores, while separate pages per variant suit products where one attribute, usually colour or model, drives distinct searches. Google supports both setups in its variant markup documentation, which describes single-page and multi-page approaches.

Hybrid setups are common too. A sofa might have one page per colour, each with a size selector inside it. In that case, colour pages are indexable and canonical to themselves, while size parameters canonicalise to their colour page.

Whichever model you choose, keep titles and H1s variant aware on indexable variant pages. “Linen Shirt” on four colour pages gives Google four identical headings; “White Linen Shirt” and “Navy Linen Shirt” make the difference obvious to both searchers and search engines. The same goes for image alt text and the first lines of the description.

Also think about stock. If a colour page sells out completely, it follows the same out of stock rules as any other product page: keep it live while a restock is likely, update availability in the markup, and point visitors to the colours that are available.

How do I add schema for product variants?

You add schema for product variants by wrapping the variants in a ProductGroup, listing the attributes they differ by in variesBy, and nesting each variant as a Product under hasVariant, or by linking each variant back to the group with isVariantOf. This structure is described in Google’s product variant documentation.

The key properties are:

• productGroupID: the parent identifier, for example the parent SKU. It can also be given on each variant with inProductGroupWithID, and if both are used they must match.
• variesBy: the attributes that distinguish variants, such as color, size, material or pattern, written as schema.org URLs.
• hasVariant: the list of variant Product entities, each with its own offer, price and availability.
• Unique IDs: Google states that each variant and each product group must have a unique ID in its markup, typically the sku.

For a single-page setup, the ProductGroup includes a url for the base product page. For multi-page setups, Google says each page must carry full and self-contained markup for the entities on that page, so the full ProductGroup definition is repeated on every variant page, and variants on other pages can be referenced with just their url.

Shared properties such as brand, description and reviews can sit on the ProductGroup, so you do not repeat them on every variant. If you already have product markup and see validation issues, my guide to fixing Search Console errors is a good place to start.

What does a variant setup look like for a real product?

Variant decisions affect templates, URLs and markup at the same time, so they are easiest to get right before a store launches or during a redesign. If you are planning either, my e-commerce SEO service covers variant strategy, and if a rebuild is on the table, the website redesign service is set up to change URL structures without losing rankings. For individual pages, the on-page SEO work of writing variant specific titles and intros is what makes separate colour pages worth indexing.

Frequently asked questions