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

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

Steps

  1. Enumerate the distinct AI crawler user agents relevant to commerce: retrieval/search bots (OAI-SearchBot, Claude-SearchBot, PerplexityBot) versus training-only bots (GPTBot, ClaudeBot, CCBot, Google-Extended) versus shopping-specific bots (Amazonbot)
  2. Check each publisher's current documentation for their crawler's exact user-agent string and stated purpose before writing rules, since bots and their behavior change over time
  3. Write per-user-agent Allow/Disallow blocks in robots.txt that allow retrieval/shopping bots onto /products/ and /catalog/ paths while disallowing training-only bots from the same paths if desired
  4. Confirm your CDN or edge platform is not silently overriding or stripping your robots.txt rules (a common cause of unexpected AI invisibility)
  5. Cross-check the resulting access pattern against server logs to confirm bots are honoring the directives, since compliance is voluntary
  6. Review the rule set quarterly, since AI companies regularly introduce new crawler identities

Known gotchas

Related routes

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
developers.google.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
Distinguish genuine AI crawler traffic (GPTBot, ClaudeBot, PerplexityBot, etc.) from spoofed user agents, and apply differentiated robots.txt directives
platform.openai.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