cd /news/ai-crawlers/how-to-check-whether-ai-search-can-r… · home › topics › ai-crawlers › article
[ARTICLE · art-153479] src=dev.to ↗ pub= topic=ai-crawlers verified=true sentiment=↑ positive

How to check whether AI search can read your website

The maintainer of GEO Doctor released an MIT-licensed checker that diagnoses why AI search crawlers cannot read a website, testing four conditions: robots.txt rules blocking search crawlers such as OAI-SearchBot and PerplexityBot, noindex tags, client-rendered text invisible without JavaScript, and firewall or CDN blocks. The tool runs from a Node.js 18+ command line or inside AI assistants like Claude Code and Codex, keeps data in local plain files with no server, and can generate a fact page, FAQ, llms.txt and structured data hosted on GitHub Pages.

by read2 min views3 publishedOct 20, 2026

Check four things: whether robots.txt blocks AI search crawlers, whether the page carries noindex, whether the main text is visible without running JavaScript, and whether crawlers are blocked by a firewall or CDN. GEO Doctor (geo-doctor) has a free, MIT-licensed checker for these.

#

Why AI search may not see your site

AI assistants that search the web fetch pages first and answer from what they fetched. If they cannot fetch your page, or get an empty shell, they will not cite you. Four usual causes:

robots.txt blocks AI search crawlers. There are two kinds of AI crawler. Search crawlers such as OAI-SearchBot, ChatGPT-User, PerplexityBot and Claude-SearchBot fetch pages to answer questions; blocking them hides you from AI search. Training crawlers such as GPTBot, ClaudeBot, Google-Extended and CCBot collect training data; blocking them usually does not affect AI search. Many templates and security plugins block both kinds at once, so look at them separately. 2. noindex. A noindex meta tag or header makes search engines and some AI search skip the page. 3. Client-rendered text. If the HTML is nearly empty until JavaScript runs, fetchers that do not run scripts see a blank page. 4. Firewall or CDN rules that treat crawlers as attacks.

#

Checking with GEO Doctor

GEO Doctor checks robots.txt, AI crawlers, noindex and whether the main text is visible, and tells you which item fails. It checks technical readability only, not whether the content is good. It runs from a Node.js 18+ command line or inside AI assistants such as Claude Code, Codex and Kimi Code. Your data stays in plain files in your own project; GEO Doctor has no server.

#

Fixing what you find

  • robots.txt: allow the search crawlers if you want AI search to read you. Whether to allow training crawlers is a separate choice.
  • noindex: check whether a staging setting leaked into production.
  • Invisible text: serve key content in the initial HTML, or publish static versions of important pages.
  • If you want a page written for AI, GEO Doctor can turn your fact card into a fact site (fact page, FAQ, llms.txt, structured data) hosted free on GitHub Pages.

Being readable is only step one: AI also needs clear, consistent content about you to cite.

Source: https://github.com/Fangx-AI/geo-doctor Disclosure: I maintain GEO Doctor, and this article was drafted with AI assistance (Claude) and reviewed by me.

── more in #ai-crawlers 4 stories · sorted by recency
── more on @geo doctor 3 stories trending now
sponsored brought to you by zahid.host 4,200+ EU-deployed projects
reading about agents? ship yours in a single git push.

Run your AI side-project on zahid.host

EU-based hosting, git-push deploys, automatic HTTPS, no cold starts. Free tier with a custom domain — perfect for shipping the agent you just read about.

$git push zahid main
→ Live at https://your-agent.zahid.host ✓
Get free account → Pricing
from €0/mo · no card required
LIVE [news/how-to-check-whether…] indexed:0 read:2min 2026-10-20 · —