Free tool · AEO Readiness Checker
AEO readiness checker: is your page built to be quoted as the answer?
See whether a page is built to be quoted as the answer — or skipped for a competitor's.
In short
The AEO Readiness Checker measures how ready one public page is to answer a question: AI crawler access, indexability, metadata, structure, answer clarity, links, freshness, structured data and authorship. You get a prioritised checklist of fixes that make the page easier to quote, with evidence for every finding and a score to track improvement.
What this checks
Coverage: Audits one public page as served to a bot (no JavaScript) plus the site's robots.txt and llms.txt. Crawler access is checked for the answer crawlers of Google, Bing, ChatGPT, Perplexity and Claude; training crawlers are reported for information only. Pages behind a login cannot be checked.
- AI crawler access: whether robots.txt lets ChatGPT, Perplexity, Claude, Google and Bing crawlers read the page; llms.txt
- Indexability: status, noindex, canonical, language, viewport
- Title, meta description and Open Graph tags
- Heading structure, landmarks and a liftable answer under the H1
- Content depth, links, freshness signals, JSON-LD validity and authorship
Limitations
- This is a heuristic readiness audit of ONE page's HTML as served to a bot without JavaScript. It is not a Google, ChatGPT or Perplexity score and does not predict rankings or citations.
- Content rendered only by client-side JavaScript is not visible to this check (and often not to answer engines either).
- AI crawler access is read from the robots.txt rules only. A firewall or bot-protection service can still block a crawler that robots.txt allows; that is not visible to this check.
- Scores are our own documented weights (see the methodology section on the tool page); treat them as a prioritised to-do list, not a grade.
What you get
- A prioritised checklist of fixes that make the page easier to quote, with evidence for every finding and a score to track improvement.
- Free and without sign-up: up to 5 checks per visitor per day; identical inputs within a few hours reuse the stored result.
- Every result names its data source and the time of the check, lists its limitations and comes with a shareable report link.
- A documented heuristic readiness score — not an official Google score and not a prediction of snippets or citations.
How to use it
- Paste the full URL of one public page. The server fetches it the way a crawler would — no JavaScript, a 10-second limit and 2 MB of HTML — and reads the site's robots.txt and llms.txt.
- Optionally add the question the page should answer. The check then measures how much of that question's wording appears in the H1 and the first two paragraphs.
- Run the check. Ten categories are scored in a few seconds, with the actual value found on the page attached to every finding.
- Work down the prioritised checklist — fails first, then warnings — and re-run after each fix to watch the score move.
- Leave your email only if you want us to follow up. The shareable report link works without it.
How to read the results
- The overall score (0–100) is the weighted average of ten category scores. Each category starts at 100; every fail deducts 40 and every warning 15, so one fail in a heavily weighted category (answer clarity, crawler access) moves the total more than several warnings in a light one.
- Every finding shows the value it was based on — the title length, the robots.txt rule, the first paragraph — so you can verify it on the page.
- The prioritised checklist lists fails as high priority and warnings as medium priority, in that order. Info findings are context and deduct nothing.
- Structured data loses points for missing JSON-LD, blocks that do not parse and FAQ questions that are not in the visible text; an Article headline that differs from the title is a warning.
- The report is stored at a shareable link. The same URL and question within one hour reuse the stored result.
Methodology
How the check works
- The server fetches the page over HTTP(S), follows up to five redirects and analyses the HTML as served — content rendered only by client-side JavaScript is invisible to this check, as it often is to answer engines.
- robots.txt is parsed with RFC 9309 matching (the crawler's own group, else the * group; longest path wins; allow wins ties) for eight answer crawlers. A blocked answer crawler fails the category; a blocked training crawler is informational.
- Each category starts at 100; every fail deducts 40 and every warning 15, never below 0. The overall score is the weighted average using the weights in the table.
- The score is our heuristic readiness measure, not a Google, ChatGPT or Perplexity score, and it does not predict rankings or citations.
| Category | Weight | What is checked |
|---|---|---|
| AI crawler access | 1.5 | robots.txt rules for the answer crawlers Googlebot, Bingbot, OAI-SearchBot, ChatGPT-User, PerplexityBot, Perplexity-User, Claude-SearchBot and Claude-User (any blocked = fail; robots.txt 5xx = fail, unreachable = warn, missing = pass). Training crawlers blocked = info. llms.txt present or missing = info. |
| Crawlability & indexing | 1.5 | HTTP 200; no noindex (meta or X-Robots-Tag); canonical present and on the same host; a lang attribute; a viewport meta tag. |
| Title & meta | 1 | Title 15–65 characters; meta description 50–160 characters; og:title, og:description and og:image present. |
| Heading structure | 1.25 | Exactly one H1; no skipped heading levels; a <main> or <article> landmark; question-style headings (info). |
| Answer clarity | 2 | The first paragraph after the H1 is 40–300 characters. With a question given: the share of its content words found in the H1 and first two paragraphs (60% or more passes, 30% or more warns, less fails). |
| Content depth & readability | 1.25 | At least 300 visible words; average paragraph 600 characters or fewer; lists or tables (info); average sentence 25 words or fewer; alt attributes on images. |
| Links | 0.75 | At least 3 internal links; at least 1 external link; 80% or more descriptive anchors. |
| Freshness signals | 0.75 | article:modified_time or og:updated_time, JSON-LD dateModified/datePublished, article:published_time, a <time datetime> or a Last-Modified header — warn when older than 365 days, info when undetectable. |
| Structured data | 1.25 | JSON-LD parses; types listed; every FAQPage question appears in the visible text; an Article headline matches the title or H1; an entity is present (info). |
| Authorship & trust | 0.75 | An author meta tag, a JSON-LD author or a visible byline; an Organization in the JSON-LD (info). |
Each category starts at 100. Every fail deducts 40 points and every warning 15; pass and info findings deduct nothing, and a category never drops below 0. The overall score is the weighted average of the category scores (total weight 12). The checklist lists fails as high priority and warnings as medium priority, in that order.
What is AEO?
AEO is the practice of structuring content so that an answer engine — a featured snippet, voice assistant, AI Overview or chatbot — can lift a clear, self-contained answer from it.
Typical AEO work includes leading each page with a direct answer, using question-shaped headings, keeping one idea per section, adding FAQ and other structured data, and showing authorship and update dates. AEO overlaps with GEO but focuses on the page-level format of the answer rather than on brand-level visibility across sources.
FAQ
AEO Readiness Checker questions
No. The ten categories, their weights and the deductions are published on this page and applied mechanically to the HTML. No platform publishes a readiness score; this one is ours, and it does not predict rankings or citations.
Let's get on a call
Book a free consultation meeting below, and let’s understand what you actually require
- Free audit, no obligation
- Reports from your own Search Console & GA4
- No fabricated metrics — ever