WooCommerce SEO site architecture is the work of structuring product categories, attributes and URLs so that commercial demand is capturable. Because WooCommerce is built on WordPress taxonomies, it offers genuine hierarchy, which is an advantage over hosted platforms and a source of its own problems.
Product categories nest properly, permalinks are configurable, and taxonomies behave as taxonomies. The corresponding risk is that nothing is constrained, so structures grow deeper and more tangled than they need to be, and several overlapping archive types end up indexable at once.
General principles are on online store site architecture. This page covers WooCommerce specifics.
The archive types you are actually running
A default WooCommerce install exposes several page types that can all list products. Most stores never decide which of them should be indexable.
- Product categories, hierarchical, and the primary commercial archive.
- Product tags, flat, and frequently duplicating category coverage with no distinct purpose.
- Attribute archives, generated per attribute taxonomy, often indexable without anyone intending it.
- The shop page, which lists everything and overlaps the top category.
- Paginated views of all of the above.
The first architectural decision is which of these earns a place in the index. For most stores the answer is categories, occasionally a small number of attribute archives with real demand, and nothing else.
Permalink structure decisions
WooCommerce permalink settings are configured once and are costly to change, because changing them rewrites every product URL.
- The product base,
/product/by default, can be renamed or removed. - The category base,
/product-category/by default, likewise. - Products can nest inside their category path, or sit flat under a single base.
- Category archives nest naturally, reflecting the taxonomy hierarchy in the URL.
Whether to nest products inside categories
This is the decision most likely to cause pain later. Nesting produces tidy URLs that mirror the hierarchy, and couples every product URL to its category.
- Nested: recategorising a product changes its URL, so routine merchandising becomes a migration with redirects.
- Flat: product URLs stay stable through any amount of category restructuring.
- A product in several categories needs a single canonical URL either way.
- For catalogues expected to grow or be reorganised, flat is usually the more durable choice.
Category hierarchy
Because WooCommerce nests genuinely, the temptation is to nest more than necessary. Depth costs crawl reach and click depth.
- Two or three levels suit most catalogues. Deeper structures need a demand justification.
- Create a subcategory when there is distinct search demand for it, not merely to tidy a long list.
- Keep commercially important categories within about three clicks of the homepage.
- Avoid categories holding only one or two products, which are thin by construction.
- Give category archives real introductory content, since by default they are only a product grid.
Attributes and variations
Attributes are full WordPress taxonomies, which means they generate archives and can be indexed, usually by accident.
- Decide per attribute whether its archive should exist publicly at all.
- Colour and size archives rarely have standalone commercial demand and are usually better excluded.
- Attributes with genuine demand, such as a brand, may deserve treatment as a real landing page.
- Layered navigation plugins generate filtered URLs; control which are crawlable at source.
- Variation handling is covered under product variants SEO.
Tags, and whether you need them
Product tags are enabled by default and frequently duplicate categories. Most stores would lose nothing by making tag archives non-indexable.
- Ask what a tag archive offers that a category archive does not. If there is no answer, exclude it.
- Where tags are used internally for merchandising, that use does not require public indexable archives.
- Tags with genuine cross-category demand, such as “waterproof”, may justify a curated landing page instead.
Frequently asked questions
Should products sit inside category URLs?
Usually not. Nesting couples product URLs to category structure, so recategorising becomes a redirect exercise. A flat product base under a single prefix is more durable for catalogues that will change.
Should product tag archives be indexed?
Rarely. They typically duplicate category coverage without adding distinct value. Use tags internally if they help merchandising, but exclude their archives from the index unless a specific tag has demonstrable standalone demand.
How deep should product categories go?
Two or three levels for most catalogues. Each additional level increases click depth and reduces crawl frequency. Add depth when there is genuine demand for the subcategory, not to shorten a long product list.
Why are attribute pages appearing in search results?
Attributes are WordPress taxonomies and generate public archives by default. Unless you have explicitly disabled them, colour and size archives may be crawlable and indexable. Decide per attribute and enforce it.
Consulting CTA
If your WooCommerce category pages are not ranking, or attribute and tag archives are filling the index, book an SEO consultation to review taxonomy structure, permalink configuration and crawl footprint.