Grok
xAI
Grok pulls from the live web. Your store has to be readable first.
Grok answers using current web and platform content. Nomu audits the groundwork that makes a store readable to any assistant — and does not yet run citation probes against Grok, which this page states plainly.
Free while you evaluate. Every change is reversible for 30 days.
Grok
No engine-specific crawler token
Readiness
4 of 6
- Search crawlabilityNo blanket disallow found
- Product structured dataavailability missing on 41 products
- llms.txtNot found
- SitemapDeclared in robots.txt
- FAQ / policy pageShipping page found, returns not
- Product descriptions63 of 214 answer no buyer question
Grok draws on live web and platform content, so the same groundwork that makes a Shopify store readable to any assistant applies — but Nomu runs no Grok citation probe and checks no Grok-specific crawler directive, so it cannot report measured Grok visibility today.
How Grok discovers and understands products
Live content, heavily social
Grok leans on current web and platform conversation, which raises the weight of what people say about a product relative to what the merchant says about it.
Common Crawl is in the mix
Broad corpora such as Common Crawl feed many models. Nomu checks CCBot among its crawler set, so a blanket block that catches CCBot is visible in the audit even where an engine-specific token is not.
Clarity still decides
Whatever the retrieval path, a product page that answers a buying constraint in plain words is usable and one that does not is not. That is engine-independent.
A real question a shopper asks Grok
“what are people actually saying about this brand's durability”
A reputation question rather than a catalogue question. It is answered from third-party discussion, which no on-site change can manufacture honestly.
Signals that may improve visibility
- No blanket Disallow that catches broad crawlers such as CCBot
- Product pages that state attributes explicitly rather than implying them
- Being discussed and reviewed in places you do not control
- Complete Product structured data
- Consistent product facts wherever the product is listed
- Plain-language policy pages
These improve whether Grok can read and verify your products. No tool can guarantee that an assistant recommends you — answers are non-deterministic and no vendor sells placement in them.
What Nomu measures for Grok today
Nomu does not probe Grok and does not check a Grok-specific crawler token. The readiness work it audits — crawler access, structured data, product content, discovery files — is what any retrieval-based assistant depends on, but Nomu cannot tell you whether Grok currently names your store.
What Nomu can detect
The audit runs nightly and reports only what it can prove.
AI crawler blocked in robots.txt
criticalAn assistant's crawler is disallowed, so nothing else about the store can matter to it. Binary, and the first thing checked.
No llms.txt or agents.md
mediumNo plain-language guide to what the store sells, so the catalogue has to be inferred by crawling.
Product structured data missing or incomplete
highPrice, currency, availability or brand absent, so a hard constraint like "under $30 and in stock" cannot be verified.
Product descriptions too thin to answer a question
highDescriptions that state a name and a size answer no buyer constraint, so the product is retrievable for nothing.
Titles, meta descriptions or image alt text missing
mediumThe fields that tell a crawler what a page and its images are, left empty.
No FAQ or policy page an assistant can quote
mediumShipping, returns and sizing questions have no answerable page to cite.
Collection pages with no descriptive text
lowCategory pages that list products without saying what the category is or who it suits.
What a fix looks like
The same product, rewritten so Grok can match it to a question.
Everyday Tee. Soft cotton. Multiple colours.
Matches nothing — no attribute a buyer filters on.
A 220gsm combed-cotton tee, pre-shrunk, with a ribbed collar that holds its shape after repeated washing. Regular fit — size up for a relaxed cut. Nine colours. Made in Portugal.
Nomu drafts the rewrite from your own product data. Nothing publishes until you approve it, and every change is reversible for 30 days.
Fixes Nomu can generate
Rewrite a product description
Drafts a description built from the attributes buyers filter on — material, fit, use case, care — from your own product data.
Fill in title, meta description and image alt text
Generates the SEO fields a product is missing, per product, for your approval.
Add Product structured data
Emits schema.org Product markup with price, currency, availability and brand populated per variant.
Create an FAQ page
Builds an FAQ from your real policies and the questions your customers actually ask.
Publish llms.txt
Writes a plain-text guide describing what you sell, to whom, and which pages are canonical.
Write a collection description
Describes what is in a category and who it suits, so the collection page can be retrieved.
Tracking improvement over time
Nomu tracks readiness for Grok, and says so rather than implying more.
Nomu re-runs the site audit after every change and shows what moved: crawler access, structured-data completeness, description coverage. It does not report Grok citations, because it does not measure them.
Re-audited
After every applied fix
Re-checked
On the nightly review
Reversible
30 days on every change
Other assistants
See what Grok can read on your store.
Connect Shopify and Nomu runs the audit on your real catalogue. Nothing changes until you approve it.