A merchant recently asked a simple question that many multilingual Shopify stores run into: “How do I translate the breadcrumbs?” It sounds like one setting, but Shopify breadcrumb translation usually has two separate layers.
The first layer is the small, static breadcrumb labels such as Home, All products, Collections, Products, Search, Blog, News, Pages, and Articles. These are interface labels controlled by the breadcrumb setup.
The second layer is the actual store content inside the breadcrumb path: collection names, product titles, page titles, blog titles, and article titles. Those are Shopify resources, so they need to be translated in Shopify through Shopify Translate & Adapt, CSV translations, or another translation app that writes translations into Shopify.
This distinction matters because a breadcrumb like Home > Packaging > Paper Bags is not made from one single translation source. Home may be a default app label, while Packaging and Paper Bags are collection titles pulled from Shopify. A correct multilingual setup needs both layers to be handled properly.
The Short Answer
For stores using Breadcrumbs & Categories, the translation logic is straightforward:
- Default static breadcrumb labels can be automatically translated by the app when the original default label values are kept.
- Custom label text is treated as merchant-defined copy, so it stays exactly as entered and is not auto-translated by the app.
- Collection names, product names, page titles, blog titles, and article titles come from Shopify. Translate those in Shopify, then the breadcrumbs can display the translated values on the storefront.
So if only “Home” is not translating, check the breadcrumb label settings. If collection or product names are not translating, check the Shopify content translations instead.
Why Breadcrumb Translation Feels Confusing in Shopify
Shopify stores often use several systems at the same time: theme language files, Shopify Markets, Translate & Adapt, third-party translation apps, product and collection data, and sometimes custom Liquid code. Breadcrumbs sit in the middle of all of that.
A breadcrumb component does not usually “own” the product title, collection title, page title, or article title. It reads those values from the storefront context. This is the right behavior because it keeps the breadcrumb aligned with the content customers already see on the page.
For example, if a collection is translated in Shopify from Packaging to Verpakkingen, the breadcrumb should reuse the translated Shopify collection title instead of asking the merchant to translate it again inside the breadcrumb app.
That also means a missing translation should be fixed at the correct source. If a collection name is still showing in the default language, the first thing to verify is whether that collection title has a published translation in Shopify for the current storefront language.
Layer 1: Static Breadcrumb Labels
Static labels are the generic words used by the breadcrumb system. They are not the merchant’s product or collection data. Common examples include:
- Home
- All products
- Collections
- Products
- Search
- Blog
- News
- Pages
- Articles
Breadcrumbs & Categories can automatically translate these default labels based on the current storefront language when the default values are still being used. This is useful for stores that want a clean multilingual experience without manually editing every small breadcrumb label.
The important detail is this: automatic label translation depends on keeping the default label value. If you customize a label, for example by changing Home to Homepage, Start, or a brand-specific word, the app respects that custom copy and keeps it as-is.
That behavior is intentional. A custom label may be a brand term, campaign phrase, or carefully chosen navigation word. Auto-translating merchant-defined custom copy could create incorrect or unexpected wording.
Layer 2: Dynamic Breadcrumb Content
Dynamic breadcrumb content is the part of the path that comes from your actual Shopify resources. This includes:
- Collection titles
- Product titles
- Page titles
- Blog titles
- Article titles
These values should be translated in Shopify, not inside the breadcrumb app. Shopify’s own localization flow supports store content translations through Shopify Translate & Adapt, CSV import, or compatible third-party translation apps. Once those translated values exist in Shopify, Breadcrumbs & Categories can read them from the storefront context and use them in the breadcrumb path.
For example:
- English path: Home > Packaging > Paper Bags
- Dutch path after Shopify translations exist: Home > Verpakkingen > Papieren tassen
In that example, the app can handle the default label layer, while Verpakkingen and Papieren tassen should come from translated Shopify collection titles.
Translation Responsibility Table
Use this table when debugging multilingual breadcrumbs. It helps separate app settings from Shopify content translations.
| Breadcrumb Text | Where It Comes From | Where to Translate It | Common Mistake |
|---|---|---|---|
| Home | Default breadcrumb label | Keep the default label so the app can auto-translate it, or manage custom wording carefully | Changing “Home” to custom text and expecting automatic translation to continue |
| All products | Default breadcrumb label | Breadcrumb label settings | Customizing the label in one language only |
| Collection name | Shopify collection title | Shopify Translate & Adapt, CSV, or translation app | Looking for collection title translations inside the breadcrumb app |
| Product name | Shopify product title | Shopify product translation | Testing a product before its translated title is published |
| Page name | Shopify page title | Shopify page translation | Translating menu labels but not the actual page title |
| Blog or article title | Shopify blog/article resource | Shopify blog or article translation | Expecting the breadcrumb to translate article titles independently |
Recommended Setup for Multilingual Shopify Breadcrumbs
The cleanest setup is to let each system do the job it is designed for. Use Shopify for store content translations, and use Breadcrumbs & Categories for breadcrumb structure, static label behavior, theme display, and breadcrumb schema.
1. Confirm the storefront language is working
Before debugging breadcrumbs, switch the storefront to the target language and verify that other Shopify content is translated. Check a product title, collection title, and page title outside the breadcrumb area.
If the page content itself is not translated, the breadcrumb will not have translated dynamic values to read.
2. Keep default breadcrumb labels unless you need custom wording
If you want automatic translation for default labels such as Home and All products, keep the default values in the breadcrumb settings. This allows the app to map those labels to the current storefront language.
If you intentionally use custom wording, test each language carefully. Custom text can be useful, but it should be treated like brand copy, not like a default system label.
3. Translate collections and products in Shopify
For collection and product breadcrumb segments, go to the Shopify translation workflow. Shopify Translate & Adapt can translate products, collections, blog posts, policies, and pages. You can also use another compatible translation app if your store already has one.
After translating, open the storefront in the target language and check the actual collection and product pages. If Shopify returns the translated title on the page, the breadcrumb has the right source to display a localized path.
4. Test collection, product, page, and article breadcrumbs separately
Do not test only the homepage or one product page. A multilingual breadcrumb audit should include the main page types where breadcrumbs appear:
- Collection pages
- Product pages
- Pages
- Blog listing pages
- Article pages
- Search results pages, if breadcrumbs are enabled there
Each page type can contain a different mix of static labels and Shopify resource titles.
5. Check the JSON-LD breadcrumb output
For SEO, the visible breadcrumb and the BreadcrumbList schema should tell the same story. If the visible breadcrumb is translated but the schema still uses old or mixed-language labels, search engines may receive inconsistent signals.
When using Breadcrumbs & Categories translation settings, verify that the storefront language, translated Shopify resource titles, and breadcrumb schema are aligned.
Common Translation Problems and How to Diagnose Them
Problem: “Home” does not translate
Check whether the Home label has been customized. If it has been changed from the default value, the app will keep the custom text as entered. Restore the default label if you want the automatic translation behavior.
Problem: Collection names remain in the original language
This usually means the collection titles have not been translated in Shopify, the translation is not published for the active language, or the storefront is not currently browsing in the expected language.
Problem: Product names translate, but collection names do not
Product and collection translations are separate Shopify resources. A translated product title does not automatically mean every related collection title has also been translated.
Problem: Menu labels are translated, but breadcrumbs are not
Navigation menu labels and Shopify resource titles are not always the same thing. A translated menu item can point to a collection whose actual collection title is still untranslated. Breadcrumbs usually read the resource title, not only the navigation menu label.
Problem: One language works, another language falls back
Check whether translations exist for every target language. Shopify can publish multiple languages, but each resource still needs available translated content for each language.
SEO Notes for Translated Breadcrumbs
Translated breadcrumbs help customers understand where they are in the store, but they also support a cleaner localized SEO setup. A good multilingual breadcrumb system should avoid mixed-language paths such as Home > Verpakkingen > Paper Bags unless that is an intentional brand choice.
For international Shopify stores, pay attention to these details:
- Keep breadcrumb language consistent: Static labels and Shopify resource titles should appear in the same storefront language.
- Translate resource titles, not just descriptions: Breadcrumbs usually rely on titles, so translated descriptions alone are not enough.
- Review localized URLs and handles: Shopify can support localized URLs, but the breadcrumb text still depends on translated resource names.
- Validate schema: If BreadcrumbList JSON-LD is enabled, confirm that schema names match the visible breadcrumb trail.
- Avoid duplicate custom labels: If custom breadcrumb labels are used, document them so future team members know why they are not auto-translating.
For a broader breadcrumb SEO workflow, you can also review how Shopify breadcrumbs support navigation and SEO, how to audit Shopify collection breadcrumb paths, and a practical Shopify breadcrumb audit template.
A Simple QA Checklist Before You Publish
Before publishing a multilingual breadcrumb setup, run through this checklist:
- Open the storefront in each target language.
- Confirm the theme language selector or Shopify Markets language routing works.
- Check whether default labels like Home and All products are still using default app values.
- Translate collection titles in Shopify.
- Translate product titles in Shopify.
- Translate page, blog, and article titles where those pages use breadcrumbs.
- Test one collection page, one product page, one page, one blog page, and one article page.
- Check mobile layout so translated labels do not overflow awkwardly.
- Validate BreadcrumbList schema if schema output is enabled.
- Document any custom label choices so the team knows they are intentionally not auto-translated.
Developer Handoff Notes
If a developer is helping with a multilingual Shopify store, the most important instruction is to avoid duplicating translation logic in the theme. Breadcrumbs should not hardcode product or collection translations if Shopify already manages those translations.
A clean handoff might look like this:
- Use Shopify translations as the source of truth for collection, product, page, blog, and article titles.
- Keep default breadcrumb labels in Breadcrumbs & Categories unless custom wording is required.
- Do not create a separate Liquid-only translation map for breadcrumb resource titles.
- Remove or disable duplicate theme breadcrumbs if they conflict with the app output.
- Test translated visual breadcrumbs and JSON-LD output together.
This keeps the setup easier to maintain when the catalog grows, new languages are added, or product and collection names change later.
Final Takeaway
Shopify breadcrumb translation works best when you separate static labels from dynamic store content. Breadcrumbs & Categories can handle default static breadcrumb labels, but collection names, product names, page titles, blog titles, and article titles should be translated in Shopify.
If a breadcrumb is only partially translated, do not assume the breadcrumb app is broken. Check which part of the path is failing. A default label issue belongs in breadcrumb settings. A collection, product, page, blog, or article title issue belongs in Shopify translations.
That simple split makes multilingual breadcrumbs easier to debug, easier to scale, and much cleaner for both shoppers and search engines.
