Filters in PrestaShop: how to avoid thousands of useless URLs for SEO

If you have a PrestaShop store with a medium or large catalog and have enabled the faceted navigation module, it is very likely that Google is trying to crawl tens of thousands of URLs that should not exist from an SEO perspective. This is not an exaggeration. A store with one thousand products distributed across fifty categories, with filters for size, color, price, brand, and material, can mathematically generate millions of unique URL combinations. Most of them display between one and three products, have content that is practically identical to other similar combinations, and do not respond to any real search intent.
The outcome is predictable: Googlebot’s crawl budget gets exhausted on low-value pages, strategic URLs are indexed less frequently, and the site accumulates thousands of duplicate or low-quality pages that dilute domain authority instead of concentrating it where it drives rankings.
This is one of the most common technical issues we find in PrestaShop audits, and also one of the highest-impact problems when it is properly resolved.

Why PrestaShop creates this problem by default

PrestaShop’s native faceted navigation module, in modern versions called “Faceted Search”, is designed to maximize the user’s filtering experience, not to protect the site’s SEO health. By default, every combination of active filters generates a unique URL that the module considers indexable. When a user selects blue color and size M in a t-shirt category, PrestaShop creates a URL like /camisetas?q=Color-Azul/Talla-M or a friendly variant depending on the module configuration and installed version.
The problem scales exponentially with each additional filter. If you have five attributes with ten values each, the theoretical combination exceeds one million URLs. Google won’t crawl all of them, but it will attempt to follow links leading to those pages from main categories, consuming crawl resources that should be allocated to your actual product and category pages.
On top of that, depending on the version and module configuration, PrestaShop does not consistently apply canonical tags or noindex directives by default on these faceted URLs. Without manual intervention or specific module configuration, many of these pages remain accessible, internally linked, and indexable.

Crawl budget: why it matters for large catalogs

The concept of crawl budget is key to understanding why this issue becomes critical in stores with more than five thousand URLs. Google does not crawl a site exhaustively or infinitely: it assigns each domain a limited number of pages to crawl over a given period, based on domain authority, server response speed, and historical content quality signals.
If your PrestaShop store has one hundred thousand URLs generated by faceted filters and Google spends 70% of its crawl budget trying to process them, your new product pages may take weeks to get indexed, your main category pages are crawled less frequently than needed, and any updates in pricing or availability take longer to be reflected in the index.
The solution is not a single action, but rather a layered strategy combining module configuration, technical directives, and—when justified—selective generation of faceted URLs with real SEO value.

Layer 1: Faceted Search module configuration

The first intervention point is the module itself. In recent versions of PrestaShop, the Faceted Search module includes configuration options that allow you to control which filter combinations generate indexable URLs and which do not.
Go to the PrestaShop back office, navigate to Modules → Faceted Search and look for indexing options. Depending on the module version, you will find options to automatically apply noindex tags to faceted URLs, generate canonical tags pointing to the parent category, or disable friendly URLs for selected filter combinations.
The most conservative—and generally safest—configuration for most stores is to apply noindex, follow to all faceted URLs without exception. This tells Google not to include these pages in the index, but to follow the links they contain to discover product pages. The follow attribute is critical: using noindex, nofollow would prevent PageRank from flowing to the individual products listed on those filtered pages.

Layer 2: canonical tags to the parent category

In parallel with the noindex directive, implementing correct canonical tags adds an additional signal layer to Google. Each faceted URL should include a canonical element in the <head> pointing to the main category URL without filters.
html
<link rel=”canonical“ href=”https://tutienda.com/camisetas/“ />
This explicitly tells Google that the canonical version of that content is the base category, not the filtered version. In practice, canonicals and noindex tags are complementary and positively redundant: if for any reason the crawler ignores the noindex, the canonical still sends the correct signal about which URL should rank.
If your module does not generate these canonicals automatically, you can implement them by modifying the category template in your theme. In PrestaShop, the relevant file is usually catalog/listing/product-list.tpl or catalog/category.tpl, depending on the version. The logic is conditional: if the current URL contains active filter parameters, inject the canonical pointing to the clean category URL.

Layer 3: robots.txt blocking for known URL patterns

The `robots.txt` file is the third line of defense. Unlike noindex, which allows crawling but prevents indexing, robots.txt blocking directly prevents Googlebot from accessing those URLs, preserving crawl budget more efficiently.
The challenge with this approach in PrestaShop is that faceted URLs do not always follow a single consistent pattern. Depending on module configuration and whether friendly URLs or GET parameters are used, patterns may vary. A common setup using GET parameters allows relatively precise blocking:
User-agent: *
Disallow: /*?q=
Disallow: /*&q=
If your setup uses friendly URLs for faceted navigation such as /camisetas/color-azul/talla-m, blocking becomes more complex because those URL segments resemble real subcategory URLs. In that case, it is safer to prioritize noindex and canonical layers instead of robots.txt blocking to avoid accidentally blocking legitimate pages.

Layer 4: when it makes sense to index faceted URLs

Not all filter combinations are useless for SEO. There is a specific scenario where generating and ranking a faceted URL has real value: when that filter combination matches a search intent with sufficient volume and when the resulting page has differentiated content compared to other combinations.
The classic example is a category plus brand combination: /zapatillas-running/nike/ or /sofas/esquineros/. These URLs combine a generic category with a high-volume attribute, generate a coherent and homogeneous product set, and target a real transactional keyword that users actually search for on Google.
To identify which combinations deserve indexing, cross-reference search volume data for your main attributes with Search Console reports. If there are queries like “category + attribute” with more than two hundred monthly searches in your market, that combination is a candidate for its own indexable URL with minimal differentiated editorial content: a specific H1, a unique meta description, and a short introductory paragraph that contextualizes the selection.
All other combinations—those involving two, three, or more simultaneous filters without proven search demand—should be treated with noindex and canonical without exception.

How to audit your current PrestaShop setup

Before implementing any changes, you need a precise diagnosis of how many faceted URLs currently exist in your setup and how many are indexed.
The audit process we follow is as follows: first, a full crawl with Screaming Frog configured to follow all parameters and friendly URLs. We then filter results by the characteristic faceted URL pattern to get the total number of generated URLs. Second, in Google Search Console we use the operator site:tudominio.com/categoria to estimate how many variants of each category are actually indexed. Third, in the Coverage report, we check the volume of pages in the states “Discovered, currently not indexed” and “Crawled, currently not indexed”: high numbers here are a direct signal that Google is spending crawl budget on pages it ultimately discards.
With this map, prioritization becomes straightforward: categories with the highest volume of faceted URLs and organic traffic are the first to address.
Faceted navigation filters in PrestaShop are essential for the shopping experience, but they become an SEO trap if not managed with technical criteria from the start. The solution is not to disable filters or limit user functionality, but to implement a layered strategy combining noindex, canonicals, selective robots.txt blocking, and deliberate generation of indexable URLs only where real search demand exists. Properly executed, this work can reduce the number of crawlable URLs by 80% or more and free up crawl budget that Google will automatically redirect to the pages that truly matter for your business.
We are a PrestaShop SEO agency, helping you achieve your goals. Contact us!