EHERO Woo Multilang – Translate WooCommerce and build a truly multilingual store

Multilingual WooCommerce store: every language with its own products, URLs and SEO, all on one stock

With EHERO Woo Multilang you build a multilingual WooCommerce store where every language is real content: its own product, page or category, with its own URL, SEO title and Google listing. No translating the page on the fly while it loads, and no keeping your texts on someone else’s servers.

Selling in several languages is not really about translating text. It is about everything else still working: an order in English has to take units from the same stock as an order in Spanish, prices must never drift apart between languages, Google has to know which version to show in each country, and the customer should get their order email in their own language. The plugin takes care of all of it.

And so you don’t have to translate a whole catalogue by hand, it translates with AI using your own API key for Claude, OpenAI, Gemini, DeepL, DeepSeek or Google Translate. You pay the provider for what you actually use, with no word quotas. This very site, consultoriaehero.com, runs on EHERO Woo Multilang in 8 languages: switch the language at the top and you will see this page in Spanish, French, German, Italian, Portuguese, Catalan and Galician.

Every language is a real product in your multilingual WooCommerce store

Each translation is a WordPress object of its own, linked to the original inside a translation group. That is why it works with your theme, filters, search and reports just like any other product.

• Products, variations, pages, posts, categories, tags and any content types you switch on.
• A translations screen showing coverage per language, with a filter to see only what is missing.
• On every row, which languages are done and which are not, with one-click “Translate with AI” and “Re-translate”.
• If you delete the original, a translation takes over as the main item: no orphaned groups left behind.
• The admin product list shows each product once, with its flags.

As many languages as you need, regional ones included

There is no cap on languages. Each one comes with its flag, its URL prefix and its WordPress language pack.

• The most widely spoken languages, every official EU language and their neighbours.
• Catalan, Galician, Basque, Valencian, Aranese and Asturian, each with its own flag.
• Right-to-left (RTL) languages such as Arabic or Hebrew.
• The main language can live without a URL prefix; the rest get /en/, /fr/ and so on.
• Turn languages on and off without losing anything already translated.

AI translation with your own key, no word quotas

The plugin talks straight to your AI provider: texts go from your site to the provider and come back translated, without passing through EHERO’s servers.

• Claude, OpenAI, Gemini, DeepSeek, DeepL and Google Translate.
• An “Automatic” model per tier (fast, balanced or quality) that moves to the provider’s newest model in that tier on its own, and falls back to the previous one if the new one fails.
• A glossary of protected terms, so your brand and product references stay the same in every language.
• Three modes: fill in only what is empty, smart re-translation of what changed in the original, or translate everything.
• Translation memory: text that has already been translated is never paid for twice.
• Usage and estimated cost for the last 30 days, based on the tokens each provider reports.

A bulk generator that works in the background

Built for large catalogues: it walks through everything translatable in your main language and creates the missing translations in the languages you pick.

• Products, pages, posts, categories, tags, attribute names and Bricks templates.
• Linked drafts with no AI cost to fill in later, or items created and translated with AI on the spot.
• Keeps going through Action Scheduler even if you close the browser; when you come back you see the real progress.
• Publish when it finishes, or keep the translations as drafts to review and then publish them in one go.
• Safe to run again: anything that already exists is skipped, and failures can be retried with a button.

URLs per language, with indexing under your control

Each translation has its own address, in its own language, and you decide what Google gets to see.

• Translated slugs for products, pages and categories, plus translated URL bases (/product/, /produit/, /produkt/…).
• A suggested slug built from the translated title, and a warning when WordPress has tacked a “-2” on the end.
• An indexing switch per item: noindex and out of the sitemap in one click.
• A 301 redirect when a slug changes, or when someone requests another language’s slug under a prefix.
• Optional redirect based on the browser language, in PHP or in JavaScript so it plays nicely with caching.

Multilingual SEO: hreflang, canonical, sitemaps and schema

Google needs to know which version of each page is meant for which language. The plugin declares it exactly as Google’s guide to localized versions asks.

