Set up structured data with Manus
Setting up structured data with Manus means asking a task agent to read which JSON-LD schema types StoreSEO has switched on, collect the business details only you have, and send back a complete settings object for the type you want enabled.
Last updated: October 2026
Set up Manus for StoreSEO
Skip this if Manus is already connected. The full guide, with the alternatives, is on the Manus page.
- 1
Create an access token in StoreSEO
In the StoreSEO app, open Settings, then AI Toolkit, and generate a named personal access token. Copy it now and keep it out of any chat.
new message to ManusStoreSEO → Settings → AI Toolkit → generate a token
- 2
Add StoreSEO as a custom MCP server
In Manus, open Settings, then Integrations, then Custom MCP Servers, and choose Add Server. Give it a name, paste this URL as the server URL and enter your token as the authentication, as a Bearer token.
server URLhttps://mcp.storeseo.com/mcp
- 3
Check it and use it
Manus verifies it can reach the server and read its tools. Then start a task that names StoreSEO, so Manus uses the connector.
new message to ManusUse StoreSEO to show me my store's SEO score breakdown.
Step-by-step guide in the docs: How to connect StoreSEO MCP to Manus
How does this work in Manus?
You describe the outcome in a Manus task that names StoreSEO, for example check which schema types are on and set up organization schema for my store. Manus calls storeseo_start and then storeseo_list_schema_types, which returns every type with whether it is enabled and whether it takes settings. The configurable ones are product, review, sale dates, product merchant, organization and local business. For the one you want, it calls storeseo_get_schema_settings, which returns the stored settings and a field template that describes the full object. All of that is reading and runs without a pause.
The next step is the one an autonomous agent can get wrong. A settings update through storeseo_update_schema_settings replaces the whole stored object, so Manus has to start from what it just read and send back the complete object with only your changes. The business name, address, phone number, logo and contact email come from you, not from the model. Give them in the task or let Manus ask, and tell it not to fill gaps from the web, because organization and local business share the same business information and a wrong address lands in both.
Dependencies show up in the report. Review, sale dates and product merchant need product schema on first, and disabling product also disables product merchant. The four FAQ schema types need the FAQ Schema feature in your plan, so a refusal there is a plan answer, not a failure to retry. Turning a type on changes the markup on your live storefront, so Manus should name the type and the settings and wait for your yes before the call.
-
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
-
Manus: Organization schema is off and its settings are empty. I need your business name, logo URL and contact email, and I will not guess them. Shall I send these settings and switch it on once you give me those?
-
You: Yes. Business name Northline Goods, logo URL and email as listed in my message.
- storeseo_update_schema_settings needs approval
What to ask Manus
Tap a prompt to copy it, then paste it into Manus.
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 Manus 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 Manus
Manus is built to finish tasks, and with a half-filled form it may try to complete the missing fields itself from public pages. Give the exact business details in the task and say not to invent an address, phone number or opening hours. Also remember the settings object is replaced, not merged, so a task that skips the read can wipe fields you had set. A scheduled Manus task can safely list schema types and report which are off. It should not change them.
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 Manus read my schema settings before it changes them?
A settings update replaces the whole stored object instead of merging. Reading first and sending back the complete object is how one field changes without wiping the others.
Can Manus enable FAQ schema on any StoreSEO plan?
No. The four FAQ schema types need the FAQ Schema feature in your plan. Without it, StoreSEO refuses any change to them and the message says the feature is not in your plan.
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 Manus guides