Is your site ready for AI agents?

See how AI agents see your site: llms.txt, crawler rules, an agent card, and whether bot protection turns them away.

This check runs in Supercheck.

The free checker isn't available on this site. The method below shows what it looks at.

How we check

HTTPS: the home page ends on an https URL.
llms.txt: /llms.txt answers 200 and its first line is a Markdown heading (llmstxt.org).
AI crawler rules: robots.txt does not disallow AI search and user agents (OAI-SearchBot, ChatGPT-User, Claude-SearchBot, Claude-User, PerplexityBot, Perplexity-User), matched by RFC 9309.
Not blocked: the home page doesn't answer SupercheckBot with a bot challenge.
Discovery, not counted: an A2A agent card at /.well-known/agent-card.json, and MCP discovery at /.well-known/ai-catalog.json or /.well-known/mcp/server-card.json. These paths are still settling.

We read the first 128 KB of robots.txt and say when it was cut short.
Blocking AI training crawlers is a valid choice, so we list them without judging.
One check from one Cloudflare data center, usually the one nearest you. It can't tell you whether the site is down for everyone.

Is not publishing an agent card a failure?: No. Most sites don't run an agent. Discovery is shown as published or not published.
Do you store the URL I check?: Results sit in a 10-minute cache. Logs keep the host and the first path segment, never the full URL or query string, and never your IP address.
Can I stop my site from being checked?: Yes. The SupercheckBot page explains how to ask for an opt-out; we add your domain to a block list.