• hreflang tags on every page, with x-default for the main language.
• A canonical of its own for every translation, so no language is mistaken for duplicate content.
• Translated URLs in the Rank Math and Yoast XML sitemaps.
• Optional noindex for anything that has no translation yet.
• Localised JSON-LD schema: product, breadcrumbs and page language.
• SEO title and meta description translated in Rank Math, Yoast and SEOPress.

A multilingual WooCommerce store with one stock and one price

Shared fields are edited once on the main product and every translation picks them up instantly, so inventory never gets out of step between languages.

• Shared SKU, stock, regular and sale price, weight, dimensions, image and gallery (each one optional).
• Meta from other plugins that you share or translate per language, and inherited taxonomies such as brand.
• Gallery inherited or set per language, for localised photos or packaging.
• Customer emails in the language of the order, with subject, heading and body editable per language, plus a test send.
• Attribute names and values translated without touching your variations, and a cart and checkout that follow the language.

A language switcher wherever you want it

When a shopper changes language, they land on the same page in the new language, not on the home page.

• 


  shortcode, widget, block and menu item.

• Automatic placement in your theme header or on the hook of your choice, as a dropdown, flags or names.
• A different menu for each language, if you need one.
• If a page has no translation yet, the switcher takes the visitor to that language’s home page instead of an error.

Cross-language link audit

On a translated site it is easy for a link in the English text to point to the Spanish page. The audit finds it and fixes it.

• Scans the content of pages, posts and products, Bricks layouts included.
• Flags links to the wrong language, old URLs that only work thanks to a redirect, targets with no translation, drafts and broken links.
• One-click fix with the correct translated URL, saved in the content itself.
• On-demand external link check, in batches, without overloading the server.

Interface, theme and image strings

Not every word in a store lives in the products: buttons, notices, the footer, theme or page-builder headers.

• Captures the strings shown on the site so you can translate them from a single screen.
• “Translate with AI” fills in every missing string for each language in one go.
• Image alternative text (ALT) translated in every language.
• Compatible with the WPML strings that themes and plugins register.

Works with your page builder and your plugins

Content built with visual builders is translated inside its own structure, without breaking the design.

• Bricks (with structure re-sync), Elementor, Divi, Beaver Builder, Oxygen, WPBakery and Flatsome.
• ACF and JetEngine fields, JetFormBuilder forms and JetSmartFilters filters.
• Rank Math, Yoast and SEOPress; SWIS cache for translated pages; FooGallery.
• HPOS compatible, and works with subscription products.

Migration from WPML or Polylang, plus repair tools

If your site is already translated with another plugin, you don’t start from scratch.

• Imports WPML or Polylang translations: it adopts the links between items without copying or touching any content.
• Bulk publishing of translated drafts, per language or all at once.
• Safe repairs: category languages, counts, translation structure, subscription products and lost escaping.
• Per-page JSON-LD localisation and clean-up of orphaned translations, always with a dry-run analysis first.

Ideal for

If you sell, or want to sell, beyond your own language, a multilingual WooCommerce store built with EHERO Woo Multilang gives you a site per language without multiplying the work. Where it pays off most:

📋 System requirements

Tested against current versions of WordPress and WooCommerce.

🛟 Technical support

Email support in Spanish* at soporte@consultoriaehero.com and a full manual inside the plugin. Your multilingual WooCommerce store gets updates straight from the dashboard throughout the licence year.

⚖️ Comparison: why EHERO Woo Multilang?

How it stacks up against the most popular translation plugins when you build a multilingual WooCommerce store.

Prices published on each plugin’s website on 23 October 2026, VAT not included. “—”: not advertised on its website.

How many sales are slipping away because your store only speaks one language? Open your multilingual WooCommerce store today from €129.99.

Translate WooCommerce with EHERO Woo Multilang and sell in every customer’s language.

Want to see more tools for your store? Discover all our plugins for WooCommerce or visit the Consultoría EHERO store.

*Support covers incidents, bugs and plugin installation; it does not include consulting, custom configurations or custom development. Terms apply.