K Structured data (JSON-LD)

Set up structured data with Kiro

Setting up structured data with Kiro means asking the AWS agentic IDE's chat to read your StoreSEO JSON-LD schema types and settings and then send complete organization, product or review settings after you approve.

Jump to the prompts Connect Kiro

Last updated: October 2026

Set up Kiro for StoreSEO

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

1
Add StoreSEO to your Kiro MCP config

Open the Command Palette (Cmd+Shift+P on Mac, Ctrl+Shift+P on Windows and Linux), search for MCP and open the workspace config (.kiro/settings/mcp.json) or the user config (~/.kiro/settings/mcp.json). Paste this and save. Kiro applies the change on save, and the first connection opens a browser sign-in: pick your Shopify store and approve.
JSON

{ "mcpServers": { "storeseo": { "url": "https://mcp.storeseo.com/mcp" } } }

How does this work in Kiro?

You work in Kiro with your project open and ask the agent in the chat panel which structured data your Shopify store has on. It calls storeseo_start, then storeseo_list_schema_types, and replies with each type, its on or off state and whether it takes settings. The server is defined in .kiro/settings/mcp.json for the project or in ~/.kiro/settings/mcp.json for every project, and Kiro applies a saved change straight away. If the sign-in points at the wrong store, check which of the two files defines storeseo, because the workspace file wins.

To configure a type, the agent calls storeseo_get_schema_settings, takes the field template and fills it from what you tell it or from a file in the project, then shows you the complete settings. The update replaces the stored object instead of merging, and organization and local business share their business information, so the agent should check both before it writes. After your yes it calls storeseo_update_schema_settings and reports the outcome. If StoreSEO rejects the call because the plan lacks the FAQ Schema feature or product schema is off, Kiro relays that reason.

Kiro gives each server an autoApprove list and a disabledTools list, and they suit this job. List the read tools, storeseo_start, storeseo_list_schema_types and storeseo_get_schema_settings, under autoApprove so the audit runs without prompts, and leave the update tool off it so Kiro still prompts you before a write. If you only want an audit, add the update tool to disabledTools and the agent cannot call it at all.

Kiro + StoreSEO Illustrative session

You: Which schema types are on for my store?
storeseo_start read-only
storeseo_list_schema_types read-only
Kiro: Product schema is on, local business is off. I can read the local business template and fill it from your spec file. Shall I read it?
You: Yes, read it.
storeseo_get_schema_settings read-only
Kiro: The template needs address, phone and opening hours, all in your spec. Send the complete local business settings and switch it on?

What to ask Kiro

Prompt 1

Use StoreSEO to list my JSON-LD schema types and tell me which are on, off and configurable.

Prompt 2

Read my local business schema settings and field template, then list what is missing before changing anything.

Prompt 3

Draft complete organization settings from the details in this spec 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.

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

An autoApprove entry with a wildcard would let Kiro run every StoreSEO tool without prompting, and that includes storeseo_update_schema_settings, which replaces your schema settings and changes live storefront markup. Name the individual read tools in autoApprove instead, so Kiro's own prompt stays in front of the write, and use disabledTools if you want an audit-only setup. A workspace .kiro/settings/mcp.json overrides a user-level entry with the same server name, which matters if two projects point at different stores. A token under headers is a secret, so do not commit a workspace file that holds one, and revoke it in StoreSEO under Settings, AI Toolkit if it leaks.

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

Which StoreSEO schema tools should I put in Kiro's autoApprove list?

The read tools only: storeseo_start, storeseo_list_schema_types and storeseo_get_schema_settings. Leave storeseo_update_schema_settings off the list so Kiro prompts before a write.

Can I make Kiro unable to change schema at all?

Yes. Add storeseo_update_schema_settings to the server's disabledTools list in mcp.json. The agent can still list and read schema types but cannot call the update tool.

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.