Guides
WooCommerce SEO Audit Checklist: Products, Variations and Bloat
WooCommerce inherits WordPress's habit of publishing an archive for everything. Most WooCommerce SEO work is deciding which of those archives should exist.
Run a fresh DomainLens audit and use the report as your priority list.
The URLs WooCommerce generates without asking
On top of products and categories, WooCommerce publishes archives for tags, attributes, and often each attribute term. A store with colour, size and material attributes generates hundreds of thin archive pages that nobody searched for.
None of them are wrong, and most of them should not be indexed. That decision is the core of a WooCommerce audit.
| URL type | Index? | Reason |
|---|---|---|
| /product/name | Yes | The product itself |
| /product-category/x | Yes | Real category demand |
| /product-tag/x | Usually no | Overlaps categories, thin |
| /?attribute_pa_color= | Rarely | One per attribute value |
| ?orderby= and ?paged= | No | Sorting and deep pagination |
| /cart, /checkout, /my-account | Never | Transactional, often personalised |
The checks that matter
The cart and checkout check is worth doing even though plugins handle it, because a store with those pages indexed is leaking session URLs into search. See index bloat and crawl discovery for measuring the total.
- 1Confirm cart, checkout and account pages are noindexed — most SEO plugins do this, but verify rather than assume.
- 2Decide on tag archives: keep the few with search demand, noindex the rest.
- 3Check whether attribute archives are enabled and whether any deserve to be.
- 4Verify product variations do not generate separate indexable URLs competing with the parent.
- 5Confirm the product base slug is what you want; changing it later renames every product URL.
- 6Check that out-of-stock products stay live rather than 404ing when inventory hits zero.
Product content is the ceiling
The technical work above stops a store hurting itself. It does not make products rank, and on most WooCommerce stores the actual limit is that every product description came from the supplier.
A description shared with two hundred other retailers gives Google no reason to prefer your page. That is the constraint, and no plugin setting addresses it.
- Write your own description for the products that matter; not every SKU deserves the effort.
- Give category pages real copy, not just a product grid.
- Use the short description for something genuinely different from the long one.
- Add specifications as structured data that matches what is visible on the page.
Performance, which WordPress makes easy to lose
WooCommerce stores accumulate plugins, and each one adds queries and front-end assets. A store running twenty plugins frequently loads scripts from all of them on every page including the ones that need none. Page caching plus a hard look at the plugin list is worth more than image optimisation on most stores. See TTFB , which is usually the constraint, and the WordPress audit checklist for the platform underneath.
How DomainLens contributes
DomainLens reports indexability, canonical, structured data and Core Web Vitals for any store URL, so you can confirm an attribute archive is genuinely excluded and a product page carries valid Product markup. For the catalogue-wide view see crawl budget for e-commerce and the e-commerce audit checklist .
- Should WooCommerce product tags be indexed?
- Usually not. They overlap categories and are typically thin. Keep the few with genuine search demand and noindex the rest.
- Do product variations create separate URLs?
- They can, via query parameters. Those should canonicalise to the parent product rather than competing with it.
- Should out-of-stock products be deleted?
- No. Keep the page live with a 200 if the product will return. Only 404 or 410 when it is genuinely discontinued.
- Why is my WooCommerce store slow?
- Usually plugin count and uncached database queries rather than images. Page caching and a plugin audit move TTFB more than anything else.