Function Scenario Guide

What Shopify Translate & Adapt Can't Translate

The content Shopify's free translation app leaves in your source language: product images, tags, collection filters, metafields and third-party app text.

Marcus Chen
Multilingual SEO Specialist

Focuses on multilingual search intent and hreflang architecture.

AudienceShopify merchants localizing on a limited budget
TopicContent Coverage
Year2026
Summary

Know which parts of the storefront the free app simply doesn't reach, so a full-looking translation doesn't ship with untranslated gaps.

Translate & Adapt works on Shopify's translatable resource types. Anything rendered by a theme section, an app block or an image doesn't exist for it.

Metafields can hold translations, yet the app's search doesn't return METAFIELD results. In practice you can't review or edit them in the interface — only through CSV export.

Tags are excluded, and collection filters are excluded too. That's a problem precisely where shoppers narrow a catalog: filter labels stay in the source language.

Why it matters

Why this translation scenario deserves its own workflow

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.

The app translates resources, not screenshots

Translate & Adapt works on Shopify's translatable resource types. Anything rendered by a theme section, an app block or an image doesn't exist for it.

Metafields are translatable but not searchable

Metafields can hold translations, yet the app's search doesn't return METAFIELD results. In practice you can't review or edit them in the interface — only through CSV export.

Tags and filters are structural, not editorial

Tags are excluded, and collection filters are excluded too. That's a problem precisely where shoppers narrow a catalog: filter labels stay in the source language.

Translation scope

What should you translate first in this scenario?

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 images, Tags, Collection filters, Forms built with the Shopify Forms app, Manual payment method instructions, and Third-party app content that isn't a Shopify translatable resource.

Important layer: METAFIELD values, EMAIL_TEMPLATE content, SHOP_POLICY entries, FILTER resources, and SELLING_PLAN and PAYMENT_GATEWAY strings.

Never translated by the appPriority: High
  • Product images
  • Tags
  • Collection filters
  • Forms built with the Shopify Forms app
  • Manual payment method instructions
  • Third-party app content that isn't a Shopify translatable resource
Translatable but not searchablePriority: Medium
  • METAFIELD values
  • EMAIL_TEMPLATE content
  • SHOP_POLICY entries
  • FILTER resources
  • SELLING_PLAN and PAYMENT_GATEWAY strings
Translated with caveatsPriority: Medium
  • URL handles: typed by hand per language, and the products segment never changes
  • Handles can't be customized per market
  • Legal policies need manual translation
Mistakes

What goes wrong most often here?

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.

Trusting the progress indicatorHigh

Wrong example: Shipping a market because Translate & Adapt shows every field complete.

Better approach: Walk the storefront in the target language and compare it with the source page by page.

Business impact: Buyers hit untranslated filters, image text and app widgets at the point of decision.

Assuming metafields are coveredHigh

Wrong example: Leaving sizing charts and spec tables in English because the products look translated.

Better approach: Metafields are translatable but don't show up in app search; handle them via CSV.

Business impact: The most technical, trust-building content stays in the wrong language.

Forgetting app-injected textMedium

Wrong example: Translating the theme but not the review widget under every product.

Better approach: Inventory the third-party apps that render text, then decide how each gets localized.

Business impact: A page that is 90% translated reads as unfinished where social proof matters most.

Translating URL handles without a redirect planMedium

Wrong example: Changing the slug and letting old localized URLs 404.

Better approach: Enter translated handles by hand before launch, and remember the products segment can't be translated.

Business impact: Lost rankings and broken inbound links in the market you just launched.

Workflow options

Which setup fits this scenario best?

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.

Native translation plus a targeted CSV pass / Theme-level patching for labels / A translation app that covers structured and app content

Native translation plus a targeted CSV pass

Advantage
  • Free
  • Reaches metafields and other resources the search skips
  • Keeps everything inside Shopify
Limitation
  • No review workflow for the CSV content
  • Re-running after catalog changes is manual
  • Still can't touch images, tags or app blocks

Theme-level patching for labels

Advantage
  • Fixes filter and section labels where the theme exposes locale keys
  • No extra app
Limitation
  • Requires theme editing
  • Breaks on updates or theme changes
  • Doesn't cover app-embedded text

A translation app that covers structured and app content

Advantage
  • Handles images, third-party app text and metafields in one place
  • Glossary keeps terms consistent
  • Continuous sync instead of manual passes
Limitation
  • Paid
  • Additional setup and migration
  • Needs review on high-traffic pages
Checklist

What should you verify before launch?

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

  • List every theme section and app block that renders customer-facing text, then mark which ones the app can't reach.
  • Search the app for metafields; if nothing returns, export a CSV instead of assuming they're covered.
  • Check your collection filter labels in a second language on the storefront, not in the admin.
  • Open a product page, a collection page and a checkout-adjacent page in the target language and compare them against the source.
  • Confirm which third-party apps inject text into the storefront: reviews, loyalty, chat, upsells, bundles.
  • Decide per gap whether to patch the theme, export a CSV, or move that content to an app that handles it.
  • Re-check the same list after any theme update or app install.
Ciwi

What Ciwi helps automate here

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.

  • Translates product metafields and metaobject entries that don't appear in the app's own search
  • Localizes product images and alt text alongside the surrounding copy
  • Covers third-party app content such as reviews, loyalty and chat widgets
  • Keeps filter and navigation labels consistent through a shared glossary
  • Flags untranslated content so gaps surface before a market goes live

See how Ciwi AI Translator handles this scenario →

Next topics

What should you read next?

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.

FAQ

Frequently asked questions

The questions that come up while doing the work, not before starting it.

Why won't Translate & Adapt translate my product images?

Product images are on Shopify's list of content types the app can't translate. Only text fields tied to translatable resources are covered, so text baked into an image stays in the source language.

What about metafields?

Metafields are a translatable resource type, but they're excluded from the app's search. You can't browse or edit them in the interface — the workable path is a CSV export and re-import.

Can I translate tags and collection filters?

Not with the app. Tags and collection filters are both unsupported content types, so filter labels stay in the source language unless your theme exposes them as locale strings.

Does it translate content injected by other apps?

Only if that content is a Shopify translatable resource or lives in a storefront locale file. Text rendered directly by a third-party app isn't reachable.

Are SEO fields translated?

Meta titles and descriptions for products, collections, pages and blog posts are translatable. What isn't: the products segment of a URL, per-market custom handles, and tags that feed filtered collection URLs.

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.