Structured data (JSON-LD) Set up structured data with Antigravity
Setting up structured data with Antigravity means asking Google's agentic coding product to read your StoreSEO JSON-LD schema types and settings and send complete settings once you approve the call in Ask mode.
Last updated: October 2026
Set up Antigravity for StoreSEO
Skip this if Antigravity is already connected. The full guide, with the alternatives, is on the Antigravity page.
- 1
Add StoreSEO in View raw config
In the Antigravity IDE open the menu in the agent side panel, choose MCP Servers, then Manage MCP Servers, then View raw config. Paste this into mcp_config.json and save. The field is serverUrl: Antigravity does not support url or httpUrl for remote servers.
JSON{ "mcpServers": { "storeseo": { "serverUrl": "https://mcp.storeseo.com/mcp" } } } - 2
Sign in, then check the connection
Open Agent settings (Cmd+, on Mac, Ctrl+, on Windows and Linux), go to Customizations and click Authenticate next to storeseo. Pick your Shopify store and approve in the browser, copy the authorization code it shows, paste it into the settings panel and click Submit. Then ask this in the agent panel.
PromptUse StoreSEO to show me my store's SEO score breakdown.
How does this work in Antigravity?
You open Antigravity's agent side panel in your project and ask which schema types your Shopify store has enabled. The agent calls storeseo_start and then storeseo_list_schema_types. Tools you have not configured run in Ask mode by default, so Antigravity asks for your approval before each call, and you approve the reads to see the list of types, their on or off state and which accept settings. The server entry in mcp_config.json uses the serverUrl field, and the sign-in ended with a code you pasted back under Customizations in Agent settings.
To configure organization, product or review schema, the agent calls storeseo_get_schema_settings, which returns the stored settings and a field template. It fills the template from your details, which can come from a file in the workspace if you point it at one, and shows you the complete object. The update replaces the stored settings, so the agent has to send every field, not only the one you changed. When you agree in the thread it calls storeseo_update_schema_settings, and Antigravity's Ask mode shows its own approval for that call too.
That gives you two separate checks on the change. StoreSEO tells the agent to describe it and wait for your yes, and Antigravity's approval prompt is the client-side stop. If you want fewer prompts for the audit, a policy of the form mcp(storeseo/storeseo_list_schema_types) allows a single read tool and leaves the update tool on Ask.
-
You: Which JSON-LD schema types are on for my store?
- storeseo_start read-only
- storeseo_list_schema_types read-only
-
Antigravity: Product schema is on. Product merchant is off and depends on product schema, which is on. Shall I read its settings?
-
You: Yes, read them.
- storeseo_get_schema_settings read-only
-
Antigravity: It needs complete settings to be enabled. Send the full product merchant settings from your details and switch it on?
What to ask Antigravity
Use StoreSEO to list my JSON-LD schema types and tell me which are on, off and configurable.
Read my product merchant schema settings and tell me what it depends on before I enable it.
Build complete organization settings from the details in this workspace file and wait for my yes before updating.
- 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 Antigravity 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 Antigravity
Antigravity's documentation says the remote field is serverUrl and that legacy fields such as url or httpUrl are not supported, so an entry copied from another client's config will not connect until you rename it. Unconfigured MCP tools run in Ask mode, which suits a schema update because it replaces your stored settings and changes live storefront markup. A policy that allows mcp(storeseo/*) would stop Antigravity asking about every StoreSEO tool, and then the confirmation StoreSEO tells the agent to request is the only check. Allow individual read tools such as storeseo_list_schema_types instead, and keep storeseo_update_schema_settings on Ask.
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 Antigravity ask before listing my schema types?
Unconfigured MCP tools run in Ask mode, which requires approval before each call. Allow the individual read tools with a mcp(server/tool) policy if you want the audit to run without prompts.
What does Antigravity send when it updates StoreSEO schema settings?
The complete settings object, based on the field template from storeseo_get_schema_settings, plus the on or off status. The update replaces the stored settings, so it has to include every field.
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 Antigravity guides