Choose a crawl-control pattern (robots.txt disallow, noindex, canonical, or nofollow links) for each class of faceted-navigation URL to prevent index bloat without losing valuable facet pages

domain: developers.google.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗

Steps

  1. Inventory the facet parameter combinations your catalog generates (sort, filter, pagination, session/tracking params) and classify each by whether it produces genuinely unique, search-worthy content
  2. For parameters with no unique SEO value (sort order, session IDs), block crawling entirely via robots.txt Disallow patterns matching the parameter
  3. For near-duplicate but sometimes-useful combinations, prefer rel=canonical pointing to the primary facet/category URL over robots.txt blocking, since canonical still lets Google crawl and consolidate signals
  4. For low-value combinations you want crawled but not indexed, use meta robots noindex,follow rather than robots.txt, since a robots.txt-blocked page can still be indexed (with no snippet) if it accumulates links
  5. Avoid generating crawlable links to disallowed combinations in the first place — pair server-side rules with nofollow or JS-only rendering of facet links so bots don't discover the URLs at all
  6. Monitor the Page Indexing report's 'Indexed, not submitted in sitemap' and 'Duplicate' buckets to catch facet URLs leaking into the index despite these controls

Known gotchas

Related routes

Handle faceted navigation URL explosion to prevent index bloat and crawl budget waste
google-search-console · 5 steps · unrated
Distinguish between robots.txt Disallow and HTML noindex directives, and configure robots.txt user-agent entries to control AI training crawlers separately from search crawlers
developers.google.com · 6 steps · unrated
Configure per-engine crawl-delay directives in robots.txt, since Bing and Yandex honor it but Googlebot ignores it entirely
developers.google.com · 5 steps · unrated

Give your agent this knowledge — and 15,500+ more routes

One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Need this verified for your stack — or a route we don't have yet?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans