syted

syted blog

Ecommerce Category Page SEO: What Ranks, Measured

The highest organic result in the US for "ecommerce category page seo" is a Reddit thread. Not a guide, not a vendor doc: a question posted in r/SEO titled "Ecommerce SEO - Should you focus on Category Pages or Product Pages", holding position 2 under the AI Overview with an estimated 363 visits a month. The guides from Semrush, Baymard, BigCommerce and seoClarity sit below it, pulling 172, 84, 62 and 39 visits.

That ordering is the brief. When a forum thread outranks four vendor guides on a query, Google is telling you the searcher has a decision to make and nobody has answered it well. The guides answer a different question, which is what to put on the page.

This article answers the decision first, with numbers pulled from live SERPs on 2026-11-20, then works through the technical handling that the two best-ranking guides either skip or get wrong. Every Google claim here is quoted from the current documentation, because two of the recommendations those guides make have expired.

Category page or product page: the measured answer

For a commercial head term, the organic slot goes to the category page. We bought the SERP for womens running shoes (6,127 searches a month in the US, parent topic running shoes for women at 29,763) and read Ahrefs' predicted page type for every organic result.

Pos Organic result DR Est. traffic Page type
3 adidas.com/us/women-running-shoes 87 9,025 Listing_Collection/Product
5 roadrunnersports.com/category/womens/shoes/running 70 4,829 Listing_Collection/Product
6 dickssportinggoods.com/f/womens-running-shoes 83 4,844 Listing_Collection/Product
7 runnersworld.com/gear/a25578469/best-running-shoes-for-women/ 85 13,774 Article/Listicle
9 nike.com/w/womens-running-shoes-37v7jz5e1x6zy7ok 91 9,049 Listing_Collection/Product
10 relaygoods.com/collections/womens-running-shoes 29 1,799 Listing_Collection/Product

Five of the six organic web results are category pages. Zero are product detail pages.

Individual products are on the page, but they arrive through a different door. Positions 2 and 8 are blocks of ten shopping results each (Hoka Clifton 10, Nike Pegasus 41, Brooks Revel 9), served from merchant feeds rather than from a store's own product page ranking organically. Your product competes there through product data, not through the page copy you rewrote.

So the answer to the thread is: both, for different queries. The category page is the only page you own that can take the head term. The product page takes the query with a model name in it, which is smaller and much more specific.

Here is that split, measured on the same catalogue:

Query Volume KD The page that answers it
running shoes for women 29,763 18 category page
best running shoes for women 30,846 18 an article, not a category page
womens trail running shoes 1,183 5 subcategory page
nike pegasus 41 womens 289 n/a product page

Note the second row. best running shoes for women carries 30,846 searches and a traffic potential of 26,000, and it is the reason Runner's World sits at position 7 with the highest estimated traffic on the page. No category page wins that query, because the searcher wants a judgement, not a grid. That demand belongs to content a store publishes alongside the catalogue.

The small-store result worth staring at

Position 10 on that SERP is relaygoods.com, a Shopify collection page, at domain rating 29. It holds a position against Nike (91), adidas (87), Dick's (83) and Road Runner Sports (70).

Read that honestly, because it is easy to oversell. Ahrefs attributes 1,799 estimated monthly visits to that URL, and the page's own top keyword is running shoes for women, so what the row proves is the position, not that the traffic came from this one query. What it does establish is that a small catalogue page is not locked out of a head commercial SERP by domain rating alone. No one can guarantee you that position, and the ranking could change next week.

What it does not establish is that the page got there by having a longer description than Nike's. It got there with a specific, well-structured collection that matches the query exactly, which is a cheaper thing to build than authority.

Which filters deserve a URL, measured

This is where most stores lose. Your platform will happily generate thousands of filtered URLs, one per facet combination, and the question is which of those deserve to be crawled and indexed at all.

Demand answers it. We measured every filter a running-shoe category would plausibly expose:

The URL a filter would create The query behind it Volume KD
/collections/womens-running-shoes running shoes for women 29,763 18
?type=trail womens trail running shoes 1,183 5
?color=black black womens running shoes 1,109 0
?price=discount cheap womens running shoes 660 6
?size=8 womens running shoes size 8 41 10
?width=wide wide womens running shoes 34 3
?type=trail&width=wide womens trail running shoes wide 4 n/a
?price=under-100 womens running shoes under 100 3 n/a

