Attributes in WooCommerce do two jobs that are easy to confuse: they drive product variations, and they can generate their own archive pages. The second is where the SEO problems come from, and it is switched on more often than anyone intends.
Global versus custom attributes
- Global attributes are defined once and reused across products. They can generate archive pages and power filtering.
- Custom attributes are defined per product. They do not create archives.
Use global attributes for anything shared across products — size, colour, material. Use custom ones for details specific to a single product. Getting this wrong either scatters your taxonomy or creates archives you did not want.
The archive problem
A global attribute can be made publicly visible, which creates an archive page listing every product with that value. These pages typically have no unique content and duplicate what your categories already show.
In most stores they should not be indexed. The exception is where the attribute is genuinely how people search — “waterproof” boots, a specific fabric — in which case it deserves a real category page with its own content rather than a bare archive. See category vs filter page.
Attributes and variations
Attributes marked as used for variations generate variant options on the product page. Where variations produce their own URLs, the same duplication questions apply as anywhere else.
Keep one canonical product URL unless a variant is genuinely searched for by name. See product variations SEO and duplicate product pages.
Attributes and filtering
Attribute-based filters generate parameter URLs. On a store with several attributes the combinations multiply quickly, and those URLs are crawl waste unless deliberately handled.
See URL parameters and faceted navigation SEO.
Getting it right
- Use global attributes for shared characteristics, custom for one-offs.
- Keep attribute archives out of the index unless you have deliberately built one into a real page.
- Name attribute values consistently — “Blue” and “blue” as separate terms fragment your filtering.
- Put attribute detail in the product content too, not only in the attributes table, so it is available as text.
- Review what your filters generate before assuming it is harmless.
Frequently asked questions
Should attribute archives be indexed?
Generally no. They duplicate category listings without adding anything. Promote one to a real category only where genuine demand exists.
Do attributes help rankings directly?
Not by existing. They help when the detail appears as content and when they support a well-built category.
How many attributes should a product have?
As many as genuinely describe it. The cost is not the count but what the archives and filters generate.
Global or custom by default?
Global for anything more than one product shares, since custom attributes cannot be filtered on. See WooCommerce category structure.
Consulting CTA
For a review of your store’s taxonomy and what it generates, book an SEO consultation.