WooCommerce SEO audit: what a manual review actually checks

1. Product and shop permalink structure

WooCommerce adds its own permalink options to the WordPress permalink screen, and the choice made once at setup shapes every product URL afterwards. One of the options, shop base with category, "uses the shop page name followed by the product category name, for example example.com/shop/hoodies/hoodie-with-logo" (WooCommerce, Permalinks).

That option is not wrong, but it has a consequence worth knowing before you pick it: a product that sits in more than one category still needs a single canonical URL, and moving a product between categories changes its address.

WordPress itself adds a second layer. Category and tag archives sit behind a prefix that you can rename but "can't remove from the URLs altogether" (WordPress, Customize permalinks), and when a post has several categories, only one appears in the permalink — chosen alphabetically.

• Which product permalink base is in use, and whether every sampled product follows it
• What the canonical tag on a product page actually declares
• Whether internal links point at the canonical URL directly or arrive through a redirect
• Whether the sitemap, navigation, and canonical tags agree on one preferred URL per product

Google treats redirects and rel="canonical" as strong signals and sitemap inclusion as a weak one, so disagreement between them is worth resolving rather than leaving to chance (Google Search Central, canonical URLs).

2. Category, tag, and attribute archives

WooCommerce gives you three overlapping ways to organise a catalog. Its documentation puts it plainly: product categories, tags, and attributes "are different ways you can use to organize, display, and filter products in your WooCommerce store", with categories hierarchical, tags flat, and attributes doing double duty because they also define variations (WooCommerce, Managing product categories, tags and attributes).

Each of those taxonomies can generate an archive page. That is useful when the archive answers a real search, and a liability when a store has accumulated dozens of tag pages listing two products each.

• Which archives exist, which are linked, and which are only reachable through a sitemap
• Whether each indexable archive has a distinct purpose rather than repeating a category
• Whether category descriptions explain the selection or sit empty
• Whether two archives are competing for the same shopper intent without a deliberate hierarchy

The decision is never "noindex everything". Some archives genuinely deserve to rank. What we check is whether each one has distinct intent, enough inventory to be useful, and someone maintaining it.

3. Filtered and faceted URLs

Layered filters, sorting, and attribute selection all produce new URLs with query strings attached. Google's guidance on this is unusually direct: because the generated URLs look novel and crawlers "can't determine whether the URLs are going to be useful without crawling first", crawlers typically access a very large number of them, and a careless implementation "can generate infinite URL spaces which harms the website" (Google Search Central, managing crawling of faceted navigation URLs).

The same document notes that rel="canonical" and rel="nofollow" on faceted URLs are "generally less effective in the long term" than preventing the crawl in the first place, and that a filter combination returning no results should return a 404 rather than an empty page.

• Which filter, sort, and search parameters your store exposes to crawlers
• Whether filtered pages are internally linked, or only discoverable by crawling
• Whether an empty filter combination returns a real page or an error
• Whether WordPress search result pages are being positioned as landing pages

4. Variable products and how variations are exposed

WooCommerce variable products offer "a set of different options on a product, with control over prices, stock, image, and more for each variation", built from attributes and selected by the shopper from dropdowns (WooCommerce, Variable products).

What that documentation does not describe is how a given store ends up representing a selected variation in the address bar, because that depends on the theme, the plugins, and how the store was built. So we check it on your pages rather than assuming it.

• Whether selecting a variation produces a distinct URL, and if so whether it resolves or canonicalises to the intended product page
• Whether marketing and tracking parameters are creating indexable duplicates of key pages
• Whether the price and availability a shopper sees match what the page reports to a crawler

5. WordPress pages that quietly become indexable

A WooCommerce store inherits everything WordPress creates. Author archives, date archives, paginated archives, media and attachment pages, tag pages from the blog, and the cart, checkout, and account pages all exist whether or not anyone intended them to be search destinations.

Most stores never look at them. We check which of them are indexable, which are linked, and which are absorbing crawling for no benefit — and, just as importantly, which ones are being blocked when they should not be.

6. Structured data, and whether more than one source is producing it

Product markup is what makes price, availability, and review information eligible to appear in richer search results (Google Search Central, Product structured data). On a WordPress store that markup can come from the theme, from WooCommerce, or from an SEO or review plugin — which is how a single product page ends up carrying more than one description of itself.

WooCommerce is one of those sources by default. Its own WC_Structured_Data class builds product markup in generate_product_data(), hooked into the woocommerce_single_product_summary action, with separate generators for breadcrumbs and reviews, and writes the result out on wp_footer (WooCommerce code reference, WC_Structured_Data). So on a WooCommerce product page the question is rarely "is there any markup". It is usually "how many copies are there, and do they agree".

• Product markup exists and describes the product, price, currency, and availability
• The marked-up values match what a shopper actually sees on the page
• Only one source is generating product markup, not a theme and a plugin in parallel
• Breadcrumb markup follows the real navigation path
• Review or rating markup appears only where the supporting reviews are visible on the page

