Get found in search and answer engines

For a site: list its pages, choose the keywords and reader questions its own pages answer, measure its search rankings and answer-engine mentions BEFORE any change and keep them as rows (search_visibility_measures in the pursuit's own database), check every served page the way an engine reads it, place each fix as metadata, structured data, a site file or markup around words already shown (never a new or reworded visible sentence), prepare robots.txt, sitemap.xml and llms.txt from the site's page list, publish through the site's own owner and read the live result back, then measure again and compare before with after.

What it asks for

  • mode (Optional, one of): new-build (the default for client websites: we build the site ourselves and the search work is part of the build from its first commit) or existing (a site we already run, changed in place)
  • site (Needed, words): The address of the site's home page
  • store (Needed, words):
  • engines (Optional, list): Answer engines to measure; Google AI Overview, ChatGPT, Perplexity and Gemini when absent
  • keywords (Optional, list): Keywords to measure; chosen from the site's own pages when absent
  • location (Optional, words): Where rankings are read from; United States when absent
  • questions (Optional, list): Questions a reader asks an AI, in the reader's words; chosen when absent
  • check_rows (Optional, list): The person's own check rows for tool:check-a-page-for-search-and-answer-engines

The steps your AI walks

  1. List every page in the site's sitemap
  2. Check every page the way an engine reads it
  3. Fix what the whole site leaves out
  4. Fix each page's missing checks, worst page first
  5. Save a destination draft, preview it, publish under existing authority, and read it back
  6. Measure where the site shows up in the engines' answers
  7. Record the scores and where the site shows up

Use it from your AI

Connect the AI you already use to Trillion once. Then ask in your own words; your AI finds this workflow by what it does and runs it.

Say to your AI: “Use Trillion to for a site: list its pages, choose the keywords and reader questions its own pages answer, measure its search rankings and answer-engine mentions BEFORE any change and keep them as rows (search_visibility_measures in the pursuit's own database), check every served page the way an engine reads it, place each fix as metadata, structured data, a site file or markup around words already shown (never a new or reworded visible sentence), prepare robots.txt, sitemap.xml and llms.txt from the site's page list, publish through the site's own owner and read the live result back, then measure again and compare before with after”