Is anyone ignoring your AI crawler block?

What the free checker can and cannot see

The AI visibility checker and the robots.txt checker read the files you publish. They can confirm that your file blocks GPTBot the way you meant it to. They cannot see who visits your server, so they cannot tell you whether GPTBot, or something calling itself GPTBot, kept requesting your pages after you blocked it.

Why a Disallow line does not settle the question

• Fetchers acting for a user follow different rules. OpenAI's crawler documentation says of ChatGPT-User that "because these actions are initiated by a user, robots.txt rules may not apply." Perplexity's documentation says its Perplexity-User fetcher "generally ignores robots.txt rules." A Disallow aimed at GPTBot or PerplexityBot does not cover either one.
• Some crawlers have no published policy to hold them to. Bytespider, DeepSeekBot and LAIONDownloader are the usual examples. For those, your logs are the only record of what they did.
• A user agent is a string anyone can send. A request that says GPTBot may not come from OpenAI at all. OpenAI (GPTBot, OAI-SearchBot, ChatGPT-User), Perplexity (PerplexityBot, Perplexity-User) and Google (Googlebot) publish the IP ranges their crawlers use, so a request can be checked against the list of the company it names.

What the check would do

You send an export of your access logs covering a few weeks, either a raw web-server log or a log export from your CDN. I match every request whose user agent names a known AI crawler or AI fetcher against two things: your robots.txt as it stood when the request arrived, and the named company's published IP ranges where it has them.

You get back a plain written report with three lists:

• crawlers you block that still requested pages your robots.txt disallows, with dates and paths
• which of those requests came from the company's own published addresses, and which only borrowed its name
• user-triggered fetchers such as ChatGPT-User and Perplexity-User that visited, and which pages they read

After that, the same check on a fresh export each month, so you can see whether a block you added is holding.

If your site runs on Cloudflare, look at its dashboard first

Cloudflare lists AI Crawl Control as available on all of its plans, and it includes a robots.txt violations table for sites that run through Cloudflare. Cloudflare's own documentation notes that the table compares past requests against your current robots.txt, so a rule you added recently can flag requests that were allowed when they happened. If you are on Cloudflare and that table answers your question, you do not need this. The check described here is for sites on other hosts and CDNs, and for anyone who wants each request judged against the file that was live when it arrived.

The honest limits

• It is not built. Nothing on this page can be bought today.
• It needs your logs. I have no other way to see traffic to your server.
• A crawler that sends an ordinary browser user agent from addresses nobody has published looks like any other visitor in a log. No log check can pin that on a company.
• It reports what happened. Stopping a crawler happens at your server or CDN, which the guide on writing a block versus enforcing one covers.
• It would be paid work, quoted up front before anything starts. There is no price yet because there is no product yet.

Would you use it?

If you block AI crawlers on purpose and want to know whether the block holds, email reese@lastminutedealshq.com. Tell me your site, where your logs live (your own server, a CDN, a hosting control panel) and the question you most want answered. There is no mailing list behind this address. If enough people ask, I will build it, and if nobody does, this page will say so.