Function Scenario Guide

How to Translate Shopify Menus & Navigation

How to translate your Shopify menus and navigation — the header, footer, and mobile menus shoppers rely on — without breaking links, layout, or per-market structure.

AudienceShopify merchants localizing their storefront for multiple markets

TopicMenus & Navigation

Year2026

Summary

A repeatable workflow for translating every navigation surface — header, footer, mobile, and breadcrumbs — so each market gets a storefront that reads as native from the first click.

Before a single product, a visitor reads your menu. If the header is still in the source language, the entire localized storefront immediately reads as unfinished.

One untranslated menu label is wrong on every page of your store — the error compounds across hundreds of URLs and quietly erodes trust.

Shopify lets you assign different menus per market, but the translation still has to be produced and wired up correctly — or links point to the wrong-language pages.

Install Ciwi Talk to us

Why it matters

Why this translation scenario deserves its own workflow

Start by explaining why this Shopify surface matters before moving into scope, errors, and rollout method.

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.

A repeatable workflow for translating every navigation surface — header, footer, mobile, and breadcrumbs — so each market gets a storefront that reads as native from the first click.

How to translate your Shopify menus and navigation — the header, footer, and mobile menus shoppers rely on — without breaking links, layout, or per-market structure.

Navigation is the first thing a shopper touches

Before a single product, a visitor reads your menu. If the header is still in the source language, the entire localized storefront immediately reads as unfinished.

Menus repeat across every page

One untranslated menu label is wrong on every page of your store — the error compounds across hundreds of URLs and quietly erodes trust.

Per-market menus are a Shopify Markets feature

Shopify lets you assign different menus per market, but the translation still has to be produced and wired up correctly — or links point to the wrong-language pages.

Translation scope

What should you translate first in this scenario?

Prioritize the fields and surfaces that customers actually see, that shape conversion, and that influence SEO.

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: Header / main menu labels, Footer menu labels, Mobile (drawer) menu, and Mega-menu titles.

Important layer: Breadcrumb labels, Collection link titles, and Dropdown submenu items.

CriticalPriority: High

Header / main menu labels
Footer menu labels
Mobile (drawer) menu
Mega-menu titles

ImportantPriority: Medium

Breadcrumb labels
Collection link titles
Dropdown submenu items

OptionalPriority: Lower

Menu item descriptions or tooltips
Search bar placeholder text
Announcement bar text

Mistakes

What goes wrong most often here?

Focus on the issues that break UX, hurt SEO, or reduce conversion, not just language quality in isolation.

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.

Translating the header but not the footer or mobile menuHigh

Wrong example: Only the main nav is translated; the footer and mobile drawer still show source-language links.

Better approach: Translate header, footer, mobile drawer, and breadcrumbs together and assign them per market.

Business impact: A partially translated store that reads as broken the moment shoppers scroll or open the menu on their phone.

Hardcoding menu text in the themeHigh

Wrong example: Writing menu labels directly into Liquid or the theme instead of using Shopify navigation objects.

Better approach: Keep labels in Shopify navigation lists so they can be translated and assigned per market.

Business impact: Labels that can't be localized without a developer and manual theme edits.

Literal translation that breaks the layoutMedium

Wrong example: A one-word label translated into a long phrase that wraps and breaks the header alignment.

Better approach: Translate with length limits and test the live header, footer, and mobile layout in each language.

Business impact: Overflowing or misaligned navigation that looks unprofessional and hurts usability.

Links pointing to source-language pagesMedium

Wrong example: The translated menu still links to /en/ pages instead of the /fr/ or /de/ equivalents.

Better approach: Verify every menu link resolves to the translated version of its target in each market.

Business impact: Shoppers bounce between languages, breaking the localized experience.

Workflow options

Which setup fits this scenario best?

Help buyers decide between manual handling, translation apps, and custom development.

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.

Manual translation (in-house or freelancer) / Shopify translation app (Translate & Adapt / Ciwi) / Custom build with the Shopify API

Manual translation (in-house or freelancer)

Advantage

Full control over label wording
Precise fit for short navigation labels
Human judgment on menu hierarchy and ordering

Limitation

Tedious across many menus
Easy to miss footer and mobile variants
Slow to redo when menu items change

Shopify translation app (Translate & Adapt / Ciwi)

Advantage

Translates header, footer, and mobile menus in one pass
Length-aware labels keep the nav layout intact
Auto-sync when you add or rename menu items

Limitation

Recurring subscription cost
Still needs a review pass on brand terms
Per-market menu assignment still needs setup

Custom build with the Shopify API

Advantage

Programmatic control over navigation and link-list objects
Integrates with a headless or PIM setup
No per-app markup on large stores

Limitation

Requires development resources
You own the sync and update logic
Slower to ship than an app

Checklist

What should you verify before launch?

Turn the rollout into a practical execution checklist so QA is easier and nothing important gets missed.

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

List every navigation surface: header, footer, mobile drawer, breadcrumbs, and any mega-menu.
Export or open your Shopify navigation lists so all labels are in one view.
Decide on a per-market structure — one menu per market, or one translated menu reused across locales.
Build a short glossary for nav-critical terms like Shop, Sale, Support, and category names.
Translate labels with length in mind — short, consistent labels keep the layout from breaking.
Assign the translated menu to the right market in Shopify Markets.
Verify every link resolves to the translated version of its target page, not the source-language page.
Check mobile and footer menus specifically — they are the most commonly forgotten surfaces.

Ciwi

What Ciwi helps automate here

Translate product capabilities into workflow outcomes users can actually understand and act on.

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.

Translate header, footer, and mobile menus in one pass
Length-aware labels that keep your nav layout intact
Per-market menu assignment in Shopify Markets
Auto-sync new menu items so navigation never falls behind

Install Ciwi Talk to us

Next topics

What should you read next?

These related topics help build a more complete Shopify localization workflow after this scenario.

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.

How to Translate Shopify Pages (About, FAQ, Policies)

Translate the destination pages your menu links point to.

How to Translate Shopify Collections

Localize collection titles so nav links and category pages match.

How to Translate Shopify URLs & Slugs

Keep the URL structure behind each menu link localized too.

FAQ

Frequently asked questions

Cover the most common execution questions users ask when working through this scenario.

Do I need a separate menu for each language?

Not always. You can translate one menu and reuse it, but Shopify Markets lets you assign a different menu per market — use that when the link structure differs, or when one market needs extra items like a local shipping page.

Why is my mobile menu still in English after translation?

Mobile menus are often a separate navigation object from the header, so they get missed. Check that the mobile drawer has its own translated menu assigned to the market.

Will translating menus break my links?

Only if links point to source-language pages. After translating, verify each menu item resolves to the localized version of its target page in that market.

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.

Install Ciwi Talk to us