Function Scenario Guide

How to Translate Shopify Structured Data (Schema)

How to translate Shopify structured data (schema) so Product, FAQ, and Breadcrumb markup stays consistent with the visible page language and keeps earning rich results in every market.

AudienceShopify merchants and developers localizing JSON-LD schema for multilingual stores

TopicStructured Data (Schema)

Year2026

Summary

A practical workflow for localizing Shopify structured data so your schema values match each page's language, currency, and product info — protecting rich results across markets.

Product price, review stars, and breadcrumb snippets come from structured data — untranslated schema means shoppers see a source-language snippet in their own market.

Google expects JSON-LD to describe the page it sits on. When the page is in German and the schema is in English, the markup looks wrong and rich results can be dropped.

priceCurrency and availability are schema fields — if they are not localized with the price, your product rich results show the wrong currency or out-of-stock status.

Install Ciwi Talk to us

Why it matters

Why this translation scenario deserves its own workflow

Start by explaining why this Shopify surface matters before moving into scope, errors, and rollout method.

This scenario is not just about translating a few strings. It usually shapes whether shoppers understand the page, trust the storefront, and continue far enough to convert.

A practical workflow for localizing Shopify structured data so your schema values match each page's language, currency, and product info — protecting rich results across markets.

How to translate Shopify structured data (schema) so Product, FAQ, and Breadcrumb markup stays consistent with the visible page language and keeps earning rich results in every market.

Schema powers your rich results, not just the page copy

Product price, review stars, and breadcrumb snippets come from structured data — untranslated schema means shoppers see a source-language snippet in their own market.

Schema values must match the visible page language

Google expects JSON-LD to describe the page it sits on. When the page is in German and the schema is in English, the markup looks wrong and rich results can be dropped.

Currency and offer data are part of localization too

priceCurrency and availability are schema fields — if they are not localized with the price, your product rich results show the wrong currency or out-of-stock status.

Translation scope

What should you translate first in this scenario?

Prioritize the fields and surfaces that customers actually see, that shape conversion, and that influence SEO.

The translation scope should follow the customer journey, not just the Shopify field list. Start with the surfaces that affect understanding and conversion first, then expand into supporting modules.

Critical layer: Product name & description in JSON-LD, priceCurrency & offer price, aggregateRating / review text, and Breadcrumb list labels.

Important layer: FAQPage question & answer text and Organization name & address.

CriticalPriority: High

Product name & description in JSON-LD
priceCurrency & offer price
aggregateRating / review text
Breadcrumb list labels

ImportantPriority: Medium

FAQPage question & answer text
Organization name & address

OptionalPriority: Lower

HowTo / Article structured data
Event or LocalBusiness schema

Mistakes

What goes wrong most often here?

Focus on the issues that break UX, hurt SEO, or reduce conversion, not just language quality in isolation.

These mistakes matter because they do more than create awkward language. They make the experience feel unreliable, disconnect the workflow, or quietly reduce SEO and conversion.

Serving one static schema block to all marketsHigh

Wrong example: A single English JSON-LD Product block reused across German, French, and Japanese pages.

Better approach: Generate schema per locale so values match the page language and market currency.

Business impact: Rich results show wrong-language data or are dropped entirely.

Forgetting currency and offer fieldsHigh

Wrong example: Translating the product name in schema but leaving priceCurrency as USD for a EUR market.

Better approach: Localize priceCurrency, price, and availability alongside the product values.

Business impact: Product snippets display the wrong currency, eroding trust and clicks.

Breaking JSON-LD with manual editsMedium

Wrong example: Hand-editing schema and leaving an unescaped quote or trailing comma that invalidates the block.

Better approach: Use a translation app or generated schema, then validate with a schema tester.

Business impact: Invalid markup that search engines ignore entirely.

Leaving FAQ schema in the source languageMedium

Wrong example: Translating the visible FAQ but leaving the FAQPage schema questions in English.