Three single facets carry real demand. Type, colour and price range are worth a crawlable, indexable page, and womens trail running shoes at KD 5 is an easier target than the parent at KD 18.

Size and width are not. Forty-one searches a month for a size filter does not pay for a page, and two facets combined collapse to 4 and 3 searches. A store that indexes every combination of six filters is asking Google to crawl thousands of URLs that together serve single-digit demand.

One trap in that table. wide womens running shoes shows 34 searches but its parent topic is running shoes with wide toe box with a traffic potential of 350, which means the demand exists and sits on a different page than the one you would build. Always read the parent topic before giving a facet its own URL, the same way you would before giving a keyword its own article.

What Google actually says about faceted navigation

Google's guidance on faceted navigation is explicit, and it starts from crawl cost rather than from ranking. The documentation warns that filter URLs can create "infinite URL spaces", causing overcrawling and slower discovery of new pages.

If you do not want those URLs indexed, the page gives four options and ranks them:

  • Block crawling in robots.txt. Disallow the filter parameters, and allow the item pages and the unfiltered listing. Google's own example disallows products=, color= and size= while allowing /*?products=all$.
  • Put filters behind a URL fragment. Google states that "Google Search generally doesn't support URL fragments in crawling and indexing", so a # filter is invisible either way.
  • rel="canonical" on the filtered URL, pointing at the unfiltered page. Google says this "may, over time, decrease the crawl volume of non-canonical versions of those URLs" but is less effective long term than the two above.
  • rel="nofollow" on every link to a filtered page. Same verdict: it may help, and every single link to that URL has to carry the attribute.

If you do want some facets crawlable, which the demand table above says you should, Google asks for three things: use & as the parameter separator rather than commas or brackets, keep filter order consistent when filters live in the path, and return a real 404 for filter combinations with no results, duplicate filters, nonsensical combinations and nonexistent pagination URLs. Do not redirect those to a generic error page.

That last instruction is the one stores skip, and it is the reason a ?type=trail&width=wide&color=black page serving zero products should not return a cheerful empty grid with a 200 status.

The robots.txt error in the guide ranking fourth

The Semrush guide at position 4 was published on 12 January 2024 and carries no update date. In its faceted navigation section it says robots.txt stops search engines from indexing faceted URLs. That is wrong, and the distinction matters for anyone trying to clean up an index.

Google's robots.txt introduction says it directly:

While Google won't crawl or index the content blocked by a robots.txt file, we might still find and index a disallowed URL if it is linked from other places on the web.

And more bluntly, on the same page: "If your web page is blocked with a robots.txt file, its URL can still appear in search results." The tool for keeping a page out of the index is noindex, delivered as a meta tag or an HTTP header, and Google's recommendation is to "block indexing with noindex or password-protect the page".

The practical consequence is a sequence, not a choice. A filtered URL already indexed cannot be removed by adding a robots.txt disallow, because blocking the crawl stops Google from ever seeing the noindex you also added. Serve noindex first, let the URLs drop out, then disallow the parameter to save the crawl budget. Doing it in the other order is a common reason pages stay in the index long after someone "fixed" them.

Canonicals: a strong signal, not a command

Category pages generate near-duplicates faster than any other page type on a store: filtered views, sort orders, session parameters, a /collections/all version of the same grid. The canonical tag is how you declare which one you want.

Google describes rel="canonical" as "A strong signal that the specified URL should become canonical", and says of the canonicalisation methods that "none of them are required". When you declare nothing, "Google will identify which version of the URL is objectively the best version to show to users in Search".

Your declaration can lose. Search Console's URL Inspection tool reports two separate fields, and the gap between them is the whole point:

  • User-declared canonical, the URL your page declares.
  • Google-selected canonical, "The page that Google selected as the canonical (authoritative) URL when it found similar pages on your site".

Google's own help page states that it "might select the user-declared canonical, but sometimes Google might choose another URL", and that "There is no guarantee that Google will choose your preferred canonical". The Page indexing report has a dedicated status for the mismatch: "Duplicate, Google chose different canonical than user".

Check that field on three category URLs before you believe your canonical strategy works. On a platform that generates duplicate paths for you, the declaration and the selection disagree more often than store owners expect, which is the same failure mode behind Shopify's four addresses for one product.

