Why facets become a crawl trap
Every filter a shopper can combine (color, size, price, brand, sort order) can create a unique URL. Multiply those options together and a single category can spawn thousands or millions of URL combinations, most of them near-identical and none worth ranking on their own.
Left unmanaged, crawlers burn their budget on these permutations instead of your real category and product pages, and the duplicate combinations dilute the pages you actually want to rank.
- Combinatorial explosion: filters multiply into endless URL variants
- Sort-order parameters that change URLs but not content
- Filter values with zero or one product creating thin pages
- Session IDs and tracking parameters compounding the count
- Infinite crawl paths where bots keep discovering new combinations
How we handle filter and sort URLs
There's no single switch. The right approach depends on which filtered views have real search demand and which are pure noise. We separate the handful of facet pages worth indexing (often high-demand attributes like a popular brand or category combination) from the vast majority that should be controlled.
Then we apply the mechanics: canonical tags, selective crawl blocking, and clean URL patterns that keep bots on the pages that matter while shoppers keep every filter they need.
- Identify a small set of high-demand facets worth indexable landing pages
- Canonicalize low-value filter combinations to the parent category
- Block crawl of sort and pure-refinement parameters where appropriate
- Keep filter links crawlable or JS-driven based on the strategy
- Ensure indexable facet pages have unique titles, copy, and internal links
- Watch Search Console and logs to confirm the trap is closed
More on technical seo
Frequently asked questions
Should I block all filter URLs from Google?
Usually not all of them. Some filtered views (like a popular brand within a category) match how people actually search and deserve to be indexable landing pages. The bulk of combinations should be controlled. We decide which is which based on your product data and search demand.
Is canonical or robots.txt the better tool here?
They solve different problems. Canonicals consolidate ranking signals onto the main page but still let bots crawl the variants. robots.txt blocks the crawl to save budget but doesn't consolidate signals. Large catalogs often need a combination, applied carefully so you don't block URLs you meant to canonicalize.
Will this change how the filters work for shoppers?
No. The goal is to keep the on-site experience exactly as flexible as it is now. The changes are about what search engines are allowed to crawl and index behind the scenes, not what customers can click.