WooCommerce product schema checks

Google separates two outcomes with different requirements, and knowing which one a store is aiming at changes how you read a validator's warnings.

• Product snippets require name, plus at least one of review, aggregateRating, or offers (Google Search Central, product snippet structured data).
• Merchant listing experiences require name, image, and offers, and inside the offer a price (or priceSpecification.price) and a priceCurrency in three-letter ISO 4217 form. availability, brand.name, description, aggregateRating, hasMerchantReturnPolicy, and shippingDetails are recommended rather than required (Google Search Central, merchant listing structured data).

Variable products are where WooCommerce's model and Google's diverge most visibly. Google's variant guidance describes a ProductGroup holding variants through hasVariant (or variants pointing back with isVariantOf), a productGroupID equivalent to the parent SKU, and variesBy naming the aspects that change, such as https://schema.org/color or https://schema.org/size. Where variants live on their own URLs, each needs a distinct crawlable URL; where they are all selected on one page, there should be a single canonical URL for the group (Google Search Central, product variant structured data). Most WooCommerce stores select variations on one page, which is a legitimate shape. The check is whether the markup and the URL behaviour describe the same shape as each other, and as section 4 found on your pages.

• Which software is emitting product JSON-LD, and whether a second copy exists from the theme or another plugin
• Whether the properties required for the outcome the store is aiming at are present, rather than only the ones a plugin happens to fill in
• Whether price and availability in the markup match the rendered page, including on a discounted product and an out-of-stock product
• Whether a variable product describes its variations at all, and if it does, whether the group and the variants are consistent with each other
• Whether aggregateRating is backed by reviews a shopper can see on the page
• Whether breadcrumb markup matches the permalink structure from section 1

Two limits we state in the report rather than leaving implied. Merchant listing eligibility depends on the page being one a shopper can buy from at a price above zero, so a catalog-only or quote-only page will not qualify however complete its markup is. And valid markup is an eligibility and clarity layer, not a ranking promise. We report it that way.

7. Plugin and theme overlap in titles, canonicals, and robots rules

This is the check with no equivalent on a hosted platform. WordPress lets several pieces of software write to the same part of the page, and a store that has changed hands a few times often has two SEO plugins installed, a theme with its own title logic, and a caching layer serving whatever was generated last.

The symptoms are recognisable: a title that differs between the page source and the search result, a canonical tag pointing somewhere unexpected, a noindex nobody remembers adding, or a sitemap listing URLs the site otherwise treats as private. We report what the live pages actually say, so you can decide which plugin should own each output.

8. Whether blog posts connect to anything you sell

WordPress makes publishing easy, so WooCommerce stores accumulate posts that answer research questions and then dead-end. The fix is not more content; it is contextual links from the guides you already have into the categories and products they discuss, with anchor text that names the destination.

WooCommerce SEO tips, written as things to check

Most WooCommerce SEO tips are written as work to do. These are the same points written as observations, because that is what a sampled review of public pages can honestly produce: what your live store shows, not what should be installed next.

• Check the site-wide visibility switch before anything else. WordPress's Reading settings include a Discourage search engines from indexing this site box, and since version 5.3 ticking it writes a noindex,nofollow robots meta tag into the head of the site (WordPress, Settings Reading screen). A store launched from staging with that box still ticked has one finding, and it outranks every other finding on the list.
• Count the sitemaps. WordPress has published a sitemap index at /wp-sitemap.xml since version 5.5, covering public post types and taxonomies, author archives, and the homepage, and it is switched off automatically when search engines are discouraged (WordPress core, new XML sitemaps functionality in 5.5). SEO plugins commonly disable it and publish their own instead. Worth establishing which one is live, which one was submitted, and whether the two list the same URLs.
• Read catalog visibility product by product. WooCommerce sets visibility on each product — shop and search, shop only, search results only, or hidden, where hidden leaves the product visible on its own page and nowhere else (WooCommerce, Product editor settings). A hidden product is still a live URL that has lost every internal link which used to point at it, which is a different problem from being noindexed.
• Treat the short description as real page copy. WooCommerce's short description is a summary of the long description, shown alongside the product and on listing pages (WooCommerce, Product editor settings). When it is the same paragraph on every product, the archives it feeds become hard to tell apart, and the question in section 2 about which archive deserves to be indexable gets harder to answer.
• Separate attributes that drive variations from attributes that create archives. Only an attribute marked used for variations feeds a variable product's variation options (WooCommerce, Product editor settings), but a global attribute can also generate an archive page of its own. Both surfaces are worth looking at, and they are rarely looked at together.

None of these is a claim about your store. They are the observations that recur across WooCommerce builds, and the report says which of them your sampled pages actually show.

What the $100 WooCommerce audit includes

WooCommerce audit questions