This is the markdown version of this page. It is the same content AI assistants and crawlers read.

Run a free AI Visibility Scan →
[Atomic Glue](atomicglue.co)

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.

scan
ungated: trueemail_required: falsedomains_logged: truereport_ttl: 30d
GET / 200 · text/html · 14.2 KB3 gaps

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.

01Can bots reach the site?dns · tls · redirect chain8s
02What does robots.txt allow?fetch · parse · group map12s
03Which AI crawlers get in?22 named agents, one at a time22s
04What loads without JavaScript?server html vs browser dom36s
05Is the structured data there?schema · meta · heading tree18s
06Does the sitemap agree with robots.txt?every url the two files disagree on16s
07Can the text be extracted?text extracted from 24 urls26s

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

403

Blocked

The bot was refused at the door. robots.txt, firewall, or CDN said no.

you fix it
200

Unreadable

It got in and could not parse the page. Usually rendering, sometimes markup.

you fix it
404

Not there

It got in, understood everything, and the file it asked for does not exist.

nobody fixes it

Readable 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 GEO
Free AI Visibility Scan | Atomic Glue

A 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)

  1. Reachability: DNS, TLS, and redirect chain.
  2. robots.txt: fetched and parsed group by group, no inherited rules assumed.
  3. Crawler access: 22 named AI crawlers probed one at a time.
  4. Rendering: server-sent HTML compared against the browser DOM.
  5. Structured data: schema.org markup, meta tags, and heading tree.
  6. Sitemap: every URL where the sitemap and robots.txt disagree.
  7. 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

Schedule a call.

30 min · Video call

1
Date
2
Time
3
Details
Opens a lens that shows what AI reads on this page.