# Faceted navigation and SEO for e-commerce

URL: https://ekom.blog/faceted-navigation-and-seo-for-e-commerce/
Published: 2023-09-08 · Updated: 2026-11-03
Author: Ekom
Topics: Technical SEO

> Filters are great for shoppers and quietly dangerous for SEO. How faceted navigation creates thousands of near-identical URLs, which filter pages deserve to rank, and how to keep the rest out of the way.

A shop with 200 products can have more URLs than a news site.

That sounds wrong until you count the filters. Colour, size, price, brand, material, in stock, sort by price, sort by newest. Every click on a filter makes a new URL, and every combination of clicks makes another. Five colours, six sizes, four price bands and three sort orders on one collection is already hundreds of addresses, and most of them show the same twelve products in a slightly different order.

Shoppers love filters, and they should. The problem is that search engines can find those URLs too. Left alone, faceted navigation turns a tidy store into a maze of thin, near-duplicate pages, and Google spends its time crawling "black, size 9, under £50, sorted by newest" instead of your actual products.

The fix isn't to remove the filters. It's to decide which filter pages are worth being found, and to keep the rest quietly out of the way.

## What faceted navigation actually is

Faceted navigation is the filter panel on a category or collection page: the checkboxes and dropdowns that narrow the list by attributes ("facets") like colour, size or brand.

Each choice usually adds a parameter to the URL:

/collections/shoes
/collections/shoes?colour=black
/collections/shoes?colour=black&size=9
/collections/shoes?size=9&colour=black
/collections/shoes?colour=black&size=9&sort=price-asc

To a person, those are one page with a few settings changed. To a crawler, they're five different URLs. The fourth one is the same as the third with the parameters swapped round, which is the kind of thing that multiplies fast.

## Why it causes SEO problems

### Duplicate and near-duplicate pages

Most filter combinations show content that already exists somewhere else on the site. Sorting changes nothing but the order. A filter that matches every product changes nothing at all. Google has to work out which version is the real one, and it doesn't always pick the one you'd choose. (I went through how that choice works in canonical tags explained with real examples.)

### Thin pages

Filter far enough and you get pages with one product, or none. An empty "no products found" page that's indexable is not doing you any favours.

### Wasted crawling

On a small store, Google will usually cope. On a store with thousands of products and a dozen facets, the number of possible URLs gets silly, and crawlers can spend a lot of time on filter combinations while new products wait. That's the one situation where crawl budget genuinely matters for a smaller site.

### Split signals

If people share or link to filtered URLs, those links are spread across dozens of versions instead of pointing at one strong collection page.

## Not every filter page is bad

Here's the part that gets missed: some filtered pages match real searches.

"Black running shoes", "waterproof hiking boots", "linen shirts for men". Those are searches with buying intent, and a page showing exactly those products is a good answer. If your store only lets Google see /collections/shoes, you're leaving those searches to competitors who built a page for them.

So the job is sorting filter pages into two groups:

- Worth indexing: a single facet (or occasionally two) that matches a real search with real volume, and shows enough products to be useful.

- Not worth indexing: sort orders, price ranges, stock filters, view options (grid or list, 24 or 48 per page), and most multi-filter combinations.

Do some e-commerce keyword research before you decide. If people search "black running shoes", that's a page. If nobody searches "black running shoes size 9 under £50", it isn't.

## How to handle the pages you don't want indexed

There are a few tools, and they do different jobs. Mixing them up is where most of the trouble comes from.

### Canonical tags

Point the filtered URL's canonical at the unfiltered collection. This tells Google "the main version is over there". It's a hint, not an order, and Google can ignore it if the pages look too different. It also doesn't stop crawling: Google still has to fetch the page to see the canonical. Good for sort orders and light filters.

### Noindex

A noindex meta tag keeps a page out of the index. Google still crawls it, at least at first, to see the tag. Good when a filtered page is genuinely different from the parent but not worth ranking.

Don't combine noindex with a canonical pointing elsewhere. They send mixed messages: one says "don't index this", the other says "this is the same as that page, index that instead".

### Robots.txt

Blocking filter parameters in robots.txt stops crawling entirely, which is the only option here that actually saves crawl time. The catch: Google can't see a noindex or canonical on a page it isn't allowed to fetch. So a blocked URL can still appear in results if other pages link to it, just without a description. I covered the difference in robots.txt and noindex: when to use which.

Use robots.txt for the endless combinations (sort, price ranges, multiple filters), and only once you're sure nothing you want indexed lives behind those patterns.

### Links that crawlers don't need to follow

Some stores build filters so the options aren't normal crawlable links at all: the filtering happens with JavaScript or a form, and the URL updates without a plain <a href> for every combination. That keeps the number of discoverable URLs down at the source. It's a development decision rather than a settings one, but it's worth asking about if you're building or redesigning.

## A sensible setup for most stores

Filter type
Example
What I'd do

Sort order
?sort=price-asc
Canonical to the collection; block in robots.txt on large stores

View options
?view=list, ?limit=48
Canonical to the collection

Price ranges
?price=0-50
Noindex, or block on large stores

Stock filters
?in_stock=1
Canonical to the collection

Single facet with search demand
"black running shoes"
Give it its own page with a clean URL, unique title and intro

Multiple facets
?colour=black&size=9
Noindex or block

The row that does the most for rankings is the fifth one. A filter that deserves to rank deserves a proper page: a clean URL, a title written for that search, a short intro, and links to it from the parent collection. On Shopify, that often means a separate collection rather than a filter state. (More on that in collection pages on Shopify.)

## A note on Shopify and WooCommerce

Shopify adds filter parameters to collection URLs when you use its built-in filtering, and its default robots.txt already blocks some sort and filter patterns. Open yourstore.com/robots.txt and read what's there before adding your own rules. Since 2021 you can edit it through the robots.txt.liquid template, but only do that if you know exactly which pattern you're blocking and why.

WooCommerce depends heavily on the filter plugin you use. Some create clean, crawlable URLs for every combination; others use parameters. Check what your plugin outputs before you assume anything, and check your SEO plugin isn't adding the filtered URLs to your sitemap.

## How to check what's happening on your store

- Search Console → Pages. Look at "Crawled – currently not indexed" and "Duplicate without user-selected canonical". If they're full of filter URLs, you've found your problem.

- Search site:yourstore.com inurl:sort (or whatever your filter parameter is) to see if filtered pages are indexed.

- Crawl the site with a crawler and count how many URLs contain parameters compared with real products and collections.

- Check your sitemap. Filter URLs shouldn't be in it.

## Related reading

- Canonical tags explained with real examples

- Crawl budget: does a small site need to care?

- Collection pages on Shopify: how to make them rank

- Robots.txt and noindex: when to use which

Pick your biggest collection, click three filters, and look at the URL. Then search Google for it. If it's indexed, you know where this week's work starts.

---

From Ekom (https://ekom.blog/). More: https://ekom.blog/llms.txt
