LLM-only crawler surface
Clustered public questions for controlled content expansion.
The query cluster surface groups repeated public questions into stable themes. Clustering prevents one-post-one-page publishing and keeps the content system from turning social listening into spam. A cluster can produce a content brief, but only after it clears scoring, deduplication, routing, and prewrite depth checks.
The query cluster surface groups repeated public questions into stable themes. Clustering prevents one-post-one-page publishing and keeps the content system from turning social listening into spam. A cluster can produce a content brief, but only after it clears scoring, deduplication, routing, and prewrite depth checks.
How this surface works
- Clusters should be based on repeated intent, not one isolated post or headline.
- Every cluster needs a destination: existing page, reinforcement opportunity, draft candidate, or parked item.
- Low-quality or off-scope signals should be discarded or archived rather than converted into public content.
- Clusters that touch sensitive mental-health topics must preserve educational boundaries and avoid diagnosis or crisis-service claims.
Use this surface to inspect how the ingestion layer groups demand before any draft becomes public.
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.