Product Variants Size Colour and Attribute Pages

Two Valid Patterns

Pattern one: a single URL per product with a JavaScript or dropdown selector for colour and size, updating images and stock without changing the URL. This consolidates all ranking signals (reviews, links, engagement) onto one page — usually the right default when variants don't have independent search demand.

Pattern two: a unique URL per significant variant (typically colour, rarely size) when each variant has its own product images and enough independent search volume — for example "nike air force 1 white" and "nike air force 1 black" both getting meaningful separate search volume. Size almost never justifies a separate URL because nobody searches by size alone at meaningful volume relative to colour.

Choosing Correctly

Check search volume for variant-specific queries before deciding. If "[product] + colour" queries show real, separate demand for at least two colours, split those into unique URLs with canonical-free unique content (different images, different H1, unique enough copy to avoid duplicate content flags). If demand is flat or near-zero for individual colours, keep one URL and let the selector do the work — it also protects conversion rate by keeping reviews and stock consolidated.

When you do split into separate URLs, cross-link every variant to every sibling variant clearly (a colour swatch row that links, not just JS-swaps) so authority and crawl paths flow between them, and consider a lightweight comparison table linking back to the parent style page if one exists.

Common Failure Modes

The most common mistake is splitting every variant into its own URL by default because the platform makes it easy, then ending up with ten near-identical pages competing against each other in search results — classic keyword cannibalisation. The second most common mistake is the opposite: consolidating everything onto one URL even when a colour variant has genuine independent demand and unique enough content to deserve its own ranking page, leaving traffic on the table.

• Check: does this variant have independent, meaningful search volume?
• Check: does this variant have unique enough content (images, description nuance) to avoid thin/duplicate flags?
• Check: will splitting fragment reviews and reduce social proof on any one page?
• If unsure, default to one URL with a selector — it's the lower-risk option

Spotting Variant Cannibalisation in RankAudit

Run RankAudit's keyword overlap report across product URLs sharing the same base product name. If three or more variant URLs are ranking for the same non-variant query, they're cannibalising each other and you should consolidate or strengthen canonical signals toward the strongest performer.

Why this lesson matters

The decision around product variants directly impacts your bottom line, extending far beyond theoretical SEO concepts. Incorrect implementation can lead to significant crawl budget wastage, as search engines may attempt to crawl hundreds or thousands of near-identical pages, diverting resources from truly unique and valuable content. This inefficiency not only slows down indexation for new products but also dilutes authority, making it harder for any single variant page to rank robustly for core product queries, ultimately suppressing organic visibility and sales.

Consider an e-commerce store selling a popular dress available in five sizes and six colours. If each size-colour combination generates a unique, indexable URL without proper canonicalisation, you could inadvertently create 30 distinct pages competing for the same search intent. This internal cannibalisation sends mixed signals to search engines, potentially causing none of them to rank well, or for an inferior page to be chosen. The result is lost organic traffic, frustrated users encountering irrelevant or duplicate content, and ultimately, a direct hit to conversion rates and revenue, even for best-selling products.

Implementing Canonicalisation for Variant Pages

When opting for the 'shared URL with selectors' pattern, rigorous canonicalisation is paramount. Every variant URL (e.g., `example.com/product-a?colour=red`, `example.com/product-a?size=M`) must explicitly point via a `rel="canonical"` tag to the primary, preferred version of that product page (e.g., `example.com/product-a`). This signals to search engines that these are not separate, unique content items but rather variations of a single entity, consolidating ranking signals to the canonical URL.

Crucially, ensure that the canonical tag is always absolute and self-referencing on the preferred URL, and consistently points to that preferred URL from all its variant permutations. This prevents situations where parameters are retained in the canonical, or where canonical tags point to non-existent pages. Mismatched or missing canonicals are a primary source of variant content issues, often leading to index bloat and search visibility fragmentation. Verify implementation after any platform updates or template changes.

• Primary canonical URL must be parameter-free (e.g., `domain.com/product-slug`).
• All variant URLs (e.g., `?colour=red`) must canonicalise to the primary.
• Canonical tags must be absolute URLs, not relative.
• No `noindex` should be applied to the canonical page.

Do it now

Immediately choose one of your core product categories that you suspect might have variant issues. Open your RankAudit project for that site and navigate to the 'Indexability' or 'Duplicate Content' reports. Look for clusters of very similar product page URLs, especially those with numerous URL parameters (e.g., `?size=`, `?colour=`). Analyse their canonical tags and status codes to identify any pages that are incorrectly canonicalising or are unexpectedly indexable.

Using your RankAudit findings, follow these steps:

1. Identify the top 3 product families with the most variant URLs.

2. For each family, manually inspect 3-5 variant pages to check their `rel="canonical"` tag.

3. Verify if the canonical tag points to the desired, primary product URL.

4. Note down any discrepancies or missing canonical tags for immediate developer review.

Key takeaways

• ✓Only split variants into separate URLs when independent search demand and unique content both exist
• ✓Size variants almost never need their own URL — colour sometimes does
• ✓Cross-link sibling variants with real anchor links, not just JS toggles
• ✓Use RankAudit's keyword overlap report to catch variant cannibalisation early

Why this lesson matters

This lesson belongs to Foundations and Technical Traps, the part of E-Commerce SEO where the goal is: understand what makes e-commerce seo structurally different and fix the technical issues that quietly bleed crawl budget and rankings.

Read it once, then do it straight away on a real site inside RankAudit. Nothing here is theory for its own sake — every step produces something you can show a client.

Do it now

1. 1Open RankAudit with sample data already loaded, so you are not stuck on setup.
2. 2Crawl a site and triage the issue list.
3. 3Run a RankAudit crawl of your store and export the URL count by template to see how big your faceted navigation problem really is.