# xAI-Bot > xAI-Bot is xAI's crawler for traffic that is neither answering nor training. The family name xAI's own robots.txt examples use. A fetch from xAI that does not name its job. The operator is known and the purpose is not, so it is counted as xAI traffic without entering either AI figure. **Category:** AI crawlers **Also known as:** xAI xAI-Bot **Updated:** 2026-09-09 **Source:** https://truestat.io/glossary/xai-bot --- ## What xAI-Bot is 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-Bot is counted as other AI traffic, 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. ## What its traffic looks like Irregular and low volume. These fetches happen for a specific reason — an ad check, a preview, an infrastructure request — rather than on a schedule, so there is no pattern worth reading into unless the count is unexpectedly high. ## How it is verified 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. ## If you block it Very little. This fetch is neither an answer nor training, so blocking it costs you nothing except the record of xAI having visited. There is not much to decide here. This fetch is neither answering a question nor collecting training material, so it neither brings readers nor takes anything you would miss. It is worth watching the volume rather than the intent. If a crawler in this category becomes a large share of your requests, that is a bandwidth question, and it is answered with a rate limit rather than a robots rule. ## How it differs from xAI's other crawlers 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: xAI-SearchBot — ai assistant. Grok fetching a page while answering. 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. 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. ## Questions ### Is xAI-Bot in my logs really xAI? There is no way to prove it. xAI publishes neither an address list nor a reverse DNS record for this crawler, so the user agent is the only evidence and anyone can send it. We record the visit as an unverified claim rather than presenting it as confirmed. ### How do I tell xAI-Bot apart from xAI's other crawlers? By the token, and only by the token. xAI also sends xAI-SearchBot, Grok-DeepSearch, xAI-Grok, and the strings differ by a few characters while the jobs differ completely — one may be answering somebody's question while another collects training material. Match on the exact token rather than on the operator's name appearing anywhere in the header, or the four end up counted as one. ### Does xAI-Bot run JavaScript? No. It requests the HTML and leaves. That is why a browser-based analytics tag never records these visits: the tag is JavaScript, and nothing runs it. Seeing this crawler at all requires reading it server-side. ### Why is xAI-Bot counted as Other AI traffic and not something else? Because that is the job this particular crawler does. xAI runs more than one — xAI-SearchBot, Grok-DeepSearch, xAI-Grok — and they are counted separately because the decisions about them are separate. Filing them together under one operator name would let ordinary indexing look like AI interest, which is the single most misleading thing an AI traffic report can do. ### Why does xAI-Bot not show up in Google Analytics? Google Analytics runs in the browser. This crawler never opens a browser — it requests the HTML, reads it, and leaves, so the tracking script is never executed and no event is ever sent. Every browser-based analytics tool has the same blind spot, which is why crawler traffic has to be read from the server side to be seen at all. ### Why can a xAI-Bot visit not be verified? xAI publishes neither a machine-readable list of the addresses its crawler uses nor a reverse DNS record pointing back at itself. With neither, the user-agent header is the only evidence, and anyone can send it. Rather than showing a confidence we cannot support, the visit is recorded as an unverified claim — which is also the honest answer to give anyone asking how much of your AI traffic is real. ## Related - https://truestat.io/glossary/xai-searchbot - https://truestat.io/glossary/xai-grok-deepsearch - https://truestat.io/glossary/xai-grok-search - https://truestat.io/glossary/xai-grokbot - https://truestat.io/glossary/fcrdns - https://truestat.io/glossary/spoofed-crawler --- From the TrueStat glossary — https://truestat.io/glossary. Privacy-first web analytics that also shows you which AI assistants are reading your site.