Ecomrank.ai
Start Free

WooCommerce SEO: permalinks, product pages, categories and the blog, without a plugin war

September 27, 2026·24 min read

WooCommerce SEO: permalinks, product pages, categories and the blog, without a plugin war

WooCommerce SEO is decided in four places you already own: the permalink screen, the product editor, the category screen and the posts you publish. WordPress and WooCommerce generate the sitemap, the robots.txt reference and the product structured data for you; what no plugin will ever do is choose your addresses, write your descriptions and link your pages to each other. This page goes through those four places in the order that pays when you run the store yourself, with the documents of WooCommerce, WordPress and Google cited at each step, and the plugin question settled once, at the end.

TL;DR

  • WordPress has published a sitemap at /wp-sitemap.xml since version 5.5 and lists it in robots.txt; WooCommerce writes Product, Review and BreadcrumbList structured data into every product page. You install nothing to get them (New XML Sitemaps Functionality in WordPress 5.5, Make WordPress Core, 22/07/2020, and WC_Structured_Data, WooCommerce code reference, both read on 27/09/2026).
  • Permalinks are set once, before launch, in Settings, then Permalinks: "Post name" for posts, one of four bases for products. WooCommerce's own note says that changing them later turns every old address into a 404 unless you set up redirects.
  • A product page is its slug, its own description of 150 to 300 words, a photo with alt text and its reviews. A category page is a slug, a description and a link to every product in it.
  • The blog is a WordPress post that answers a question a buyer types before knowing which product they want, linked to that product. It is in the sitemap the minute it is published.
  • In Google's Keyword Planner at the reading of 27/09/2026, "yoast woocommerce seo" shows about 170 searches a month and "woocommerce seo" 140: more people look for a plugin than for the practice. On a WooCommerce store we run ourselves, a technical score of 82 out of 100 goes with 92 posts out of 100 that never earned a single Google impression.

Table of contents

WooCommerce SEO: what WordPress and WooCommerce already do

WooCommerce describes itself, in its developer documentation, as an open-source ecommerce platform built on WordPress (WooCommerce developer docs, read on 27/09/2026). That one sentence settles half of the questions: everything WordPress does for a blog, it does for your store, and WooCommerce adds the product layer on top.

What WordPress does on its own. Since version 5.5, every public WordPress site exposes a sitemap index at /wp-sitemap.xml, built for every public post type and taxonomy, so your products, product categories, posts and pages are listed without a plugin. The robots.txt file WordPress serves points to that index, and each sitemap file holds up to 2,000 entries (New XML Sitemaps Functionality in WordPress 5.5, Make WordPress Core, 22/07/2020, read on 27/09/2026). Google's sitemap documentation says the same from its side: on a CMS such as WordPress the sitemap is most likely already there, and a sitemap helps a site that is new and has few links pointing to it, without guaranteeing that anything in it gets crawled or indexed (Learn about sitemaps, Google Search Central, last updated 10/12/2025, read on 27/09/2026).

What WooCommerce does on its own. On a product page it generates Product structured data, one Review block per customer review, a BreadcrumbList and a WebSite block, and prints them in the page footer (WC_Structured_Data, WooCommerce code reference, read on 27/09/2026). At install it creates the Shop, Cart, Checkout and My Account pages, and the /shop/ address cannot be deleted (WooCommerce Pages, WooCommerce documentation, read on 27/09/2026).

What is left to you, and it is the whole job: the shape of your addresses, the words on product and category pages, the links between them, the posts, and two fields core WordPress does not have, the page title and the meta description. Those two fields are the one thing a plugin genuinely adds; we come back to them at the end.

One warning before you go looking for the official WooCommerce SEO page: at the reading of 27/09/2026, the address woocommerce.com/document/seo/ that older guides still link to redirects to an image file. The platform's current guidance is a post from its own team, Ecommerce SEO in 2026: what to know when you're starting out (Kevin Bates, WooCommerce, 13/05/2026, read on 27/09/2026), and the settings themselves are documented page by page. Both are cited below.

Before the settings: the checkbox and Google Search Console

WooCommerce's guide puts one check before everything else: in Settings, then Reading, the box "Discourage search engines from indexing this site" must be unchecked, because it keeps Google out quietly until someone notices (Ecommerce SEO in 2026, read on 27/09/2026). The WordPress documentation says what the box does: since version 5.3 it writes a robots meta tag with noindex,nofollow into every page, and it is up to search engines to honor it (Settings Reading screen, WordPress documentation, read on 27/09/2026). Since 5.5 it also switches the sitemap off (Make WordPress Core, 22/07/2020, cited above). A store built with the box ticked to keep the draft out of Google, then launched with the box still ticked, is the most silent failure WooCommerce has.

