# Only what the application itself defines lives here. Which crawlers may visit at all is decided
# at Cloudflare: its managed robots.txt block is prepended to this file at the edge, and the
# per-crawler blocks are WAF custom rules, where their effect can be observed.

# ---------------------------------------------------------------------------
# The filter facet space
#
# /f/{filter}/{selection} is a combinatorial URL space, and it is what crawlers actually
# enumerate: in two separate incidents it carried ~100% of the flood, at 8 and at 13-16
# active facets. Left to the default Allow below, this file was inviting them in.
#
# The cut matches FilterController::NOINDEX_FACET_THRESHOLD — selections of four or more
# facets (three commas) are already noindex, so disallowing them costs nothing in search
# visibility. Filter landing pages and shallow 1-3 facet URLs stay crawlable.
# ---------------------------------------------------------------------------

User-agent: *
Disallow: /*/f/*/*,*,*,*
Allow: /

# Generated by the application (epics/seo-measures, C1): every published page, item and filter
# landing page, in every language it exists in, with hreflang alternates. Edge-cached like the
# pages it lists.

Sitemap: https://substratec.com/.well-known/sitemap.xml