Product JSON-LD · MyCashflow
Add product JSON-LD to MyCashflow (for developers and for your AI agent)
The exact, verified way to put AI-search JSON-LD on a MyCashflow 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.
MyCashflow store templates are edited over FTP (the REST API is data-only). FTP/API needs the Advanced plan or higher.
Connect with the official mycashflow-sync CLI (or SFTP), edit the product template to emit the `<script type="application/ld+json">`.
For multiple languages, MyCashflow uses per-language templates — emit each language's JSON-LD in its template. Sync the template back.
- Verify
- View source per language URL: application/ld+json present server-side.
- Multilingual
- MyCashflow uses per-language templates — each language emits its own JSON-LD.
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 MyCashflow 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:
MyCashflow FTP/SFTP credentials (Advanced+ plan) and the mycashflow-sync CLI.
TASK:
1. Connect with mycashflow-sync (or SFTP) and pull the templates.
2. Edit the product template to output the JSON-LD <script>.
3. For each language, put that language's JSON-LD in its per-language template.
4. Sync back, verify the rendered source, then have the human publish.
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: MyCashflow. 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 MyCashflow 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.