AI Readiness Checker
See how LLMs, AI assistants and browser agents read your page — content extraction, structured data, entity clarity, trust, crawler policy and agent usability, scored with concrete fixes.
How the score works
Seven weighted categories (summing to 100), based on Google Search guidance for AI features and the broader practice of making content easy for LLMs and agents to extract, understand and act on.
- Crawlability & indexability (20)Returns 200, not noindexed, not blocked by robots.txt — Google's AI features rely on ordinary indexing.
- Content extraction quality (20)Main content present in the server HTML, low boilerplate noise, single H1, clean heading order, declared language.
- Entity & service clarity (15)Title, description, descriptive H1 and a discoverable contact route — who you are, what you do, how to reach you.
- Structured data (15)Valid JSON-LD with core identity types, aligned with visible content.
- Trust & citation signals (10)HTTPS, visible dates, author/organisation attribution, privacy/terms links.
- AI crawler governance (10)robots.txt exists and takes an explicit position on major AI crawlers.
- Agent readiness (10)Labelled form fields, meaningfully named links, image alt attributes — so browser agents can act.
How we read your page: we analyse the server-rendered HTML — we do not execute JavaScript. That is deliberate: it is what most crawlers and many LLM fetchers actually see. If your content only appears after client-side rendering, this tool will show you what an AI system sees without it.
Honest note on Google: Google says appearing in AI Overviews and AI Mode needs no special setup beyond ordinary Search best practices — so the biggest wins here are classic technical SEO: be crawlable, indexable, fast and clearly structured. Blocking or allowing AI training crawlers is a separate, legitimate business choice; we report your policy without judging it.
FAQ
Does a high score guarantee I appear in ChatGPT or Gemini?
No — no tool can promise that. A high score means AI systems can cleanly read, understand and cite your page. Whether a given assistant surfaces it depends on its own retrieval and your topical authority.
Should I block AI crawlers?
That is your call. Blocking training bots (GPTBot, CCBot, Google-Extended) protects content; allowing them can increase citations. We flag only the absence of an explicit policy, because leaving it to the default looks unconsidered either way.
Why does my JS app score low on extraction?
Because the main content is not in the initial HTML. Server-render or prerender it so the text exists before JavaScript runs — good for crawlers, LLM fetchers and Core Web Vitals alike.
Related tools
- llms.txt Checker — validate the llms.txt this page’s site publishes.
- llms.txt Generator — build one from your sitemap.
Last reviewed: 2026-07-09. Category weights follow the project’s AI-readiness model and Google Search Central guidance current at that date.
Frequently asked questions
▸ ▾ What does AI readiness measure?
How easily LLMs and AI agents can read and understand your page — content extraction, structured data, entity clarity, trust signals, crawler policy and agent usability.
▸ ▾ Why did it score my page low when it looks fine?
Usually because the content is rendered client-side (only after JavaScript runs), so a bot sees an empty shell. Server-render your content to fix it.