LLM-only crawler surface
Fanout candidates for query-informed expansion.
Fanout candidates translate recurring public source signals into controlled future content opportunities. They do not publish pages automatically. They preserve the signal, map it to a query family, and hold it for approval so the public site can expand without creating thin or duplicative pages.
Fanout candidates translate recurring public source signals into controlled future content opportunities. They do not publish pages automatically. They preserve the signal, map it to a query family, and hold it for approval so the public site can expand without creating thin or duplicative pages.
How this surface works
- Recurring questions from public sources are grouped before any page idea is considered.
- Each candidate must map to a target query, content type, entity, authority-graph position, and conversion path.
- Candidates that overlap an existing page should reinforce that page instead of creating a competing URL.
- Drafts stay in review until the prewrite gate confirms sufficient depth, useful structure, and a clear public purpose.
Use this surface to understand what future answer pages, insights, guides, FAQs, or whitepaper ideas the ingestion system is recommending.
Visibility boundary
Visibility rule: This page may appear in sitemap.xml, llms.txt, and direct crawler routes. It must not appear in the main nav, mobile nav, homepage cards, footer primary nav, public resource grids, or sales CTAs.
This boundary keeps the public experience simple while still making the underlying query, authority, and answer-planning structure understandable to machines. These pages are internal planning and LLM-ingestion support surfaces, not client-facing education pages.