Set up structured data with Windsurf
Setting up structured data with Windsurf means asking the Cascade agent in your editor to check which StoreSEO JSON-LD schema types are on, fill in your organization or product settings from the field template, and switch types on once you agree.
Last updated: October 2026
Set up Windsurf for StoreSEO
Skip this if Windsurf is already connected. The full guide, with the alternatives, is on the Windsurf page.
- 1
Add StoreSEO to mcp_config.json
In the Cascade panel, open the ... menu and click the Open MCP config file icon in the MCPs section. Add the entry under mcpServers and save. Remote servers use serverUrl.
JSON{ "mcpServers": { "storeseo": { "serverUrl": "https://mcp.storeseo.com/mcp" } } } - 2
Sign in to your store
Windsurf supports OAuth for remote servers. When it asks you to sign in to storeseo, a browser window opens: pick your Shopify store and approve access. Then ask this to confirm the connection.
PromptUse StoreSEO to show me my store's SEO score breakdown.
How does this work in Windsurf?
You are in Windsurf, usually with a theme or app repository open, and you type the request into the Cascade panel: which schema types are enabled on my store, and is organization schema set up. Cascade calls storeseo_start first to get the conversation id, then storeseo_list_schema_types, which returns every type with an on or off flag and whether it is configurable. Those two calls are reads, so you see them appear in the panel as tool calls and the answer is a short table of what is on, what is off and which types take settings.
To configure a type, Cascade calls storeseo_get_schema_settings for it. For product, review, product merchant, organization and local business that response includes a field template, the full shape of the settings object. Cascade fills the template with details you give it, such as business name, logo URL and contact email, and shows you the finished object before it sends anything. Because storeseo_update_schema_settings replaces the stored settings instead of merging into them, Cascade has to read first and send the whole object back. Organization and local business share their basic business information, so a change in one shows up in the other, which is worth telling Cascade if your two entries differ.
The editor is useful here in one specific way: if your theme already prints its own JSON-LD, you can ask Cascade to search the repository for existing script tags of type application/ld+json before you switch StoreSEO's types on, so you do not publish the same entity twice. That search is a Windsurf file operation and has nothing to do with StoreSEO. The update call itself changes your live storefront markup, so StoreSEO tells the agent to describe the change and wait for your yes in the chat.
-
You: Which schema types are on for my store, and is organization set up?
- storeseo_start read-only
- storeseo_list_schema_types read-only
- storeseo_get_schema_settings read-only
-
Windsurf: Product and review schema are on. Organization is off and has no business details yet. Using your name, logo URL and contact email, shall I send the complete organization settings and switch it on?
-
You: Yes, go ahead.
- storeseo_update_schema_settings needs approval
What to ask Windsurf
Use StoreSEO to list my JSON-LD schema types and tell me which are on, which are off and which take settings.
Read my organization schema settings and field template, then draft the full settings object from this business info before sending anything.
Before we enable StoreSEO schema, search this repo for application/ld+json in the theme so we do not duplicate it.
- 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 Windsurf 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 Windsurf
Windsurf's MCP page says mcp_config.json applies to the legacy Cascade agent, while the default Devin Local agent reads Devin CLI configuration, so confirm which agent your tab uses before assuming storeseo is loaded. Cascade also caps MCP tools at 100 across all servers, and StoreSEO takes 44 of them, so with several servers enabled the three schema tools may be among those you have to leave on. The docs do not describe Cascade's tool-approval behavior, which means the confirmation StoreSEO asks the agent for is your main check on a schema update. Read the settings object Cascade proposes before you accept the write.
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
Does Windsurf need to read my theme files to set up StoreSEO schema?
No. The schema tools work on your StoreSEO settings through the MCP server. Reading the theme is optional and only useful to spot JSON-LD your theme already prints.
Why does Cascade read the schema settings before every update?
Because storeseo_update_schema_settings replaces the stored object instead of merging. Cascade reads the current settings and field template, edits them and sends the complete object, so no existing field is dropped.
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 Windsurf guides