We use cookies to improve your experience on our website. By clicking "Accept all", you agree to the use of all cookies. Privacy Policy
Settings
BACK TO BLOG

WooCommerce SEO: A Practical Guide for UK Stores

SEO
27 August 2026
·  Updated 
7min read
Nicolaas Kerkmeester
Nicolaas Kerkmeester
Director, Clear Click
Illustration of a WooCommerce settings panel with plugin toggle rows, one switched off
Table of contents
Heading
Heading

WooCommerce SEO in practice: permalinks, attribute filter URLs, plugin weight, hosting and structured data, and which of them is costing you rankings.

WooCommerce gives you more SEO control than any hosted platform and hands you the maintenance bill for it. The four things that decide whether a WooCommerce store ranks are permalink structure, attribute filtering, plugin weight and hosting. Get those right and the WordPress content stack behind the shop becomes a real advantage. Get them wrong and you have a slow store generating thousands of URLs nobody searches for.

This is what we look at, in the order we look at it.

What makes WooCommerce different from a hosted platform?

WooCommerce is a plugin on WordPress, not a commerce platform with a content bolt-on. That distinction explains most of its strengths and all of its weaknesses.

The strengths: you own the URL structure, the robots rules, the redirects, the server configuration and the caching layer. There is no platform fee. Editorial content and product content live in the same system, so the guide that supports a category can sit alongside it, be edited by the same person, and link to it without any integration work. For content-led retailers, that is worth more than it sounds.

The weakness is the same sentence read differently: you own all of it. Nobody is maintaining your performance baseline, checking your plugin conflicts, or stopping your filter URLs from being crawled. That is the job.

How should WooCommerce permalinks be set up?

Settle this before the store has any traffic, because changing it afterwards means a redirect map.

WooCommerce defaults put products under a /product/ base and categories under /product-category/. Both are editable in permalink settings, and there is a long-running argument about whether removing them helps.

Our position: the base itself makes very little difference to rankings, and the risk of changing it on an established store is greater than the upside. What does matter is consistency and depth. A product sitting at /product/item-name/ is fine. A product sitting at /shop/category/subcategory/sub-subcategory/item-name/ is a maintenance problem, because moving that product between categories changes its URL.

Two things worth deciding deliberately:

  • Do not nest product URLs inside category paths unless you are certain the taxonomy will never change. It always changes.
  • Pick one canonical route to each product and link to it consistently from menus, related products and internal content.

Why do WooCommerce stores generate so many URLs?

Because WordPress taxonomies and WooCommerce attributes both produce archive pages, and layered navigation adds parameters on top.

The usual sources, in rough order of damage:

  • Attribute filtering. Layered nav filters produce parameter URLs such as ?filter_colour=blue&filter_size=large. Every combination is a distinct URL. On a store with five attributes and a handful of values each, that is tens of thousands of crawlable pages generated from a catalogue of a few hundred products.
  • Product tags. WooCommerce tag archives are indexable by default and are frequently near duplicates of category pages. Most stores use tags loosely, which means most tag archives are thin.
  • Sort and view parameters. ?orderby=, ?per_page= and similar produce more URLs with identical content.
  • WordPress archives. Author archives, date archives and attachment pages come from WordPress rather than WooCommerce, and are often left on.

The fix is a set of decisions rather than a plugin setting. Which filtered views have genuine search demand behind them, and therefore deserve to be real category pages with content. Everything else gets excluded from the index and, where possible, from being crawled at all. An SEO plugin will let you noindex tag and attribute archives in a few clicks. Deciding which ones to promote first is the part that needs judgement.

The diagnostic is the same one we use on any store: compare the URL count in your sitemap against what Google reports discovering. Our ecommerce SEO audit framework starts with exactly that comparison.

How much do plugins cost you?

More than most store owners expect, and the cost is cumulative.

A typical WooCommerce store we inherit is running somewhere between twenty and forty plugins. Each one may add front-end CSS and JavaScript to every page, whether that page uses the plugin or not. Several will query the database on every page load. Two or three will conflict with each other in ways that only show up under load.

What we do about it:

  • Audit what is installed, what is active, and what is actually used by anyone
  • Check which plugins load assets globally, and restrict them to the pages that need them
  • Remove rather than deactivate, because deactivated plugins still leave database tables and options behind
  • Test after each removal, because something always depends on something

