Can AI actually read your website?
Below is your homepage the way a person sees it, and the way a crawler sees it. If the two disagree, that is the whole problem. Full audit in about two minutes. No email, no signup, no catch.
wireframe placeholder · your real homepage goes here
The scan runs seven checks, in order.
Seven checks, run in order, in about two minutes. Each bar is one check, sized by how long it takes. The red line is a scan in progress.
Rules leak between crawler groups.
Groups do not inherit. /pricing is shut to one bot and wide open to its sibling. Almost nobody means that.
Your sitemap arguing with your robots.txt.
A sitemap invites. A Disallow refuses. Do both to one URL and search consoles flag it, then the crawler resolves it the least useful way.
exit codes · three ways a site fails a bot
Blocked
The bot was refused at the door. robots.txt, firewall, or CDN said no.
you fix itUnreadable
It got in and could not parse the page. Usually rendering, sometimes markup.
you fix itNot there
It got in, understood everything, and the file it asked for does not exist.
nobody fixes itReadable is not the same as cited. Fixing access gets you in the room; getting named in the answer is generative engine optimization.
talk to us about GEOA free tool that checks whether AI crawlers (GPTBot, ClaudeBot, Claude-User, OAI-SearchBot, PerplexityBot, Google-Extended, and more) can actually read a public website. No login required.
How to use
Submit any public URL at: ai-visibility-scan
The scan takes about two minutes and checks seven layers: reachability, robots.txt, crawler access, rendering, structured data, sitemap, and content parseability.
What it checks (7 layers)
- Reachability: DNS, TLS, and redirect chain.
- robots.txt: fetched and parsed group by group, no inherited rules assumed.
- Crawler access: 22 named AI crawlers probed one at a time.
- Rendering: server-sent HTML compared against the browser DOM.
- Structured data: schema.org markup, meta tags, and heading tree.
- Sitemap: every URL where the sitemap and robots.txt disagree.
- Content parseability: text actually extracted from up to 24 URLs.
Output
A report at a shareable link (/report/:token) with a plain-language verdict, a crawler
permissions table, a leak matrix showing where sibling crawlers get different answers on the same
path, severity-ranked findings with fixes, and a PDF version. Never a 0-100 score.
Built by
Atomic Glue, [email protected], atomicglue.co