Structured data (JSON-LD)

Set up structured data with Codex

Setting up structured data with Codex means asking OpenAI's coding agent to list your Shopify store's JSON-LD schema types through the StoreSEO server in config.toml, read settings and write the complete object back after your yes.

Jump to the prompts Connect Codex

Last updated: October 2026

Set up Codex for StoreSEO

Skip this if Codex is already connected. The full guide, with the alternatives, is on the Codex page.

1
Add StoreSEO to Codex

Run this in any terminal. It writes a [mcp_servers.storeseo] table to ~/.codex/config.toml, which the Codex CLI, the IDE extension and the ChatGPT desktop app all read.
Terminal

codex mcp add storeseo --url https://mcp.storeseo.com/mcp
2
Sign in to your store

Run the login command. Your browser opens: pick your Shopify store and approve access. Then run codex mcp list, or type /mcp inside Codex, to confirm storeseo is there.
Terminal

codex mcp login storeseo codex mcp list

How does this work in Codex?

You run codex in the theme repository, or use the same server from the IDE extension or the ChatGPT desktop app, all of which read the same config.toml. You ask which schema types are on, and Codex calls storeseo_start and storeseo_list_schema_types, printing each call in its transcript. If you signed in with codex mcp login storeseo earlier, the read calls go straight through, and you get a short list of types with their state and whether each takes settings.

The approval mode you set on the server decides what happens at the write. With default_tools_approval_mode set to writes, Codex runs the list and get tools that are marked read-only without asking and stops to prompt you before storeseo_update_schema_settings, which is exactly the split this job wants. With prompt, every call asks, which is slower but fine for a one-off setup. With approve, nothing asks, and the only check left is the confirmation StoreSEO tells the agent to request in the conversation, so avoid it for this server.

A typical run goes: Codex reads organization settings with storeseo_get_schema_settings, takes the field template, fills what you have given it and anything it can read from files in the repository, and asks about the rest. It then sends the full object once you approve. Because Codex works on the repository you started it in, you can ask it to write the before and after type lists to a file there, which is a convenient record of what changed on the storefront and something you can hand to a client or a colleague afterwards.

Codex + StoreSEO Illustrative session

You: Is organization schema configured? If not, set it up with these details: Harbor and Pine, [email protected].
storeseo_start read-only
storeseo_get_schema_settings read-only
Codex: Organization schema is off with no settings, and it needs a logo URL too. I will save the name and email with your logo link and enable it. Shall I send that now?
You: Yes. The logo is https://cdn.harborpine.example/logo.png
storeseo_update_schema_settings needs approval

What to ask Codex

Prompt 1

Use the storeseo MCP server to list my JSON-LD schema types and say which are enabled. Do not call any update tool.

Prompt 2

Read my local business schema settings, list the empty fields and ask me for them. After my yes, save the full object and enable the type.

Prompt 3

Enable product schema through StoreSEO, then list the types again and write both lists to schema-before-after.md.

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.

storeseo_list_schema_typesstoreseo_get_schema_settingsstoreseo_update_schema_settings

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 Codex 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 Codex

Codex waits 60 seconds for a tool by default, which is plenty for the schema tools, so the usual timeout advice for generation does not apply here. The setting that matters is the server's approval mode: use writes or prompt so Codex stops before storeseo_update_schema_settings, and avoid approve, because then no client prompt stands between the agent and a change to your live storefront markup.

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

Which Codex approval mode suits StoreSEO schema changes?

Writes mode suits it well, because Codex runs the read-only list and get tools without asking and prompts before storeseo_update_schema_settings. Prompt mode asks for every call, and approve mode skips the prompts entirely.

Does the Codex IDE extension see the same StoreSEO server as the CLI?

Yes. The CLI, the IDE extension and the ChatGPT desktop app share config.toml, so a storeseo server added once is available in each of them, including its approval settings.

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.