Then Google Search Console, which Google's launch guide puts at step one for a new store: verify ownership, ask for indexing (the URL inspection tool for a few pages, a sitemap for many), then follow the Page indexing report (How to launch a new ecommerce website, Google Search Central, last updated 10/12/2025, read on 27/09/2026).

Verify the store

Google offers several methods; two matter on WordPress (Verify your site ownership, Google Search Console Help, read on 27/09/2026):

  • HTML tag, for a URL-prefix property (https://yourstore.com): a <meta name="google-site-verification"> tag placed inside the <head> of your home page, on a page that does not require a login. Core WordPress has no field for it: it goes in through your theme's header option, or through a plugin option that inserts code into the head.
  • Domain name provider, for a Domain property (yourstore.com, every protocol and subdomain at once): a TXT record added at your registrar. Nothing to edit in WordPress, and the verification survives a change of theme.

Submit the sitemap

In Search Console, Indexing, then Sitemaps, type the address of your sitemap and submit it. WooCommerce's guide gives the default address, yoursite.com/wp-sitemap.xml, tells you to expect indexing to take a couple of weeks, and names the error beginners meet most often, "submitted URL not found", which usually means a product was deleted or its address changed (Ecommerce SEO in 2026, read on 27/09/2026). If you install an SEO plugin, it may replace the core sitemap with its own at another address: submit that one, and only one.

The three numbers, in the order to read them

  1. Pages indexed (Indexing, then Pages). Indexed pages can appear in results; the others cannot. Read the reasons given for the excluded ones before you touch anything else.
  2. Queries (Performance, then Queries). If the list is your store name and nothing else, your pages do not carry the words buyers type yet.
  3. Clicks (Performance). The number that pays. Compare the same weekdays four weeks apart, and give any change a month before judging it.

This site is a live example of what those numbers look like on a young domain. At the reading of 27/09/2026, ecomrank.ai had 26 articles in its sitemap after a clean-up done that day, 17 of the 36 URLs Google knew about were indexed, 13 had never been requested by Google at all, and Google had sent 0 clicks in the 7 days before the reading. A sitemap submitted is not a page read, and a page read is not a visit. How long SEO takes for a new online store gives the realistic timeline.

WordPress ships with "Plain" permalinks, addresses of the form example.com/?p=123, which its documentation describes as working everywhere but not user-friendly and not optimized for search engines (Customize permalinks, WordPress documentation, last updated 28/06/2025, read on 27/09/2026). The same page lists the six choices and the rule that gives permalinks their name: they are permanent and should never be changed. Go to Settings, then Permalinks, and choose "Post name": example.com/post-name/. The optional Category base and Tag base fields prefix your post archives (category and tag by default); you can change the words, not remove them.

WooCommerce adds its own block to the same screen, Product permalinks, with four options (Permalinks, WooCommerce documentation, read on 27/09/2026):

Option Product address
Default example.com/product/hoodie-with-logo (with plain permalinks it falls back to example.com/?product=111)
Shop base example.com/shop/hoodie-with-logo
Shop base with category example.com/shop/hoodies/hoodie-with-logo
Custom base example.com/superstore/hoodie-with-logo, the word is yours

Below it, the Optional section sets three bases: Product category base (product-category by default, giving example.com/product-category/accessories), Product tag base (product-tag) and Product attribute base (empty by default, giving example.com/size/medium, and only reachable when archives are enabled for that attribute). WooCommerce's advice on the page is to keep structures as short as possible and to include words that relate to the content, and its warning is that a custom base must not be the same word as the category base, because WordPress needs to tell a category from a product.

Which one to pick. "Shop base with category" is the most descriptive, and Google's URL guide does say that descriptive words in a path may help it understand the page (Designing a URL structure for ecommerce sites, Google Search Central, last updated 10/12/2025, read on 27/09/2026). It also ties every product address to a category: since WooCommerce 10.5, when a product sits in several categories, the deepest one is used in the address, and the platform redirects the old address to the new one with a 301 on its own (Product Permalink Changes Coming in WooCommerce 10.5, WooCommerce Developer Blog, 13/01/2026, read on 27/09/2026). If you reorganize categories often, "Shop base" or the default /product/ gives you addresses that never move. Google's same guide says that on an ecommerce platform the URL work has most likely been done for you, so the honest answer is: any of the four, chosen before launch, and never changed afterwards.

Why never. WooCommerce's note on the permalinks page is explicit: changing the structure updates the address of every existing product, and links already shared or already in a search engine's index return 404 errors unless you set up redirects. Google's canonical documentation ranks a permanent redirect as the strongest signal it has for moving a page (How to specify a canonical URL, Google Search Central, last updated 10/07/2026, read on 27/09/2026), so a change is survivable, but it is one redirect per product, written by you. One last detail from the same WooCommerce page: if product pages return 404 right after a permalink change, open Settings, then Permalinks, and click Save Changes again without editing anything; WordPress regenerates its rewrite rules on save.

Product pages: slug, description, image, reviews

Everything below happens in the product editor, whose fields are documented one by one (WooCommerce Product Editor settings, WooCommerce documentation, read on 27/09/2026).

The slug. WooCommerce generates it from the product name on the first save, and changing the name later does not change the slug: you edit it with the Edit button next to the address under the name field, or in the Slug panel. Set it before you publish, in the buyer's words, short: stoneware-pour-over-mug rather than the full marketing name. WooCommerce's guide gives the rule in one line, short, clean, keyword-first, and the counter-example of an address that stacks several levels of category folders (Ecommerce SEO in 2026, read on 27/09/2026).

The description. The same guide asks for 150 to 300 words that do three things at once: tell readers and robots what the page is about, answer the questions a customer has before buying (condition, compatibility, what is included, what to expect on arrival) and sell. Its example is a buyer typing the exact name of a vinyl pressing and landing on a page with a photo and a price: they leave for the competitor who described the pressing. The Product description field accepts text, images, video and tables; the Product short description sits next to the images on listing pages, one sentence of benefit and format. A supplier text pasted as is exists on every other store selling the item: the method for writing your own, with three filled examples, is in how to write product descriptions.

The image. The editor documentation says the product image is what search engines and social networks pick up for listings off your site. Name the file with the product's words before upload and write the alt text as a description of what is shown: the WooCommerce guide's own contrast is "Miles Davis Kind of Blue vinyl" against "product image 3".

Reviews. Each product has an Enable Reviews switch. Every published review becomes a Review structured data block generated by WooCommerce (code reference, cited above), and Google's Product structured data documentation lists ratings and reviews among the enhancements a product result can show (Intro to Product structured data, Google Search Central, last updated 10/12/2025, read on 27/09/2026). Reviews are the only text on the page you do not write yourself; how to get the first ones when you sell little is in product page SEO, reviews included.

What ties these four together is the checklist in how to rank a product page on Google: title in the buyer's words, readable address, a description of your own, pre-sale questions answered, your own photos, reviews on display, facts in the text that match the markup, and a link from a category and from an article.

Categories, tags and attributes: which pages deserve to exist

WooCommerce gives you three ways to group products, and each one creates public pages (Managing Product Categories, Tags and Attributes, WooCommerce documentation, read on 27/09/2026).

Categories are hierarchical, one parent per subcategory, and WooCommerce's own recommendation is to keep things as simple as possible. Each one has a Name, a Slug, a Parent, a Description that some themes display under the category name on its page, a Display type (subcategories, products, or both) and an image. Two consequences for search. First, the category page is the page that catches the searches no single product can win: "pour-over mugs", "linen napkins", "gift sets under 50". Give it the buyer's term as name and slug, and use the Description field for a paragraph of your own on who the products are for and how to choose among them; a grid of thumbnails under a title says nothing to Google. Second, every product must be in a category, and the default one is called "Uncategorized": rename it or make another category the default before a single product lands on /product-category/uncategorized/.

Google's guide on site structure says how it reads those pages: it analyzes the links between pages, not the shape of the URLs, to work out which pages matter; it wants menus to link to category pages, category pages to subcategories, and subcategories to all the products in them, because Googlebot does not type into your search box and a product only reachable through search may never be found (Help Google understand your ecommerce site structure, Google Search Central, last updated 10/12/2025, read on 27/09/2026). It adds that a best seller linked from the home page and from posts is read as more important. WooCommerce's guide says the same in shop terms: any product within three clicks of the home page, with breadcrumbs showing the path.

Tags have no hierarchy and are meant for a characteristic that cuts across categories, WooCommerce's example being "Cotton" across men's, women's and children's clothing. Each tag gets a public archive at /product-tag/.... Google's URL guide asks you to avoid linking to, or at least indexing, pages without useful content, and to noindex or return a 404 for an empty category (Designing a URL structure for ecommerce sites, read on 27/09/2026). A tag with one product behind it is that kind of page. Use tags when a group of products genuinely shares a trait a buyer searches for, and not as a second set of keywords.

Attributes (size, color, material) define variations and power filters. Their archive pages exist only if you tick "Enable archives" on the attribute, and the permalinks documentation says the same: the attribute base URL only answers when archives are on. Leave that box unticked unless a page listing every black item is a page a buyer would search for.

The longer version of what to write on a category page is in your collection pages, the most neglected asset, and the method for finding the buyer's words without a paid tool is in the words your buyers actually type.

The blog: a WordPress post linked to a product

On WooCommerce the blog is not a feature to install: it is WordPress itself. Posts get the "Post name" address you chose, appear in the core sitemap under the posts section the minute they are published (Make WordPress Core, 22/07/2020, cited above), and can carry the same page title and meta description fields as a product once a plugin provides them.

WooCommerce's guide explains what it is for: a product page targets someone who already knows what they want, a post targets someone earlier, curious or comparing or trying to solve a problem, and the post that answers the question and links to a product builds a path search engines can follow. Its examples are a record store answering "how do I know if a record is warped" and linking to a cleaning kit, or explaining the difference between 180 g and standard vinyl and linking to a category of audiophile pressings. The same guide adds a rule worth keeping: be picky, because what goes on the blog represents the store (Ecommerce SEO in 2026, read on 27/09/2026).

Two mechanics on WooCommerce specifically. Every post links to one product page, in the text, with the product's name as the link text: Google's structure guide asks for real <a href> links with meaningful text, never "click here", and reads a product linked from posts as more important. And the product links back: the description of a product can point to the post that answers the question buyers ask about it, which is the link from an article that closes the product checklist above.

Which questions to write about, taken from your own catalog, and how often to publish when you run the store alone are in ecommerce blog: how to make it sell. If posts exist and nothing comes, the three causes to check, in order, are in why my store blog gets no traffic.

Structured data: what WooCommerce writes, and what has to match

Google's ecommerce guide lists the structured data types that matter for a store, Product, BreadcrumbList, Organization and Review first, with LocalBusiness when you also have a physical shop, and says that on a platform an extension or plugin is easier than markup written by hand (Include structured data relevant to ecommerce, Google Search Central, last updated 10/12/2025, read on 27/09/2026). On WooCommerce that plugin is the platform: the code reference cited above generates Product, Review, BreadcrumbList and WebSite data by default, and validates a GTIN as a string of 8, 12, 13 or 14 digits.

Google's Product documentation separates two cases: product snippets, for pages where people cannot buy, and merchant listings, for pages where they can, the second carrying more detail on sizes, shipping and returns; it also says that structured data on the page plus a Google Merchant Center feed maximizes eligibility, and that a feed can fill a price the page markup lacks (Intro to Product structured data, cited above). Your job is not to write any of it. It is to keep the visible page and the markup saying the same thing: a price only present in an image, a size chart saved as a photo, a stock status in a theme block the markup does not read, are the places where the two diverge. And if you add an SEO plugin that also writes Product markup, check the page source once: two Product blocks on one page is a job done twice.

The plugin question, settled once

The Keyword Planner shows where the attention goes. At the reading of 27/09/2026, "yoast woocommerce seo" shows about 170 searches a month, "woocommerce seo" 140, "woocommerce seo plugin" 50, "best seo plugin for woocommerce" 30, and "woocommerce permalinks" 10. The plugin's name is typed more often than the practice, and the permalink screen, where the one irreversible decision lives, almost never.

What a plugin genuinely adds, and it is real:

  • The page title and meta description fields. Core WordPress has none, and WooCommerce's guide puts them first among the six places a keyword goes, with a title under 60 characters and a description of about 155 characters that does not affect ranking but decides whether someone clicks.
  • A more detailed sitemap than the core one, in WooCommerce's guide's words, with the last-modified dates the core sitemap leaves out.
  • Settings for the Shop page, which is a product archive rather than a normal page: the WooCommerce Pages documentation says that an SEO plugin may include settings specific to custom post type archives, and that those are where the Shop page's search behavior is controlled (WooCommerce Pages, read on 27/09/2026).
  • A canonical setting, which Google's documentation says a CMS usually exposes through a search engine settings page rather than in the HTML (How to specify a canonical URL, cited above).

What no plugin adds, measured on a WooCommerce store we run ourselves: a store selling guided audio and ebooks for sleep and calm, on a WordPress theme with a free SEO plugin scoring the site about 82 out of 100. At the reading of 20/09/2026 it had 100 blog posts, and 92 of them had never received a single Google impression. Of the clicks it does get, 79 percent come from searches for its own name, and its domain rating is 1.2. The page that beats it on one of its target queries is 358 words long with an audio player on it; ours is 3,019 words with none. Five unused advertising plugins were deactivated on 07/09/2026 and changed nothing to page speed: three product pages still took 13 seconds to show their main image, and a cache plugin was the next step. The lesson costs nothing to read: the fields were filled, the score was green, and the bottleneck was links from other sites and what the page offered, neither of which a plugin sells.

So: one SEO plugin, the free tier, installed once for the four items above, with its sitemap submitted instead of the core one, and a cache plugin because a slow product page loses the buyer before it loses Google. Then close the plugin directory and open the product editor.

The WooCommerce SEO checklist

Once, before launch:

  1. Settings, then Reading: "Discourage search engines from indexing this site" unchecked.
  2. Settings, then Permalinks: "Post name" for posts, one of the four product bases, category and tag bases left as they are, and never changed afterwards.
  3. Search Console verified, by HTML tag in the head or by DNS record at the registrar.
  4. One sitemap submitted, the core /wp-sitemap.xml or the plugin's, never both.
  5. The default product category renamed from "Uncategorized".
  6. One SEO plugin for titles and descriptions, one cache plugin, and no second plugin that writes Product markup.

On every product:

  1. A slug in the buyer's words, set before publication.
  2. A page title under 60 characters and a distinct meta description of about 155 characters.
  3. A description of 150 to 300 words of your own that answers the pre-sale questions.
  4. A photo named and described in the product's words.
  5. Reviews enabled, and asked for.
  6. One link in from its category, one from a post, and one link out to the post that answers its question.

On every category:

  1. Name and slug on the term buyers type, a paragraph of your own in the Description field.
  2. Every product in it linked from the page, subcategories linked from the parent.
  3. No tag or attribute archive left public with nothing behind it.

Every month:

  1. Pages report read, with the reasons for the excluded pages.
  2. Queries report read: are they the words you chose, or only your store name?
  3. Clicks compared with the same weekdays four weeks earlier.

The mistakes that cost you

  • Launching with the search engine box still ticked. Every page carries a noindex tag and the sitemap is off; nothing else on this list matters until it is unticked.
  • Changing the product permalink base on a store that already sells. Every product address dies at once, and each one needs its own redirect. WooCommerce's documentation says it; the permalink screen does not warn you.
  • Copying the supplier's description. It exists on every other store selling the item, and WooCommerce's guide says the buyer who typed a precise query leaves for the page that described the product.
  • A category page that is only a grid. The Description field is empty on most stores; it is the only text Google has to understand what the category is for.
  • A tag for every adjective. Each one is a public page, and Google asks you not to link to pages without useful content.
  • Two sitemaps submitted, or the wrong one. After a plugin is installed, the core sitemap may be off; check which address answers before you submit.
  • Blocking purchases to keep the store "private" while it is being built. Google's launch guide says not to disable add-to-cart as a way of stopping purchases, because it uses it to verify final prices; use the reading setting or a password during the build, then remove it.
  • Judging the store on its desktop version. WooCommerce's guide states that Google ranks the mobile version of your site and puts more than 70 percent of ecommerce purchases on mobile; open your own product page on your phone before you open the Search Console.

Where to start this week

Open Settings, then Reading, and Settings, then Permalinks, and look, without changing anything on a store that already sells. Verify the store in Search Console, submit one sitemap, note today's indexed count. Then take the five products that make you the most money and their categories and run items 7 to 15 of the checklist on each of them. Count an hour for the first page and less for the next ones. The following week, five more.

That leaves the blog, the part that never ends on any platform: finding the questions buyers type before they know which product they want, writing the posts, publishing them and linking each one to the right product page. That is exactly what Ecomrank does for WooCommerce and Shopify stores: it connects your store, imports your catalog, writes articles around that catalog, publishes them on your store blog and links them to your product pages. The trial is free for 7 days, a card is requested to start it, and you can cancel anytime.

Start your free trial