Schema Markup for International Shopify Stores

Most Shopify merchants who translate their store stop at what customers can see. Google reads something else entirely.

You added a translation app. Your product titles, descriptions, and checkout now appear in French, German, Arabic, or Japanese. Customers in those languages can find your store, understand your products, and make purchases. That part works.

What often does not work is the data layer Google reads when deciding what to show in search results. That layer, your schema markup, may still use your primary language. And when it does, your translated pages can miss out on rich results, such as product listings with prices, ratings, and availability.

This is the multilingual schema gap. It is common, easy to overlook, and important to fix.

What Schema Markup Actually Does #

Schema markup is structured data added to your store's pages as JSON-LD code. It tells Google not only what your page says, but also what the page means. A product page with correct schema can appear in search with a star rating, price, stock status, and shipping information shown directly below the title, before the user clicks.

Google calls these rich results. They help listings stand out and can improve click-through rates. They are powered by the schema data your store provides.

The important point: schema is separate from your visible page content. Your translation app changes what visitors see and read. Schema is what search engines read. These are two different layers, and most translation workflows only update one of them.

Why Translation Apps Do Not Fix This #

Translation apps such as Weglot, Langify, and Shopify's native translation layer work by showing visible page content in the selected language. Product names, descriptions, navigation labels, checkout text, and other content can be served in the languages supported by the store.

Schema markup is not part of this visible content. It sits in the page's <head> or in a script block in the background. Most translation apps do not update it. Some offer partial support for basic fields, but shipping data, return policies, and offer-level details are often missed.

The result: a French-speaking shopper may find your French-translated product page, while Google's index still reads English schema from the same URL. Rich results may not appear, or they may show incorrect currency, language, or availability for that region.

What Google Looks at for Multilingual Rich Results #

Google's documentation on multilingual schema recommends the following for stores serving multiple languages:

• Serve schema in each page's language. Each language version of a page should have schema served in that language. The name, description, and offers fields in your Product schema should match the language of the page, rather than your default store language.
• Set the inLanguage field. It should be set on content schemas to indicate which language the structured data represents.
• Localize shipping and return policies. These should reflect the destination region. A German buyer searching Google Germany expects shipping information relevant to Germany, not US shipping rates stored in your default schema.

These are not edge-case requirements. They can affect whether rich results appear, how Google understands your translated pages, and how international visitors interact with your store from search.

The Webrex Approach: Schema Served Per Language #

Webrex SEO Schema JSON-LD handles this automatically through its multi-language schema feature.

When you add a language to your Webrex settings, the app does not simply copy your existing schema and translate it. It generates schema for that language version of your store independently, using product data, offer details, and policy information relevant to that language and region.

Here is what that means in practice:

Product schema in the correct language. When a French customer visits your French product page, the schema Google reads for that URL is in French. The name, description, and offer fields are served in the page's language rather than your store's default language.

Country-specific shipping schema. Webrex allows you to configure shipping details for different regions. When a language is connected to a region, such as German for Germany or French for France or Canada, the shipping schema reflects that region's rates and estimates. Google can then show more relevant shipping information in rich results for those regions.

Return policy schema per language. Return policies can vary by region because of local consumer protection laws. Webrex serves return policy schema in the correct language and with region-appropriate terms, so Google's rich results for those pages can show accurate policy information.

All of this happens without manually editing JSON-LD. You add a language, and Webrex handles the rest.

What This Fixes in Search #

The gap between what your translation app covers and what Webrex covers can become visible in Google Search Console and in actual search results.

Before multi-language schema: Translated pages may show no rich results, or rich results may appear in your primary language even when the search query and user's region are different. Google may also have difficulty understanding translated versions when the schema signals do not match the page's language.

After multi-language schema: Each language version of your product pages has its own schema, in the correct language, with region-specific shipping and policy data. Google can better understand these pages. Rich results can then appear for searches in those languages with the correct prices, currency, and availability.

The traffic implication is direct. Rich results can improve click-through rates for product searches. When they appear for international searches in the right language, with shipping information relevant to buyers in that region, organic traffic can perform better.

The Common Mistake Merchants Make #

Most merchants who discover this issue assume their translation app has already handled it. They check the front end of their store, see the content in the correct language, and consider the job complete.

The front end is not where Google gets all of its information. Run a Google Rich Results Test on a translated product URL from your store. In many cases, if you have not specifically configured schema to serve per language, you may still see schema in your default language, even when testing a different language version of the URL.

This is not necessarily a translation app failure. Translation apps solve a different problem. They are designed to serve human readers. Schema is designed to help search engines understand your content. Both layers need to be handled.

How to Set Up Multi-language Schema in Webrex #

Getting multi-language schema active in Webrex is straightforward.

In your Webrex app dashboard, go to the Multi-language Settings section. From there, you can add each language supported by your store. For each language, Webrex uses the relevant product data and generates schema in that language for pages where that language is active.

For shipping and return policy details, you can configure region-specific values for each language. These values are added to the schema served on translated pages, helping rich results display accurate and localized information.

Once enabled, you can verify the setup using Google's Rich Results Test by testing the translated version of any product URL. You should see schema in the correct language along with the correct offer and shipping information.

Why This Matters More in 2026 #

International ecommerce competition has increased significantly. Merchants running multilingual stores now compete not only with domestic sellers in each language market, but also with established local retailers that have years of indexed, language-specific structured data.

Schema can help close this gap. A store that provides correct multilingual schema gives Google the information it needs to understand and display rich results for each language. This can become more valuable over time as those pages gain impressions, clicks, and other search signals.

It is also becoming more relevant for AI search. Generative search experiences such as Google's AI Overviews, Perplexity, and similar platforms can use product and entity information from structured data. A product page with schema in the correct language provides clearer signals for searches made in that language.