Free tool · no sign-up

Can AI actually read your website?

Most AI crawlers never run your JavaScript. We fetch your page exactly the way they do, then show you what is left — the words they can read, the crawlers you are blocking, and what to fix first.

Or try:

Takes about a second. We read the public HTML only, store nothing, and never run your JavaScript — because most AI crawlers don't either.

Four questions an assistant asks before it quotes you.

SEO tools assume a crawler that renders your page. AI crawlers mostly don't. This scores the harsher, more honest case.

01

Reachable

Does the page answer a plain, non-browser request — and does your robots.txt let in the crawlers that feed live answers?

02

Readable

Are the words in the HTML, or assembled by JavaScript the crawler will never execute?

03

Quotable

Is the content shaped into passages a model can lift — clear headings, direct answers, structured data?

04

Citable

Can it tell who you are and when this was last true, so it is willing to name you as the source?

Coming soon

The same check, on every page you visit.

A Chrome extension that shows a page's AI-readability the moment you land on it — yours or a competitor's. Same engine as this page, no tab switching.

In build. Tell us where to send it and you'll get it first.

Get it first

What it will do

  • A readability score in the toolbar on every page load
  • Toggle to view any page as a non-rendering crawler sees it
  • Flags blocked AI crawlers and missing structured data inline
  • Compare a competitor's page against yours, side by side

Straight answers.

Why would an AI assistant not be able to read my website?

Most AI crawlers do not execute JavaScript. If your page builds its content in the browser, the crawler receives an almost empty HTML shell — your site looks perfect to you and close to blank to the model. The other common cause is robots.txt: plenty of sites block AI crawlers without realising which of them feed the answers people see today.

Is this the same as an SEO audit?

No. An SEO audit assumes a rendering crawler like Googlebot, which does run your JavaScript. This checks the harsher case: a non-rendering fetch, the crawler allow-list that governs AI answers, and whether your content is shaped into passages a model can quote and attribute.

Does blocking GPTBot hurt me?

It is a rights decision, not a mistake, so we do not score it against you. Blocking training crawlers keeps your content out of future model weights — which is where long-term brand recall comes from — but it does not affect live answers. The crawlers that matter for answers today are OAI-SearchBot, ChatGPT-User, ClaudeBot, Claude-User, PerplexityBot and Google-Extended.

How accurate is the score?

Every check shows the evidence it scored on, so you can verify it yourself. What we cannot observe, we do not assert: we read one page's raw HTML, robots.txt, llms.txt and sitemap, and we say so. It is a diagnostic, not a ranking prediction — nobody can promise a model's output.

Do you store the sites people audit?

No. The audit runs on request, returns the result and keeps nothing. No sign-up, no database, no follow-up email unless you ask for one.

Know what's broken. Want it fixed?

We run a growth engine that tests, learns and compounds — on our own sites first, then on yours.

Talk to us