What you can conclude
- OAI-SearchBot reached the recorded URL.
- The response status shows whether the crawler could access it.
- Official IP ranges are available for stronger verification.
Measure OpenAI search crawler activity separately from training and user-triggered requests, down to the requested path and response status.
OAI-SearchBot discovers and indexes web content for search experiences in OpenAI products.
A request shows that the search crawler fetched a URL for discovery or index maintenance. It should be evaluated separately from GPTBot training traffic and ChatGPT-User page retrieval.
Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko); compatible; OAI-SearchBot/1.0; +https://openai.com/searchbotTalivia looks for the stable OAI-SearchBot token in the normalized User-Agent.
User-agent: OAI-SearchBot
Allow: /
# To block instead:
# Disallow: /Use robots.txt to express an allow or block preference for this crawler.
When the integration supplies a source IP from a trusted network boundary, Talivia can compare it with provider-published ranges.
View official sourceTurn on collection in website settings.
Send the minimal event from trusted server code or middleware.
Review pages, statuses, trends, and verification confidence.
Talivia first matches the OAI-SearchBot User-Agent token. When a trusted source IP matches provider-published ranges, the request can receive stronger verification confidence.
Add a rule for OAI-SearchBot in robots.txt and check the provider’s official documentation for behavior. robots.txt expresses crawl preferences; it is not access control or identity verification.
Talivia stores the hostname, sanitized path, method, User-Agent, optional status, classification, and verification result. It does not store page bodies, cookies, authorization headers, query strings, or raw IP addresses.
Start recording real requests with server-side tracking.
Add your website