In short
Noindex for filtered pages is an indexing directive used when a filter URL is useful for navigation but is not a page the site wants indexed.
Mechanism and decision
Noindex for filtered pages is an indexing policy for facets that help visitors narrow a catalogue but do not deserve independent search results. It can preserve useful navigation while limiting thin, unstable or duplicative parameter combinations.
Classify every filter pattern first. Intentionally indexable facets need demand, enough matching inventory and distinct content; remaining combinations need a consistent directive, canonical and sitemap policy.
What you can control
Noindex does not instantly remove a URL and robots.txt is not a replacement for an indexing policy.
Practical workflow
- Inventory parameters, selected values, sort states and pagination.
- Document the small set of indexable facet landings.
- Deliver noindex in the crawler-visible version.
- Test common, empty and edge-case combinations.
FAQ
No. Useful, distinct landing pages may be intended for search. Decide the purpose of each filter class first.
Yes. A crawl block can stop Google from fetching the page containing the directive.