# Is your site agent-ready? A practical checklist "Agent-ready" has become a score you can get from several tools, and the scores disagree. A company website can pass every check that matters for being found and cited by AI assistants and still score low, because the same checklist also covers OAuth servers, MCP endpoints and payment protocols that only an API or an online shop would publish. This checklist sorts the signals by the kind of site that needs them. Start at the top; stop where your site stops. ## Who the agents are Three kinds of software read your site on behalf of AI products: - **Crawlers** collect pages for search indexes and model training: `OAI-SearchBot`, `GPTBot`, `ClaudeBot`, `PerplexityBot`. - **User-triggered fetchers** load one page because a person asked about it: `ChatGPT-User`, `Claude-User`, `Perplexity-User`. - **Browser agents** operate a real browser for a person: they read the page, click, and fill in forms. Most of them do not run JavaScript, and none of them get past a login. What they get is what your server sends. ## Every site: can agents get in and read the page? These decide whether you appear in AI answers at all. They matter for a one-page brochure site as much as for a SaaS product. 1. **robots.txt lets AI search bots in.** Allow the search and user-triggered bots; decide on training bots separately. See [AI crawlers in robots.txt](/guides/ai-crawlers-robots-txt). 2. **The firewall agrees with robots.txt.** A CDN or bot manager that returns 403 to `GPTBot` overrides the file. See [Is Cloudflare blocking AI crawlers on your site?](/guides/cloudflare-ai-crawlers). 3. **The content is in the HTML.** The main text, prices and facts arrive in the server response, not after JavaScript runs. See [Do AI crawlers run JavaScript?](/guides/ai-crawlers-javascript). 4. **The page is indexable.** No `noindex`, a canonical URL that points to itself, a sitemap that lists the page. 5. **The structure is clear.** One `h1`, descriptive headings, real links, text not baked into images. 6. **Structured data describes the page.** An `Organization`, the page type and breadcrumbs in JSON-LD. See [Structured data for AI search](/guides/structured-data-ai-search). 7. **The page works for assistive technology.** Browser agents read the accessibility tree, so labelled buttons and form fields help them the way they help screen readers. ## Content sites: make the content easy to take in These are cheap, help agents that already found you, and cost nothing in search. 1. **A Markdown version of each page**, linked from the HTML, and served for `Accept: text/markdown`. See [Serve Markdown to AI agents](/guides/markdown-for-agents). 2. **An `llms.txt` index** of your most useful pages. Useful for documentation and products people ask assistants about. See [llms.txt: what it is](/guides/llms-txt). 3. **A content usage preference** in robots.txt, such as `Content-Signal: search=yes, ai-input=yes, ai-train=no`. It states how fetched content may be used; it does not block anything. 4. **Link headers on the home page** that point to the Markdown version and, if you have one, the API catalog. ## Sites with forms or actions: let browser agents act If people book, buy, search or submit something on your site, a browser agent will try to do it for them. - **Plain HTML forms with labels** work for agents today: every field with a `name` and a `