Guide
AI Search Readiness, in six chapters.
Everything the audit checks, explained so you could do it by hand. No promises about citations; this is about whether an assistant can fetch, read and understand your site.
Chapter 1
What AI systems actually fetch from your site
Four kinds of crawler visit a site on behalf of AI products, and they are not one thing. Which one matters depends on what you want.
ReadChapter 2
robots.txt for AI crawlers, line by line
How a crawler chooses which group applies, why wildcards catch more than you meant, and the two lines that matter for search.
ReadChapter 3
Server-visible content: what a fetcher receives before JavaScript runs
Client-rendered apps send an empty shell to anything that does not execute scripts. Most AI fetchers do not. This is the single most common critical finding on builder sites.
ReadChapter 4
Entity and page markup: saying clearly what the site is
Assistants and search engines identify a business from consistent names and valid structured data. Three places have to agree.
ReadChapter 5
llms.txt: what it is and what it is not
A markdown map of your site for agents and documentation tools. Useful, cheap, and not a ranking signal. Here is how to write one honestly.
ReadChapter 6
Keeping it fixed: every prompt can undo the fix
Builder sites are rewritten with every session. Watching the live site after each push is the only way to know a fix survived.
Read
Shorter: the readiness checklist, and the documentation of how each check is measured.