Why your WooCommerce store isn’t ranking (and how to fix it)

A store that does not rank is rarely a content problem. In nearly every WooCommerce audit we run, the cause is structural — decisions baked into the build long before anyone wrote a product description. The good news is that structural problems are the fixable kind. Here are the four we find most often, in the order they usually matter.

1. Your product URLs carry no meaning

WooCommerce ships with a /product/ base and, on many installs, a category path stacked on top of it. What starts as a tidy idea ends up as /product-category/accessories/cables/product/usb-c-cable-2m/ — deep, repetitive, and full of words search engines have already seen twice on the same URL.

Flatten it. A product should live at /product/usb-c-cable-2m/ and nowhere else. Categories get their own clean paths. If you change an existing structure, map every old URL to its new one with 301 redirects before you flip the switch — a rankings drop after a restructure is almost always a redirect that was never written.

2. Faceted navigation is eating your crawl budget

Filters are the single biggest source of index bloat in e-commerce. Every combination of colour, size, brand and price generates a URL. Left alone, a 400-product store can produce tens of thousands of crawlable variations, most of them near-duplicates of a page that already exists.

The fix is not one setting, it is a policy:

• Canonical every filtered view back to the unfiltered category page.
• Noindex combinations that add no unique value — sort orders, price bands, pagination beyond a sensible depth.
• Keep indexable the handful of filter pages that match real search demand, and give each one genuine copy. “Waterproof hiking boots” deserves a page. “Boots, sorted by price, page 7” does not.
• Block the rest in robots.txt only once canonicals and noindex are in place — blocking first stops crawlers from ever seeing the directives you added.

3. Your product pages have no structured data worth reading

Rich results — price, availability, review stars — are not decoration. They change click-through rate on a results page where you are otherwise indistinguishable from six competitors selling the same SKU.

WooCommerce outputs basic Product schema, but the defaults are frequently incomplete: no brand, no sku, an availability value that does not update with stock, and aggregate ratings that quietly disappear when a plugin updates. Validate a real product URL in Google’s Rich Results Test, not a staging page, and check it again after every major plugin update. This is a five-minute check that catches an entire category of silent failure.

4. The store is slow where it counts

Speed is not a tiebreaker any more; it is a gate. A category page carrying thirty product images, a slider, three tracking scripts and an uncached wp_query per filter will lose on Core Web Vitals no matter how good the copy is.

What actually moves the numbers, in rough order of impact:

• Serve product images at display size in WebP or AVIF. Most stores ship 2000px files into a 400px grid slot.
• Cache pages at the edge and exclude only cart, checkout and my-account. Excluding the whole store because of the cart fragment is a common and expensive mistake.
• Unload plugin assets on pages that do not use them. A booking plugin has no business loading on a product page.
• Add database indexes for the meta keys your filters query. Faceted search on an unindexed postmeta table is the slowest thing in most stores.

What to do first

Run the four checks in order and you will usually find the constraint inside an hour. Export your indexed URLs from Search Console and look at what is actually in there — if more than a third of it is filter combinations, that is your problem, and no amount of new content will outrun it.

Fix structure first, then speed, then content. In that order the content work compounds. In the other order it mostly disappears.