Why it matters
Facets create near-infinite URL spaces (the same filters in another order, conflicting or excessive combinations, facets on paginated or search pages), one of the things named as burning crawl budget. Google's faceted navigation guide prefers prevention: disallow filter URLs in robots.txt or use URL fragments, which Google generally does not crawl; rel=canonical and nofollow are weaker, slower options.
How to meet it
Decide per facet whether it deserves an indexable landing page, for example a main category or brand with real search demand, and give those a clean URL, unique content and <a href> links. Put every other filter, sort and view parameter behind a robots.txt Disallow pattern or in the # fragment, and do not link filter combinations with crawlable hrefs. Also disallow internal search results and action URLs (cart, wishlist, compare). Audit CMS plug-ins for generated URL spaces: Google's crawling team said many crawling complaints it receives turn out to come from a plug-in, such as a calendar plug-in that adds calendar parameters to the URLs of every post, page, category and tag page, and Google crawls such URLs until its systems learn from large samples that they are useless. A Google panelist added that useless plug-in parameter URLs can also be handled at the web server, for example with a rewrite rule or a custom module, so that crawl budget goes to the URLs that matter.
How to test it
A crawl that respects robots.txt finds a bounded number of listing URLs; server logs and Crawl stats show Googlebot not spending fetches on parameter URLs; Google's open-source robots.txt parser (github.com/google/robotstxt), run with the Googlebot token, returns disallowed for sample filter URLs and allowed for item pages, and URL Inspection shows item pages as Crawl allowed.
How Regensbot covers it
Regensbot proposes a verdict with the evidence; a person on your team confirms it.
The evidence comes from a crawl of your site. Where content needs judging, Claude proposes the verdict as an assistant judge and never fails a page on its own.
The crawl is polite: sitemap first, one request per second per host. A problem it finds is definite, and “none found” passes only on a complete crawl.
Sources
Google documents02
- 01Managing crawling of faceted navigation URLsGoogle (opens in a new tab)
- 02Optimize your crawl budgetGoogle (opens in a new tab)
Claims in the knowledge base12
- D1-C101SourceHow Google thinks about crawl budgetGoogle's documentation
- D1-C100ConsistentHow Google thinks about crawl budgetShown on screen
- D1-C099ConsistentHow Google thinks about crawl budgetShown on screen
- D1-C103ConsistentHow Google thinks about crawl budgetShown on screen
- D2-C188n/aLightning session D: Rendering and JavaScriptThe author's interpretation
- D1-C469ConsistentQ&ASaid on stage
- D1-C430ConsistentQ&ASaid on stage
- D1-C446UndocumentedQ&ASaid on stage
- D1-C447ConsistentQ&ASaid on stage
- D1-C378ConsistentHow Google thinks about crawl budgetSaid on stage
- D1-C444ConsistentQ&ASaid on stage
- D1-C539ConsistentQ&ASaid on stage
Claim IDs refer to the Search Central Live 2026 knowledge base. The knowledge base (opens in a new tab)
- Consistent
- Google's documentation supports it without stating it.
- Undocumented
- Said or shown at the event, not in the documentation.
- Source
- The claim is the cited document itself.
- n/a
- Nothing to verify: a quotation, framing, opinion or analysis.