Free test — 30 seconds, no sign-up
Can AI agents see your site?
We query your page live using the user agents of GPTBot, ClaudeBot, PerplexityBot and Google, then show you exactly what they receive. Not an estimate: your server's actual response.
We keep the address tested and its score to follow how the tool is used, and each test reaches our internal mailbox with the technical connection data — described in our privacy policy. Nothing is published or shared with any third party.
- Reading robots.txt
- Querying with each AI crawler
- Rendering the page without JavaScript
- Looking for structured data
We could not test your site
Your server refused our reference request, made with an ordinary browser user agent. The refusals then given to AI agents prove nothing: it is not them being turned away, it is our address.
This is how IP-range filtering behaves — common with Cloudflare, Datadome or Akamai, which turn away datacentre traffic. It can only be observed in your own server logs.
That is exactly what the full audit examines.
Request an auditAccessibility score
What each agent sees
Reuse of your pages, as declared in robots.txt
What the agent can read
This test queries your server from our own infrastructure, announcing each agent by name. Two things escape it, and they cut both ways. IP-range filtering may refuse us while your visitors get through. And some firewalls verify a bot's real identity by its address: they will turn our request away while letting the genuine crawler in, making us report a block that is not one. Only your server logs settle it — that is what the full audit is for.
Want to know what this test cannot see?
The full audit opens your server logs and WAF rules, template by template, and puts a cost on every fix.
About this test
What this test measures, and what it does not
How exactly does the test work?
Our server sends ten requests to the address you give: one with an ordinary browser user agent, used as a reference, and nine with those of the agents tested — ChatGPT-User, Claude-User, Perplexity-User, OAI-SearchBot, PerplexityBot, Bingbot, Googlebot, GPTBot and ClaudeBot. Two more go to the domain root, to read robots.txt and check for an llms.txt — twelve in total, which you will find in your logs. It then reads your robots.txt, measures the text actually present in the HTML once tags and scripts are stripped, looks for your Schema.org structured data, and checks whether an llms.txt exists. No page beyond the one you supply is crawled.
Why is Google-Extended tested with Googlebot's user agent?
Because Google-Extended has no HTTP user agent of its own. It is a control token Google reads in your robots.txt: the crawling itself is done by Googlebot. Querying your site with a "Google-Extended" string would prove nothing. So we query with Googlebot and read the directive in your robots.txt — the only correct method.
Can the test be wrong?
Yes, in one specific direction, and you should know it. It detects blocks based on user agent and robots.txt. It does not detect IP-range filtering — and Cloudflare, Datadome and Akamai often verify IP and reverse DNS on top of the string. A site can therefore score well here and still refuse real crawlers. The reverse is rarer. That is exactly what separates this test from the full audit, which reads your server logs.
My score is low. Where do I start?
In this order, because each step makes the next one worth doing: first the refusals (401, 403, 429), since nothing else matters while a crawler cannot get in; then text readable without JavaScript, since an empty page equals an absent one; then structured data, which spares the model from guessing your prices; llms.txt last, its effect being modest.
Can I test a competitor's site?
Nothing stops you: the test only issues public requests, as any browser would. It bypasses no protection and collects nothing beyond what the server answers. We simply cap the number of scans per hour and per connection.