AEO Readiness Checker

Checks whether AI answer engines and search engines can read a web page, and tells you what to fix. Give it up to 100 page addresses. You get one row per page with a 0 to 100 readiness score and, for every failed or weak check, a plain-language fix.

What it checks

• Crawler rules. Whether robots.txt lets the main AI search and assistant crawlers and the big search engines in, and whether the training crawlers are allowed or blocked (reported, not scored).
• Indexing signals. noindex, canonical link, page title, description and language.
• Structured data. JSON-LD that parses, and which schema types it declares.
• Answer-first text. Whether the first paragraph is a direct answer of about 40 to 60 words.
• Headings. Exactly one H1, and subheadings with enough of them written as questions.
• Site files. A sitemap, an llms.txt, a Bing site tag, and a visible date.

The score says whether engines can read and lift the page. It is not a prediction that any engine will mention you.

Input

Field	What it does
urls	1 to 100 public web pages. Each is fetched once, plus that site's robots.txt, sitemap.xml and llms.txt.
includeFixFiles	Off by default. When on, also writes starting files per page: a robots.txt block, an llms.txt, and FAQ structured data built only from question headings that already have an answer paragraph on the page.

Private, local and non-web addresses are refused. There is no option to change that.

Output

One dataset row per page:

{
  "url": "https://example.com/guide",
  "finalUrl": "https://example.com/guide",
  "status": "ok",
  "score": 74,
  "checks": [
    {"id": "answer", "title": "Answer-first paragraph", "result": "warn", "message": "First paragraph is 112 words.", "fix": "Open with a 40 to 60 word direct answer."}
  ],
  "robots": "found",
  "sitemap": 200,
  "llmsTxt": null,
  "error": null,
  "fetchedAt": "2026-10-09T12:00:00Z",
  "checkerVersion": "1.0.0"
}

status is unreadable (with the reason in error) when the page cannot be fetched or answers an HTTP error. Open the Overview view for a table, or All checks for every check with its fix. With includeFixFiles, the starting files are in the run's key-value store under FIX_FILES.

Price

Pay per event: USD 0.01 per page audited and USD 0.02 per page for the starting files (only when you turn them on). Pages that cannot be read are never charged. Set a maximum charge for the run and it stops there. Platform usage is included in these prices.

How it behaves

• One request a second to any one site, at most 4 pages at a time. It identifies itself as AEO-Readiness-Checker/1.0.
• It fetches only the pages you list and that site's robots.txt, sitemap.xml and llms.txt. It sends no cookies and does not log in anywhere.
• It does not rank your page against others, track citations, or tell you what to write. It checks technical readiness only.
• It cannot see pages that need JavaScript to show their text: it reads the HTML the server sends.

Support

Open an issue on this Actor's page, or write to hello@ticassociation.com. Made by Tori, under the name TIC.