Pagination: page 2 is not a duplicate of page 1

Two pieces of advice still circulating are dead, and one of them appears in the guide at position 4.

rel="next" and rel="prev" no longer do anything for Google. The current ecommerce pagination documentation says plainly: "Google no longer uses these tags." Other engines may still read them, so leaving them in place is harmless, but adding them solves nothing.

Canonicalising page 2 to page 1 is worse than useless. Google's instruction is "Don't use the first page of a paginated sequence as the canonical page", and each page in the sequence should have its own canonical URL pointing at itself. Collapse the sequence into page 1 and you tell Google that the products on pages 2 through 14 live on a URL where they do not appear.

What Google does want is crawlable links. The documentation asks you to "include links from each page to the following page using <a href> tags", and suggests linking back to the first page of the collection too. Googlebot does not click buttons: on infinite scroll and load-more patterns, Google states its crawlers "don't 'click' buttons and generally don't trigger JavaScript functions that require user actions".

A load-more button with no underlying <a href> is a catalogue that ends at product 24, whatever the shopper sees.

Structured data on a category page: what it can and cannot win

Here the ranking guides are selling you work that no longer pays. The Semrush guide recommends ItemList, AggregateRating and FAQ markup on category pages. Two of those three have no rich result behind them today.

FAQ rich results are gone. Google's structured data changelog records the deprecation notice added on 8 May 2026, stating that the feature "will no longer appear in Google Search starting May 7, 2026", followed by the removal of the documentation itself on 15 June 2026 with the note that "The FAQ rich result feature is no longer shown in Google Search results". FAQPage remains valid schema.org vocabulary. It just buys you nothing in Google's results, so adding it to a category page in 2026 is a task with no payoff.

ItemList alone is not eligible for anything. The carousel documentation is specific: a host carousel requires ItemList markup combined with one of four supported features, Course list, Movie, Recipe or Restaurant. A product listing is not on that list. Google also repeats the standard caveat that it does not guarantee any feature will appear.

What Google's own ecommerce structured data page recommends is a short list: Product and ProductGroup, BreadcrumbList, Review, Organization, LocalBusiness, VideoObject. It says nothing about marking up a listing page's grid.

That leaves BreadcrumbList as the one piece of markup with a documented result on a category page, since it can produce a clearer breadcrumb trail in the SERP:

{
  "@context": "https://schema.org",
  "@type": "BreadcrumbList",
  "itemListElement": [
    {
      "@type": "ListItem",
      "position": 1,
      "name": "Women",
      "item": "https://example.com/collections/womens"
    },
    {
      "@type": "ListItem",
      "position": 2,
      "name": "Running Shoes",
      "item": "https://example.com/collections/womens-running-shoes"
    }
  ]
}

Structured data is not a ranking factor, and no markup makes a thin category page rank. It changes how an already-ranking result is displayed, which is worth ten minutes and not worth an afternoon. The rest of the markup inventory belongs on product pages and the store's organisation data.

Thin and empty categories are soft 404s

A category page with two products in it, or none, is a liability rather than a weak asset.

Google's definition of a soft 404 is a page that returns a success status while the content "suggests an error for Google Search, an empty page or an error message". Search Console reports those under Page indexing, and they are the natural output of a store that auto-generates a page for every tag and every filter combination.

This is the same mechanism as the 404 instruction in the faceted navigation guidance. An empty filter combination should return 404, not an empty grid with a 200 status, and a category that exists only because someone created a tag once should be merged into its parent.

Two checks worth running before anything else:

  1. Open Search Console, Page indexing, and look for "Soft 404". Every URL there is a page you are asking Google to crawl for nothing.
  2. Count products per category in your admin export. Anything under five products is a candidate for merging upward, and on most platforms the auto-generated tag pages are where the empties hide.

How to tell whether your category pages earn anything

None of the above matters if you cannot see the result, and this is the section missing from every guide on that first SERP: neither the Semrush article nor the Baymard article mentions Search Console at all.

The measurement is a URL-path comparison. Category URLs share a prefix on every platform (/collections/ on Shopify, /product-category/ on WooCommerce, whatever your path is), so you can read the two page types against each other.

