Free 20-point conversion & SEO audit for export stores — Free website audit — claim yours

hello@woo.one Mon–Fri · 9:00–18:00 (UTC+8)

How to Build a Multilingual WooCommerce Store That Google Can Actually Index

URL structure, hreflang, translation quality, currency and tax for multilingual WooCommerce. A practical setup guide for exporters entering new markets.

Most multilingual WooCommerce projects fail in the same place: the translation is finished, the language switcher works, and almost none of the new pages are indexed. Google sees duplicate content, broken hreflang or a switcher that changes a cookie instead of a URL.

This guide covers the decisions that determine whether a multilingual store ranks or merely exists.

Start with URL architecture

Choose one of these and stay consistent:

  • Subdirectory: example.com/de/ — usually the best balance of authority consolidation and simplicity. Recommended for most exporters.
  • Subdomain: de.example.com — clearer operational separation, but splits authority and complicates analytics.
  • Country-code domain: example.de — strongest local signal, highest cost and operational overhead.

Parameter-based language switching (?lang=de) and cookie-only switching are the most common indexing failures. Every translated page needs its own crawlable, stable URL.

Get hreflang right

Every language version must reference all versions, including itself. Each reference must point to a live, canonical, indexable URL — not a redirect and not a 404.

Example for three markets:

<link rel="alternate" hreflang="en" href="https://example.com/product/widget/">
<link rel="alternate" hreflang="de" href="https://example.com/de/produkt/widget/">
<link rel="alternate" hreflang="fr" href="https://example.com/fr/produit/widget/">
<link rel="alternate" hreflang="x-default" href="https://example.com/product/widget/">

Use en for a language target, or en-GB / en-US when you genuinely serve different content or offers per country. Do not mix language and country targeting without a reason.

Translate products, not just menus

Machine translation of interface strings is fine for buttons and checkout labels. Product titles, descriptions, specifications and buying guides need human review — not because Google demands it, but because buyers notice. A German buyer searching for “Edelstahlgehäuse” will not convert on a page that says “Stainless steel case” with a translated theme.

What to translate first

  1. Category titles and descriptions.
  2. Top 50 products by revenue or ad spend.
  3. Shipping, returns and FAQ pages.
  4. Checkout and transactional emails.
  5. Everything else, in priority order.

Choosing the stack

WPML is the most established option for WooCommerce, with strong support for product fields, taxonomies and currencies. Polylang is lighter and developer-friendly. TranslatePress offers a front-end translation experience that suits smaller catalogues. Whatever you choose, verify:

  • Translated URLs are crawlable and can be edited.
  • Canonical tags point to the same language version.
  • Hreflang is generated automatically and validation passes.
  • Product variations, attributes and reviews are translatable or correctly shared.
  • The sitemap includes every language version.

Currency, tax and local payment

Displaying prices in EUR is not the same as selling in the EU. Consider local payment methods (SEPA, iDEAL, Klarna, BLIK), VAT display rules, IOSS/OSS registration, and shipping thresholds that make sense per market. A US-style checkout with a card-only form and a surprise shipping fee will lose European buyers.

Localise search intent, not just words

Keyword research must be done per market. A literal translation of your English category page often targets a term nobody searches. Work with a native speaker or a local SEO partner to identify:

  • The terms buyers actually use for the product category.
  • Local units, certifications and compliance language.
  • Seasonality and buying cycles.
  • Competitor positioning in that market.

Indexing checklist before launch

  • Crawl the translated site and confirm every URL returns 200.
  • Validate hreflang with a tool or Search Console international targeting report.
  • Check that language switchers use links, not JavaScript-only toggles.
  • Submit language-specific sitemaps.
  • Confirm lang attributes and translated metadata are correct.
  • Set up separate Search Console properties or filters per market where useful.
  • Monitor indexation weekly for the first month.

The five mistakes we see most

  1. Translating only theme strings and leaving product content in English.
  2. Hreflang pointing to redirected or parameter URLs.
  3. A language switcher that changes a cookie without changing the URL.
  4. Publishing thousands of machine-translated pages at once and wondering why quality signals collapse.
  5. Ignoring local payment and tax expectations because “the checkout works in English”.

If you are planning a second or third market, send us your target countries and catalogue size. We will map the URL, hreflang and localisation work before you commit to a platform.

S

Infrastructure and security engineer at woo.one, based in Foshan, China. Works on WordPress, WooCommerce and OpenCart systems, self-hosted mail, and the operational side of running stores for exporters.

More about the team

No pressure · No sales script

Ready for a store that sells while you sleep?

Send us your current site or product list. You will receive a fixed-scope proposal, a 20-point audit and a realistic timeline within two business days.

Reply within 1 business day NDA on request 100% code ownership
Chat with us
WhatsApp Get a quote