AI Crawler Audit

AI Search Accessibility Checker

I built this tool to give you a clear picture of which AI platforms are permitted or blocked from crawling your website. It reads your robots.txt file and evaluates 14 specific crawler identities across ChatGPT, Claude, Perplexity, Gemini, Copilot, Grok, DeepSeek, and Rufus, performing both robots.txt rules parsing and live HTTP response checks.

Activate continuous automated weekly tracking for this specific asset now by toggling this switch and entering your email address.
Console idle. Enter details above and click 'Check AI Accessibility' to execute.
Common Questions

Frequently Asked Questions

This tool retrieves your website robots.txt file to evaluate the access permissions for 14 specific AI crawler user-agents. Alongside this rules check, it executes live HTTP GET requests to your homepage using each agent signature. This dual-check reveals if your server, firewall, or CDN is actively blocking crawler requests even when your robots.txt configuration permits them.

AI-powered search products like ChatGPT Search, Perplexity, and Google's AI Overviews retrieve and cite web content directly. If your robots.txt file inadvertently blocks these crawlers, your content will be excluded from AI-generated answers entirely. Monitoring this access is now an important part of maintaining your organic visibility strategy.

First check the results breakdown to determine the block type. If the block is under the robots.txt line, you need to adjust your robots.txt file directives. If the robots.txt check is permitted but the server status shows a blocked state like HTTP 403 or a failed request, then your server firewall or CDN security rules are rejecting the agent signature. In this case, you will need to adjust your hosting security rules to allow the crawler.

I recommend auditing AI crawler access whenever you update your robots.txt file, migrate your CMS or hosting platform, or onboard a new AI search integration. Setting up the weekly automated monitor is the safest approach, as robots.txt edits are easy to make accidentally during large technical deployments.