Guide · Webflow Ecommerce
Webflow Ecommerce Multilingual: Why Your Store Can't Use Webflow Localization — and What to Do Instead
Your Webflow store gets traffic from France, Germany or Spain. Those visitors land on English product pages, hesitate, and leave. The fix sounds obvious — make the store multilingual — until you open Webflow's own localization feature and discover the sentence that stops every store owner cold: Webflow Localization does not work with Webflow Ecommerce sites.
This guide explains what a multilingual store actually requires, why the official tool leaves stores out, and the real options you have today — with their trade-offs stated plainly.
What "multilingual" actually means for a store
For a blog or a marketing site, multilingual mostly means translated pages. A store is a different animal. Going multilingual properly means all of this at once:
- The whole catalog, translated in bulk — every product title, description, variant and collection page, kept in sync when products change. Nobody hand-translates 300 SKUs.
- Localized URLs — a real page per language, typically under subdirectories like yourstore.com/fr/, that search engines can crawl and rank independently.
- Correct hreflang — the tags that tell Google which language version belongs to which visitor, including self-references, reciprocal links and an x-default. An Ahrefs study of 374,756 domains found 67% had at least one hreflang error.
- A multilingual sitemap — every language version listed, so new translations actually get discovered.
- Translated SEO metadata — titles and meta descriptions adapted to how people search in each language, not just the visible body text translated word for word.
Miss any layer and the result is predictable: Google indexes the wrong version, or none, and your "multilingual store" is invisible in the markets you built it for.
Why Webflow Localization leaves stores out
Webflow Localization is the platform's official multilingual feature, priced per locale. It handles regular sites — pages, CMS content, static text. But Webflow Ecommerce sites are explicitly outside its scope: the ecommerce layer (products, collections, cart, checkout) is not covered.
That exclusion lands hardest exactly where multilingual matters most. A portfolio site can survive in one language; a store selling cross-border cannot. The store owners who most need localization are the ones the official tool doesn't serve.
The options stores actually have today
1. Third-party translation tools (e.g. Weglot)
These do work with Webflow ecommerce, and for many stores they're the current default. The catch is the pricing model: you pay per translated word, and the allowance is a single pool shared across all your languages, consumed as you translate rather than renewed monthly. Catalogs are word-heavy and multiply by language, so stores climb tiers quickly — Weglot's published plans run from €15/month (10,000 words, 1 language) to €699/month. On its G2 review page, "expensive" is among the most-mentioned complaints. It works; the meter is the problem.
2. JavaScript language switchers
Cheap widgets that swap the visible text when a visitor picks a language. They translate what a human sees — and almost nothing of what Google sees. There is one URL, one title, no per-language pages to rank. As an SEO strategy it's a dead end; as a courtesy feature it's fine.
3. Duplicated sites or hand-built subfolders
Full control, full workload. Every product change has to be mirrored by hand in every language, forever. This survives for a five-product boutique and collapses at fifty.
4. Wait for a store-first tool
Which is the gap we're testing with LocalePress: bulk catalog translation plus the full SEO layer (localized subdirectory URLs, checked hreflang, multilingual sitemap, translated metadata), priced by catalog size instead of a cross-language word pool. It's in development and being validated by a founder presale — if five store owners won't pre-order a refundable $15, it won't be built. The presale terms are on the LocalePress page.
The short version
If you sell on Webflow and want other languages: the official tool doesn't cover you, switcher widgets don't rank, manual duplication doesn't scale, and the established tool charges you by the word across every language at once. Whatever route you choose, judge it against the five layers above — catalog, URLs, hreflang, sitemap, metadata. A translation that Google can't index per-language is a courtesy, not a channel.
FAQ
Does Webflow Localization work with Webflow Ecommerce?
No. Webflow Localization covers regular Webflow sites, but it does not support Webflow Ecommerce sites — product pages, collections, cart and checkout are outside its scope.
Can I translate a Webflow store today?
Yes, but every current route has a trade-off: third-party tools like Weglot work with Webflow ecommerce but charge by translated words across all languages; JavaScript switchers translate what visitors see without creating indexable localized pages; manual duplicated sites work but don't scale with a catalog.
Does Google index translations shown by a JavaScript language switcher?
Poorly at best. A switcher that swaps text on a single URL gives Google one page, not one page per language — no localized URLs to rank, no per-language titles, no hreflang structure. Proper multilingual SEO needs a real, crawlable page per language.