15 min read
How to Make Your WooCommerce Store Multilingual: Translate Products, Categories & Checkout
Making your WooCommerce store multilingual opens your products to buyers in their native language – and research consistently shows that people are significantly more likely to purchase when shopping in their own language. In 2026, the two primary approaches for WooCommerce multilingual stores are WPML (the established standard for complex stores) and Weglot (the faster, cloud-based option). This guide compares both, walks through complete setup for each, and covers currency, SEO, and multi-vendor marketplace considerations.
Why Multilingual Matters for WooCommerce
English-only stores miss a substantial portion of global buyers. The data is consistent: CSA Research found that 76% of online shoppers prefer to buy products with information in their own language, and 40% will not buy from a site in a foreign language at all. Shopify’s global commerce data shows similar patterns – stores that localize to target markets see conversion rate increases of 30-80% in those markets compared to English-only presentation.
The business case is strongest for: stores that ship internationally, digital product stores (software, templates, courses, ebooks) where buyers globally can access the product, service businesses where customers in non-English speaking regions discover you via local language search, and marketplaces with vendors or buyers from multiple countries.
For WooCommerce specifically, multilingual is a revenue multiplier: each language you add properly is a new market segment with its own organic search potential, its own conversion dynamics, and its own buyer intent patterns. French-speaking buyers in Canada, Belgium, and Switzerland are three distinct markets with overlapping language but different products expectations, pricing sensitivities, and shipping considerations. If you source products from China for these international markets, cross-border eCommerce buying agents can handle the purchasing and logistics while you focus on localizing the storefront for each audience.
40% of global online shoppers will not buy from a site in a foreign language. Every language you add properly is a market you unlock.
CSA Research
Option 1: WPML – The Established Standard
WPML (WordPress Multilingual Plugin) is the most widely used multilingual solution for WordPress, with over 1 million active installations and a dedicated WooCommerce Multilingual extension that has been developed and tested specifically for WooCommerce’s complex data structure.
How WPML Works with WooCommerce
WPML creates separate translated versions of each page, product, and category. Your product “Blue Running Shoes” becomes a separate WooCommerce product entity in German (“Blaue Laufschuhe”) and Spanish (“Zapatillas de Correr Azules”) – each with its own URL, meta description, and content. These translated versions are linked as translations of the original and share inventory management. Orders, inventory counts, and stock management are synchronized across all language versions.
This architecture is WPML’s key advantage: genuine separate translated content means each language version can be independently SEO-optimized. German product titles can use the actual German search terms buyers use, not just translated English terms. This matters because “running shoes” translates differently from how German shoppers actually search for athletic footwear.
WPML Setup: Step by Step
- Purchase WPML Multilingual CMS from wpml.org (required base plugin). WooCommerce Multilingual is a free add-on from the WPML plugin downloads section.
- Install both plugins in your WordPress dashboard via Plugins > Add New > Upload Plugin.
- Activate WPML and complete the setup wizard: select your site’s default language, choose target languages to add, and configure the language switcher.
- Install and activate WooCommerce Multilingual (the free WPML add-on for WooCommerce).
- Navigate to WooCommerce > WooCommerce Multilingual to run the compatibility check. WPML will flag any WooCommerce settings that need adjustment for multilingual operation.
- Translate your WooCommerce system pages: go to WPML > String Translation and translate strings from WooCommerce’s shop, cart, checkout, and account pages.
- Begin translating products: edit any product, and the WPML translation management panel appears below the editor. Click “+” to add a translation for each language. The translation editor shows source and translated fields side by side.
- Configure per-language currency settings (WooCommerce Multilingual Settings > Multi-currency) if you want to show different currencies to different language audiences.
WPML Translation Methods
WPML offers three ways to translate your content, and you can use different methods for different content types:
- Manual translation: You or your team types translations directly in WPML’s translation editor. Full control, highest quality, most time-consuming. Best for short product descriptions and titles where exact wording matters.
- Professional translation: Send content to professional translators via WPML’s Translation Management interface. Translators receive assignments, complete them in WPML’s translation editor, and send back for review. Best for product-heavy stores where quality is critical but volume is high.
- Automatic translation: WPML uses DeepL (preferred) or Google Translate to automatically translate content. Results are good enough for a working starting point and improve with editing. Best for stores with large catalogs where perfect quality on first pass is less important than having all content translated and searchable.
WPML for Multi-Currency WooCommerce
WooCommerce Multilingual includes built-in multi-currency support. Navigate to WooCommerce > WooCommerce Multilingual > Multi-currency. Add currencies for each language/region you serve. Configure: the exchange rate (manual or automatic from a rate feed), the currency symbol and format, and whether prices are set manually per currency or calculated automatically from the exchange rate.
Per-currency pricing allows you to set specific prices in each currency rather than relying on exchange rate calculation – important when you want German buyers to see €89 rather than a calculated €88.42 that looks like a conversion artifact rather than a deliberate price point.
Option 2: Weglot – Fast Setup, Cloud-Based
Weglot takes a fundamentally different approach from WPML. Rather than creating translated WordPress content, Weglot detects all text rendered on your pages, translates it automatically using AI, and delivers translated versions under language-specific URLs – all without creating additional WordPress posts, products, or pages.
How Weglot Works
When a visitor accesses yourstore.com/de/ (the German version), Weglot intercepts the page rendering, translates all visible text via its translation layer (which sits in the cloud), and serves the translated version. The WooCommerce backend remains unchanged – there is only one product in your database, but it renders in German for German visitors. Weglot stores all translations in its cloud service and serves them with a very small performance overhead.
Weglot Setup: Step by Step
- Create a Weglot account at weglot.com and select your plan based on the languages and word count you need.
- Install the Weglot plugin from Plugins > Add New in WordPress.
- Enter your Weglot API key (from your Weglot dashboard) in the plugin settings.
- Configure: select your original language, add your target languages, and choose where to place the language switcher (header, footer, or a specific position).
- Weglot automatically translates your entire WooCommerce store – products, categories, checkout, account pages, email templates, everything visible on the frontend.
- Review and edit translations in the Weglot Visual Editor (in your Weglot dashboard, navigate to any page of your store and edit translations inline on the actual page). Override any automated translation that needs human refinement.
The entire process from account creation to working multilingual store: 10-20 minutes. This is Weglot’s primary advantage over WPML for stores that want to test a new language market before investing heavily in perfect translations.
Weglot and WooCommerce: Special Considerations
Weglot handles most WooCommerce elements automatically – product titles, descriptions, short descriptions, attribute values, category names, page content. However, some WooCommerce elements require attention:
- Product-specific metadata: Custom product fields from plugins (custom fields, product builders) may need to be manually added to Weglot’s translation scope via the Weglot dashboard settings.
- Order confirmation emails: Weglot translates transactional emails to the language the customer used during checkout. Verify this in Weglot Settings > Emails.
- Dynamic strings: Text generated by JavaScript or loaded via AJAX after page load may not be captured by Weglot’s initial scan. Test these thoroughly after setup.
- Multi-currency: Weglot does not include multi-currency. You need a separate currency plugin (WOOCS – Currency Switcher for WooCommerce, or WooCommerce’s built-in currency switcher) alongside Weglot for price localization.
WPML vs. Weglot: Complete Comparison
| Factor | WPML | Weglot |
|---|---|---|
| Setup time | 2-5 hours for complete setup | 10-20 minutes |
| Translation architecture | Creates separate translated WP content | Translates rendered HTML in cloud |
| Translation control | Full per-field, per-product control | Good, via visual editor or dashboard |
| SEO approach | Separate URLs, full hreflang support | Separate URLs, full hreflang support |
| Per-language pricing | Yes, native WooCommerce multi-currency | No – requires separate currency plugin |
| Price (annual) | $99 (Multilingual Blog) to $249 (Multilingual CMS) | $99 (1 language, 10K words) to $490+ (5 languages, 200K words) |
| Performance impact | Server-side, no additional round-trips | Small added latency from cloud translation layer |
| Content update sync | Manual – you must create/update translations when content changes | Automatic – new content detected and translated |
| Automatic translation engines | DeepL, Google Translate (configurable) | DeepL, Google Translate, Microsoft (automatic) |
| WooCommerce compatibility | Excellent – dedicated WC add-on, extensively tested | Good – handles most WooCommerce elements automatically |
| Best for | Stores with complex products, per-language pricing needs, long-term investment | Stores wanting fast setup, testing new language markets, simpler product catalogs |
SEO for Multilingual WooCommerce Stores
Both WPML and Weglot create language-specific URLs and add the hreflang tags that tell Google which language version to serve to which users. This is the technically correct multilingual SEO implementation and avoids the duplicate content penalties that naive multilingual approaches (one page showing different content based on IP) can trigger.
URL Structure Options
- Subdirectory (recommended): yourstore.com/de/ for German, yourstore.com/es/ for Spanish. Clean, uses your main domain’s authority, easiest to set up with either plugin.
- Subdomain: de.yourstore.com for German. Technically fine but requires additional DNS configuration and some SEO considerations around subdomain versus subdirectory authority.
- Separate domain: yourstore.de for the German version. Maximum geographic targeting signal; significant complexity to manage two separate sites sharing inventory.
Keyword Research Per Language
Direct word-for-word translation of product titles and descriptions often misses local search terms. What buyers in Germany search for when looking for “running shoes” may differ significantly from the literal German translation of your English keyword. Doing keyword research for each target language – using Google Keyword Planner, Semrush, or Ahrefs with language filtering – and applying those findings to your translated product titles is the difference between multilingual content that ranks and multilingual content that merely exists.
Even basic keyword research reveals these gaps quickly. For a product category where you sell “eco-friendly water bottles,” German buyers might search “nachhaltige Trinkflasche” (sustainable drinking bottle) while the literal German translation of “eco-friendly water bottle” returns very different search volumes. Using the locally preferred terminology in translated product titles and meta descriptions is where multilingual SEO investment pays off.
Currency and Payment Considerations
A multilingual store without currency localization creates friction: French buyers see USD prices, which looks wrong and reduces trust. For a complete localization experience, pair your multilingual plugin with a multi-currency solution:
- WPML + WooCommerce Multilingual: Built-in per-language currency support. Assign a currency to each language. Set prices manually or auto-calculate from exchange rates. German visitors see EUR prices; US visitors see USD prices automatically.
- Weglot + Currency Switcher plugin: Weglot does not include currency switching. Add WOOCS (WooCommerce Currency Switcher) or a similar plugin. WOOCS can auto-detect visitor location via IP and display the appropriate currency.
- WooCommerce Payments: WooCommerce’s own payment processing supports “presentment currency” – showing buyers a local currency price while settling in your home currency. Works independently of your multilingual plugin.
Payment Gateway Localization
Beyond currency, buyers in different markets have different payment method preferences. Germany has a high preference for SEPA direct debit and Klarna. The Netherlands uses iDEAL. Brazil uses Boleto Bancário. Poland uses Przelewy24. Stripe supports all of these and WooCommerce Stripe integration has settings to enable local payment methods per region. Offering a familiar local payment method alongside international cards meaningfully increases conversion rates in markets where card payments are not the dominant preference.
Multilingual for WooCommerce Marketplaces
If you are running a WooCommerce marketplace with Dokan or WCFM, multilingual implementation requires additional planning beyond standard store translation.
Vendor Dashboard Translation
Vendor dashboards, product submission forms, and order management interfaces need translation if your vendors operate in different languages. WPML has documented compatibility with both Dokan and WCFM – follow their specific documentation for marketplace setup to avoid conflicts between WPML’s content duplication system and the marketplace plugin’s vendor product ownership model.
A key consideration: when a vendor submits a product in one language on a WPML multilingual marketplace, what happens to other language versions? The default behavior in WPML is that translated versions need to be created separately – either by you as admin, by the vendor (if you grant them translation access), or via automatic translation. Define your policy for this before launch and configure WPML accordingly.
Vendor Notification Email Translation
Vendor notification emails (new order received, payout processed, product approved) need translation into the vendor’s language. Both Dokan and WCFM use WordPress email templates that WPML can translate. Set vendor language preferences in their profile so emails go out in the correct language automatically.
BuddyPress Community + Multilingual
If your marketplace includes a BuddyPress community layer, additional translation considerations apply: profile fields need translated labels and option values, BuddyPress notification strings need translation, and group descriptions need translation if the community serves multilingual audiences. WPML has BuddyPress compatibility documentation and string translation tools specifically for BuddyPress user-facing text.
Common Mistakes to Avoid When Going Multilingual
Multilingual WooCommerce setup has enough moving parts that predictable mistakes come up repeatedly. Knowing them before you start saves significant troubleshooting time.
- Launching without testing checkout end-to-end in each language: Automated translation handles product pages well but checkout pages contain a mix of WooCommerce system strings, payment gateway text, and dynamic form labels that may not all translate automatically. Always complete a full test purchase in each language – add to cart, go through checkout, place the order, check the confirmation email – before pointing traffic at the translated store.
- Skipping translated product meta descriptions: Both WPML and Weglot translate body content, but meta descriptions for SEO require deliberate attention. Auto-translated meta descriptions are often awkward for the target language. Write custom meta descriptions for your highest-traffic product and category pages in each language rather than relying entirely on automated translation for SEO copy.
- Not configuring the language switcher for mobile: Language switchers that work well on desktop often become hard to find or tap on mobile. Check your language switcher placement and tap target size on actual mobile devices. Many WooCommerce stores have language switchers embedded in navigation menus that collapse or become inaccessible on small screens.
- Ignoring translated product variation names: Product variations (sizes, colors, materials) need translation just like product titles. An English product with size options “Small, Medium, Large” should show “Klein, Mittel, Groß” to German buyers. Both WPML and Weglot handle attribute value translation, but you need to verify these are being translated correctly – attribute values are one of the areas where automated translation quality is most variable.
- Starting Weglot on a plan that underestimates word count: Weglot’s pricing is based on total translated word count across all your content. New users frequently underestimate this because they count only product descriptions. WooCommerce adds thousands of words in system strings, button labels, email templates, and checkout page text. Run Weglot’s word count checker on your store before committing to a plan, not after you have already exceeded the limit on the starter plan.
Testing Your Multilingual Store
Never launch a new language without thorough testing. A broken checkout or incorrect pricing in a language you cannot read creates customer trust damage that is hard to recover from in that market. Testing checklist:
- Product pages display correctly in each language (title, description, short description, attributes)
- Category pages and navigation display in the correct language
- Search works and returns results in the active language
- Cart and checkout pages display in the correct language
- Payment gateway screens (Stripe, PayPal) display in the correct language
- Order confirmation emails go out in the buyer’s language
- Currency switcher shows the correct price format for each currency (not just symbol – decimal separators and number formats differ by locale)
- hreflang tags are correctly implemented (test with Google Search Console’s URL inspection tool)
- Test purchase completed: product accessible, order recorded, inventory decremented correctly
- Admin order management shows translated product names and attributes correctly
Frequently Asked Questions About WooCommerce Multilingual
Does multilingual affect WooCommerce store performance?
WPML adds a moderate amount of database complexity (translated posts are linked via WPML’s translation tables) but with proper object caching the performance impact is minimal. Weglot adds a small latency for its translation layer on the first page load; subsequent loads use the cache. Neither solution should cause noticeable performance degradation on properly hosted WooCommerce stores.
Can I add languages later after starting with one?
Yes. Both WPML and Weglot allow adding languages at any time. With WPML, adding a language means you then need to create translations for all existing content – the plugin shows an untranslated content count and provides tools for batch translation. With Weglot, adding a language immediately auto-translates all existing content in the new language.
Does Weglot count WooCommerce dynamic content in its word count?
Yes, Weglot charges based on total word count across all translated content, including dynamic WooCommerce strings (checkout labels, button text, system messages, email templates). For a small catalog, typical WooCommerce string translation adds 5,000-15,000 words to your Weglot word count. For a large catalog with many product descriptions, this can significantly affect which Weglot plan you need.
Which languages generate the most ROI for WooCommerce stores?
This depends entirely on your product category and target markets. Generally, the languages with the highest per-capita online spending for most ecommerce categories are: German (DE, AT, CH), French (FR, BE, CA), Spanish (ES, LATAM), Portuguese (BR), and Japanese. Start with the language that represents the largest existing traffic segment in your Google Analytics data from non-English visitors – these are buyers already finding you who are not converting because of the language barrier.
Can I migrate from Weglot to WPML later if my needs change?
Migration from Weglot to WPML is possible but not automatic. Weglot stores translations in its cloud; WPML stores them in WordPress. You would need to export your refined translations from Weglot and re-import them as WPML translations. The volume of content and the quality of your Weglot translations determine how much effort this takes. If per-language pricing or deep WPML integration is a foreseeable need, starting with WPML from the beginning avoids this migration entirely.
Which Option Is Right for Your Store?
The decision between WPML and Weglot comes down to complexity, budget, and timeline. Choose WPML when: you need per-language pricing (essential for true localization), you have complex products with many custom fields, you are running a marketplace with vendor products that each need language management, or you want maximum control over translations quality and each language’s SEO. Choose Weglot when: you want to launch a new language in under an hour to test market response, your product catalog is standard WooCommerce without heavy customization, you do not need per-language pricing, and ongoing automatic translation updates matter more than perfect initial translation quality.
Both options work reliably for most WooCommerce stores. The most common regret is choosing Weglot for a store that eventually needs per-language pricing – that gap requires adding a currency plugin later, creating additional complexity. If per-language pricing is a definite requirement, start with WPML regardless of the longer setup time.
Wbcom Designs has experience implementing multilingual solutions for WooCommerce stores and marketplace platforms, including complex setups combining WPML with Dokan or WCFM multi-vendor functionality alongside BuddyPress community features. If you need implementation help for a multilingual store, reach out to our team.
Related reading