Free AI visibility check

Can AI assistants actually read your website?

When a buyer asks ChatGPT, Google or Perplexity who to hire, it can only recommend you if it can open and read your site. If it can’t, you aren’t ranked lower — you’re left out of the answer.

We email the results. The audit itself needs no account, no credit card and no API key.

The audit is free. It isn’t a trial — the audit is the product.

yourcompany.com2 of 6 AI crawlers blocked
GPTBotChatGPT Search200 OK
OAI-SearchBotChatGPT Search200 OK
Google-ExtendedAI Overviews200 OK
ClaudeBotClaude citations403 Forbidden
PerplexityBotPerplexity answers403 Forbidden
BytespiderRate limited429
Your robots.txt says Allow. Your CDN returns 403. Every other audit tool reads the file — the file states an intention, the status code is the answer. Example result.

Checked against every known AI crawler

ChatGPTClaudePerplexityAI OverviewsGeminiCopilotMeta AI

Find out whether your site can be reached, read and quoted

Step #1

Paste your address

Enter any URL you want checked. No account, no API key, nothing to install.

Step #2

We fetch it as every AI crawler

Each known AI user-agent, twice — once with JavaScript and once without.

Step #3

Get your results

See which engines can reach you, what they can quote, and what to fix first.

Measured, not guessed

Your robots.txt says Allow. Your CDN says otherwise.

A low rank puts you somewhere. A 403 is absence. Every other audit tool reads the file rather than the response.

  • Every known AI user-agent, judged by HTTP status rather than by policy text.
  • A blocked crawler is reported with the answer surface it feeds — “ChatGPT Search”, “AI Overviews”, “Perplexity answers”.
  • Because a user-agent string is not something anyone can act on.

Verify any line yourself

$ curl -sI -A "PerplexityBot" https://yourcompany.com

HTTP/2 403
server: cloudflare
cf-mitigated: challenge

$ curl -s https://yourcompany.com/robots.txt

User-agent: PerplexityBot
Allow: /

The file and the server disagree. Only one of them met the crawler.

Fetched twice

Catch what blocks AI engines from reading you

AI crawlers largely do not run JavaScript. The gap between the two fetches is content no engine can quote, however good it looks in your browser.

  • Render parity measured per page, not assumed from your framework.
  • Structured data, semantic HTML, internal linking and content structure checked on the no-JS version — the one crawlers actually see.
  • Pages that block AI systems from finding or citing your content are flagged by name.

Render parity — /pricing

With JavaScript1,842 words
Without JavaScript210 words
Headings visible14 → 1
Structured datapresent → missing
Quotable by AI crawlers11%

Your pricing page exists. For a crawler, almost none of it does. Example result.

How scoring works

Computed in code, not by a language model

The same evidence always produces the same number. Access and render parity are gates, not contributions — they multiply the readiness score rather than adding to it.

  • A site that cannot be fetched cannot be fixed by better headings, so a 403 zeroes the score.
  • Off-site presence is reported separately, because it is the larger lever for citation.
  • Every claim in every generated file traces to a span on your own page. Untraceable claims are dropped, and the ratio is shown.

Readiness weights

Passage structure20
Entity consistency15
Structured data10
Freshness5
Off-site corroboration5

Gates — they multiply, they do not add

Verified crawler access× 0
Render parity× 0.1

The things nobody is measuring

97%

of domains that publish an llms.txt had it requested zero times in a month.

Ahrefs, 137,210 domains, May 2026
0

invented claims. Untraceable statements are dropped rather than published, and the ratio is shown in the report.

Provenance is checked on every run
×0

is what a blocked crawler does to your readiness score. Content work cannot compensate for a 403.

Access is a gate, not a weight
Being unreadable is worse than ranking badly.

A low rank puts you somewhere on the page. A 403 removes you from the answer entirely — and no ranking report shows that, because every other audit tool reads your robots.txt rather than the response your server actually gave.

Questions

Is it really free?

Yes. The audit needs no account, no credit card and no API key. An account buys history, the re-audit delta and engine-backed brand runs. That is not a trial — the audit is the product.

How is this different from an SEO audit?

An SEO audit tells you where you rank. This tells you whether you can be read at all. Ranking lower puts you somewhere on a page; a 403 removes you from the answer, and no ranking report shows that.

Which crawlers do you test?

Every known AI user-agent, including GPTBot and OAI-SearchBot (ChatGPT), ClaudeBot, PerplexityBot and Google-Extended (AI Overviews). Each is reported with the answer surface it feeds rather than as a raw user-agent string.

Do you score llms.txt?

We generate the file and score it zero for citation. Google states its Search and AI surfaces do not use it, and of 137,210 domains Ahrefs checked in May 2026, 97% of those publishing one were never requested that month.

Will this change anything on my site?

No. The check only makes HTTP requests to pages that are already public. Generated artifacts are files you ship yourself, and nothing is live until you ship it and verify-deploy.sh passes.

Audit your website now

Find out whether an AI assistant can open, read and quote you — before the next buyer asks it who to hire.

Free, about a minute. We email the results.

Free audit
No sign-up
No API key
Re-runnable with curl
Nothing deployed for you