Set up structured data with Muse
Setting up structured data with Muse means asking Meta's personal AI agent to read which JSON-LD schema types StoreSEO has switched on for your store, and then to enable one or change its settings with details you give it in the thread.
Last updated: October 2026
Set up Muse for StoreSEO
Skip this if Muse is already connected. The full guide, with the alternatives, is on the Muse page.
- 1
Send this message to Muse
Paste it into a new chat with Muse in the app, on muse.ai or in WhatsApp. Muse is rolling out in the US first, so you need access to it before this works.
new message to MuseAdd a custom connector for my Shopify SEO app StoreSEO: https://mcp.storeseo.com/mcp - It is an MCP server over HTTP and it signs in with OAuth. Send me the sign-in link and I will approve it. - Once it is connected, show me my store's SEO score breakdown.
- 2
Approve the sign-in for your store
Open the sign-in link Muse sends back, pick your Shopify store in the browser and approve access. Meta does not review custom connectors, so only approve this one if you started it.
server URLhttps://mcp.storeseo.com/mcp
Step-by-step guide in the docs: How to connect StoreSEO MCP to Muse
How does this work in Muse?
Structured data is a good first job to hand a conversational agent because the starting point is a plain list. You ask Muse which schema types are enabled, and it calls storeseo_start and storeseo_list_schema_types. Each row says whether a type is on and whether it is configurable: product, review, product merchant, organization and local business take settings, and the rest are simply on or off. Muse can read one type in detail with storeseo_get_schema_settings, which returns the current settings and a field template describing every field.
The write is storeseo_update_schema_settings, and it replaces the stored settings object as a whole. That is why Muse must read the current settings first and send the edited copy back, rather than patching one field from memory. Business details come from you. If you ask for organization schema, Muse should ask for your business name, logo and contact email in the thread, and it must not invent an address or opening hours. Replying from a phone, you can paste a line at a time. Turning a type on or off changes the markup your storefront serves, so expect a confirmation question first.
Dependencies surface as refusals you can act on. Review, sale dates and product merchant need product schema on first, and the FAQ types need the FAQ Schema feature in your plan, so a change to them can fail even when you say yes. Muse should name the missing piece, not retry. Sale dates also need an optional Shopify scope that only the app's own toggle can request. When a change goes through, ask Muse to read the type back so the thread ends with the stored state instead of an assumption.
-
You: Use StoreSEO to set up organization schema for my store.
- storeseo_start read-only
- storeseo_list_schema_types read-only
- storeseo_get_schema_settings read-only
-
Muse: Organization schema is off and has no settings. It needs a name, logo and contact email. What are they?
-
You: Linen & Loom, our logo, [email protected].
-
Muse: This turns on organization markup on your live storefront. Should I save these settings and enable it?
-
You: Yes, enable it.
- storeseo_update_schema_settings needs approval
What to ask Muse
Tap a prompt to copy it, then paste it into Muse.
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 Muse 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 Muse
Details you type into a message thread can arrive in a form schema does not want, such as a logo described in words instead of an address. If StoreSEO rejects the settings, Muse should report the field and ask again, not guess. Because the update replaces the whole object, do not accept a shortened version that drops fields you set earlier. Muse has no per-tool switch for this connector, so confirm what the saved object will contain before you say yes.
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 did Muse read my schema settings before changing them?
StoreSEO replaces the whole settings object on an update instead of merging, so the agent reads the current one, edits it and sends the full copy back. Skipping the read could erase fields you set before.
Can Muse turn on FAQ schema for my pages?
Only if the FAQ Schema feature is in your StoreSEO plan. Without it any change to the four FAQ schema types, on or off, is refused, and Muse should tell you that.
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 Muse guides