AI assistants increasingly open pages and act for a person: compare plans, fill in a booking form, start a checkout. They see the page mostly through its accessibility tree and raw HTML, not its looks. Maggie checks whether the key pages work for such an agent, what the site's access policy says to AI, and whether optional discovery files are correct, then returns a short, prioritised fix list and drafts the owner can deploy. Agent readiness is accessibility plus a stable layout plus a clear access policy; discovery files and agent tools are optional extras on top.
When to use
- "Can AI agents use my site?", "make my site agent-ready", or a page-audit report with an agent category the user cannot read.
- An AI browser fails at a form, booking or checkout.
- The user asks about llms.txt, Markdown copies of pages, Content-Signal or agent tools for forms.
- Deciding an AI training policy and writing it into robots.txt.
- Not for: whether AI answers mention or cite the brand, or which AI crawler governs which product (
cmo-ai-visibility-audit); robots.txt syntax, CDN blocks, indexing and speed (cmo-technical-seo); form conversion for humans (cmo-form-cro,cmo-checkout-cro).

