Product JSON-LD · BigCommerce
Add product JSON-LD to BigCommerce (for developers and for your AI agent)
The exact, verified way to put AI-search JSON-LD on a BigCommerce product page — server-side, and multilingual. Do it yourself with the steps below, hand the runbook to your AI agent, or let Store Operators do it for you.
Put the JSON-LD server-side in the Stencil theme (NOT the Scripts API — injected scripts run client-side, which AI crawlers may not execute).
Create a store-level API Account (Advanced Settings → API Accounts): scopes Content=modify, Products=read. The access token is static and non-expiring.
Edit the Stencil theme's product template (e.g. via the Stencil CLI, the Themes API, or the control panel), adding the `<script type="application/ld+json">`, then apply the theme.
- Verify
- View source on the product URL: application/ld+json present server-side (not only after JS).
- Multilingual
- Multilingual: BigCommerce Translations (GraphQL, channel + locale); emit the matching locale's JSON-LD per storefront.
Hand this to your own agent
This runbook adds product JSON-LD to one product at a time. It backs up first, works on an unpublished copy, verifies the result and publishes nothing without you.
You are helping me add AI-search JSON-LD to ONE product on my BigCommerce store, safely.
SAFETY (follow exactly, in order):
1. Back up first: duplicate the current theme (or export it) BEFORE any write. No exceptions.
2. Work on an UNPUBLISHED copy / preview — never edit the live theme directly.
3. Use a least-privilege token: only the scopes the task needs.
4. After each change, VERIFY (fetch the page, confirm the JSON-LD renders and is valid).
5. Do NOT publish. Show the human the preview and the verification, and let the human approve the publish.
6. Keep the rollback ready: if anything looks wrong, restore the backed-up theme.
CONTEXT: Product URL: https://your-store.example/product/your-product. Store locales: your primary language.
ACCESS:
A store-level API Account token (X-Auth-Token; static, non-expiring) with Content=modify, Products=read; plus Stencil CLI access to the theme.
TASK:
1. Pull the active theme: `stencil pull`.
2. Add the JSON-LD <script> to the product template (templates/pages/product.html or a component).
3. Push it back with `stencil push` to an unpublished variation, verify the rendered source, then have the human publish.
4. For multilingual, emit the matching locale's JSON-LD (BigCommerce Translations GraphQL API).
JSON-LD to inject:
{}The runbook is in English on purpose — agent prompts work most reliably in English. You can still talk to the agent in your own language.
Already have your JSON-LD?
Outcite outputs a finished, per-language JSON-LD. Then the agent doesn't invent fields, it only installs the blocks correctly. Tell it how many language versions you have and the prompt adapts.
I already have a finished product JSON-LD from Outcite. Do NOT generate a new one and do NOT change its contents. Platform: BigCommerce. Locales: I have one JSON-LD block. Do this: 1. Install it so it renders server-side on the product page. 2. Do not alter any field values. 3. Verify the rendered page and show me the JSON-LD it outputs. SAFETY: back up before any write, work on an unpublished copy, publish nothing without my approval, and tell me the rollback. Paste the Outcite blocks below this line: ---
Don't have your JSON-LD yet? Generate it with Outcite — it outputs a per-language block for every language version.
See where your store is invisible to AI.
Rather not do it yourself?Generate the JSON-LD now (Outcite)A ready, citable page + schema, per run.
Rather not do it yourself?Done for you: AI Visibility FixWe build and maintain the whole data layer.
Rather not do it yourself?Agentic commerceThe customer's own AI buys directly from your store.
Rather not do it yourself?Learn the whole system (book + course)Use the runbook on this page — paste it into Claude. It connects to your BigCommerce store with your own credentials and adds the schema.org JSON-LD, with backup, preview, verification and your approval before publishing.
The same runbook works for ChatGPT (or any capable AI agent): it authenticates to your store and injects the JSON-LD server-side, safely, and stops for your approval before publishing.
Yes — server-side (client-side-only JavaScript is not reliably seen by AI crawlers). Do it with the agent runbook here, hand it to a developer, or have Store Operators do it for you.