What you can conclude
- GPTBot requested the recorded path and received an HTTP response.
- You can compare request timing, pages, methods, and status codes.
- Published IP evidence can strengthen identity verification.
See when OpenAI’s training crawler requests your pages, verify the available signals, and inspect the paths and HTTP statuses behind every visit.
GPTBot is OpenAI’s automated crawler for content that may be used to improve its generative AI foundation models.
A matching request means a client presented the GPTBot identity while requesting a page. When a trusted source IP matches OpenAI’s published ranges, Talivia can raise the verification confidence for that request.
Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko); compatible; GPTBot/1.3; +https://openai.com/gptbotTalivia looks for the stable GPTBot token in the normalized User-Agent.
User-agent: GPTBot
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 GPTBot User-Agent token. When a trusted source IP matches provider-published ranges, the request can receive stronger verification confidence.
Add a rule for GPTBot 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