Distinguish between robots.txt Disallow and HTML noindex directives, and configure robots.txt user-agent entries to control AI training crawlers separately from search crawlers

domain: developers.google.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗

Steps

  1. Understand the fundamental difference: 'Disallow' in robots.txt prevents crawling (Googlebot will not fetch the URL), while 'noindex' in a meta tag or X-Robots-Tag prevents indexing (Googlebot fetches the URL but excludes it from the index)
  2. Add specific user-agent blocks for AI training crawlers: 'User-agent: GPTBot\nDisallow: /' blocks OpenAI's training crawler; 'User-agent: Google-Extended\nDisallow: /' blocks Google's AI training use separate from Search
  3. Add 'User-agent: ClaudeBot\nDisallow: /' to block Anthropic's training crawler; use 'User-agent: CCBot\nDisallow: /' for Common Crawl
  4. Keep your Googlebot rules in a separate user-agent block from AI crawler rules to avoid accidentally affecting Search indexing when editing AI crawler policies
  5. Validate the final robots.txt using Google's robots.txt Tester in Search Console to confirm Googlebot rules are unaffected after adding AI crawler blocks
  6. Test that a URL disallowed for GPTBot is still crawlable by Googlebot by checking with the URL Inspection tool — the two user-agent blocks must be independent

Known gotchas

Related routes

Configure robots.txt directives that allow AI shopping and search-agent crawlers (e.g. OAI-SearchBot, PerplexityBot, Amazonbot) onto product pages while blocking pure AI-training crawlers from the same paths
platform.openai.com · 6 steps · unrated
Configure per-engine crawl-delay directives in robots.txt, since Bing and Yandex honor it but Googlebot ignores it entirely
developers.google.com · 5 steps · unrated
Use X-Robots-Tag HTTP response headers to control indexing of non-HTML resources and to block specific AI training crawlers
developers.google.com · 6 steps · unrated

Give your agent this knowledge — and 15,500+ more routes

One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Need this verified for your stack — or a route we don't have yet?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans