How robots.txt Is Quietly Blocking the AI Crawlers You Actually Want
By Adam McClarin, CISSP · Meraki is Love (Soulful Tech) · Friendswood, Texas
The assumption that breaks visibility
Blocking bad bots and blocking AI crawlers often use the same rule by accident.
When we found our own crawler activity was lopsided, one engine dominant, two others barely present, the first place we looked was robots.txt. Most teams write that file once, early, usually to keep aggressive scrapers off a staging environment. Nobody revisits it once the site is live.
The problem is that a rule written to block a scraper three years ago can end up blocking GPTBot, ClaudeBot, or Google-Extended today, without anyone noticing, because the site still ranks fine in traditional search. AI visibility fails silently. There is no error page, no broken link. The crawler just does not come back.
Three patterns worth checking today
A wildcard rule, a missing allow, and a crawl budget nobody planned for.
A blanket Disallow rule under User-agent: * catches every crawler unless a specific engine is explicitly allowed underneath it. If the file only has one generic block, check whether it is silently catching the AI engines too.
Some teams add rules for GPTBot without knowing ClaudeBot and Google-Extended are separate user agents entirely. Blocking one does nothing to the other two, and allowing one does not mean the others are welcome.
Crawl budget matters more than people expect. A site with thousands of pages and a thin server response can get deprioritized by a crawler long before robots.txt becomes the issue. Check response times before assuming access is the only variable.
How to check your own site
Three steps, no special tools required.
Pull up yourdomain.com/robots.txt directly in a browser and read every line. Look for User-agent: * blocks and check what falls under them.
Search for GPTBot, ClaudeBot, and Google-Extended by name. If they are not mentioned at all, that usually means they are allowed by default, which is good. If they are listed under a Disallow, that is the fix.
Run the domain through an audit tool that checks crawler access specifically, not just traditional SEO signals. That is the piece most general purpose SEO tools skip entirely.
See where your own site stands across SEO, AEO, GEO, and security in about 30 seconds.