Aizii Learn · AI Search

[← Back to Learn](https://aizii.ai/learn)

# How to get Grok Bot to recommend your brand

There is no crawler to allowlist. Grok Bot is not a search engine you get indexed into; it is a personal agent teammate that shops for the user, and it browses your site with its own browser, on a persistent cloud computer, the way a human would. It recommends brands whose pages render in a real browser, whose price and stock it can check against structured data, and whose checkout it can actually complete. Everything about robots.txt allowlisting in the other guides in this series does not apply here.

**One warning first:** there is no way to submit your brand to Grok Bot. Anyone selling guaranteed placement is selling something they do not control.

One clarification: Grok Bot is a separate product from Grok, not a rename. Grok is the chatbot inside X, and Grok gets its own guide. Grok Bot is xAI's separate agent product. Each Bot works on a persistent cloud computer with a browser, filesystem, and terminal, takes on multi-step work across apps and websites, and comes back when something needs your approval. Work continues while the laptop is closed, and browser sessions persist between tasks. xAI publishes no crawler page for Grok Bot in the docs checked for this guide, and no token or IP range is listed there, so there is nothing to build an allowlist on. Do not confuse Grok Bot with the reported GrokBot crawler name. That name belongs to the Grok chatbot crawl lane, and writing it into robots.txt does nothing to Grok Bot. At checkout, a Bot can use a card saved in Vault, a card entered in a Secure Form, or a connected wallet such as Link or X Money. That is context, not something you optimize for.

## Why Grok Bot skips your brand

Grok Bot's failure modes are its own, and none of them involve a crawler:

1.  Bot protection fires on it. Grok Bot presents a standard browser, so a bot challenge that fires on real browsers fires on Grok Bot too. There is no allowlist token to add, and blocking it would mean blocking real shoppers, so the fix lives in your edge rules. A site can still block automation, expire a session, or require a human step, and the Bot hands those steps to its user rather than working around them.
2.  The checkout assumes a logged-in human. Account-required checkout, shipping options hidden until sign-in, sessions that depend on earlier visits: all of these stall when Grok Bot arrives with no session. A returning Bot may stay signed in, because browser sessions persist on its computer, but a first visit has no session to rely on. It can recommend you and still abandon the cart.
3.  There is nothing to verify against. Grok Bot reads the page like a human, but structured data is one lever it can use to check what the page claims. Prices baked into images and pages with no product schema give it nothing to confirm, and unconfirmed facts lose to brands it can verify.
4.  The page breaks outside your test environment. JS-driven widgets and checkout flows that fail in a clean session fail for Grok Bot the same way. A CAPTCHA, a passkey, a single sign-on step, a bank card verification, or a site that explicitly requires a human all hand the work back to the user, and a purchase that cannot get past that step does not complete.

## Step 1: Test through Grok Bot itself

There are no webmaster tools and no log tokens for Grok Bot, so the test is the verification. Ask Grok Bot to research your product and work toward a purchase, then watch where it stalls: the search step, the price check, or the checkout. Your server logs will only show normal browser traffic, so skip the log grep entirely. You can also start a task from X by tagging @bot in a post or reply, and your main Bot picks it up as a task. That is a way to start work, not a way to get recommended. A recommendation is built from what the Bot can read and buy on your site.

## Step 2: Make the site survive a real browser

Open \[yourdomain.com\] in a private window, replacing yourdomain.com with your actual domain, logged out, and complete the path a shopper takes. The checkout must finish without a login, price and stock must be text rather than images, and any bot protection or challenge must not fire on an ordinary browser session. If it breaks for you there, it breaks for Grok Bot.

## Step 3: Give it schema to verify against

Grok Bot cross-checks the page against your structured data, so the schema has to match the visible page exactly: price, availability, SKU, no conflicts between the two. A mismatch between what the page shows and what the schema claims creates conflicting facts, and the agent may pick the brand with consistent data. Do not claim Grok Bot verifies price and stock from schema as a documented fact. Treat structured data as one lever it can use to check what the page claims, and keep it consistent with the page.

## Step 4: Walk the full transaction path

Product to cart to checkout to confirmation, as a guest, in a fresh browser session, and confirm the order actually goes through. This is the step the other engine guides never ask for, and for Grok Bot it is the one that matters most: recommendation without transactability is a dead end. Test the fresh session first, because that is the hardest case. A returning Bot with a saved session may get further, but a first-time shopper does not have that session.

### A hypothetical, to make it concrete

Say you run a direct-to-consumer skincare brand. The site looks perfect, the product pages rank well, and the checkout is a polished single-page app. But shipping options only appear after sign-in, some prices live inside lifestyle images, and there is no product schema on the page. A scan would flag the pattern in one pass: nothing here is a crawl problem, so no allowlist can fix it. The fix is the transaction path: guest checkout that completes in a fresh browser session, prices as text with matching schema, and edge rules that treat Grok Bot's browser like any shopper's.

### The fundamentals

These mechanics are shared across every engine and covered in full in their own guides:

-   •llms.txt: the file format, a complete sample, and per-platform publish steps, see our [guide to writing a good llms.txt file](https://aizii.ai/learn/ai-search/how-to-write-a-good-llms-txt-file)
-   •Product schema: the JSON-LD markup structured data is one lever Grok Bot can use to check what the page claims, see our [product schema guide for AI search](https://aizii.ai/learn/ai-search/how-to-add-product-schema-markup-for-ai-search)
-   •The robots.txt pillar matters less here than for any other engine: there is no Grok Bot crawler token to allowlist. Check your edge rules instead, since anything that blocks real browsers blocks Grok Bot, see our [robots.txt guide for AI search](https://aizii.ai/learn/ai-search/how-to-write-robots-txt-for-ai-search)

## What this guide does not cover

Getting Grok Bot to recommend you is only half its job, because Grok Bot does not stop at recommending. It goes on to buy, which makes this guide the closest in the series to the transaction layer: keeping catalog data accurate as it changes, handling variants and pricing reliably, and making the purchase path work at scale is ASO work, and this series does not cover it. It also does not cover monitoring and drift: your site changes, the agent changes, and neither waits for you. It also does not cover Grok Bot routines, skills, or team controls. A Bot can learn a workflow from demonstration and rerun it on a schedule, and all of a user's Bots share one cloud computer, so treat anything placed on that computer as available to every Bot on the account.

For the Grok chatbot version of this playbook, see our [guide to getting Grok to recommend your brand](https://aizii.ai/learn/ai-search/how-to-get-grok-to-recommend-your-brand). For the Muse version, see our [guide to getting Muse to recommend your brand](https://aizii.ai/learn/ai-search/how-to-get-muse-to-recommend-your-brand).

## Check your own brand now

Run the free scan. It takes seconds, no signup, and shows exactly where Grok Bot stands with your site: aizii.ai/aeo-scan

[Run the free scan](https://aizii.ai/aeo-audit)

## Sources

-   xAI Grok Bot overview (specific): [https://docs.x.ai/grok-bot/overview](https://docs.x.ai/grok-bot/overview)
-   xAI Grok Bot computer and apps (specific): [https://docs.x.ai/grok-bot/computer-and-apps](https://docs.x.ai/grok-bot/computer-and-apps)
-   xAI Grok Bot product page (specific): [https://x.ai/bot](https://x.ai/bot)
-   xAI Grok API documentation home (general docs): [https://docs.x.ai/overview](https://docs.x.ai/overview)
-   Schema.org Product (general standard): [https://schema.org/Product](https://schema.org/Product)
-   RFC 9309, Robots Exclusion Protocol (general standard): [https://www.rfc-editor.org/rfc/rfc9309.html](https://www.rfc-editor.org/rfc/rfc9309.html)

Note: links marked specific point to the page that supports the claim in this guide. Links marked general docs point to the vendor's general docs section for that topic, not to a page that proves every step. Check the vendor docs for the current path before relying on a menu name or click path in this guide.
