Set up structured data with GitHub Copilot
Setting up structured data with GitHub Copilot means asking Agent mode in VS Code to call the StoreSEO tools that list your Shopify store's JSON-LD types, read a type's settings and write them back, with VS Code's confirmation dialog in front of the write.
Last updated: October 2026
Set up GitHub Copilot for StoreSEO
Skip this if GitHub Copilot is already connected. The full guide, with the alternatives, is on the GitHub Copilot page.
- 1
Add StoreSEO to .vscode/mcp.json
Create or open .vscode/mcp.json in your workspace and paste this. VS Code uses a top-level servers key, not mcpServers, and a remote server needs type http.
JSON{ "servers": { "storeseo": { "type": "http", "url": "https://mcp.storeseo.com/mcp" } } } - 2
Start the server and sign in
Run MCP: List Servers from the Command Palette, pick storeseo and start it. If it asks you to sign in, pick your Shopify store in the browser and approve access. Then open Copilot Chat in Agent mode, check the tools icon lists StoreSEO and ask this.
PromptUse StoreSEO to show me my store's SEO score breakdown.
How does this work in GitHub Copilot?
You have the theme workspace open in VS Code with Copilot Chat in Agent mode, and the storeseo server started from .vscode/mcp.json. You ask which schema types are on for the store. Agent mode calls storeseo_start and storeseo_list_schema_types, and VS Code shows a confirmation card for each tool call, with the arguments visible and a choice to allow it once, for the session or for the workspace. For the read tools, allowing them for the session keeps an audit quick.
To set up local business schema, the agent calls storeseo_get_schema_settings, takes the field template and asks you for what it lacks. Because it sits in your workspace it can read the theme's footer and contact templates to propose values, and it should present them for you to correct. Organization and local business share basic information, so one set of answers fills both. You then confirm storeseo_update_schema_settings, and the card shows the full settings object that will be sent, which is the thing to read before you click continue.
A workspace-level server file brings one practical point. A .vscode/mcp.json committed to the repository is shared with your team, so a colleague who opens the project gets the same StoreSEO server, and each person signs in to the store themselves. Decide among you who is allowed to approve schema updates, since the change goes to the live storefront rather than to the repository, and a pull request review will not catch it. Agreeing that in advance saves an awkward surprise later.
-
You: List my schema types, then read the local business settings.
- storeseo_start read-only
- storeseo_list_schema_types read-only
- storeseo_get_schema_settings read-only
-
GitHub Copilot: Local business schema is off and its settings are empty. The footer template has an address and phone I can use. Do you want me to save those and enable it?
-
You: Yes, save them and enable it.
- storeseo_update_schema_settings needs approval
What to ask GitHub Copilot
Use StoreSEO to list which JSON-LD schema types are enabled and which ones take settings.
Get my organization schema settings from StoreSEO and list every empty field. Ask me for the values before you update anything.
Enable product schema through StoreSEO. If review schema depends on it, tell me the order you will do it in and wait for my yes.
- 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 GitHub Copilot 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 GitHub Copilot
A schema update goes to your live storefront, not to the repository, so no pull request or diff review will show it. VS Code's tool confirmation is the hard stop, so choose Allow once rather than for the workspace on storeseo_update_schema_settings. On Copilot Business and Enterprise plans an organization admin must also enable MCP servers in Copilot policy, otherwise the server will not start.
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
Will a schema change from Copilot appear in my git diff?
No. storeseo_update_schema_settings changes the schema configuration held by StoreSEO for your live store, so nothing in the workspace changes. Only edits to theme files show up in git.
Do my teammates need to sign in separately if .vscode/mcp.json is committed?
Yes. The file shares the server definition, not your credentials, so each person opens MCP: List Servers, starts storeseo and signs in with their own Shopify access.
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 GitHub Copilot guides