Grok-User
Grok-User is a live-fetch agent operated by xAI. It does not crawl the web on a schedule. It hits your site only when an end-user asks the underlying AI a question that requires fresh information from a specific page.
Traffic is bursty and unpredictable. A single trending topic can send hundreds of Grok-User requests in an hour, then nothing for days. Each request typically reads one or two pages, not your whole site.
Allowing Grok-User is how your content becomes part of xAI's answers. Blocking it means users asking that AI about your topic will be answered using someone else's content instead.
See Grok-User on your own site
Match the User-Agent header on incoming requests against the pattern below.
regex
For higher confidence, also verify the source IP against the operator's published ranges. UA strings can be spoofed; IP ownership is harder to fake.
Renders JavaScript
Sometimes
IP verification
User-Agent only
Crawl frequency
Burst, user-driven
Honors robots.txt
Yes
Honors Crawl-delay
Varies
xAI runs 6 bots in total. Each one is a separate user-agent so you can allow or block them independently.
Share of AI bot traffic
0.40%
↑ 700% vs 12 mo ago
% of top sites blocking it
2.6%
↑ 225% vs 12 mo ago
Top page categories crawled
Live-Fetch AIs as a category, share of all bot traffic
10%
↑ 135% vs 12 mo ago
Sum of every live-fetch ai we have public stats on. Compare to Grok-User's individual trend above to see if it's pulling ahead of its category or falling behind.
Crawl-to-click ratio
95 : 1
For every 1,000 fetches, this agent sends ~11 human visits back. Cloudflare crawl-to-click data
Snapshot updated
2026-04
Connect Agent Analytics for daily, per-site numbers.
Source: xAI Grok user-agent traces, Cloudflare Radar AI Insights
Should I let Grok-User through?
In most cases, yes. Live-fetch agents drive citations inside AI answers. Allowing keeps your content in the conversation. If volume gets noisy, rate-limit it before you block it outright.
Does blocking Grok-User affect my Google rankings?
No. Grok-User fetches a page only when a user is actively asking xAI a question. It has nothing to do with how Google or Bing rank you. The cost of blocking is that xAI can't quote your content in its answer.
How do I confirm a request is really from Grok-User?
Look at the User-Agent header in your access logs and match it against the strings listed above. Worth knowing that the User-Agent is easy to fake, so this check tells you "the traffic claims to be Grok-User", not "the traffic is genuinely Grok-User". If you need stronger guarantees, look for a reverse-DNS check or wait for xAI to publish IP ranges.
Does a Grok-User visit count as a real user visit?
Sort of. There is a human asking xAI a question on the other end, but they never load your page in their own browser. They see whatever xAI quotes back, usually a snippet plus a citation link. Count it as upstream attention rather than as a session.
How is Grok-User different from xAI's other bots?
xAI splits work across multiple user-agents so site owners can decide on each one independently. Training crawlers, live-fetch agents, search indexers, and agentic browsers each get their own name. Worth scanning the rest of the xAI family above to see which ones actually matter for your site.
What's the cleanest way to control Grok-User?
Two layers. Robots.txt for the polite crawlers that read it, and rules at your CDN or edge for the ones that don't. Rankly's Agent Experience handles both from a single config, so you can allow, block, rate-limit, or serve a stripped-down version per bot. Agent Analytics handles the observation half so you know which bots are actually worth a rule.
Verify everything above against the operator's own documentation.