LingoWP
Does Loco Translate Include a WordPress Language Switcher?
The short answer is no. Loco Translate does not provide a visitor-facing language switcher.
Loco Translate is designed to edit translation files used by WordPress themes and plugins. Its official documentation describes it as a tool for file management and string editing, not for changing the language dynamically for each visitor.
That distinction matters. Translating a button such as “Add to cart” into French is not the same as creating separate English and French product pages, assigning language-specific URLs, and letting customers switch between them.
This guide, published by LingoWP, explains what Loco Translate can do, why it has no language switcher, and what you need instead for a multilingual WordPress or WooCommerce site.
What Loco Translate actually does
Loco Translate is primarily a PO-file editor available inside the WordPress dashboard. It can help you translate static interface strings contained in WordPress, a theme, or a plugin.
Examples include:
- “Add to cart”
- “Read more”
- “Search”
- “Out of stock”
- “Related products”
- Labels and messages supplied by your theme or plugins
The plugin can extract translatable strings, edit PO files, compile MO and JSON translation files, and integrate with several translation APIs.
This makes Loco Translate useful when:
- Your theme contains an untranslated label.
- A plugin translation is incomplete.
- You want to replace an existing translation with wording that better matches your business.
- A WooCommerce interface string remains in the wrong language.
- You are localizing a theme or plugin you developed.
However, those capabilities do not turn the site into a complete multilingual website.
Why Loco Translate has no language switcher
A language switcher must do more than change a few visible labels. It normally needs to determine which language the visitor selected and load the corresponding version of the current page.
Depending on the implementation, it may also need to manage:
- Translations of posts, pages, products, categories, and menus
- Relationships between translated pages
- Language-specific URLs
- The language selected by the visitor
- Navigation between equivalent page versions
- SEO metadata and alternate-language annotations
- Missing or unpublished translations
Loco Translate does not manage this system. Its documentation states that dynamically changing the language for anonymous visitors is not a native WordPress feature and requires custom code or another plugin. It also states that there are currently no plans to add a language-switching feature.
Loco Translate versus a multilingual plugin
| Capability | Loco Translate | Multilingual system |
|---|---|---|
| Edit theme and plugin strings | Yes | Varies |
| Translate PO and MO files | Yes | Varies |
| Translate posts and pages | No | Expected |
| Translate product content | No | Expected for WooCommerce support |
| Connect equivalent pages | No | Expected |
| Provide a visitor language switcher | No | Expected |
| Manage language-specific URLs | No | Expected |
| Handle multilingual SEO | No | Should be verified |
Loco’s documentation explicitly says that posts, pages, taxonomies, and site settings are stored in the database and are outside the plugin’s purpose. It recommends using a tool designed for database content when those elements need translation.
Doesn’t WordPress already have a language setting?
WordPress includes a Site Language option under Settings → General. Changing it sets the language used by that WordPress installation when translations are available.
It is a site setting, not a visitor-facing multilingual switcher. Changing it does not create parallel language versions that customers can select independently.
For example, changing the site language from English to French can load French translations for WordPress and compatible plugins. It does not automatically create:
- A French version of every English page
- Translated product descriptions
- Separate
/en/and/fr/URLs - Links between corresponding pages
- A language selector in the header
This approach is suitable when you want the entire site to operate in one primary language. It is not enough when visitors must choose between several languages.
Can you use Loco Translate with a multilingual plugin?
Potentially, yes, but each tool needs a clearly defined responsibility.
A sensible division is:
- Use the multilingual system for visitor languages, content translations, URLs, page relationships, menus, and the language switcher.
- Use Loco Translate only when you need to customize static strings supplied by a theme or plugin.
Before combining translation tools, test the setup on a staging site. Two plugins may attempt to load or override the same strings, and updates can affect custom language files.
When saving a custom translation in Loco Translate, avoid modifying translation files managed directly by WordPress. Loco recommends creating an override in its custom location because system translation files can be replaced or removed during updates.
A practical multilingual workflow
1. Decide which content needs translation
List the elements visitors must be able to read in each language:
- Main pages
- Blog posts
- Contact forms
- Navigation menus
- Calls to action
- SEO titles and descriptions
For a WooCommerce store, include:
- Product names and descriptions
- Categories and attributes
- Cart and checkout content
- Shipping and payment information
- Customer-account pages
- Transactional messages
2. Choose the system responsible for multilingual content
Your primary multilingual solution should manage the languages visitors can access and connect translated versions of the same content.
Before choosing, verify whether it supports:
- Your theme or page builder
- WooCommerce, if applicable
- Your required URL structure
- Menu and language-switcher placement
- SEO metadata
- Your translation workflow
Feature availability can change between versions and plans, so check the product’s current official documentation rather than relying on an old comparison article.
3. Create or review the translations
Translate the meaningful page content, not only interface labels. A page with translated navigation but an untranslated body is not a complete language version.
Google recommends using separate URLs for language versions and providing links that let visitors select another language. It also recommends hreflang annotations when different URLs represent localized versions of the same page.
4. Add the language switcher
Place the switcher somewhere consistently visible, commonly in the header navigation or mobile menu.
Test it from several types of pages:
- Homepage
- Standard page
- Blog post
- Product page
- Product category
- Cart and checkout
- A page without a completed translation
The switcher should lead to the corresponding translated page when one exists. Its fallback behavior for missing translations should be deliberate and predictable.
5. Use Loco Translate for remaining static strings
If the multilingual workflow is working but a theme or plugin label remains untranslated, Loco Translate may be appropriate.
WooCommerce officially documents Loco Translate as one method for creating custom translations of WooCommerce interface strings. The same documentation distinguishes these strings from products, categories, posts, pages, and menus, which require broader multilingual content handling.
Common problems
“I created two languages in Loco, but there is no switcher”
Creating translation files does not create public language versions. You still need a multilingual system or custom implementation responsible for selecting and loading the correct language.
“Changing Site Language switches the whole website”
That is expected. Site Language is a global WordPress setting, not an independent preference for each anonymous visitor.
“My pages and product descriptions remain untranslated”
Loco Translate does not translate database content such as posts, pages, taxonomies, settings, or product descriptions. Use the content-translation workflow supplied by your multilingual solution.
“My custom translation disappeared after an update”
You may have edited a system or plugin-managed language file. Loco recommends keeping custom overrides in its protected custom location rather than changing files that WordPress can replace.
“Some WooCommerce text is translated and some is not”
The untranslated text may come from different places:
- A WooCommerce language file
- Your active theme
- Another extension
- A value saved in WooCommerce settings
- Product or category content stored in the database
Identify the source before editing anything. Loco can help with eligible theme and plugin strings, but it cannot translate every type of store content.
Is Loco Translate enough for a multilingual store?
Not by itself.
Loco Translate can be valuable for correcting or completing software-interface translations. A multilingual store additionally needs a system for products, categories, pages, menus, language-specific navigation, and visitor language selection.
The safest way to evaluate a WordPress translation solution is to ask whether it manages the entire visitor journey:
- Can customers discover another language?
- Can they switch from the current page to its translated version?
- Are the products and purchasing steps translated?
- Does each language have a usable URL?
- Can search engines discover and understand the language versions?
A language switcher is only the visible control. The multilingual content and routing behind it are what make the website work.
Conclusion
Loco Translate does not include a WordPress language switcher because its purpose is editing translation files, not managing multilingual content for individual visitors.
Use it when you need to translate or customize static strings from WordPress themes and plugins. If customers must choose between complete language versions of your pages or products, use a multilingual system that manages content, URLs, page relationships, and the switcher itself.
Related guides
Sources
Checked on October 8, 2026.