Not yet, in most cases. xAI publishes no crawler documentation, and two independent tests found Grok fetching robots.txt-blocked pages using faked browser user-agents. Grok holds 2 to 3 percent of AI search traffic, and its real-time grounding leans on X, which reaches a small share of South Africans. One free action is worth taking: claim and correct your Grokipedia entity page. Skip paid Grok optimisation.

OpenAI publishes its search crawler’s IP ranges at a fixed URL. Anthropic publishes a help article naming its three crawlers and explaining how to block each one. Perplexity publishes both user-agent strings and address ranges.

xAI publishes nothing.

We looked for a crawler page, a robots.txt guide, an IP allowlist, anything. docs.x.ai documents the developer API. It does not tell a site owner which user-agent to expect or how to control it. No equivalent page exists anywhere on xAI’s site.

That absence is the story, and it shapes each recommendation below.

The user-agent strings no one can confirm

Third-party trackers name several: GrokBot/1.0, xAI-Grok/1.0, Grok-DeepSearch/1.0, xAI-SearchBot/1.0, and a bare xAI-Bot. They contradict each other on which is current.

None appears in xAI documentation. One tracker that profiles the crawler concedes that xAI publishes no verifiable IP allowlist and no formal bot policy, and that compliance “has not been independently verified at scale”.

Writing a robots.txt rule for a user-agent no one can confirm produces a line that may match nothing. That is the position xAI leaves you in.

Two tests, and what they found

Independent researchers ran controlled experiments rather than guessing. Both are self-published rather than peer reviewed, and we treat them as evidence rather than proof.

StackFox, February 2026. A controlled server with full request logging recorded 30 requests inside one second from two datacentre addresses, presenting a stale Chrome 139 user-agent. No bot token identified the requester.

SearchEngineWorld, June 2026. Andre Alpar planted secret canary strings on URLs blocked by Disallow, then asked twelve AI assistants about those pages. ChatGPT, Claude and Perplexity respected the block and were verifiable by IP. Grok retrieved the blocked canary, using faked Mac browser user-agents from 17 addresses across France, Italy, Mexico, Brazil and Chile.

Cloudflare adds a third data point. Its September 2025 crawler analysis states that xAI’s bot does not self-identify at all.

We searched for a response from xAI to any of this and found none. No statement, no rebuttal, no acknowledgement.

What that means for you

A robots.txt rule is a request that a well-behaved crawler honours. On this evidence, treat Grok as a crawler that may not.

If you have content you need withheld from Grok, robots.txt is not a sufficient control. Server-level or WAF blocking is your route, and the absence of published IP ranges makes even that awkward. You would be blocking on behavioural patterns rather than published identity.

For most South African businesses this is theoretical, because you want to be found rather than hidden. Know it anyway, because it tells you how much weight xAI’s stated intentions deserve.

Grok answers from X more than from the web

Grok holds privileged access to X, and that shapes what it knows.

For queries with a social dimension, Grok can answer from X posts alone and cite no web sources. Its coverage is query-dependent rather than fixed.

xAI does document two separate developer tools, web_search and x_search, each with domain or handle allow and exclude lists, returning a structured citations field. That confirms open web retrieval exists as a capability. It says nothing about how sources get chosen.

DeepSearch and DeeperSearch are tiered multi-step research modes rather than separate crawlers. The citation display format users see, inline links plus a closing list, we could only confirm through third-party analysis.

The South African arithmetic

Grok stops being interesting for a local business at this point.

Grok’s real-time grounding leans on X. X reaches a small slice of South Africa, somewhere in the region of 3 to 6 percent of the population depending on source and date, skewed toward higher-income adults between 25 and 44, and flat to declining. WhatsApp reaches around 31 million South Africans. Facebook reaches somewhere between 25 and 35 million.

The platform Grok knows best is therefore the platform South Africans use least. Its picture of South African business conversation is thin by construction, and no amount of website work changes that.

The global numbers point the same way. Grok takes 2.4 to 2.8 percent of AI search traffic against ChatGPT’s 53 to 59 percent. Its share of United States mobile chatbot use peaked at 17.8 percent in January 2026 and fell to 8.7 percent by June.

SpaceX’s February 2026 filing claims 117 million monthly active users, which counts anyone who touches Grok inside X rather than people choosing it to search. By revenue, xAI runs at 350 to 500 million dollars against OpenAI’s 25 to 30 billion and Anthropic’s 47 billion.

Grok works in South Africa wherever X does. A free tier allows ten prompts per two-hour window. X Premium runs about eight dollars a month, near R150, and SuperGrok around thirty. We found no local Rand pricing or South African billing, so conversion applies.

The one thing worth doing

Grokipedia launched in October 2025 and accepts requests and suggestions for entity articles, including business entities, with citation links that pass authority. Third-party reporting suggests other answer engines cite it.

Claiming and correcting your entity page costs an hour and no money. Do that.

Beyond it, nothing exists. Grok has no business directory, no local search surface, no publisher programme, no commerce feature. The product at x.ai/grok/business is enterprise workflow automation with connectors into Salesforce, HubSpot and Slack. It is not a discovery channel for a Cape Town accountant.

What we cannot tell you

We cannot confirm any Grok user-agent string, because xAI publishes none.

We cannot tell you how Grok selects or ranks sources, whether it honours robots.txt from one request to the next, or which addresses it crawls from.

We found no South African usage figures for Grok from xAI or any neutral measurement body. The share numbers above come from third-party trackers with varying methods.

Elon Musk was born in Pretoria, which generates reliable local press and tells you nothing about whether Grok will recommend your business. We mention it only because somebody will raise it.

Where this leaves you

Grok is the one engine where our honest recommendation is to spend nothing.

Claim your Grokipedia page. Skip everything else. Put the budget into the engines that publish their crawlers, honour your robots.txt, and reach buyers you can name.

We test Grok anyway, because a baseline that omits an engine cannot tell you when that engine starts mattering. If it grows, or if xAI starts documenting its crawlers, we will say so here.

If you want that baseline across Grok and seven other engines with the raw results handed over, our AI search visibility service sets out the scope, the price, and what we cannot promise.