Skip to content

Ecommerce SEO · focused work

Faceted navigation SEO

Filters are useful to shoppers and expensive for search engines. Every combination of size, color, brand and price creates a URL, and a catalog of a few hundred products can generate millions of them. Faceted navigation SEO decides which of those URLs deserve a place in the index, keeps crawlers away from the rest, and turns the combinations with real demand into pages that rank.

Get a Growth AnalysisAbout SEO

This is the right work if

  • Search Console shows hundreds of thousands of discovered URLs against a catalog of a few thousand products
  • Crawl stats show most requests going to parameter URLs while new products wait days to be crawled
  • Filtered pages outrank the parent category for its own term and split the ranking between them
  • Shoppers search for brand-within-category or attribute-within-category terms and the store has no page for them
  • A recent theme or filter app change has created URL patterns nobody has reviewed

What it is

What faceted navigation SEO involves

Faceted navigation SEO is the set of rules that govern filter, sort and pagination URLs on a store. Left alone, a filter system produces near-duplicate pages in every order the parameters can be combined. Crawlers spend their budget on those pages instead of new products, the index fills with variants that compete with the parent category, and the combinations shoppers search for, such as a brand within a category or a size within a range, never get a page that could rank.

The work sorts facets into three groups. Combinations with search demand and enough products become indexable landing pages with their own title, copy and static URL. Combinations that help browsing but have no demand stay usable and canonicalize to the parent. Sorts, price sliders and stacked multi-select combinations are kept out of the crawl with robots rules or link handling. The output is a rulebook the platform enforces on every category, plus a small set of new pages that capture demand the store was missing.

How it is done

The work, in order

What changes

  • The index holds one URL per category plus the filter combinations that earn traffic
  • Crawl requests shift from parameter noise to products and categories, so new stock indexes faster
  • Brand-within-category and attribute-within-category searches land on pages built for them
  • The parent category ranks alone for its own term instead of sharing position with its own filters

  1. Inventory every URL pattern

    Crawl the store with parameters preserved and list every pattern the filter system emits: single facets, multi-select, sort orders, pagination, price ranges and their combinations. Join the list with Search Console and log data to see which patterns are crawled, indexed and receiving clicks today.

  2. Score facets by demand

    For each facet value within each category, check keyword research for the combined term, such as a brand inside a category or a material inside a range, and count the products it returns. Demand plus enough products earns an indexable page; either one missing keeps the combination out.

  3. Write the rulebook

    Set the handling for each group: indexable combinations get static URLs, a self-referencing canonical and a unique title; helpful but undemanded combinations canonicalize to the parent; sorts, price ranges and stacked facets are excluded with robots directives or served in a way crawlers do not follow. Paginated pages keep their own canonicals.

  4. Build the indexable combinations as real pages

    Create the earning combinations as collections or category pages inside the platform, with an introduction, a heading in the buyer's wording and a place in the navigation so they receive internal links. A filter URL that merely canonicalizes to itself is not a landing page until it is linked and written.

  5. Ship, then watch the crawl

    Apply the rules in the theme or filter app, test them on a staging copy, then track crawl requests, indexed page counts and category rankings for the following weeks. Removing URLs from the index takes time; the first sign it worked is crawl budget moving back to products and categories.

Platform notes

Shopify

Filters from the Search and Discovery app write filter.v.option and filter.p.vendor parameters that should canonicalize to the collection; indexable combinations are built as separate collections, which also gives them a place in the navigation.

WooCommerce

Attribute archives are real pages that can be indexed selectively, while layered navigation plugins add filter query strings that need canonical rules; pagination uses /page/2/ paths that should stay crawlable.

Headless

A filter state held only in the browser is invisible to crawlers; indexable combinations must be server-rendered at their own routes, and everything else should update the page without producing a crawlable link.

Questions

Faceted navigation SEO questions

By CartKernel · Last reviewed

How many filter combinations should a store let Google index?

As many as have search demand and enough products to make a useful page, which is usually a small fraction of what the filter system can produce. A category with ten facets does not need ten indexed pages; it needs the two or three that people search for.

Is noindex or canonical the right tool for filter URLs?

Canonical when the filtered page is a subset of the parent and should pass its signals upward. Noindex when the page should be crawled but never appear. Robots disallow when crawl budget is the problem and the page has no value to pass.

Will removing filter URLs from the index lose traffic?

Only if some of those URLs were earning clicks, which the inventory step reveals. Filtered URLs that rank are candidates for an indexable page of their own, not for removal. The rest were sharing signals with the parent, which usually gains position when they go.

Can a filter app handle faceted navigation SEO on its own?

A filter app controls how facets display and which parameters it writes, but it rarely sets canonicals, writes copy or adds a page to the navigation. The SEO rules sit in the theme and in how indexable combinations are built, and the app has to be configured to respect them.

Part of

Get foundEcommerce SEOCategory and product pages that rank for buying queriesExploreBuild the storeEcommerce DevelopmentStorefront engineering built for speed and conversionExplore

Related work and answers

Ecommerce SEOEcommerce category page SEOEcommerce category page SEO: mapping buying queries to collections, copy that sells, filter and pagination control, and revenue reported by category.OpenProgrammatic SEOProgrammatic collection pagesProgrammatic collection pages: a demand table, a publication gate, templates that vary with the data behind them, and a lifecycle that retires pages cleanly.OpenEcommerce SEOEcommerce product page SEOEcommerce product page SEO: titles that match product-name queries, original descriptions, one URL per product, Product markup and links from the category.OpenAnswerIs infinite scroll bad for SEO?Infinite scroll only harms SEO when products exist solely after an interaction. How to keep crawlable URLs behind the scroll and what it costs shoppers.OpenAnswerDo canonical tags fix duplicate product pages?Canonical tags consolidate duplicate product pages when Google accepts them, but they are a hint rather than a rule. What they fix and what they cannot.OpenAnswerDo subcategory pages help ecommerce SEO?Subcategory pages help ecommerce SEO when the narrower term has real demand and enough products behind it. Where the threshold sits and how to link them.OpenAnswerHow many products should a collection page show?A collection page should show as many products as it loads quickly on a phone, usually 24 to 48, with real paginated URLs for the rest. The trade-offs.Open

Find the leak.

A free Growth Analysis ranks what your store should fix first, by revenue at stake.

Get a Growth Analysis