Z Structured data (JSON-LD)

Set up structured data with Zed

Setting up structured data with Zed means asking the Agent Panel in your editor to read your StoreSEO JSON-LD schema types and settings, then send complete settings once you approve both Zed's prompt and the agent's question.

Jump to the prompts Connect Zed

Last updated: October 2026

Set up Zed for StoreSEO

Skip this if Zed is already connected. The full guide, with the alternatives, is on the Zed page.

1
Add StoreSEO as a remote server

Open Settings, then AI, then MCP Servers and add a remote server, or add this to settings.json yourself. Leave out headers so Zed can sign you in.
JSON

{ "context_servers": { "storeseo": { "url": "https://mcp.storeseo.com/mcp" } } }
2
Sign in and check the dot

Because the entry has no Authorization header, Zed prompts you to authenticate. Pick your Shopify store and approve in the browser. In Settings, AI, MCP Servers a green dot next to storeseo means the server is active. Then ask this in the Agent Panel.
Prompt

Use StoreSEO to show me my store's SEO score breakdown.

How does this work in Zed?

You open Zed's Agent Panel and ask which schema types your Shopify store has switched on. The agent calls storeseo_start, then storeseo_list_schema_types, and Zed shows each call in the thread. Zed's default for agent.tool_permissions is confirm, so it asks before it runs a tool action, reads included. Expect a prompt for each of the first three calls in a schema review, and approve them to see the table of types, their on or off state and which of them accept settings.

Setting up organization or local business schema continues in the same thread. The agent calls storeseo_get_schema_settings to get the current settings and the field template, fills it from details you type or from a file open in your project, and shows you the complete object. Then there are two separate checks on the write. StoreSEO tells the agent to describe the change and wait for your yes in the conversation, and Zed's own prompt for storeseo_update_schema_settings appears when the agent tries to run it. The update replaces the stored settings, so read the object in the panel before you approve either one.

You can make the prompts less repetitive without losing the stop on writes. Zed allows per-tool keys of the form mcp:storeseo:storeseo_list_schema_types, so you can set the list and get tools to allow and leave the update tool on confirm. A schema audit then runs without interruption and only the change asks you.

Zed + StoreSEO Illustrative session

You: Which schema types are enabled for my store?
storeseo_start read-only
storeseo_list_schema_types read-only
Zed: Product and review schema are on. Organization is off and takes settings. Shall I read its field template?
You: Yes, read it.
storeseo_get_schema_settings read-only
Zed: I have the template. With the name and logo you gave me, send the complete organization settings and switch it on?

What to ask Zed

Prompt 1

Use StoreSEO to list my JSON-LD schema types and show which are on. Read only.

Prompt 2

Read the product schema settings and field template, then tell me which fields are empty.

Prompt 3

Prepare the full organization settings from this business info and wait for my yes before calling the update tool.

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.

storeseo_list_schema_typesstoreseo_get_schema_settingsstoreseo_update_schema_settings

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 Zed 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 Zed

Zed asks before every tool action by default, so a schema review means several prompts even though the first three calls only read. Allow the read tools with per-tool keys such as mcp:storeseo:storeseo_get_schema_settings and leave mcp:storeseo:storeseo_update_schema_settings on confirm, so Zed's own prompt stays in front of the write. If you set agent.tool_permissions.default to allow, Zed stops asking and the confirmation StoreSEO tells the agent to request becomes the only check on a change to your live storefront markup. A token in settings.json, if you use one instead of the OAuth prompt, is a secret to keep out of version control.

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 Zed prompt me for read-only StoreSEO schema calls?

Zed's default is confirm for tool actions, reads included. Set per-tool keys for the StoreSEO list and get tools to allow and leave the update tool on confirm.

Who confirms a schema change in Zed, StoreSEO or Zed?

Both can. StoreSEO tells the agent to wait for your yes in the thread, and Zed's tool permission setting is the hard stop when it prompts before storeseo_update_schema_settings runs.

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.