StoreBuilt’s review of Shopify localisation documentation and our existing translation QA guidance exposed an important distinction: translated content can exist without customers having a usable route to it. Our implementation approach starts with the public journey, then traces the configuration behind it. A translation dashboard alone cannot prove that a shopper can choose their preferred language.
A Shopify language selector not showing can mean several different things. The whole control might be missing, one language might be absent, or a choice might appear to work before navigation returns the customer to English. For UK ecommerce teams expanding abroad, those symptoms deserve separate tests. This guide focuses on access and navigation; it does not replace a review of translation quality.
In this guide
- Identify which part is missing
- Separate language from country and currency
- Check publication before changing the theme
- Inspect the published theme and responsive placement
- Trace a language change through the whole visit
- An illustrative French launch investigation
- Use a compact acceptance matrix
- Protect discoverability during changes
- StoreBuilt point of view
Identify which part is missing
Start with an exact page URL and a fresh browser session. Record the country selected, language shown, device width and whether you arrived through a campaign link or the homepage. Compare a product page with the homepage. A footer control can exist on both but become difficult to find beneath a long mobile page, while a custom header may be absent from a specialist landing template.
Describe the failure in one sentence: “French is absent from the language menu when browsing the France market” is useful. “Translations are broken” leaves too many possibilities open. Save a screenshot and one working comparison before changing settings. That comparison makes it easier to tell whether you fixed language availability, rendering or navigation.
Separate language from country and currency
A language preference is not a shipping destination. An English-speaking customer may be shopping for delivery to France, while a French-speaking customer may live in Britain. Treat country, language and currency as separate pieces of the experience even when a theme places them inside one menu.
Shopify’s market localisation guidance explains that market context and browser preferences influence the initial experience, and manual selections can persist. In your test notes, record the complete context rather than using a national flag as shorthand for a language. The final checkout address can also change the market experience; a working header selector does not guarantee the same currency after an address change.
| Symptom | First evidence to collect | Likely investigation |
|---|---|---|
| No selector anywhere | Published theme and mobile screenshot | Theme placement and support |
| Selector has only English | Available languages for this market | Publication and market configuration |
| French selected, text stays English | Exact resource and destination URL | Translation coverage or navigation |
| Language resets after a click | Starting and destination URLs | Hard-coded internal links |
| Country changes unexpectedly | Saved preference and checkout address | Market context |
Check publication before changing the theme
Shopify distinguishes adding a language, translating resources and publishing that language. Review the current translation and publication guidance, then inspect the actual store settings. A language being available in a translation app is not sufficient evidence that it is published for customers.
Confirm the intended language is available in the market being tested. Keep a small record of each supported combination, such as Britain with English and France with French. Do not assume every language must be offered in every market. Make the intended combinations an explicit trading decision, then verify the configuration reflects that decision.
Inspect the published theme and responsive placement
Open the theme customers actually receive, then review its header and footer settings. Theme controls and supported versions vary. Check the theme’s own documentation before assuming a setting from another theme should exist. If the control appears in preview only, compare theme identity and saved settings before touching translation data.
On mobile, inspect the drawer as well as the visible header. A selector may have moved into an expandable panel, inherited a hidden state or become covered by another overlay. Keyboard users should be able to open it, choose a language and understand the resulting selection. For custom work, our Shopify design and development service can address the navigation and theme layer.
Trace a language change through the whole visit
Choose a language from an ordinary product page and note the resulting address. Continue to a collection, another product and the basket. Use both menu links and in-content links. A single manually entered English URL in a promotional block can undo an otherwise correct localised journey.
Repeat the journey from a direct campaign landing page. Saved preferences can conceal first-visit behaviour, so compare a returning session with a fresh session. Do not interpret a VPN test as the only valid market test: the customer’s selected experience and the final delivery address matter as well. Record what you actually observed rather than assuming the location of the tester determines every setting.
An illustrative French launch investigation
Imagine a British skincare retailer has translated product descriptions into French, but its published footer offers only English. The translation editor looks complete. The team first verifies the intended France market and language publication, then enables the appropriate selector on the published theme. The control becomes visible, but a homepage promotion still links to the English path.
The second fix belongs to navigation, not translation. The team corrects that link using the theme’s supported localisation approach and repeats the product-to-basket journey. This is an illustrative investigation, not a reported client result. It shows why one screenshot of a translated page cannot close the issue: each route into and through the store must preserve the intended experience.
Use a compact acceptance matrix
Choose representative templates rather than clicking every page randomly. Include the homepage, a collection, an ordinary product, a product with custom content and the basket. Add a page with an app-powered widget if that widget contains important buying information. Translation support for third-party content should be checked with its provider.
| Test | Expected result | Evidence to retain |
|---|---|---|
| First visit on mobile | Intended choices are discoverable | Screenshot and market context |
| Language change on product | Correct localised destination | Before and after URLs |
| Internal navigation | Preference remains coherent | Three-step journey |
| Basket and checkout handoff | Understandable language and market | Selected context and address scenario |
| Return visit | Saved choice behaves as intended | New visit observation |
Set a clear stopping point for the investigation. If configuration is correct but the control still fails in an unmodified compatible theme, give Shopify or the theme developer a reproducible case. Include the affected template and browser behaviour. Avoid sending private customer details when a clean test product demonstrates the same failure.
Protect discoverability during changes
Do not unpublish and republish languages merely to make a menu refresh. Shopify warns that links to an unpublished language can return a missing-page response. Review incoming campaigns and internal links before changing language availability. If the business is withdrawing a language, plan the destination of existing links deliberately.
For SEO work, check that localised pages remain reachable and that the rendered canonical and language relationships match the intended architecture. A selector repair does not establish that Google has indexed a page. Our Shopify SEO and AI search service can connect the navigation fix with a wider crawlability review. Continue with our translation QA guide when access works but meaning or terminology still needs attention.
StoreBuilt point of view
A multilingual store succeeds when customers can choose a language and keep using it without having to understand the site’s architecture. StoreBuilt treats that as a complete navigation task, with publication, market configuration and theme behaviour tested together. Start with one reproducible journey, repair the layer that fails and preserve the evidence for the next theme release.