In Search Console, open Performance, then Search results:

  1. Add a filter on Page, set it to Custom (regex), and enter the category prefix, for example ^https://example\.com/collections/.
  2. Note clicks, impressions and average position for the last three months.
  3. Swap the regex for the product prefix (/products/) and note the same three numbers.
  4. Compare the ratio of impressions to clicks. Category pages with impressions and no clicks are ranking on page three for head terms, which is a position problem. Product pages with neither are an indexing problem.

Then go one level deeper on the pages that show impressions. Switch to the Queries tab with the page filter still applied, and read what each category page actually gets shown for. A collection ranking for the brand name of one product in the grid is mislabelled, and a collection with impressions on a query you never targeted is usually the subcategory you should have built.

Run that comparison before and after any of the work in this article, and keep the numbers. Three months of clicks per page type is worth more than any checklist, including this one, and it is the same discipline as a content audit on a blog.

What to do first, in order

The order matters more than the list, because the first two items change what the rest of them are worth.

  1. Measure the split. Search Console regex on category and product prefixes, three months, write down the six numbers.
  2. Measure facet demand. For every filter you expose, pull the volume of the query it would target, and read the parent topic. Keep the ones with real demand, and decide the fate of the rest.
  3. Fix indexation in the right order. noindex first on the facets you do not want, then robots.txt disallow once they have dropped out.
  4. Return 404 on empty combinations, and merge categories with almost no products.
  5. Check the Google-selected canonical on three category URLs in URL Inspection.
  6. Fix pagination links so each page has a real <a href> to the next and its own self-referencing canonical.
  7. Add BreadcrumbList, and skip FAQ and ItemList markup on listing pages.

Most of that is not writing. The one writing task worth doing is a short, specific intro on the categories that already show impressions, because a category page competes on matching the query and covering the catalogue, not on word count. There is no length that ranks, on a category page or anywhere else, and the platform you run on changes how much of this you can even edit.

FAQ

Should I focus on category pages or product pages?

Category pages for the head terms, product pages for the model-name queries. Measured on womens running shoes (6,127 a month), five of the six organic results were category or listing pages and none were product detail pages, while the individual products appeared in the shopping blocks instead. The head term in that cluster carries 29,763 searches a month against 289 for a single shoe model, so the category page is where the volume sits, and the product page is where the specific buyer lands.

How many products does a category page need?

There is no documented threshold, but Google's soft 404 rule sets the floor in practice: a page whose content "suggests an error for Google Search, an empty page or an error message" can be treated as an error even when it returns 200. A category with fewer than about five products is usually better merged into its parent, and the ones generated automatically from tags are where near-empty pages accumulate on WooCommerce and Shopify alike.

Should category page filters have their own URLs?

Only the filters with measurable demand. In our measurement, filtering by type (1,183 a month), colour (1,109) and price range (660) each had a real query behind it, while size (41) and width (34) did not, and two filters combined fell to 4 and 3 searches a month. Google's guidance is to allow crawling for the ones you want indexed and to block or 404 the rest, including "filter combinations with no results".

Do category pages need a description?

They need enough content to not read as an empty page, and enough specificity to match the query, which is a lower bar than the thousand-word blocks some guides recommend. No word count ranks by itself. The useful test is whether the text answers something the grid cannot, such as what distinguishes the subcategories or how sizing runs, and that is also the text most likely to be quoted back by an AI assistant.

Is a Shopify collection page the same as a category page?

Yes, in search terms. Shopify calls it a collection and serves it at /collections/<handle>, WooCommerce calls it a product category at /product-category/<slug>, and Google treats both as a listing page. The platform differences that matter are which parts of the URL and the title you can edit, which is a narrower set than most store owners expect on Shopify in particular.

Can a small store rank for a competitive category term?

It happens, and position is not awarded by domain rating alone: on the SERP we measured, a Shopify collection page at domain rating 29 held position 10 against Nike at 91 and adidas at 87. That is one page on one query on one day, not a promise. No one can guarantee a ranking, results vary by catalogue and competition, and anyone who tells you otherwise is selling something.

Get cited by ChatGPT. Rank on Google.

You found this article through search. That is the whole product.

  • One researched article a day
  • Published on your own domain
  • Keywords checked against live results
Start writing

Get cited by ChatGPT. Rank on Google.

You found this article through search. That is the whole product.

  • One researched article a day
  • Published on your own domain
  • Keywords checked against live results
Start writing