Translations usually go missing on Shopify for one of a few concrete reasons: the language was added but never published, the storefront has no way to switch languages, a specific resource type (like policies, filters, or app text) was never translated, or the source content changed after it was translated and never re-synced. To fix translation missing shopify problems, you work through these causes in order rather than re-translating everything blindly. Below is a diagnostic checklist that maps each symptom to its actual cause and fix.
The frustrating part is that Shopify translation is not one switch. It translates content type by type, and several categories are easy to miss. A store can look fully translated on product pages while the checkout, footer policies, and a reviews app still show the original language. That patchwork is almost always one of the six causes below.
Published July 2026.
First: Confirm the Language Is Actually Published
The most common reason a whole language looks missing is that it was added in Shopify Markets but never published. Adding a language enables the translation layer so you can enter translations, but it does not make that language visible to shoppers until you publish it.
How to check: Go to Settings, then Languages. Each language shows a status. If it says anything other than Published, shoppers cannot see it, no matter how much translated content sits behind it. Set the language to Published.
Related to this: even a published language is invisible if shoppers have no way to select it. Many themes do not include a language selector by default, or it sits hidden in the footer. If your translations exist and are published but nobody sees them, the storefront language switcher is likely missing from your theme.
The fix: In your theme editor, add the language selector block (most Online Store 2.0 themes offer one in the header or footer sections). If you are on Dawn or a Dawn-based theme, our guide to translating the Dawn theme walks through where the selector lives and how theme text gets translated. Once the selector is present and the language is published, shoppers can switch and the translated content appears.
Second: Find the Resource Type That Was Skipped
If most of your store is translated but specific areas are not, the issue is almost never the whole language. It is a single resource type that was never translated. Shopify groups translatable content into separate buckets, and it is common for one bucket to be left behind.
Watch for these commonly missed resource types:
- Store policies (refund, privacy, shipping, terms) are a separate content type and frequently stay in the source language.
- Filters and facets on collection pages, along with some form labels at checkout and in contact forms.
- Theme and section content such as button labels, section headings, and static blocks the theme author hardcoded. If only your buttons and labels look untranslated, this is usually why.
- Metafields, which power custom fields, specs, and many app-driven page sections. These are often untranslated because they require the metafield to be flagged as translatable first. Our metafield translation guide covers how to expose them.
- Third-party app text, like reviews, upsells, or subscription widgets. Many apps store their strings outside Shopify’s native translation system, so a translation app may not reach them at all. In those cases the app itself needs a translation setting.
The fix: Identify which bucket is untranslated, then translate that specific resource type. Do not re-run a full translation hoping it catches the gap. Note that Shopify-specific behavior varies by theme and by app, so app-owned text in particular may need to be handled inside that app’s own settings rather than through your translation layer.
Third: Check Whether the Source Content Changed
A translation that looks stuck is often not stuck. It is orphaned. When you edit the source-language version of a product, page, or collection after it was translated, the original translation stays attached to the old text. Some translation tools do not automatically re-sync when the source changes, so the storefront shows the outdated translation, or reverts to source, depending on the setup.
This is why a product you clearly translated last month can suddenly appear untranslated after you tweaked its description. The same applies to newly added products and collections: content created after your initial translation pass starts in the source language only and will not translate itself.
The fix: Re-translate anything you have edited since the last pass, and translate new products and collections as you add them. If you are doing this manually, keep a habit of translating right after publishing new content. This is exactly the gap that causes translations to slowly rot as a catalog grows.
Fourth: Rule Out Caching
If translated content is published and correct in the admin but still shows the original language to you specifically, suspect caching before anything else. Shopify’s CDN and your browser can both serve a stale copy of a page in the previous language.
The fix: Hard-refresh the page, clear your browser cache, and test in a private or incognito window. Try a different device or network too. If the translation appears correctly in a clean session, the content is fine and it was only a cached copy misleading you. For a broader walkthrough of publish, cache, and configuration issues, see our guide on what to do when Shopify translation is not working.
How LocaleFlow Prevents Missing Translations
Most missing-translation problems come from two habits: translating resource types unevenly, and letting new or edited content fall out of sync. LocaleFlow addresses both. It translates Shopify-native content across all your active languages, covering the resource types merchants commonly skip, and it auto-syncs so that new and edited content is picked up rather than left in the source language.
To set it up:
- Install LocaleFlow from the Shopify App Store and connect your store.
- Select your published languages from your Shopify Markets configuration so translation targets match what shoppers can actually switch to.
- Choose the resource types to translate (products, collections, theme and section content, policies, metafields, and more) so no bucket gets left behind.
- Run the translation across every selected language and resource type in one pass.
- Leave auto-sync on. When you add a product or edit source text, LocaleFlow picks up the change and translates it, so translations do not silently drift out of coverage as your catalog grows.
Auto-sync is the piece that keeps the fix from unraveling. Translating once is easy. Staying translated as you add products and edit descriptions is where most stores quietly slip back into a half-translated state.
Quick Diagnostic Recap
Work through these in order and the missing content almost always turns up:
- Language added but not published, so set it to Published.
- No language selector in the theme, so add the selector block.
- A resource type (policies, filters, forms, theme text, metafields, app strings) never translated, so translate that type specifically.
- Source content edited after translation, so re-sync or re-translate it.
- New products and collections not yet translated, so translate them as you add them.
- Stale CDN or browser cache, so hard-refresh and test in a private window.
Ready to close the gaps for good? Install LocaleFlow from the Shopify App Store and start translating today.
Written by Kwadwo Adu, Co-founder of LocaleFlow