Answer first
Search discovery is maintained as a build artifact. Each release should check whether the most useful pages have clear titles, concise descriptions, visible answers, source panels, canonical links, structured data, and generated discovery files.
Release loop
FUNCTION review_search_discovery(release_id, reviewed_at_utc)
pages <- LOAD_CURATED_PAGES()
FOR EACH page IN pages
CHECK title_is_specific(page)
CHECK description_matches_visible_content(page)
CHECK canonical_url_is_stable(page)
CHECK answer_first_or_clear_intro(page)
CHECK source_reports_exist(page)
CHECK internal_links_resolve(page)
CHECK structured_data_matches_page(page)
END FOR
BUILD sitemap_xml
BUILD canonical_answers_json
BUILD entity_map_json
BUILD search_intent_map_json
BUILD metadata_coverage_json
RUN route_smoke_tests
RUN private_path_blocking_tests
WRITE release_evidence(release_id, reviewed_at_utc)
END FUNCTIONReview cadence
| Trigger | Review action |
|---|---|
| New major concept | Add canonical answer, entity record, source reports, and internal links. |
| New tool | Add sitemap route, tool card, route inventory record, and answer card if it solves a common question. |
| New report batch | Update /docs, manifest, research page, topic pages, and source evidence map. |
| Layout change | Re-check mobile title wrapping, skip links, keyboard access, and semantic landmarks. |
| Deployment | Confirm /health, /sitemap.xml, /llms.txt, /ai-ready.json, and private-path blocking. |
Success definition
A good search round makes the site easier to understand, not noisier. It should reduce ambiguity, improve internal routing, and help visitors reach the best guide faster.
Source reports used for this guide
These reports are preserved verbatim in the site archive. The guide above is an editorial synthesis and may narrow, qualify, or reorganize claims from the source material.