Structured data (JSON-LD) Set up structured data with Gemini CLI
Setting up structured data with Gemini CLI means asking Google's terminal agent to call the StoreSEO tools that list your Shopify store's JSON-LD types, read a type's settings and write the full settings object back after you confirm.
Last updated: October 2026
Set up Gemini CLI for StoreSEO
Skip this if Gemini CLI is already connected. The full guide, with the alternatives, is on the Gemini CLI page.
- 1
Add StoreSEO to Gemini CLI
Run this in any terminal. The user scope writes the server to ~/.gemini/settings.json so every project sees it. Without --scope user the command writes to the current project's .gemini/settings.json.
Terminalgemini mcp add --scope user --transport http storeseo https://mcp.storeseo.com/mcp
- 2
Sign in to your store
Start gemini. The first time it calls StoreSEO it opens your browser: pick your Shopify store and approve access. If the window does not open, type /mcp auth storeseo inside Gemini CLI. Then gemini mcp list should show storeseo as connected.
Prompt/mcp auth storeseo
How does this work in Gemini CLI?
You start gemini in the theme folder and ask which schema types are enabled. Gemini CLI exposes the server's tools under names such as mcp_storeseo_storeseo_list_schema_types, and the model calls storeseo_start first and then the list tool. With trust off, which is the default, Gemini CLI shows a confirmation for each MCP tool call, and you choose to allow it once or for the session. Allowing the read tools for the session is reasonable here and saves repeated prompts during an audit.
For a configurable type the model calls storeseo_get_schema_settings, reads the field template and asks you for the missing business details. Since Gemini CLI reads the folder you started it in, it can pull a company name or address from a README, a brand file or the theme's footer, then show you what it found before you accept it. When you confirm, it calls storeseo_update_schema_settings with the full object. Organization and local business share their basic information, so it should tell you that one save covers both.
The control worth using here is the includeTools list on the server entry in settings.json. If you only want Gemini CLI to audit schema, list the three schema tools and nothing else, and the model cannot reach the apply or delete tools in that session at all. That is a stricter guard than a prompt, and it keeps tool lists short, which helps the model pick the right call.
-
You: What JSON-LD types are enabled for my store?
- storeseo_start read-only
- storeseo_list_schema_types read-only
-
Gemini CLI: Product schema is on, and review, sale dates and product merchant are off. Product merchant needs complete settings before it can be enabled. Do you want me to read its field template and ask you for the details?
-
You: Yes, go ahead and read it.
- storeseo_get_schema_settings read-only
-
Gemini CLI: It needs return policy and shipping details. Send me those and I will ask once more before saving.
What to ask Gemini CLI
Use StoreSEO to list my JSON-LD schema types and tell me which are on and which accept settings.
Read my organization schema settings, then ask me for any empty field. Do not call an update tool until I say yes.
Turn on product schema in StoreSEO, then check whether review schema can be enabled and tell me if it is refused.
- 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 Gemini CLI 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 Gemini CLI
Do not set trust on the storeseo server, because trust skips every tool confirmation and then storeseo_update_schema_settings can change live markup with no prompt from the client. The browser sign-in also needs a browser on the same machine, so over SSH or in a headless session use the access token header instead. Check too that your account can still use Gemini CLI, since Google says it was replaced by Antigravity CLI for some unpaid and Google One users on June 18th, 2026.
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 I limit Gemini CLI to only the StoreSEO schema tools?
Yes. Add an includeTools list to the storeseo entry in settings.json naming storeseo_start, storeseo_list_schema_types, storeseo_get_schema_settings and storeseo_update_schema_settings, and the model sees only those from that server.
Why does Gemini CLI prompt me for each StoreSEO call?
Trust is off by default for MCP servers, so Gemini CLI asks before each tool call. You can allow a tool for the session, which is sensible for reads, while keeping the update tool on a prompt.
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 Gemini CLI guides