AI Ready Check
EN RU

Check how AI sees your site

Enter a domain and see how understandable your site is to AI systems, what they extract from your content, and what to improve for an AI-ready presence.

By entering a site address you agree to our privacy policy.
Visibility in AI search
See how visible your site is in answers from AI systems and search services.
Content understanding
Check whether AI correctly interprets your text, meaning and offers.
AI-ready score
Get a readiness score and concrete recommendations to improve.
What it is

Ready when you are

AI Site Scorer is a public readiness scanner. Give it any domain and it runs real HTTP probes — as GPTBot, ClaudeBot, PerplexityBot and other agents — then checks the emerging standards that decide whether AI systems can find, read and cite your site: llms.txt, robots Content Signals, structured data, MCP and API catalogs. You get a graded scorecard, the exact failing checks, and how to fix them.

→ llms.txt · robots Content Signals · MCP
→ Real HTTP probes across 8 AI bot user-agents
→ Independent evidence-based AI trust evaluation
37%
Overall readiness
67 / 182 F
Poor
✓ Homepage reachable over HTTPS
✕ No CAPTCHA / bot challenge on homepage
✕ llms.txt present
Why it matters

Search is turning into answers

The web is shifting from ranked links to AI-generated answers — and those answers are assembled by machines that crawl, parse and judge your pages on their own terms. If an agent can't reach, read or trust your site, you never appear in the reply a user sees, and you never find out why.

01
Answers, not ten blue links
Google's top result is now a Gemini answer and DuckDuckGo shows AI summaries. Most users read the generated answer and never click through — if you are not in it, the visit never happens.
02
Meta tags are fading
Agents fetch your raw HTML, summarize it and rank it with their own algorithms. Google is deprecating FAQ rich results in 2026 — hand-tuned meta tags matter less than whether the content is actually there and readable.
03
Readiness is measurable
Bot access, llms.txt, Content Signals, structured data and MCP are concrete, testable signals. This tool probes each one as a real AI crawler and scores exactly what agents see.
agent://checkout live
→ GET /product/42
← 402 Payment Required
→ POST /pay x402
← 200 Paid ✓
$29.00 settled agent-to-agent
Where this is going

AI agents will soon browse — and buy

The next web is not just read by AI, it is acted on by it. Standards like x402 let autonomous agents complete a purchase end to end — discover a product, evaluate the seller and pay — without a human ever opening the page.

x402
Agents that pay
Checkout becomes a machine-to-machine call, not a form a person fills in.
MCP
Chosen before you're seen
If your site is unreadable or blocked, you are filtered out before a human is shown a choice.
REV
Revenue tracks AI-readability
Readiness becomes revenue infrastructure, not SEO hygiene.
What we check

Six dimensions, one scorecard

Every scan is live. We fetch your domain in real time — no cached third-party index — and grade what an agent actually receives. Each dimension is scored on its own, so the report shows exactly where the points are lost and what to change.

01
Discoverability
sitemap.xml, robots.txt, llms.txt, /.well-known/ descriptors and API catalogs (RFC 9727) — whether an agent can find the map of your site at all.
02
Content
Text present in raw HTML without JavaScript, JSON-LD structured data, Markdown content negotiation, compression. GPTBot, ClaudeBot and PerplexityBot largely do not run JS — an empty SPA shell reads as an empty page.
03
Bot access
Real requests sent as GPTBot, ClaudeBot, PerplexityBot, Applebot, Bingbot, Amazonbot and others, looking for blocks, CAPTCHAs and challenge pages served instead of content.
04
Policy
robots.txt rules for AI crawlers, Cloudflare Content Signals, AIPREF and content-usage declarations — whether your terms are stated in a form machines can read rather than buried in a legal page.
05
Capabilities
MCP server cards, A2A agent cards, Agent Skills indexes, OpenAPI descriptions and OAuth metadata — what an agent can do with you once reading is not enough.
06
Commerce
x402 payment endpoints: whether an autonomous buyer could complete a transaction unassisted. Informational today — reported, not scored — because almost nobody supports it yet.

Checks are weighted by requirement level: established standards count for more than recommended or experimental ones, so a site is never punished for skipping a signal the industry has not settled on. llms.txt is recommended, not required.