How to Translate Your WooCommerce Store (Complete 2026 Guide)

73% of online shoppers prefer to buy in their native language. For WooCommerce store owners, that's not a fun fact — it's the difference between making the sale and losing it.

But translating a WooCommerce store isn't just translating product titles. It's translating the entire buying experience: product descriptions, cart strings, checkout fields, order emails, My Account area, URL slugs, and SEO metadata. Miss any piece and the experience feels broken.

This guide covers everything. By the end, you'll know exactly what needs translating, how to do it, and what it costs.

What Needs Translating in a WooCommerce Store

Most people think "translate products" and stop there. Here's the full list:

The Obvious

Product titles — "Wireless Bluetooth Headphones" → "Kabellose Bluetooth-Kopfhörer"
Product descriptions — short and long descriptions
Category names — "Electronics" → "Elektronik"
Tag names — "Sale," "New Arrival," "Best Seller"

The Often Forgotten

Product attributes — Size, Color, Material and their values
Variable product options — "Small / Medium / Large" in the dropdown
Purchase notes — post-purchase instructions shown to customers
Gallery image alt text — for accessibility and SEO
Product reviews — the existing reviews on your products

The Checkout Flow

Cart page strings — "Your cart is empty," "Subtotal," "Proceed to checkout"
Checkout field labels — "First name," "Email address," "Order notes"
Payment gateway text — "Pay with credit card," "PayPal checkout"
Shipping method names — "Free shipping," "Express delivery"
Coupon messages — "Coupon applied successfully"

The Post-Purchase Experience

Order confirmation emails — the most important email your store sends
Processing/shipped emails — order status updates
Refund/cancelled emails — handling returns
Customer note emails — personalized messages
New order admin emails — so you know what happened, in context
My Account area — menu items, order history columns, address labels

SEO Elements

Product URL slugs — /product/headphones → /produkt/kopfhoerer
Category URL slugs — /category/electronics → /kategorie/elektronik
Meta titles and descriptions — what shows in Google search results
JSON-LD product schema — structured data for rich snippets
OpenGraph tags — what shows when someone shares your product on social media

That's a lot. Let's talk about how to actually do it.

Method 1: Manual Translation (Free, Slow)

If you have 10 products in 1 language, manual translation is fine. Install any translation plugin with a free tier, and translate string by string.

When it works: Very small stores, 1-2 languages, you speak both languages.

When it doesn't: 50+ products, 3+ languages, you don't speak the target language. Manual translation of a 100-product store in 5 languages means translating roughly 15,000 strings. At 30 seconds per string, that's 125 hours of work.

Method 2: Automatic Translation + Review (Fast, Smart)

This is what most successful multilingual stores do:

Machine translate everything in one batch
Review and edit the critical parts (product titles, checkout, emails)
Let the rest be — modern AI translation is good enough for descriptions, categories, and UI strings
Let Translation Memory learn — corrections improve future translations

With Polyglot Translate's Magic Translate, step 1 is literally one button click. The entire store gets translated in the background — products, pages, checkout, everything.

What to Review First

Not all translations are equally important. Prioritize:

Product titles — this is what customers see first. Wrong here = lost sale.
Checkout flow — any confusion here = abandoned cart.
Order emails — broken email = panicked customer contacting support.
Homepage — first impression matters.
Category names — navigation must make sense.

Everything else (descriptions, UI strings, footer text) can be reviewed over time. AI handles these well enough for initial launch.

Method 3: Professional Human Translation (Best Quality, Expensive)

Hire professional translators for your highest-value content. Use machine translation for everything else.

Professional e-commerce translation typically runs a per-word rate that adds up fast: a 100-product store, roughly 200 words each, across 5 languages is 100,000 words — enough that a fully human-translated catalog runs into the thousands of euros and takes weeks.

For most WooCommerce stores, that's overkill. The sweet spot: machine translate everything, then have a human review your top 20 product pages and the checkout flow — a fraction of the cost.

With Polyglot Translate, you can export translations as XLIFF files, send them to a human translator, and import the reviewed versions. They go straight into Translation Memory at the highest quality tier.

Step-by-Step: Translating Your Store with Polyglot Translate

Step 1: Install the Plugin (2 minutes)

Go to WordPress.org, search "Polyglot Translate," install, activate. Or upload from polyglot-translate.cloud.

Step 2: Connect Your Account (1 minute)

Grab a free API key from polyglot-translate.cloud (no credit card needed). Paste it in Plugin Settings → API Key.

Step 3: Choose Your Languages (30 seconds)

Settings → Languages → Add your target languages. The free tier covers 1 language; add the Pro addon for unlimited languages.

Step 4: Install WooCommerce Addon (1 minute)

If you have the WooCommerce addon, activate it. It automatically detects your WooCommerce installation and adds translation support for products, cart, checkout, emails, and My Account.

Step 5: Magic Translate (1 click)

With the Pro addon, click "Magic Translate." The plugin translates your entire store:

Products (titles, descriptions, attributes, variations)
Pages (homepage, about, contact, etc.)
WooCommerce strings (cart, checkout, account)
Menus and widgets

