Product data language in Merchant Center: page and checkout
Your product data, product pages and checkout must use one language for each data source, or the products can be disapproved. Translate the whole path a buyer walks, not just the menu. A translated homepage over an untranslated checkout is still an untranslated checkout.
You run this check yourself
Our scanner can’t see inside your Google accounts, so this one’s on you. Work through the checklist below without running a scan.
Why this matters
Google's checkout requirements are direct about this: “You must use the same language in your product data source and throughout the checkout process to avoid product disapproval.” The landing page requirements say the same about the product page, “Show the same language as your product data”, with an example that settles the bilingual question: if you target Canada, “you shouldn't submit your product data in English and show your landing page in French.”
What has to be translated is spelled out on Google's “Supported languages and currencies” page: “Elements of the landing page and checkout process that enable the user to navigate and make an informed purchase decision must be in the same language as your data source language.” The page is just as clear about the product record itself. When key elements such as title, description and variant information don't match the data source language, products “might have limited performance”, and “If the majority of your product data doesn't match the data source language your products may be disapproved.”
The usual culprit is a half-translated store: a translation app that covers product pages but not the cart, the returns page or the terms, or a checkout that falls back to the platform’s default language. More than one language is fine. The same page says “You may upload a data source in any supported language”, and some countries support several. The rule is one language per data source, carried from listing to payment. Selling abroad? Target country settings and currency in Merchant Center cover the rest of the setup.
Manual check: StoreVerifier does not see your product data or its language setting, so confirming the data source language is yours. The free scan flags policy and other store pages that read in a different language from your homepage, which is where an unfinished translation usually shows. The language check sits with the rest on the misrepresentation checker.
Typical evidence
One feed, wrong language for the market
The German feed was cloned from the UK feed and never translated. Product titles are English, pages have lang='en', but the GMC feed is configured for German. Three mismatches.
The public signals this check looks for:
Product data and product pages are in English, but the returns page and the checkout load …
Product data and product pages are in English, but the returns page and the checkout load in German because the translation app skipped them.
Titles and descriptions are translated, while variant names such as sizes and colours stay…
Titles and descriptions are translated, while variant names such as sizes and colours stay in the source language.
The store switches language by visitor location, so a product link opens in a language the…
The store switches language by visitor location, so a product link opens in a language the product data does not use.
Checkout buttons, delivery options or error messages fall back to the platform’s default l…
Checkout buttons, delivery options or error messages fall back to the platform’s default language.
One data source targets two countries with different languages, and only one of them match…
One data source targets two countries with different languages, and only one of them matches the pages.
What it looks like once it is right
The same shop extends the translation to cart, checkout and every policy page, and adds a Dutch data source linked to its /nl/ pages. Each language now runs from listing to payment on its own.
Common mistakes
Common mistake
Self-check steps
One feed per market — the correct multi-market architecture
Each language market has its own GMC account (or sub-account), its own feed file in the correct language, and product pages with the correct HTML lang attribute. No cross-contamination.
Questions merchants ask
Can my store use more than one language for Google Shopping?
Yes. Google's languages page says you may upload a data source in any supported language, and some countries support several. Each data source then needs product pages and a checkout in its own language, so a French data source should link to French pages.
Does the checkout have to be in the same language as my product data?
Yes. Google's checkout requirements say you must use the same language in your product data source and throughout the checkout process to avoid product disapproval. That covers the elements a shopper needs to navigate and make an informed purchase decision.
What happens if only some of my titles are translated?
Google says products whose key elements, such as title, description and variant information, don't match the data source language might have limited performance, and that if the majority of your product data doesn't match, the products may be disapproved. Translate the whole record, variant names included.
Remediation
Risk signal
Similar cases
Sources
Last reviewed 23 Sep 2026.
That is one issue. The library documents 134.
The free scan lists what it finds on your store. The paid report adds the affected pages, captured evidence and step-by-step fixes. Start free, with no account needed.