Write JSON-LDMagento / Adobe Commerce

Product JSON-LD · Magento / Adobe Commerce

Add product JSON-LD to Magento / Adobe Commerce (for developers and for your AI agent)

The exact, verified way to put AI-search JSON-LD on a Magento / Adobe Commerce 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.

developer guide · stepsNeeds server access

Auth is OAuth 1.0a (integration token; admin bearer tokens expire in 4h and require 2FA). Create an Integration for a stable token.

Fastest server-side path: create/update a CMS Block via REST (POST /V1/cmsBlock) whose content includes the JSON-LD `<script>`, then PLACE that block on the product page via a widget or layout XML (a REST-created block is not shown until placed); or edit the theme .phtml over SSH.

Per store-view: scope via the store code in the route (/rest/<store_code>/V1/...) and emit that store-view's JSON-LD.

verification and languages

Verify: View source on the product URL per store-view: application/ld+json present.
Multilingual: Per store-view via the store code in the REST route; emit that view's JSON-LD.

Diagram: how to add product JSON-LD to Magento / Adobe Commerce for AI search — Create an Integration (OAuth 1.0a token); JSON-LD as a CMS Block (REST) OR .phtml (SSH); Per store-view (store_code); Verify, publish — The Magento / Adobe Commerce JSON-LD flow at a glance (illustrative diagram).

Agent prompt

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.

runbook · magento-json-ld.md · en1 217 merkkiä

You are helping me add AI-search JSON-LD to ONE product on my Magento / Adobe Commerce 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 Magento/Adobe Commerce Integration token (OAuth 1.0a); or SSH + bin/magento for theme .phtml edits.

TASK:
  1. Create an Integration and use its OAuth 1.0a token.
  2. POST the JSON-LD as a CMS Block (/V1/cmsBlock) and render it on the product page — OR edit the theme .phtml over SSH.
  3. Scope per store-view (/rest/<store_code>/V1/...) for multilingual, verify the source, then have the human publish.

JSON-LD to inject:
{}

Writes only after your approval. The runbook forces the agent to back up before writing, work on an unpublished copy and verify the result. Publishing stays with you.

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.

install · magento-json-ld.md0 / 1 täytetty542 merkkiä

I already have a finished product JSON-LD from Outcite. Do NOT generate a new one and do NOT change its contents.

Platform: Magento / Adobe Commerce. 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:
---

Installs, doesn't invent. The prompt forbids the agent from altering field values. With several locales it forces the platform's own translation mechanism instead of duplicated code.

Don't have your JSON-LD yet? Generate it with Outcite — it outputs a per-language block for every language version.

Rather not do it yourself?Free AI-visibility audit

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 Fix

We build and maintain the whole data layer.

Rather not do it yourself?Agentic commerce

The customer's own AI buys directly from your store.

Rather not do it yourself?Learn the whole system (book + course)

Frequently asked

01What is the prompt to connect Claude to Magento / Adobe Commerce to add product JSON-LD?

Use the runbook on this page — paste it into Claude. It connects to your Magento / Adobe Commerce store with your own credentials and adds the schema.org JSON-LD, with backup, preview, verification and your approval before publishing.

02How do I connect ChatGPT to my Magento / Adobe Commerce store to add schema.org JSON-LD?

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.

03Can an AI agent add product JSON-LD to Magento / Adobe Commerce for AI search (ChatGPT, Perplexity, Google AI)?

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.

Sources

01: Adobe Commerce — OAuth authentication (integration tokens)
02: Adobe Commerce — admin token (4h, 2FA)
03: Google — generate structured data with JavaScript (Google renders JS)
04: Independent AI-crawler behaviour testing (JS execution)

next · 30 seconds

What does your store look like to AI?

A free audit. No signup, works on every platform.

Book a call