Optimize for
AI crawlers like GPTBot, ClaudeBot, and Google-Extended are scanning your site right now. Learn how to configure robots.txt to control what AI models can and cannot access.
If you haven't looked at your server logs recently, you might be surprised. AI companies are actively crawling the web to feed their models. GPTBot (OpenAI), ClaudeBot (Anthropic), PerplexityBot, and Google-Extended are just a few of the bots scanning your pages right now.
Unlike traditional search engine crawlers, AI crawlers don't just index your content for search results. They ingest it to train large language models or to power real-time AI search answers. This distinction matters because it changes the risk-reward calculation for allowing or blocking them.
Your robots.txt file is the first line of defense and opportunity when it comes to AI crawlers. Block them entirely, and your content will never appear in AI-generated answers. Allow them without a strategy, and you lose control over how your content is used.
The smart approach is selective: allow crawlers that drive citations and referral traffic, while setting boundaries on what content they can access.
OpenAI's web crawler powers ChatGPT's browsing feature and contributes to training data. Allowing GPTBot means your content can appear in ChatGPT's real-time search answers with citations back to your site.
User-Agent: GPTBot
Anthropic's crawler collects data for Claude's training. While Claude doesn't currently offer web browsing with citations, allowing ClaudeBot means your content shapes Claude's knowledge base.
User-Agent: ClaudeBot
Perplexity's crawler powers its AI search engine, which always provides source citations. This is one of the highest-value crawlers to allow because Perplexity directly links to your content in its answers.
User-Agent: PerplexityBot
Google's dedicated AI training crawler, separate from Googlebot. Blocking Google-Extended does not affect your Google Search rankings it only prevents your content from being used to train Google's Gemini models.
User-Agent: Google-Extended
Here is a balanced configuration that maximizes AI search visibility while protecting sensitive content:
Allow all AI crawlers (recommended for visibility):
Allow GPTBot to access public content
Allow PerplexityBot for citation-driven traffic
Allow Google-Extended for Gemini visibility
Block all crawlers from admin, staging, and private pages
Not everything should be accessible to AI bots. Consider blocking:
Admin and internal pages: /admin/, /dashboard/, /internal/
User-generated content: /profiles/, /comments/ (if sensitive)
Staging and development: /staging/, /dev/, /test/
Premium or gated content: Content behind paywalls or signups
Duplicate or thin content: /tag/, /archive/ pages that add no value
After updating your robots.txt, verify it works correctly:
Use Sourceable's free Robots.txt Checker tool to test AI crawler access
Check server logs for AI crawler activity after changes
Monitor AI citation frequency to see if allowing crawlers improves visibility
Review Google Search Console for any crawling issues
Your robots.txt is no longer just about search engines. It's about controlling how AI models interact with your content. A well-configured robots.txt can be the difference between your brand being cited in AI answers or being invisible to the fastest-growing search channel in history.
Start by auditing your current robots.txt. Use Sourceable's free checker tool to see exactly which AI crawlers can access your site, then adjust accordingly.
Continue reading our latest insights
Search Console now shows AI Overview impressions—but the biggest AI visibility story is still happening outside Google.
AI crawlers read millions of pages every day, but only a tiny fraction become citations. Here's how to improve your odds.