xAI-SearchBot

xAI publishes no crawler documentation at all, which is unusual for an operator of its size — it does not appear even in the community-maintained agent lists. What is known comes from logs: several of its crawlers sign themselves with an x.ai URL, which is how the fleet was identified.

On this site xAI-SearchBot is counted as an AI answer, which is the row it appears in on your dashboard. The category matters because it decides which number moves when this crawler visits, and the four are reported separately for exactly that reason.

Usually a single request for one URL, arriving while somebody waits — no sweep of the site, no repeated visits, and often no robots.txt fetch first. If you see one hit on one page and nothing else, that is the normal shape. A burst of ten to fifty pages in a few minutes is also normal and means an agent was researching rather than answering a single question.

xAI publishes neither a machine-readable list of the addresses this crawler uses nor a reverse DNS record pointing back at itself. The user-agent header is therefore the only evidence, and anyone can send it — so a visit is recorded as an unverified claim rather than as a confirmed fetch.

That is not a gap in the measurement so much as an honest ceiling. A report that showed these as verified would be inventing a confidence nobody can support, and the number it produced would be the first thing to fall apart when somebody asked where it came from.

xAI's assistant can no longer open your page to answer a question about it. People will still be told about you from whatever the model already knows, but without the current page, a link, or a citation — which is usually the opposite of what a site owner wants.

This is the crawler that brings people back. When an assistant fetches a page to answer with, it usually shows the source and links to it, so the visit can turn into a reader. Blocking it removes you from the answer without removing the question.

The argument for blocking is the same one that applies to any zero-click surface: if a model can answer from your page, some readers get what they came for without visiting. That matters most if your pages are the product — reference material, calculators, documentation — and least if they exist to sell something the model cannot deliver.

xAI sends 5 crawlers and gives each its own token, so they can be allowed and refused separately. The tokens differ by a few characters and what the fetch means does not:

Grok-DeepSearch — ai assistant. Grok's deep research mode gathering sources for a long answer. xAI-Grok — search indexing. Retrieves and indexes pages so Grok can find them later. GrokBot — ai training. xAI's training crawler, signed with its own address at x.ai. xAI-Bot — other bots. The family name xAI's own robots.txt examples use.

Confusing two of these is the most common mistake with this operator, and it is expensive in one direction: a rule meant for the training crawler that lands on the search crawler removes you from results without stopping any training.