PlatformHow it worksPricingFull Intelligence ReportFor small businessEnterprise Contact
Platform · xAI

Grok visibility:
what can actually be verified

This page is shorter than the others for a reason worth stating plainly. As at 2026-09-08, xAI publishes no crawler or webmaster documentation — no user-agent list, no IP ranges, no stated robots.txt policy. Advice you will find elsewhere naming specific Grok crawlers is drawn from third-party observation rather than from a vendor page, so OG01 does not repeat it as fact. What remains verifiable is what Grok actually returns when asked about your business, and the condition of your own domain underneath that.

The gap

Every other major assistant documents its crawlers

OpenAI documents four agents and says what each is for. Google documents its crawler tokens and states explicitly what Google-Extended does and does not affect. Perplexity publishes a bots guide covering both its indexing and user-initiated agents. Against that, the absence of any equivalent from xAI is not a small gap — it means a site owner has no vendor-confirmed way to express a preference about Grok's access, and no authoritative list to check their server logs against.

That has a direct consequence for anyone selling you Grok optimisation: the mechanism they are describing cannot be verified against anything the vendor has published. It may be an accurate description of observed behaviour. It is not documentation, and the difference matters when you are being asked to change your infrastructure on the strength of it.

What OG01 will not do here
We will not list user-agent strings we cannot attribute to xAI, will not tell you a robots.txt rule that we cannot show is honoured, and will not present a Grok visibility score derived from an unverifiable model of how Grok retrieves. Where a page on this site makes a platform claim, it cites the vendor. This page cannot, so it does not make one.
What is still measurable

Observation, and the conditions underneath

Two things remain solid even without vendor documentation. The first is observation: asking Grok the questions your customers ask and recording what comes back — whether your business is named, and how it is described when it is. That is a record of a moment rather than a position, and OG01 reports it as such, because responses vary between runs and presenting them as a stable ranking would be its own kind of invention.

The second is the state of your own domain. Whether your pages can be fetched and parsed, whether your organisation resolves to one clear entity, whether your claims are corroborated somewhere that is not you, and whether stale or contradictory information about you is in circulation. Those conditions are measurable regardless of which assistant is reading, they are the ones you control, and they are why OG01's measurement is deliberately platform-independent.

Sources

The source position, recorded

There is no vendor documentation to cite. That absence was checked and recorded rather than papered over, and it is held in the same source file as the other platforms so it can be re-reviewed rather than forgotten. Reviewed 2026-09-08.

  • Checked 8 Sep 2026: xAI publishes no crawler or webmaster documentation — no user-agent list, no IP ranges, no stated robots.txt policy.
  • Third-party lists circulate several candidate user-agent names, none confirmed by a vendor page. They are therefore NOT stated as fact on the page.
  • The page must say the documentation does not exist rather than repeating an unattributable claim, and must confine itself to what OG01 can observe: what Grok returns when prompted.
  • If xAI publishes documentation later, add it here and revise the page rather than leaving the absence recorded as permanent.
Questions

Grok questions

How do I allow or block Grok in robots.txt?
There is no vendor-published answer to give you. xAI does not publish a user-agent list or a robots.txt policy, so any rule you write is aimed at a name nobody has confirmed. If controlling automated access matters to you, the honest approach is infrastructure-level rather than a robots.txt line taken from a blog post — and that is a decision for your own team.
Why do other sites list Grok user agents if xAI does not?
Because those lists come from observed traffic and from each other rather than from xAI. Observation can be genuinely useful, but it is not the same as documentation, and several widely repeated names appear without any vendor page behind them. OG01 states facts it can attribute, so it does not reprint them.
Can you give me a Grok visibility score?
Not a per-platform score, and not for any of the assistants. A number implying a measured standing inside a system whose retrieval and selection are unpublished would be a confident-looking guess. What is reported instead is what Grok returned when prompted, and a measurement of the conditions on your own domain that any retrieval-based system depends on.
Is it worth doing anything specific for Grok?
Nothing that differs from the rest. Because no Grok-specific mechanism is documented, there is no Grok-specific technique anyone can justify. The work that helps is the same work that helps everywhere: be retrievable, resolve as one entity, state your answers plainly, and be corroborated by sources other than yourself.
Will this page change if xAI publishes documentation?
Yes. The absence is recorded in a maintained source file with a review date rather than written into the page as a permanent fact, precisely so it gets revisited. If xAI publishes crawler documentation, the source entry is updated and this page is rewritten around it.
Measure the part that is actually yours.

Your domain's condition is measurable whichever assistant is reading it. Free, about ninety seconds, no card.