Multilingual SEO

How to Translate Shopify Store Search Ads and Google Shopping Campaigns for International Markets

Running paid search in a market where your product titles, landing pages, and ad copy are all in English while the shopper searches in French or German isn't just a conversion problem — it's a Quality Score problem, an impression-share problem, and a wasted-budget problem, all at once. Getting Shopify Google Shopping translation right means aligning three separate systems — your Merchant Center feed, your ad copy, and your on-site content — so they all speak the same language to the same shopper.

This guide walks through each layer with concrete steps.


Why the Feed Comes First — and What "Translated" Actually Means in Merchant Center

Google Shopping ads are driven by your product feed, not your ad copy. If your feed titles, descriptions, and product types are in English, Google will serve your ads primarily to English-language queries regardless of which target country you've selected. Selecting "France" in Merchant Center does not translate your feed — it changes where your ads appear, not what language they're in.

For each target locale, Merchant Center needs feed attributes in the local language. The core attributes that must be localized are:

  • title — the most important signal for query matching; a 150-character field where the first 70 characters carry the most weight
  • description — up to 5,000 characters; affects relevance for longer-tail queries
  • product_type — your internal taxonomy; translate it to match how shoppers in that market categorize products
  • google_product_category — taxonomy IDs are universal and do not need translation, but subcategory strings do if you're submitting them as text
  • shipping and tax — these must match the target country's rules, not just be translated

Attributes that don't need translation: id, gtin, mpn, condition, availability, price (localize the currency, not the text), image_link.

Two Practical Ways to Deliver Localized Feeds in Merchant Center

Option 1 — Supplemental feed per locale. Create a primary feed in your default language, then use a supplemental feed to override title, description, and product_type for each target country. In Merchant Center: go to Products → Feeds → Add supplemental feed, upload a sheet or connect a URL, and use feed rules to apply overrides by target_country. This keeps your primary feed clean and lets you manage translations separately without touching the main data source.

Option 2 — Separate primary feed per locale. Create a dedicated primary feed for each country target (e.g., one for FR, one for DE, one for NL). This gives you full control over every attribute per locale but multiplies maintenance overhead as your catalog grows. It's practical for stores with fewer than 500 SKUs or where locale-specific pricing differs significantly.

Feed rules (under Products → Feeds → [your feed] → Feed rules) let you apply transformations automatically — for example, prepending a brand name to all titles, or mapping your internal product_type values to localized equivalents. Use them to enforce consistency before a single impression is served.

Shopify's native Google channel syncs your product catalog to Merchant Center, but as of this writing it submits data in your store's primary language. If you've set up localized storefronts using Shopify Markets and have translated your products, those translated fields can be included in your feed — but you need to verify this is actually happening in Merchant Center's Diagnostics tab, not assume it. Check Products → Diagnostics → Item issues filtered by country to catch missing or disapproved localized attributes early.


Translating Product Titles for Shopping Ads — Not Just Word-for-Word

A translated title is not automatically an optimized one. Keyword order matters differently across languages — in German, compound nouns like "Lederhandtasche" often outperform "Handtasche aus Leder" because that's the term shoppers type. In French, adjective placement affects natural readability, which in turn affects click-through rate.

The practical process:

  1. Pull your highest-spending English product titles from your Shopping campaign's Search terms report — these show you the exact queries triggering your ads.
  2. Do multilingual keyword research for each title's product category in the target locale. Look at local Google Suggest, competitor product pages in that language, and your own Search Console data from that country (see how to use Search Console to monitor multilingual performance).
  3. Reconstruct the title using the local keyword order, not a literal translation. Tools like DeepL and AI models are good at fluency but may miss commercial keyword intent — a step that AI translation comparison data makes clear.
  4. Keep brand terms, model numbers, and material descriptors in their internationally recognized form unless the local market uses a different convention.

Consistency between your feed titles and your on-page product titles matters. If your Shopping ad says "Sac à main en cuir marron" but your product page headline says "Sac cuir brun," Google notices the mismatch and shoppers do too. Maintaining a localized glossary of core brand and product terms — and applying it across both feeds and storefront — prevents this drift.


Search Ads: Matching Ad Copy to Localized Landing Pages

