Set up structured data with OpenClaw
Setting up structured data with OpenClaw means messaging your self-hosted agent runtime to review StoreSEO's JSON-LD schema types and configure organization or product settings, with scheduled checks kept to reports.
Last updated: October 2026
Set up OpenClaw for StoreSEO
Skip this if OpenClaw is already connected. The full guide, with the alternatives, is on the OpenClaw page.
- 1
Add StoreSEO to OpenClaw
Run this on the installation that owns the connector. The --auth oauth flag marks the server as an OAuth server, which is what openclaw mcp login needs.
Terminalopenclaw mcp add storeseo \ --url https://mcp.storeseo.com/mcp \ --transport streamable-http \ --auth oauth
- 2
Sign in to your store
The login prints an authorization URL. Open it in a browser, pick your Shopify store and approve access. OpenClaw captures the redirect and saves the credentials.
Terminalopenclaw mcp login storeseo
- 3
Check the connection
The probe opens a live connection and reports the tools the server offers. A saved server entry proves nothing until the probe passes.
Terminalopenclaw mcp doctor storeseo --probe
How does this work in OpenClaw?
You reach OpenClaw through a chat app such as Telegram or Slack, or through its Control UI, and ask which schema types are on for your store. The agent calls storeseo_start, then storeseo_list_schema_types, and replies in the same thread with each type, its on or off state and whether it is configurable. The storeseo server was added once with openclaw mcp add and signed in with openclaw mcp login, and that sign-in lives on the installation that owns the connector, so the same credentials serve both a chat message and a scheduled run.
A change is a conversation in that thread. You give the business details, OpenClaw calls storeseo_get_schema_settings to fetch the stored settings and the field template, and it posts the complete settings object back to you for review. Only after you answer yes does it call storeseo_update_schema_settings. The update replaces the stored object, which is why the read comes first, and enabling organization, local business or product merchant needs a complete object in the same call or already stored. If StoreSEO refuses because a dependency is missing, the reply in your chat says which one.
The scheduler is what makes OpenClaw different for this job. An automation created with openclaw automations create can wake the agent every week in an isolated session, list the schema types and announce the result in your chat, so a type that was switched off or a business detail that went missing shows up without you asking. That run has nobody to say yes, so the prompt should ask for reads only: list the types, read the settings, report the differences. Edits stay in a message you can answer.
-
You: Which schema types are on for my shop?
- storeseo_start read-only
- storeseo_list_schema_types read-only
-
OpenClaw: Product and review schema are on, local business is off. Local business takes settings, so I can read its template now. Shall I?
-
You: Yes, read it and show me the empty fields.
- storeseo_get_schema_settings read-only
-
OpenClaw: Address and opening hours are empty. Send me those and I will post the full object for your yes before updating.
What to ask OpenClaw
Use StoreSEO to list my JSON-LD schema types and tell me which are on. Read only.
Read my local business schema settings and tell me which fields are empty. Do not send an update.
Draft the complete organization settings from my business details, post them here and wait for my yes before you update.
- 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 OpenClaw 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 OpenClaw
A scheduled OpenClaw automation cannot wait for a yes, so a recurring schema check should ask only for storeseo_list_schema_types and storeseo_get_schema_settings and say plainly that it must not call the update tool. Run the openclaw mcp commands on the installation that owns the connector, since a Gateway or agent on another host needs its own reload before it sees storeseo. OpenClaw also has a per-server approval setting through openclaw mcp configure, and a mode that skips the check would leave StoreSEO's own confirmation as the only stop on a schema update. If you want the scheduled agent unable to write at all, narrow its tools with openclaw mcp tools and exclude the update tool.
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 an OpenClaw automation switch schema types on by itself?
It should not. A scheduled run has nobody to answer, so keep it to reading and reporting. Ask for changes in a chat message where you can say yes, or exclude the update tool from the agent.
Where does OpenClaw keep the StoreSEO sign-in for scheduled runs?
On the installation that owns the connector. openclaw mcp login saves the credentials there, so scheduled automations reuse the same sign-in as your chat messages.
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 OpenClaw guides