This is unglamorous work and it is frequently the single largest performance gain available on a WooCommerce store. Page speed is a modest ranking factor and a significant conversion factor, so the commercial argument holds even when the ranking one is marginal.

Does hosting really matter for WooCommerce SEO?

Yes, more than on any hosted platform, because there is no CDN and no server tuning being done for you.

WooCommerce is database heavy. Product queries, cart sessions and layered navigation all hit the database, and cart pages cannot be cached the way a static page can. Shared hosting that is adequate for a blog will struggle with a catalogue under any real traffic.

What makes a measurable difference: object caching, a properly configured page cache that excludes cart and checkout, a CDN in front of static assets, and enough resource that the database is not the bottleneck. Managed WooCommerce hosting handles most of this. It costs more and it is usually worth it.

What structured data does WooCommerce output?

WooCommerce emits Product markup by default, including price and availability, which is a better starting position than many themes on hosted platforms.

The problems tend to come from duplication rather than absence. A store running WooCommerce's native markup alongside an SEO plugin's markup alongside a review plugin's markup can end up with three Product blocks on one page, describing the same product slightly differently. Validate a product template, a category template and the homepage rather than assuming.

Two specifics worth checking: variable products should describe their price range correctly rather than reporting a single variant's price, and review markup should reflect reviews that actually exist on the page.

How do you handle out of stock and discontinued products?

This is a commercial decision before it is a technical one, and the wrong default is expensive.

A product that is temporarily out of stock should stay live, keep its URL, keep its content, and tell the customer when it is coming back. Removing it and redirecting throws away the rankings you will want when it returns.

A product that is permanently discontinued should redirect to the closest equivalent or to its category, not to the homepage. A homepage redirect is a soft signal that the page is gone and the redirect is meaningless.

Where a store carries seasonal ranges, the pattern that works is a permanent category page that persists year to year, with the seasonal products moving in and out of it. That way the accumulated authority sits on something that does not disappear every year.

Does WooCommerce handle multiple languages and countries?

Not natively. Multilingual selling needs a translation plugin, and the two common choices behave differently enough to matter.

What to insist on regardless of which you use: distinct, crawlable URLs per language or region, hreflang tags rendered server side in the initial HTML, self-referencing canonicals on each version, and translated URLs rather than translated content on the same URL. Automatic redirection based on visitor location should never apply to search engine crawlers, or only one version will ever be indexed.

Our hreflang implementation guide covers the tag logic in detail, and it applies whatever the plugin.

Questions we get asked about WooCommerce SEO

Is WooCommerce good for SEO?

It is capable of excellent SEO and it is not automatic. You get complete control over URLs, crawl rules and structured data, and you are responsible for performance and for keeping the URL count under control. With development support it is a strong platform. Without it, a hosted platform will get you further.

Do I need an SEO plugin for WooCommerce?

Yes, for practical reasons: bulk meta data editing, sitemap generation, and the indexation controls for taxonomy archives. Any of the mainstream options will do this. None of them will decide your category structure or write your content.

Why is my WooCommerce store slow?

Usually plugins, then hosting, then images, in that order. Start by auditing what is installed and what each plugin loads globally. Chasing a performance score before doing that tends to produce a lot of effort and very little improvement.

Should I noindex WooCommerce product tags?

In most cases yes. Tag archives are usually thin and overlap with categories. The exception is a tag that has genuine search demand behind it, in which case it should be promoted to a proper category page with its own content rather than left as an archive.

What does a WooCommerce SEO agency actually do?

The valuable work is diagnostic and commercial: finding where crawl budget is going, identifying which categories are missing against real demand, and prioritising fixes by revenue rather than by a tool's severity score. The plugin configuration is the easy part.

Is WooCommerce better than Shopify for SEO?

Different rather than better. WooCommerce has a higher ceiling and a lower floor. We compare them properly in our guide to choosing an ecommerce platform for SEO.

Where this usually leads

WooCommerce stores rarely have one big problem. They have an accumulation of small ones: a plugin nobody remembers installing, a filter generating URLs nobody reviewed, a hosting plan chosen when the catalogue was a tenth of its current size. Sorted in the right order, the compounding works in your favour instead.

Our ecommerce SEO service works across WooCommerce, Shopify and Adobe Commerce, and we are happy to give a second opinion on a plan you already have.

Clear Strategy. Clear Growth. Clear Click.

Prefer to start with a conversation? Ask us for a second opinion on your current strategy. We will share where we would focus, and why.
Speak to Us