Home / Free tools / AI agent readiness checker
Free tool, no sign-up to useFree AI agent readiness checker
See whether AI agents can reach your page, read it and get something done on it. We check robots.txt, firewall access for AI bots, llms.txt, markdown versions served to AI bots, structured data, pricing and forms.
Enter a page URL
Try your homepage or a key service pageWhat the checker looks at
AI agents are starting to research, compare and book on behalf of real people. They skip sites they cannot get into, cannot read, or cannot make sense of. The checker runs twelve tests across three questions.
Can agents get in?
robots.txt rules for agents that act for users (ChatGPT-User, Claude-User, Perplexity-User), AI search bots and training bots. Whether your firewall or CDN serves the page to nine AI user agents, from GPTBot to Perplexity-User. Your llms.txt and XML sitemap.
Can agents read it?
Markdown for AI, checked three ways and reported separately: user-agent auto-render, Accept: text/markdown negotiation, and a static .md URL with its link tag, llms.txt entry and duplicate-content headers. How much content exists before JavaScript runs. Title, description, headings and indexing directives.
Can agents act on it?
Structured data about your business and what you sell, prices an agent can compare, form fields with proper labels, and CAPTCHAs that stop an agent from finishing the job.
Questions
What does AI agent readiness mean?
AI agents like ChatGPT agent, Claude and Perplexity can visit a website for a person to research, compare, book or buy. A page is agent-ready when those agents are allowed in, can read the content without running JavaScript, and can find the facts they need, like what you sell, prices and how to contact or book.
How is this different from an SEO or GEO check?
SEO checks focus on ranking in search results, and GEO checks focus on being mentioned and cited in AI answers. This checker focuses on the next step: whether an agent that lands on your page can actually use it to get a task done.
What is a markdown version for AI bots?
Markdown is easier and cheaper for AI systems to read than full HTML. Sites deliver it three ways: by detecting AI bot user agents, by answering requests that send Accept: text/markdown, or by publishing a separate .md URL linked from the page and llms.txt. The checker tests all three and reports each one separately.
Is serving markdown only to AI bots a problem?
It works for the bots on your list, but agents not on it miss out and audits cannot see it. Accept: text/markdown negotiation is safer because it is opt-in: browsers and Googlebot never send that header. Whichever you use, keep the markdown in sync with the page, send a Vary header, and never serve markdown to Googlebot or Bingbot.
Why does it say inconclusive for user-agent markdown?
Many sites only serve markdown to bots they can verify by IP range or reverse DNS. Our requests cannot pass that check, so when every AI user agent gets HTML we report inconclusive instead of not found. Your server or CDN logs will show what the real bots receive.
Why did a bot get blocked when my robots.txt allows it?
Firewalls, CDNs and security plugins often block AI bots by user agent before robots.txt ever matters. The checker requests your page with AI bot user agents from our server, so a firewall that verifies real bots by IP address may treat the real bot differently.
What happens to the URL I enter?
Our server fetches the public page to run the checks, and we keep a record of the URLs entered into our tools. The report shows on screen for free. If you download it, we ask for your email. Details are in our privacy policy.
Want these fixed for you?
The free intro audit turns this report into a short, prioritized fix list covering classic search, AI answers and agents.