How variants create duplicates
Many products come in options: a shirt in five colors and six sizes, a phone case for twelve models, a mug in two capacities. Store software handles this in different ways. Some systems create one page with a selector. Others create a separate URL for every combination. Others do both at once, with a parent page plus a page for each child.
When every combination gets its own address and the content is nearly identical, a store can end up with dozens of pages that differ by a single word. Visitors rarely benefit from that. Search engines see several versions of almost the same page and must choose between them, which may not be the one you would pick. This is a store-specific form of the broader problem described in the guide on duplicate content.
It is not a penalty in itself. The practical costs are diluted signals, spent crawling effort and an untidy site. On very large catalogs, the crawl budget consequences can matter.
Three common approaches
1. One page for the product, options chosen on the page. The color and size selectors change what is shown but not the address. This is the simplest to manage and often a good default when the variants are minor and share one description. The risk is that a specific variant, such as a particular color, is harder for people to find through search or to share by link.
2. Separate pages for each variant, with a preferred version. Each has its own address, and the others point to a main version using canonical tags. Search engines are told which one to treat as the primary. This is workable when the system insists on separate URLs. Note that a canonical tag is a hint, not a command, so search engines may ignore it if pages differ significantly.
3. Separate, genuinely distinct pages. If variants are really different products, each deserves its own page with its own content. A hypothetical example: a lightweight and a heavy-duty version of the same tool may have different uses, specifications and audiences.
A test for whether a variant deserves its own page
Ask three questions:
- Do people search for this variant specifically, such as a particular color or model? Keyword research can give a rough sense, though results are only indicative.
- Is the page meaningfully different: different images, specifications, price, availability or description?
- Would a visitor looking for it be disappointed to land on a general page instead?
If the honest answers are no, a single page with options is usually enough. If yes, a separate page with its own useful content may be justified. A size that only affects the dropdown rarely qualifies. A color with its own photos that many shoppers ask for sometimes does.
What to check in an audit
- Count the URLs. Compare the number of product pages in the sitemap or crawl with the number of products you actually sell. A big gap suggests variants are generating extra pages.
- Look for patterns in addresses. Parameters such as
?color=blue&size=moften reveal variant URLs; see url parameters. - Compare titles and descriptions. Identical titles across variants are a sign of duplication. If a variant is indexed separately, its title should say what is different about it.
- Check canonical tags. Do variant pages point to the main version? Does the main version point to itself? Contradictory or circular signals cause confusion.
- Check the sitemap. It should list the versions you want indexed, not every combination.
- Check internal links. Category pages should link to the preferred version, not a random variant; see internal linking.
- Check structured data. Product markup should reflect the real price and availability of the specific variant shown. Review markup is a particular risk, since reviews may be attached to the parent, as discussed in the review markup article.
Managing availability by variant
An item may be sold out in one size but available in others. Show that clearly on the page without hiding the product. If all variants are gone, the guidance on out-of-stock pages applies to the whole group. Avoid creating separate pages simply to represent stock levels.
Handling the descriptions
When variants share one page, write the content once, well, and mention what changes between options. When they have separate pages, add details that really are specific: dimensions for that size, photos of that color, compatibility with that model. Swapping a single word in otherwise identical text is the pattern to avoid; see product pages for what makes content original.
Cleaning up an existing mess
If you find a large set of unnecessary variant URLs already indexed, plan carefully before changing anything. Options include setting canonical tags, redirecting retired addresses to the preferred page, and removing them from the sitemap. Redirects should be permanent and direct, without chains; see redirect chains. Make the change in stages, note it in a change log, and expect search engines to take time to reflect it.
Back up the site before large changes, as covered in site backups. Outcomes vary by platform and catalog, and no setup guarantees a particular result, but a clear rule for variants keeps a growing store manageable.