Weglot for Multilingual WooCommerce: What It Translates (and What Comes Next)

If you're running a WooCommerce store and thinking about going multilingual, Weglot is one of the cleanest options on the market. Cloud-based translations, no database bloat, working in 100+ languages, and you can have a translated store live in about five minutes. This post covers what Weglot does well, where its limits sit, and how AI search fits with a multilingual stack.

Weglot is a translation plugin for WordPress and WooCommerce that takes a different approach from most of the competition. Instead of duplicating posts in your database (the WPML/Polylang model), Weglot stores translations on its own cloud servers. Your WordPress install stays lean, and the translations are served to visitors based on URL prefix — /fr/, /de/, /es/ — automatically.

Founded in France in 2016, Weglot now powers translations for 100,000+ websites including stores on Shopify, Webflow, BigCommerce, and naturally WordPress + WooCommerce. The selling point is simplicity: install plugin, paste API key, pick languages, done.

Out of the box, Weglot covers everything a typical WooCommerce store needs:

• Theme UI — buttons, navigation, forms, footer text, breadcrumbs
• Posts and pages — full content with formatting preserved
• Meta tags — page titles, descriptions, Open Graph, Twitter Cards (important for international SEO)
• URL slugs — /about becomes /fr/a-propos, /products/red-jacket becomes /de/produkte/rote-jacke
• WooCommerce product data — names, descriptions, short descriptions, attribute labels, category names, tag names
• Email content — order confirmations, shipping notifications, password resets (with the Email Translation add-on)
• Image alt text — for accessibility and image search SEO
• Custom strings from your theme or other plugins — discovered automatically as visitors browse the site

Most translation work is done by Weglot's machine translation (DeepL or Google Translate under the hood) on first install, then you refine manually in their visual editor. For a 100-product store with 2 target languages, the auto-translation gives you 80% quality immediately, and the visual editor lets you fix the remaining 20% in an afternoon.

Weglot's pricing is word-based, not feature-based. You unlock more languages and word counts as you scale.

For a typical WooCommerce store with 100-200 products, you'll land between Starter and Business depending on how many languages you need. The free tier is genuinely useful for testing — 10,000 words covers a small site and lets you see exactly what Weglot does on your store before paying.

Word count includes everything Weglot translates: products, posts, pages, theme strings, meta tags. A typical product description (~80 words) plus title, attributes, and short description adds up to ~150 words per product. Math: 200 products × 150 words × 2 languages = 60,000 words → Starter plan.

WooCommerce introduces a few wrinkles that not every translation plugin handles well — Weglot does:

Variable products — a T-shirt with size and color variations gets each variation's attributes translated independently. "Red, Large" becomes "Rouge, Grand" in French, automatically.

Product attributes — global attributes (defined in Products → Attributes) translate once and apply across all products that use them. Saves significant word count on stores with consistent attribute taxonomies.

Cart, checkout, and account pages — fully translated, including dynamic content like order summaries and shipping methods.

Currency switching — Weglot doesn't do this natively, but plays well with WooCommerce currency switchers (CURCY, WC Currency Switcher) when you want price localization alongside language.

Stock messages — "In stock," "Only 3 left," "Out of stock" — all translated. These are part of WooCommerce core text domain so Weglot picks them up automatically.

One practical tip: Weglot's WooCommerce integration improved significantly with version 4.x. If you're using an older version, update before evaluating — early Weglot had gaps in cart/checkout translation that are now closed.

Here's where it gets interesting. Weglot translates *content* and *interface*. It does not interpret search query intent — and by design, it shouldn't.

When a visitor on /fr/ types veste imperméable into a search box, what happens depends on which search system you're using:

• Default WordPress search — looks for the literal string "veste imperméable" in your content. If your products are translated to French, it works. If you're using basic keyword matching only, *partial* synonyms like "veste pour la pluie" may not match "veste imperméable."
• Keyword search plugins (Relevanssi, SearchWP) — same fundamental approach. Better keyword matching, but still bound to the exact words in your content.
• AI semantic search — interprets the *meaning* of the query. "veste imperméable", "jacket for rain," "raincoat," and "wasserdichte Jacke" all map to the same semantic concept and find the same products. Language detection is automatic; no per-language synonym lists.

The distinction matters because translation and search are fundamentally different problems. Translation maps text from language A to language B. Search interprets *what the user wants* and finds matching content. A great translation plugin doesn't need to be a great search engine — these are different specialties.

Queryra (our AI search plugin) is designed for this exact stack. The multilingual parser sits in the search pipeline and handles language detection at query time — completely independent of which translation plugin you use.

From our test logs:

``
'wasserdichte jacket' (DE+EN mix) → semantic = waterproof jacket → 3 results
'kurtka wodoodporna' (PL) → semantic = waterproof jacket → 3 results
'veste imperméable' (FR) → semantic = waterproof jacket → 3 results
'waterproof jacket' (EN) → semantic = waterproof jacket → 3 results
``

Every query — regardless of language, mixed languages, or how the user phrases their intent — resolves to the same vector embedding and returns the same products. This works on a Weglot site because Queryra doesn't care about the URL prefix or the active language; it cares about the *meaning* of the query.

For visitors, this is the experience you want: language switching at the UI level (handled by Weglot) plus semantic search that understands queries in any language (handled by Queryra). Two specialized tools, each doing what they're designed for.

Here's the configuration that works cleanly:

Why turn off Weglot's Translate Search: that toggle is designed for sites using default WordPress ?s= search. When you're using Queryra (or any search plugin with its own endpoint), Weglot's translate-search hook doesn't intercept the query anyway. Leaving it off avoids any confusion and makes the responsibility split explicit: Weglot for content, Queryra for search.

Setup time: about 10 minutes total. Install Weglot, pick languages, install Queryra, sync your records. Done.

• Weglot translates WooCommerce content (products, UI, meta, slugs, emails) into 100+ languages with cloud-based storage — no database bloat
• Free tier: 10k words / 1 language. Starter: $15/mo for typical small stores. Business: $29/mo for 3 languages
• Weglot handles content translation. It is not designed to interpret search query intent — and that's fine, because that's a different problem
• AI search (like Queryra) handles multilingual query interpretation natively: French, German, Polish, mixed languages, all resolve to the same semantic match
• Recommended stack: Weglot for translations + Queryra for search. Weglot's Translate Search toggle: OFF

For more on multilingual WooCommerce search options, see our translation plugin compatibility guide.