Structured data (JSON-LD) Set up structured data with Grok Bot
Setting up structured data with Grok Bot means asking a Bot to list your StoreSEO schema types, read the current settings of the ones you care about, and send back a complete, edited settings object once you confirm the change to your live markup.
Last updated: October 2026
Set up Grok Bot for StoreSEO
Skip this if Grok Bot is already connected. The full guide, with the alternatives, is on the Grok Bot page.
- 1
Ask your Bot to add StoreSEO
In a chat with your Bot, ask it to add a custom remote HTTPS MCP server with this URL. xAI's documentation says a plugin added from your own chat is personal and account-wide, so every Bot on your account can use it. Complete the StoreSEO sign-in when the browser opens: pick your Shopify store and approve access.
PromptAdd a custom remote HTTPS MCP server called StoreSEO with the URL https://mcp.storeseo.com/mcp and sign me in.
- 2
Attach it and check it works
In a chat, type @ to attach the StoreSEO connector to the task, then ask this to confirm the connection.
PromptUse @StoreSEO to show me my store's SEO score breakdown.
How does this work in Grok Bot?
Structured data is a place where one careless write can overwrite good settings, so the sequence matters. You attach StoreSEO with @ and ask which schema types are on. The Bot calls storeseo_start and storeseo_list_schema_types, which shows every JSON-LD type, whether it is enabled and whether it can be configured. For one type, say organization, it calls storeseo_get_schema_settings, which returns the current values and a field template describing the full object to send back. These calls are reads, so you can have the Bot summarize the whole set in a single reply.
Updates through storeseo_update_schema_settings replace the stored settings wholesale. That is a good fit for a Bot with a filesystem, because you can ask it to save the settings it just read to a file on its cloud computer before it edits anything. If the new version looks wrong, the saved copy is what you ask it to send back. You supply the business details, such as the legal name, address and opening hours, in the chat, and the Bot fills the template. It should not invent any of them.
Some types depend on others. Review and product merchant schema need product schema on first, and the four FAQ types need the FAQ Schema feature in your plan, so the Bot may report a refusal rather than a success. Each change alters the markup your live storefront serves, so keep it in a conversation and out of routines. A routine that reads the type list and tells you what changed since last week is the most a scheduled run should do here.
-
You: Use @StoreSEO to check my structured data and set up organization schema.
- storeseo_start read-only
- storeseo_list_schema_types read-only
- storeseo_get_schema_settings read-only
-
Grok Bot: Organization schema is off and its settings are empty. I need your business name, logo and contact details, then I will send the full object, which changes the markup on your live storefront. Do you want me to enable it once you give me those?
-
You: Yes, here are the details.
- storeseo_update_schema_settings needs approval
What to ask Grok Bot
Use @StoreSEO to list my schema types and tell me which are on, which are off and which I can configure.
Read my organization schema settings, save them to a file first, then show me what a complete set would look like with my business details.
Turn on product schema and send the full settings, but show me the change and wait for my yes before you call the update.
- Which JSON-LD schema types are enabled on my store?
- Set up organization schema with my business name, logo and contact email. Read the current settings first.
- Turn on product schema and review schema.
- Is local business schema configured? Show me what is missing.
- Enable FAQ schema for products if my plan includes it.
What StoreSEO does: structured data (json-ld)
StoreSEO adds JSON-LD schema to your storefront so search engines and AI assistants can read your products, business and FAQs as data. The agent lists every schema type, reads a type's settings and its field template, and sends back a complete settings object.
Requires: The FAQ schema types need the FAQ Schema feature in your plan.
- 1
List the schema types
The agent lists every type with whether it is on and whether it takes settings. Configurable types are product, review, sale dates, product merchant, organization and local business.
- 2
Read before writing
For a configurable type it reads the current settings and the field template, because an update replaces the whole settings object rather than merging into it.
- 3
Fill in your details
Business name, address, contact details and similar fields come from you. Organization and local business share the same business information, so changing one changes both.
- 4
Switch it on
After your yes the agent sends the complete settings with the status. Organization, local business and product merchant need complete settings to be enabled.
Structured data (JSON-LD) reference
| Configurable types | Product, review, sale dates, product merchant, organization, local business |
|---|---|
| Toggle-only types | Every other type, including the four FAQ types |
| Update behaviour | Settings replace the stored object; read first, then send the full object |
| Dependencies | Review, sale dates and product merchant need product schema on; disabling product also disables product merchant |
| Shared data | Organization and local business share basic business information |
| FAQ types | Product, collection, article and page FAQ need the FAQ Schema feature in your plan |
| Sale dates | Also needs a discount permission that only the app's own Sale Dates toggle can request |
Rules Grok Bot follows
- The agent reads the current settings before every settings update, because the update replaces them wholesale.
- Business details come from you; the agent does not invent an address, phone number or opening hours.
- Turning a schema type on or off changes your live storefront markup, so the agent confirms the change first.
- When a type is refused for a missing plan feature or dependency, the agent says which one rather than retrying.
In Grok Bot
Because storeseo_update_schema_settings replaces the stored object, an Always allow rule in Grok Bot turns a mistaken edit into a silent overwrite of working settings. The client no longer asks, and StoreSEO's read-before-write instruction is the only check, so keep the tool on Allow once or an Ask first rule. If you need a rollback, ask the Bot to save the object it read before the update.
What runs without asking. Reads such as SEO scores, store listings, settings and Google reports run straight away. Generating a preview spends AI credit but writes nothing, and StoreSEO tells the agent to say what a generation will cost before it runs one. Applying content, optimizing images, changing settings, publishing llms.txt or agents.md, writing a product description and deleting anything wait for your yes in the conversation. That yes is an instruction the agent follows, not a lock on the server, so your client's own tool-approval setting is the hard stop.
Questions
Can Grok Bot invent my business address for organization schema?
It should not. StoreSEO's guidance is that business details come from you, so give the Bot the name, address and hours and have it show the complete object before it calls the update.
Why did the Bot say a schema type was refused?
Some types need a plan feature or another schema on first. The FAQ types need the FAQ Schema feature, and review needs product schema enabled, so the Bot should name the missing piece instead of retrying.
What schema types can StoreSEO add to my store?
StoreSEO manages product, review, sale dates, product merchant, organization and local business schema with settings, plus toggle-only types such as the FAQ types for products, collections, articles and pages.
Why does the agent read my schema settings before changing them?
A settings update replaces the whole stored object instead of merging. Reading first and sending back the complete object is the only way to change one field without wiping the others.
Why was review schema refused?
Review, sale dates and product merchant schema depend on product schema. Turn product schema on first, then enable the dependent type.
Do I need a particular plan for FAQ schema?
Yes. The four FAQ schema types need the FAQ Schema feature in your StoreSEO plan. Without it, any change to them is refused with a message saying the feature is not in your plan.
Keep going
Structured data (JSON-LD) with other agents
More Grok Bot guides