Set up structured data with Kimi Code
Setting up structured data in Kimi Code means asking Moonshot AI's terminal agent to list the JSON-LD schema types StoreSEO manages, read each type's settings before editing, and switch on the markup you want for your Shopify storefront.
Last updated: October 2026
Set up Kimi Code for StoreSEO
Skip this if Kimi Code is already connected. The full guide, with the alternatives, is on the Kimi Code page.
- 1
Add StoreSEO to Kimi Code
Create or edit ~/.kimi-code/mcp.json so every project on your machine can use StoreSEO. For one repository only, use .kimi-code/mcp.json inside it. You can also run /mcp-config in Kimi Code and have it add the server for you.
json config{ "mcpServers": { "storeseo": { "url": "https://mcp.storeseo.com/mcp" } } } - 2
Sign in to your store
Start a new Kimi Code session (a server added mid-session registers in the next one), run this command, then follow the browser window: pick your Shopify store and approve access.
new message to Kimi Code/mcp-config login storeseo
Step-by-step guide in the docs: How to connect StoreSEO MCP to Kimi Code
How does this work in Kimi Code?
You ask which schema types are on and which are off, and Kimi Code calls storeseo_list_schema_types, which says for every type whether it is enabled and whether it is configurable. Product, review, organization and local business types take settings, while the rest only switch on or off. The agent then calls storeseo_get_schema_settings for the type you care about, and that response includes a field template describing the full settings object.
That template is the center of the job. storeseo_update_schema_settings replaces a type's settings wholesale instead of merging, so the agent must read first, edit the whole object and send it back. In a terminal you can keep that object in a scratch file, review it as JSON and ask Kimi Code to diff it against what StoreSEO returned. Business details such as address, phone and opening hours come from you, since the agent does not invent them, and organization and local business share the same basic information, so changing it in one updates both.
Some switches have prerequisites. Review and product merchant markup need product schema enabled first, and the four FAQ schema types need the FAQ Schema feature in your plan. If a change is refused, Kimi Code should report the reason and not retry. Because schema changes alter live markup, ask the agent to name the type and the new state before it calls the write, then confirm in your own tab with a structured data test tool if you want an outside check.
-
You: Which structured data is switched on in my store?
- storeseo_start read-only
- storeseo_list_schema_types read-only
- storeseo_get_schema_settings read-only
-
Kimi Code: Illustrative result: product schema is off and organization is on but has no phone number. Turning product schema on changes your live storefront markup. Should I enable it?
-
You: Yes, enable product schema.
- storeseo_update_schema_settings needs approval
-
Kimi Code: Product schema is on. Review and product merchant schema can follow. Which one next?
What to ask Kimi Code
Tap a prompt to copy it, then paste it into Kimi Code.
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 Kimi Code 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 Kimi Code
Because the settings update replaces the stored object, a stale copy is the main risk in a long Kimi Code session. If you saved a schema object to a scratch file an hour ago and someone changed the setting in the StoreSEO app since, sending the old file back overwrites their change. Have the agent call storeseo_get_schema_settings again right before each write, and keep the write tool on ask so you see the exact object before it goes.
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
Why does Kimi Code read schema settings before every update?
StoreSEO replaces a type's settings with whatever object it receives, with no partial merge. Reading first, editing the whole object and sending it back keeps fields you did not mention from being wiped out.
Can Kimi Code turn on FAQ schema for my store?
Only if your plan includes the FAQ Schema feature. Without it StoreSEO rejects any change to the four FAQ types, on or off, and the agent should tell you which feature is missing 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 Kimi Code guides