Free tool
Is your website ready for AI agents?
Agents now browse, read and buy on behalf of millions of people. Enter a URL and we will run 18 checks that decide whether they can find your site, understand it and act on it.
What the score means
Twelve checks are scored, weighted by how much they matter today. The rest are shown for information, because they only apply to sites with APIs, logins or shops. 80 and above is agent-native; below 20 means agents see you like any old web page.
We fetch only public pages of the site you enter, identify ourselves as dots.online, store nothing and cache results for five minutes.
- 1Served over HTTPS
- 2Title, description and language
- 3Structured data (JSON-LD)
- 4robots.txt present
- 5XML sitemap
- 6Discovery Link headers
- 7llms.txt
- 8Markdown on request
- 9AI user agents allowed
- 10Content signals
- 11Page loads for an agent
- 12API catalog
- 13MCP server card
- 14Agent skills index
- 15WebMCP tools in the page
- 16OAuth discovery
- 17Web Bot Auth keys
- 18Agentic commerce
Questions and answers
What is agent readiness?
Agent readiness describes how easily AI agents can discover your website, read it accurately and take actions on it. It covers crawl rules, machine-readable content like llms.txt and markdown, and interfaces such as MCP servers, WebMCP tools and API catalogs.
Should I block AI bots?
Separate training crawlers from user agents. You may block GPTBot or Google-Extended to keep content out of training, while allowing ChatGPT-User, Claude-User and similar agents that visit only when a person asks. Blocking those makes your site invisible to people using assistants.
Does llms.txt help SEO?
Not directly for classic search rankings. It helps AI assistants and agents understand and cite your site, which is where more and more discovery happens.