Better approach: Mirror every translated question and answer in the FAQPage structured data.

Business impact: FAQ rich results show untranslated text and may be flagged as mismatched.

Workflow options

Which setup fits this scenario best?

Help buyers decide between manual handling, translation apps, and custom development.

There is no single best setup for every team. The right choice is the one your team can maintain consistently as content changes and more markets are added.

Manual translation (in-house or freelancer) / Shopify translation app (Translate & Adapt / Ciwi) / Custom build with the Shopify API

Manual translation (in-house or freelancer)

Advantage

Full control over every JSON-LD value
Best for a handful of high-value product or FAQ pages
No tooling required for small changes

Limitation

Error-prone when editing raw JSON-LD by hand
Slow to keep in sync with product changes
Easy to break schema with a single typo

Shopify translation app (Translate & Adapt / Ciwi)

Advantage

Localizes schema values alongside page copy in bulk
Keeps Product and FAQ schema in sync with translations
Handles currency and locale-aware offer fields

Limitation

Recurring subscription cost
May not cover every custom schema type
Still needs a validation pass with a schema tester

Custom build with the Shopify API

Advantage

Full control over schema generation in Liquid or API
Can inject locale-aware JSON-LD per market
Integrates with your headless or SEO pipeline

Limitation

Requires development resources
Ongoing maintenance as schema.org evolves
Slower to launch than an app

Checklist

What should you verify before launch?

Turn the rollout into a practical execution checklist so QA is easier and nothing important gets missed.

If you are ready to publish this scenario, treat the steps below as one release checklist instead of a few disconnected settings.

Audit which schema types your store actually emits (Product, FAQPage, BreadcrumbList, Organization).
Map every user-visible schema value to the translated string it should mirror on each locale.
Localize the product name and description in JSON-LD to match the translated page copy.
Update priceCurrency and the offer price to each market's currency and formatting.
Translate FAQPage and review text in the same pass as the visible content.
Generate the schema per locale — never serve one static JSON-LD block to every market.
Validate each locale's markup with Google's Rich Results Test or Schema.org validator.
Re-check schema after any product or price update so markup and page stay in sync.

Ciwi

What Ciwi helps automate here

Translate product capabilities into workflow outcomes users can actually understand and act on.

If you want this scenario to become an ongoing workflow instead of a one-time cleanup, these Ciwi capabilities are the parts that usually help most.

Localize JSON-LD values in sync with page copy
Currency- and locale-aware offer fields
Bulk Product and FAQPage schema translation
Validate markup before it goes live

Install Ciwi Talk to us

Next topics

What should you read next?

These related topics help build a more complete Shopify localization workflow after this scenario.

Once this page is handled, the next step is usually a cluster of adjacent Shopify surfaces. These related topics help turn one translated page into a fuller multilingual workflow.

How to Translate Shopify Meta Titles & Descriptions

Keep metadata consistent with your localized schema values.

How to Translate Shopify Product Descriptions

Align the Product schema with the translated description it describes.

How to Translate Shopify Sitemap

Ensure search engines crawl every localized, schema-annotated page.

FAQ

Frequently asked questions

Cover the most common execution questions users ask when working through this scenario.

Does structured data actually need translating?

Yes, if it contains user-visible values like product names, descriptions, prices, or FAQ text. Schema should mirror the page it sits on — a German page with English JSON-LD looks mismatched to Google and can lose rich results.

How do I localize priceCurrency in schema?

Set priceCurrency to the ISO code of the market's currency (for example EUR for Germany) and provide the offer price in that currency. Keep availability in sync with the market's stock.

Will translating schema break my rich results?

Only if the markup becomes invalid. Generate schema per locale and validate each version with Google's Rich Results Test — valid, localized markup preserves and often improves your snippets.

Next step

Ready to operationalize this workflow?

Start with the Shopify surfaces that affect UX and conversion most, then scale the workflow into more markets and content types.

Install Ciwi Talk to us