Separate a shopping control from a search destination
A filter helps someone already browsing your catalogue. A landing page must also make sense to someone arriving directly from search. Start by listing important collection questions, the assortment available to answer them and the team responsible for maintaining each destination. Treat search demand as evidence to investigate, rather than a reason to publish every possible combination.
For example, an enduring linen-trouser collection may support a focused destination with useful fabric and styling guidance. A temporary combination of size, sort order and a price slider may serve the current shopper without needing its own editorial page. Make that judgement before generating URLs.
Give crawling a deliberate scope
Google documents how filter parameters can create very large URL spaces and consume crawling resources. Its guidance distinguishes filters that need to be crawled from those that do not. Canonical hints are not a reliable substitute for a deliberate crawl strategy. A robots rule controls fetching; it should not be treated as an instruction to remove an already indexed URL.
Ask the developer to inventory the actual filter URLs before changing rules. Review representative valid, duplicate and empty combinations. Keep valuable collections and product discovery accessible. Record exceptions so that a broad rule does not accidentally block an intended landing page.
Source: Google: managing faceted navigation ↗ · Google: introduction to robots.txt ↗
Make selected pages useful and maintainable
For each selected destination, specify its shopper question, available assortment, internal parent and content owner. Write an introduction that helps with selection, followed by accurate product information. Avoid changing only the colour word in hundreds of otherwise identical paragraphs. Include related collections where the relationship helps the shopper continue.
Assign a stock review and a seasonal review. Decide what the page should show when its assortment temporarily falls below a useful level. A merchandising change should trigger a content check rather than leave an attractive search snippet pointing to an irrelevant collection.
Check a small release before expanding
Start with one collection family. Test links, preferred URLs, crawl accessibility and the actual rendered content. Compare search performance over a documented period while noting stock, promotional and seasonal changes. Monitor whether new useful pages are discovered and whether unwanted combinations keep appearing.
Keep a register of approved destinations and excluded patterns. That register can become a shared brief for merchandising, development and the SEO Agent. Expand the pattern only after the team can maintain the first group without duplicate content or conflicting technical instructions.
A considered linen collection
Illustrative plan: publish one maintained linen-trouser destination with a stable URL, available products and fabric guidance. Keep size selection and price sorting as shopping controls. Before release, check that navigation reaches the collection directly and that its chosen crawl rules do not block the products. This is a planning example, not a recommendation to apply one robots pattern to every storefront.
Turn the guide into a useful review
- Inventory filter URLs and their purpose.
- Choose a small set of useful search destinations.
- Review crawl rules and preferred URLs with development.
- Assign assortment, content and performance reviews.
Reference material
Platform guidance checked 3 October 2026. Examples and working checklists are Faccelerate editorial illustrations.
Bring the question.
Keep the context.
Map the relevant sources and specialist workflow for your team.
Explore your stack
