Skip to content

Free tool · Free, no signup

AI readiness checker: a free AEO checker for your site

This AEO checker runs eight checks on whether ChatGPT, Claude, Perplexity, and Gemini can fetch your site, work out what your company is, and find something worth quoting. Every verdict comes with the evidence it was based on. Nothing is scored by a model, so two runs on an unchanged site give the same answer.

Reads your homepage, robots.txt, llms.txt, and looks for an about and pricing page. Takes up to half a minute. Free, no signup.

How it works

Free, no signup. Up to half a minute.

  1. Enter your domain

    The site as a whole, like example.com. For one article, use the GEO checker instead.

  2. We fetch what the engines fetch

    Your homepage, robots.txt and llms.txt, and an about and a pricing page if we can find them: up to ten requests, read without running JavaScript.

  3. Read eight verdicts with evidence

    Each check passes, warns or fails with what we found. When we can tell what the site is built on, the fixes are written for that platform.

A real run

Example result

basecamp.com, checked on 9 October 2026. Five of the eight checks pass. The one blocking finding is the missing Organization schema on the homepage. There is no /llms.txt and no FAQPage markup, which are warnings rather than blocks.

Result · https://basecamp.com

1 thing is stopping an engine reading this site

5 of 8 passing1 blocking

A warn is not counted as a pass. Rounding those up would make this number flatter than the site deserves, which is the one direction a score like this must never be wrong in.

AI crawlers allowed in robots.txt

Pass

GPTBot, ClaudeBot, PerplexityBot and Google-Extended can all reach your pages.

  • GPTBot
  • ClaudeBot
  • PerplexityBot
  • Google-Extended

GPTBot, ClaudeBot, PerplexityBot and Google-Extended have to reach your pages before any of them can quote you.

llms.txt present and parseable

Worth fixing

No /llms.txt. Assistants have to work out what you are from your marketing copy.

How to fix it: Publish /llms.txt as plain markdown — an H1 with your product name, a line on what it does, and links to the pages worth quoting.

The file assistants read to orient themselves: what you are, and which of your pages answer what.

Organization schema with sameAs links

Blocking

No Organization schema on your homepage. To an engine your brand name is a string, not a company.

How to fix it: Add Organization JSON-LD to your homepage with sameAs links to your Wikipedia, Wikidata, LinkedIn or Crunchbase pages.

sameAs is what ties your name to an entity the engines already know. Without it you are a string, not a company.

FAQPage schema present

Worth fixing

No FAQPage schema on the pages we read. Question-shaped markup is the easiest thing for an engine to quote.

How to fix it: Add FAQPage JSON-LD to a page that already answers real buyer questions. Do not invent questions to hold the markup.

Question-shaped markup on the pages that answer questions is the format an answer engine can lift verbatim.

Canonical, title and meta description set

Pass

Title, meta description and canonical are all set on your homepage.

  • Basecamp

These are the three strings an engine quotes back when it names you at all.

Content readable without JavaScript

Pass

Your homepage ships about 25904 characters of readable text before any JavaScript runs.

Most crawlers do not run your app. Text that only appears after hydration is text the engines never saw.

An /about page reachable

Pass

Your about page is reachable at https://basecamp.com/about.

It is where assistants look to describe who you are, and the answer they give when they cannot find one is usually wrong.

Public pricing page reachable

Pass

Your pricing page is reachable at https://basecamp.com/pricing.

Assistants skip products whose price they cannot find, and recommend the ones whose price they can.

What gets checked

The list is short on purpose. Everything here is provable from bytes we fetched and fixable in an afternoon.

  1. AI crawlers allowed in robots.txt. GPTBot, ClaudeBot, PerplexityBot and Google-Extended have to reach your pages before any of them can quote you.
  2. llms.txt present and parseable. The file assistants read to orient themselves: what you are, and which of your pages answer what.
  3. Organization schema with sameAs links. sameAs ties your name to an entity the engines already know. Without it you are a string, not a company.
  4. FAQPage schema present. Question-shaped markup on the pages that answer questions is the format an answer engine can lift verbatim.
  5. Canonical, title and meta description set. These are the three strings an engine quotes back when it names you at all.
  6. Content readable without JavaScript. Most crawlers do not run your app. Text that only appears after hydration is text the engines never saw.
  7. An about page reachable. It is where assistants look to describe who you are, and the answer they give when they cannot find one is usually wrong.
  8. Public pricing page reachable. Assistants skip products whose price they cannot find, and recommend the ones whose price they can.

What this is not

It is not a site audit. There is a whole category of tool that will hand you 200 findings about heading hierarchy and image alt text, and if that is what you need, Screaming Frog does it better than we would. Two of the eight checks have a deeper standalone version here, though: the sitemap validator reads every URL rather than confirming the file exists, and the structured data validator parses the JSON-LD you already publish instead of only checking for its presence.

It also cannot tell you the two things that most often cost a brand its citations, because neither lives on your own site: whether you have profiles on the directories and review sites the engines lean on, and whether anyone independent has written about your category with you in it. Those are off-page, and no crawler pointed at your domain will ever find them. Passing all eight of these and still being invisible is common, and it means the problem was never your markup. If on-page readiness is the half you want to go deeper on, Botric audits more of it than we do and we say so on the comparison page.

Every day, not once

The GEO audit

The free check runs once, on one URL. The GEO audit keeps the results for your site, turns failures into To-dos, and rechecks a page after you fix it.

Questions

What is AI readiness?

Whether an answer engine can fetch your pages, understand what your company is, and find something quotable. It is separate from whether it recommends you, which depends on what other sites say about your category. Readiness is the part you control entirely.

What does this checker actually do?

It fetches your homepage, your robots.txt, your llms.txt, and looks for an about and a pricing page, then runs eight deterministic checks over what came back. No AI is involved in grading, which is why every verdict comes with the evidence behind it. These are the same checks CueScout runs for paying customers.

Is this an SEO audit?

No, and deliberately not. Title lengths, alt text, and readability scores are what Screaming Frog and Ahrefs already do well. This checks the narrower set of things that decide whether an AI engine can use your site as a source, which conventional SEO tools mostly do not look at.

Why does a pricing page matter to an AI engine?

Because assistants answering "what does X cost" need a number they can repeat. "Contact us for pricing" gives them nothing, so they tend to recommend the competitor whose price they can state. This is one of the more annoying findings to act on and one of the more reliable ones.

What is llms.txt?

A plain markdown file at /llms.txt that tells assistants what your product is and which of your pages are worth reading. It is a convention rather than a standard, adoption is uneven, and no engine requires it. It costs an hour to write, which is why it is on the list.

My site passes everything and AI still does not mention me. Why?

Because readiness is necessary and not sufficient. Passing all eight means the engines can read you. Whether they recommend you depends on independent coverage: reviews, comparisons, and community threads where other people name you. That is the harder half, and the visibility checker is where you measure it.

Is this an AEO grader?

It grades the half of AEO you control on your own site: whether answer engines can fetch it, understand what your company is, and find something to quote. It does not score how often engines actually name your brand. For that, the AI visibility checker asks a buying question on four engines and shows which ones mention you.

Do you keep the sites people check?

Each run is logged with the URL, the verdicts and the network it came from, so we can spot abuse and see which tools get used. It is not tied to an account. Tracking the checks over time is the paid product, which runs against a site you have added to your own account.

Track it every day instead of once

CueScout runs these checks on a schedule and turns the gaps into To-dos.