Set up structured data with Paperclip
Setting up structured data from Paperclip means tasking an agent to list which StoreSEO JSON-LD types are on and what each is missing, then switching a type on only when you have supplied the business details in a task you approve.
Last updated: October 2026
Set up Paperclip for StoreSEO
Skip this if Paperclip is already connected. The full guide, with the alternatives, is on the Paperclip page.
- 1
Add StoreSEO to the agent Paperclip runs
Run this on the machine that hosts the agent, as the same OS user the Paperclip heartbeat runs as, from the agent's working directory. It is the claude_local adapter path, and user scope makes StoreSEO available to every Claude Code agent that user runs.
terminalclaude mcp add --transport http --scope user storeseo https://mcp.storeseo.com/mcp
- 2
Sign in once, then let Paperclip run headless
Start claude interactively as that same user, run /mcp, choose storeseo and finish the browser sign-in: pick your Shopify store and approve. Claude Code keeps the credentials, so later Paperclip runs need no browser. Check with claude mcp get storeseo.
new message to Paperclip/mcp
Step-by-step guide in the docs: How to connect StoreSEO MCP to Paperclip
How does this work in Paperclip?
A schema ticket begins with an inventory. The agent calls storeseo_list_schema_types, which shows every type, whether it is on and whether it takes settings, then storeseo_get_schema_settings for the configurable ones: product, review, sale dates, product merchant, organization and local business. It posts what is missing, for example organization schema with no contact email, or review schema blocked because product schema is off. That is a read-only report and a reasonable weekly routine for a store that keeps changing plans or themes.
The change is a separate task because storeseo_update_schema_settings replaces the whole settings object rather than merging, so the agent has to read first and send back every field. The details are yours: business name, logo, address, phone and opening hours should come from the ticket text or a Paperclip secret or file you attach, not from the model's guess. Organization and local business share business information, so editing one edits the other. Turning a type on changes the markup on your live storefront, and the FAQ types need the FAQ Schema feature in your plan.
A Paperclip ticket is a good place to keep the before and after: ask the agent to paste the current settings before it writes, so a reviewer can see what changed. If a type is refused for a missing dependency or a plan feature, the agent should name which one on the ticket and stop, rather than retrying the call or switching on other types to get around it.
-
You: Ticket: check structured data and set up organization schema from the details in the description.
- storeseo_list_schema_types read-only
- storeseo_get_schema_settings read-only
-
Paperclip: Organization schema is off and its settings are empty. I will send the full settings object with the business name, logo and contact email from the ticket, nothing invented, and switch it on. That changes your live markup. Go ahead?
-
You: Yes, go ahead.
- storeseo_update_schema_settings needs approval
-
Paperclip: Organization schema is on with the details from the ticket. I pasted the previous empty settings above for the record.
What to ask Paperclip
Tap a prompt to copy it, then paste it into Paperclip.
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 Paperclip 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 Paperclip
Because a schema update replaces the whole stored object, an agent that skips the read can wipe fields you set earlier. The Claude Code adapter that Paperclip uses runs without permission prompts by default, so nothing but the task text and the agent's habits enforce read-then-write. Put read the current settings first and paste them on the ticket in every schema task, and keep business details in the ticket or a secret so the agent never invents an address.
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 a Paperclip routine switch schema types on for me?
It can only if you let an unattended agent write to your live storefront markup, which is a poor trade. Use the routine to list types and report gaps, and switch a type on in a task you start with the business details attached.
Where should I keep my business address for the agent?
In the ticket description or in a Paperclip secret or attached file, so the agent copies it verbatim. StoreSEO's tools expect complete settings for organization, local business and product merchant, and the agent is meant not to invent any detail.
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 Paperclip guides