xAI · AI answers
Grok-DeepSearch
Identify Grok-DeepSearch by its user agent. Check request identity, review robots.txt controls and track visits in Aiola Analytics.
Key facts
Grok-DeepSearchWhat Grok-DeepSearch is
Grok-DeepSearch fetches sources while a Grok user runs DeepSearch. Aiola classifies it as AI answers because access happens on demand.
In Aiola's taxonomy, AI answers means fetched to answer a user's question now.
Grok-DeepSearch user agent
Look for the match token inside the complete HTTP User-Agent header. Tokens can be spoofed, so use the network checks below for authentication.
Grok-DeepSearchGrok-DeepSearchOfficial IP ranges
xAI has not published official IP ranges that Aiola successfully fetched for Grok-DeepSearch. Aiola does not list cloud-provider ranges or community guesses as if they authenticated this crawler.
Verify a Grok-DeepSearch request
No IP authentication method is documented in this record for Grok-DeepSearch. Its user-agent token is a claim, not proof of identity.
Use the exact header token for classification and apply your own access controls. Check the vendor documentation for any newly published IP, token or header verification method.
Control Grok-DeepSearch with robots.txt
Grok-DeepSearch is user-triggered. xAI's controls may differ from automated crawling, so do not assume a robots.txt block is an authentication boundary.
User-agent: Grok-DeepSearch
Allow: /User-agent: Grok-DeepSearch
Disallow: /No official crawler documentation URL is listed because Aiola could not verify one confidently.
Aiola Analytics
See every Grok-DeepSearch visit on your site
Aiola tracks 70 AI, search and link-preview crawlers next to your human traffic. See when Grok-DeepSearch arrives, which pages it requests and how that changes over time. Hosted Analytics needs Pro or a trial.
Common questions
Build, ship and fix in one app
Errors, user feedback, GitHub and analytics live next to your coding agents in one desktop app. Every issue becomes a task an agent can take.