Progress bar shows real-time status. Background processing means you can close the browser.

Step 6: Review Critical Translations (30-60 minutes)

Open the visual translation editor. Browse your store in each language. Focus on:

Top 10 product titles
Checkout page
Cart page
One order email template (the rest follow the same pattern)

Edit anything that doesn't sound right. Your edits go into Translation Memory — same corrections won't be needed again.

Step 7: Configure WooCommerce-Specific Settings (5 minutes)

URL slugs: Set translated slugs for /product/, /category/, /tag/ per language
Email translation: Verify all 9 email types have proper translations
My Account: Check menu items and order status labels
Payment gateways: Verify payment button text is translated

Step 8: Test the Full Buying Flow (10 minutes)

Switch to each language and:

Browse a product
Add to cart
Go through checkout
Check the order confirmation email
Check My Account page

If everything reads naturally — you're done.

Total time: Under 2 hours for a complete multilingual WooCommerce store. Compare that to 125 hours of manual translation.

URL Strategy: Subdirectories vs. Subdomains

For SEO, you need translated URLs. Two approaches:

Subdirectories (Recommended)

example.com/         → English (default)
example.com/de/      → German
example.com/fr/      → French
example.com/de/produkt/kopfhoerer  → German product

Pros: Single domain authority, easier to manage, preferred by most SEO experts.

Subdomains

example.com    → English
de.example.com → German
fr.example.com → French

Pros: Complete separation, good for very different markets.

Our recommendation: Subdirectories. Simpler, better for SEO authority consolidation, and all translation plugins support them.

SEO Checklist for Multilingual WooCommerce

After translating, verify these SEO elements:

[ ] Hreflang tags present on every page (check with hreflang tag checker)
[ ] Each language has its own XML sitemap
[ ] Product meta titles are translated (not just page content)
[ ] Product meta descriptions are translated
[ ] URL slugs are translated per language
[ ] Category/tag URLs are translated
[ ] JSON-LD product schema shows correct language
[ ] OpenGraph tags show translated content
[ ] Canonical URLs point to the correct language version
[ ] Google Search Console added for each language version

With Polyglot Translate's SEO addon, most of these happen automatically. Hreflang, meta translation, JSON-LD, and sitemaps are handled out of the box.

Common Mistakes to Avoid

1. Translating Only Products, Forgetting Checkout

A German customer browsing products in German who suddenly sees an English checkout will leave. The entire flow must be consistent.

2. Ignoring Email Translation

Order confirmation emails in the wrong language look unprofessional. Worse — if the customer can't read the email, they'll contact support. That costs you time and money.

3. Not Translating Currency Context

Translation isn't just language. €49.99 and other currencies mean different things to different buyers. While currency conversion is a separate topic, make sure price-related strings ("Starting from," "On sale," "Tax included") are translated.

4. Forgetting Mobile

Check your translated store on mobile. German words are longer than English. "Shopping Cart" → "Einkaufswagen" might break your mobile layout. Test every language on every screen size.

5. Launching Without Testing the Buy Flow

Always complete a test purchase in every language before going live. Place a real order, check the email, check the My Account page. Five minutes of testing saves hours of support tickets.

What It Costs

The exact numbers depend on your catalog and how many languages you run, but the shape of each option is what matters. Competitor prices below were checked against each vendor's own pricing page in 2026 — confirm on their site before buying, since plans change.

| Approach | Cost pattern (as of 2026) | Setup time | |----------|---------------------------|------------| | Manual translation | Free — but your time (125+ hours for a 100-product, 5-language store) | 125+ hours | | Professional human | Thousands of euros for a full catalog | 2-4 weeks | | Weglot | Subscription that grows with content — Pro $92/mo (~$1,100/yr) for 200K words, 5 languages | Minutes | | WPML | Multilingual CMS €99/yr (3 sites) + 90K auto-translate credits | 2-4 hours | | TranslatePress | Business €199/yr (3 sites, 200K AI words) | 2-3 hours | | Polyglot Translate | Bundle Pro €129/yr (3 sites, all addons, 1.5M chars/mo) — and your effective bill trends down as Translation Memory covers repeated content | < 2 hours |

Polyglot Translate's Bundle Pro is €129/yr — 3 sites, unlimited languages (with Pro), all five addons, and 1.5M characters a month. Because the first translation of each string is stored in Translation Memory and reused for free, your character usage drops over time instead of resetting every cycle. Want to try before you buy? The free tier gives you 10,000 characters every month, no card required.

Ready to Go Global?

Your WooCommerce store has products people want. The only question is whether they can find them in their language.

73% of shoppers prefer their native language. You're leaving international customers behind if your store only speaks English.

Two hours of setup. One plugin. Every language your customers speak.

Get Polyglot Translate →

Related reading:

Polyglot Translate Addons Guide — WooCommerce addon deep dive
WPML vs Weglot vs TranslatePress vs Polyglot — honest comparison
7 WordPress Myths Debunked — including "translation is expensive"

How to Translate Your WooCommerce Store