Signal
Agent infrastructure reachability
Whether a crawler you allow in robots.txt actually receives your full page - a 200 over HTTPS, not a WAF challenge, rate-limit, or geoblock - rather than being silently turned away.
Per-platform status
Where a platform documents relevant behavior, its status and source are shown. Undocumented platforms show "unknown" - honest unknowns, never invented.
| Platform | Status | Notes | Source |
|---|---|---|---|
| ChatGPT | Supported | OpenAI publishes verifiable IP/user-agent endpoints (gptbot.json, searchbot.json, chatgpt-user.json) precisely so you can allow-list the real agents. | Source (opens in new tab) · verified 2026-07-08 |
| Gemini / Google AI Mode | Unknown | Not documented by this platform. | - |
| Perplexity | Unknown | Not documented by this platform. | - |
| Copilot | Unknown | Not documented by this platform. | - |
| Claude | Unknown | Not documented by this platform. | - |
Evidence and sources
This signal is typed hypothesis (Low confidence).
- Overview of OpenAI Crawlers (opens in new tab) · 2026-07-08
- ACP product feed specification (opens in new tab) · 2026-07-08
How to act on this
Fetch your own product URL with each vendor's published user-agent and IP range, confirm a 200 (not a challenge), serve everything over HTTPS with no mixed content, and re-test after any WAF or CDN change.
Related checklist items
Handbook chapters