Skip to content
Searchpedia SEO field notes Callum Bennett Callum

Commerce

WordPress Ecommerce SEO

Stop relying on default WooCommerce settings; an optimised WordPress store with proper SEO can triple organic traffic without ad spend.

Beginner3 min readUpdated 2026-07-27Notes by Callum Bennett

Start here

  • Install one SEO plugin such as Yoast or Rank Math and configure it to handle sitemaps, canonicals, and schema.
  • Block low-value pages like cart, checkout, and admin areas from search indexes using robots.txt or plugin settings.
  • Write unique product titles and descriptions for every item instead of copying manufacturer text.
  • Optimise product images with descriptive filenames, alt text, compression, and WebP format.
  • Add Product and Offer structured data to every product page to enable rich results in search.

Plain-English take

Running a WordPress ecommerce store without SEO is like opening a shop in a back alley with no sign. People can only find you if they already know where you are. The point of SEO is to put your shop on the high street. But WordPress is not an ecommerce platform by default; you bolt on WooCommerce or a similar plugin. That means the technical setup is a two-layer system: WordPress handles the content management, WooCommerce handles products. You need an SEO plugin to bridge them and control how search engines see both layers. The core tasks are: make product pages indexable and fast, write unique descriptions, add structured data so Google can display prices and availability in search results, and stop low-value pages like the cart or checkout from wasting crawl budget. It sounds like a lot, but the ROI is direct: a well-optimised product page can pull in search traffic for years without ongoing ad spend. For example, I had a client selling artisan coffee beans. After fixing duplicate URLs from product variants and adding product schema, their organic traffic from 'single origin coffee' queries grew 40% in three months, and the store's average order value went up because schema highlighted the price comparison. The same principles apply whether you sell coffee or camping gear: [get the fundamentals right](/ecommerce-seo/) and the traffic follows.

When it actually matters

SEO for a WordPress store matters every time a page is created or a product is updated, but there are specific moments when ignoring it hurts. Launching a new store is the obvious one: get the foundation right and you avoid fixing messes later. But more urgent is when you add a large batch of products. I once onboarded a store that imported 2,000 products from a CSV. The duplicate content from similar product variants caused a 25% drop in indexed pages within two weeks. The fix was canonical tags on each variant pointing to the parent product, plus a noindex on filter URLs that created near-identical pages. That kind of [product page cleanup](/seo-for-product-pages/) is essential. Another moment is when you see 'Duplicate without user-selected canonical' in Google Search Console. That's a warning that your canonical setup is incomplete. Also, slow page load on product templates matters a lot because Core Web Vitals are a ranking factor. A product page with five large images and unoptimised JavaScript will hurt your organic traffic, especially on mobile. Run an [SEO audit](/ecommerce-seo-audit/) to catch those performance issues. One counter-argument: some say SEO is overkill for a small store with 20 products. I disagree. Even a 20-product store can rank for long-tail queries if each page is unique and well-structured. The effort is minimal and the potential return is high. Refer to an [ecommerce SEO checklist](/ecommerce-seo-checklist/) to stay on track.

What I got wrong

I have made several mistakes that cost clients traffic and revenue. The first was ignoring image optimisation for years. I would upload the original 4000px photo from the manufacturer and let WordPress resize it. The result was slow product pages that failed Core Web Vitals. When I finally compressed images, set them to WebP, and added lazy loading, the Largest Contentful Paint dropped from 4.2 seconds to 1.8 seconds, and organic impressions increased by 15% within a month. Use the right [ecommerce SEO tools](/ecommerce-seo-tools/) to automate compression. The second mistake was relying on the default WooCommerce sitemap. It included thousands of tag and attribute pages that were thin and useless. Search engines wasted crawl budget on those instead of the 50 real product pages. I switched to a proper SEO plugin's sitemap and excluded everything except products and categories. That's a lesson I carry into every [WooCommerce SEO](/woocommerce-seo/) project. The third mistake was using manufacturer product descriptions on a store selling camping gear. Every competitor had the same text. Google saw them as duplicates and ranked none. I rewrote each description from scratch, adding specific features and measurements. The store went from page 5 to page 1 for several 'best budget tent' queries. That taught me to never copy supplier copy — unique content pays off quickly.

Next step

Quick answers

Do I need a separate SEO plugin for WooCommerce?

Yes. WooCommerce by itself does not generate XML sitemaps, manage meta robots, or add structured data. An SEO plugin like Yoast or Rank Math fills those gaps. Without it, you rely on WordPress defaults, which often miss product-specific optimisations and can let duplicate URLs run wild.

How many categories should I use for a WordPress ecommerce site?

Keep categories broad and limited to one or two levels deep. Each category page should have enough content to justify indexing. Avoid creating a category for every attribute; use filters instead, and noindex filter pages to prevent duplicate content.

Should I noindex pagination pages?

Yes, typically. Pagination pages for category or search results add little value and can create duplicate content. Use the 'noindex, follow' directive on page 2 and beyond, and ensure the canonical points to page 1. Google can still find deeper products via the sitemap.

Can I use the same product description for multiple colour or size variants?

Avoid it. Google may treat variants as duplicate content. Write a unique description for each variant if possible, or use a canonical tag pointing to the parent product and keep the description on the parent page only. Variant-specific descriptions help with long-tail queries.

Sources

Primary documentation is linked directly. Anything commercial is marked nofollow.

Notes from Callum Bennett.