Set up structured data with NanoClaw
Setting up structured data with NanoClaw means asking your self-hosted agent in a chat to list your StoreSEO schema types, read the current settings of the one you care about, and send back a complete edited object after you confirm.
Last updated: October 2026
Set up NanoClaw for StoreSEO
Skip this if NanoClaw is already connected. The full guide, with the alternatives, is on the NanoClaw page.
- 1
Create a StoreSEO access token
In the StoreSEO app open Settings, AI Toolkit and generate a personal access token. Keep it out of chat messages and out of Git.
new message to NanoClawSettings → AI Toolkit → create a token
- 2
Add StoreSEO to your agent's container
Run this on the machine that hosts NanoClaw, using your agent group's ID from ncl groups list. The header goes in as a JSON object. NanoClaw may ask an admin to approve the change.
terminalncl groups config add-mcp-server --id <group-id> --name storeseo \ --url https://mcp.storeseo.com/mcp \ --headers '{"Authorization":"Bearer YOUR_TOKEN"}' - 3
Restart the agent's container
The new server takes effect after a restart. Then message your agent with its trigger word, @Andy by default, and ask for your store's SEO score.
terminalncl groups restart --id <group-id>
Step-by-step guide in the docs: How to connect StoreSEO MCP to NanoClaw
How does this work in NanoClaw?
Structured data rewards a careful order of steps, and a chat thread is a good place to keep them visible. You message @Andy and ask which schema types are on. The agent calls storeseo_start and storeseo_list_schema_types, which shows every JSON-LD type, whether it is enabled and whether it is configurable. For one type, say organization, it calls storeseo_get_schema_settings, which returns the current values and a field template describing the full object to send back. These are reads, so a single reply can summarize the whole set.
storeseo_update_schema_settings replaces the stored settings wholesale, so a half filled object can wipe good values. Before it edits anything, ask the agent to paste the settings it just read into the chat. That message becomes your rollback copy, kept in your own history. Then give it the business details in the thread, such as legal name, address and opening hours, and have it show the complete object back before the update. It should not invent any of those details, and the agent should tell you if a required field is still missing.
Some types depend on others. Review and product merchant schema need product schema on first, and the four FAQ types need the FAQ Schema feature in your plan, so a refusal is possible and the agent should name the missing piece instead of retrying. Each update changes the markup your live storefront serves, so keep it in a conversation. A scheduled task that only lists the type states and sends you any change since last week is as far as automation should go here.
-
You: @Andy use StoreSEO to check my structured data and set up organization schema.
- storeseo_start read-only
- storeseo_list_schema_types read-only
- storeseo_get_schema_settings read-only
-
NanoClaw: Organization schema is off and its settings are empty. I need your business name, logo and contact details, then I will send the full object, which changes the markup on your live storefront. Shall I enable it once you give me those?
-
You: Yes, here are the details.
- storeseo_update_schema_settings needs approval
What to ask NanoClaw
Tap a prompt to copy it, then paste it into NanoClaw.
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 NanoClaw 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 NanoClaw
Pasting your address and phone number into a WhatsApp or Telegram thread stores them in that chat's history and in NanoClaw's memory for the agent group. For organization and local business schema that is usually public business information, but do not paste anything you would not publish. Keep tokens out of the thread entirely, since the StoreSEO access token belongs in the container configuration, not in a message.
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
Can NanoClaw make up my business details for organization schema?
It should not. StoreSEO's guidance is that business details come from you, so message the agent your name, address and hours and have it show the whole object before it calls the update.
Why did NanoClaw report that a schema type was refused?
Some types need a plan feature or another type enabled first. FAQ types need the FAQ Schema feature, and review needs product schema on, so the agent should name what is missing and stop.
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 NanoClaw guides