The Field Manual / Agent Readiness
What is a website knowledge catalog, and why does it matter?
The short answer
A website knowledge catalog is a maintained set of approved business answers with sources, owners and review dates. It helps people and software check what you do, what it costs and where to go next. Agent Readiness also requires clear limits on what an agent may do.
What belongs in the eight catalog sections?
Use customer questions and answers; services and service areas; expertise and credentials; definitions and FAQs; pricing and scope; policies and processes; verified reviews and case studies; and customer insights. Give each record a public source, an owner, a review date and a publication status.
Keep unknowns and draft answers in the internal working copy. Leave out placeholder testimonials and unsupported performance claims. Summarize call themes only with appropriate permission and remove personal details; raw transcripts do not belong in a public catalog.
Should we use web pages, JSON-LD or an API?
Keep the complete approved answer on a crawlable web page first. Add structured data that accurately describes the visible content. A read-only JSON endpoint can help your own tools reuse approved records, but it is not a requirement for search inclusion.
Generate the page and JSON from the same records so pricing and policies do not diverge. Public catalog data must be safe for anyone to read. Private operational records need authentication and authorization in a separate system.
Does llms.txt make a website visible in AI search?
llms.txt is a proposed convention for giving agents a concise index and context. It is optional, does not control crawler access and does not guarantee that an assistant will read or cite your site. Google says it does not use these files for Search visibility or ranking.
Keep ordinary pages, internal links and sitemap entries accurate. Search Console ownership verification grants access to Google's site tools; it is not universal verification with other AI providers. Structured data must reflect the page, and there is no special AI schema that guarantees inclusion.
What connects the catalog to workflow safety?
For each workflow, record where the authoritative information lives, who owns the next step and what requires approval. Reading a public answer does not grant an agent permission to send messages, spend money or change a customer record.
Begin with ten recurring prospect questions. Have the business owner approve the answers, publish them, then set a review date. The free kit includes an eight-section inventory, publishing checks, action rules and a log for testing how assistants describe the business.