For text-based search campaigns (Performance Max, Standard Shopping's "search themes," or traditional Search campaigns running alongside Shopping), ad relevance is evaluated in part by how well the ad's messaging matches the landing page it points to.

This is not about a numeric Quality Score threshold — Google's ad relevance signals are more nuanced than a single number and apply differently across campaign types. What's consistently true: if your ad headline is in German but your landing page is in English, expect lower conversion rates and worse auction outcomes regardless of how QS is reported.

The fix is straightforward but requires all three layers to move together:

For Performance Max campaigns targeting multiple countries, use separate asset groups per locale rather than one global asset group. This lets you write ad headlines and descriptions in the local language and point to the localized landing page URL — typically a Shopify Markets subfolder like /fr/ or /de/.

Don't overlook promotional content. If you're running a campaign tied to a seasonal discount, your ad copy, your banner, and your discount terms all need to match — in the same language. Translating promotional content consistently prevents the jarring experience of a localized ad leading to an English-only offer page.


Connecting Feed Translation to Your Shopify Storefront

Your Merchant Center feed should reflect what's actually on your storefront. If Shopify's translated product content isn't flowing into your feed correctly, you end up with a localized Shopping ad pointing to a product page that loads in the wrong language — or worse, throws a 404 because the URL structure doesn't match.

Shopify Markets uses subfolders by default (/fr/products/...), which is generally the preferred structure for multilingual SEO (the subfolders vs subdomains debate is settled in most cases). Your feed's link attribute for French products should point to the /fr/ version of the product URL, not the default English URL. Verify this in Merchant Center's item-level data: click any approved product and check the link value in its attributes.

If your product content isn't translated yet, that's the prerequisite. Bulk-translating your product catalog before launching paid campaigns in a new locale saves you from serving ads into a storefront that isn't ready. StoreLingo translates product titles, descriptions, and SEO meta fields directly within Shopify's native translation layer — so translated content flows through to your Shopify Markets URLs without any custom feed work on your part.

Add StoreLingo on the Shopify App Store →

Beyond product pages, make sure image alt text is also localized — it contributes to both organic and Shopping relevance signals, as covered in translating Shopify image alt text for international SEO. And if you're using structured data, ensure your schema markup is also localized so Google's rich result parsing aligns with your Shopping feed data.


Monitoring What's Working After Launch

Once your localized campaigns are live, watch these signals weekly:

  • Merchant Center Diagnostics — filter by country to catch feed disapprovals specific to a locale
  • Search terms report by country target — identifies queries you're matching that are untranslated or off-intent
  • Impression share by locale — a drop in one market often points to a feed quality issue, not a bid issue
  • Conversion rate by country — a significant gap between your English baseline and a localized market often points to a landing page or checkout experience problem, not the ad itself

Search Console's performance data filtered by country complements your paid data — it shows whether your translated organic pages are also building relevance for the queries your Shopping ads are targeting.


FAQ

Do I need a separate Google Merchant Center account for each country? No. A single Merchant Center account supports multiple target countries. You manage locale-specific feeds (either supplemental or separate primary feeds) within the same account, and assign each feed a target country when you set it up.

Can I use AI translation for my Shopping feed titles, or do I need a human translator? AI translation produces fluent, commercially usable output for feed titles and descriptions in most major European and Asian languages — but it works best when you review the output against actual search term data in that locale and adjust for keyword order and local terminology. Human review adds value for nuanced brand voice; for high-volume catalog translation where speed matters, AI translation with a glossary and a spot-check process is a practical and well-documented approach.

What happens if my Shopify product content is updated after my feed is already submitted? Merchant Center re-crawls feed URLs or re-ingests uploaded files on a schedule — typically every few days for crawled feeds, or immediately for manually uploaded files. If you auto-publish product translations in Shopify when content changes, your feed will eventually reflect those updates, but there's a lag. For time-sensitive changes like price updates or stock status, use Merchant Center's Content API or the Google channel in Shopify to push updates on demand rather than waiting for the next crawl cycle.

Choose from 47 languages

StoreLingo translates products, collections, pages and articles with AI — review and approve by default. On paid plans from Starter, auto-translate is off by default and publishes new or updated products automatically. Keep your brand terms consistent.

Add to Shopify →