Multilingual WordPress: WPML vs Polylang vs Translation Services

Taking a site into a second language looks like a plugin decision, but it touches your URLs, SEO, checkout and weekly publishing. A multilingual WordPress site built on the wrong foundation usually works fine at first, then causes trouble when you add a third language or try to rank in a new market. This guide compares the main options (WPML, Polylang, TranslatePress and Weglot) and covers the structural decisions around them, so you can choose once and not rebuild.

The Four Main Ways to Build a Multilingual WordPress Site

Most serious projects end up on one of four options. They differ mainly in where the translations live and who does the translating.

WPML

WPML is the most complete option. Each translation is stored as its own WordPress post or page, linked to the original. That means every language version can have its own slug, SEO title, custom fields and even a slightly different layout if you need it.

Strengths:

• Deep compatibility with page builders, custom post types and major plugins.
• A translation management dashboard where you can assign jobs to in-house translators or send them to connected translation agencies.
• Built-in automatic translation using credits, with a review step before content goes live.
• Strong WooCommerce support through its companion WooCommerce Multilingual plugin, which also handles multiple currencies.

Trade-offs: WPML is paid (yearly plans, so check current pricing), it adds weight to the admin, and its extensive settings reward a developer who knows it.

Polylang

Polylang also stores each translation as a separate post, so the SEO flexibility is similar to WPML. The core plugin is free and lighter. Polylang Pro adds features such as shared slugs across languages and better handling for custom content, and there is a separate paid add-on for WooCommerce.

Strengths:

• Lean and fast, with a clean admin experience.
• Free version is genuinely usable for a brochure site or blog in two or three languages.

Trade-offs: fewer built-in workflow tools, and automatic translation depends on a connected service (Polylang offers a DeepL-based integration, so check what is currently included). Compatibility with complex page builders can require more manual effort than WPML.

TranslatePress

TranslatePress takes a different approach. Instead of duplicating posts, it stores translated strings in its own database tables and lets you translate by clicking text directly on the front end of your site. What you see is what you translate.

Strengths:

• Very approachable for non-technical editors.
• Translates everything visible on the page, including theme and plugin text, without hunting through string settings.
• Free version for one extra language, paid tiers for more languages, SEO features and automatic translation.

Trade-offs: because a translation is tied to a source string, changing one word in the original can orphan the translation. Deep structural differences between languages (a different layout or different images on the German page) are harder than with a post-per-language model.

Weglot as a Translation Service

Weglot is not really a plugin in the traditional sense. It is a subscription service with a WordPress connector. Your content is detected, sent to Weglot, machine translated, and served back through your site. Translations live on Weglot's servers and are edited in its dashboard.

Strengths:

• The fastest setup of any option. A small site can be live in multiple languages in an afternoon.
• Works across platforms, useful if you also run a Shopify store.
• Handles subdirectory URLs on WordPress, so translated pages are indexable.

Trade-offs: pricing scales with word count and number of languages, and it is an ongoing fee for as long as you use it. If you stop paying, the translations stop being served. That dependency is the main thing to weigh.

URL Structure: Subdirectory vs Subdomain vs Separate Domains

Before picking a plugin, decide how each language will appear in the address bar. This choice is hard to reverse later, because changing it means redirecting every translated URL.

Subdirectories (example.com/de/)

This is the default for most multilingual WordPress setups and our usual recommendation. All languages share one domain, so authority built by the main site benefits every language, and there is only one install to maintain.

Subdomains (de.example.com)

Subdomains are workable but offer few advantages for most businesses. They are sometimes chosen when a regional team needs a separate install, and each subdomain may need more of its own link building.

Separate Country Domains (example.de)

Country code domains send the clearest local signal and can help trust where shoppers prefer local domains. They also cost the most: separate domains, often separate installs, and link authority split across sites. They make sense when each country is effectively its own business.

WPML and Polylang can map languages to separate domains within a single WordPress install, which gives you the local domain without running several sites. It needs careful setup for cookies, logins and checkout, so test it thoroughly.

Hreflang and Multilingual SEO

Hreflang tags tell search engines which page is the equivalent in each language or region, so a Spanish speaker sees the Spanish page in results. All four options generate hreflang automatically when configured correctly; the mistakes happen around them.

What to check after launch:

1. Every page references every version, including itself. Hreflang must be reciprocal. If the English page points to the French page, the French page must point back.
2. Use an x-default. This tells search engines which page to show when no language matches, usually your main language or a language picker page.
3. Only link to indexable pages. Hreflang pointing at a redirected, noindexed or 404 page is ignored.
4. Translate the SEO fields, not just the body. Titles, meta descriptions, image alt text and URL slugs all need translation. A German page with an English slug and English title is a missed opportunity.
5. Include translated pages in your sitemap. Most SEO plugins integrate with WPML and Polylang to do this. Verify it rather than assuming.
6. Avoid forced redirects by IP address. Automatically sending visitors to a language based on location can prevent search engine crawlers from seeing all versions. A visible language switcher, or a gentle suggestion banner, is safer.

Also remember that translating is not localizing. The phrase your German customers search for may not be a direct translation of your English keyword, so do keyword research per language.

Translation Quality: Machine, Human or AI

The plugin decides the mechanics. The quality of your multilingual WordPress site depends on who (or what) writes the translations.

Machine Translation

Engines such as DeepL, Google Translate and Microsoft Translator connect with all four options. Quality for common European language pairs is often fine for informational pages, but struggles with brand voice, idioms, product terminology and legal text. Unedited output on a product page can read as slightly off, which erodes trust at the point of purchase.

AI Translation with a Glossary and Review

Large language models can produce more natural phrasing and follow instructions such as "never translate our product line names." In our projects, the practical sweet spot for most businesses in 2026 is AI or machine translation as a first draft, a glossary of terms that must stay consistent, and a native speaker reviewing the pages that matter most. Some plugins now offer AI-based options directly, so check the current feature list of the one you pick.

Human Translation

Professional translators remain the right call for legal pages (terms, privacy policy, returns policy), regulated industries, and high-value landing pages. WPML's translation management is designed for this workflow, sending jobs to agencies and receiving them back into the site.

A tiered approach usually works best:

• Human: legal pages, homepage, top landing pages, checkout text.
• AI or machine plus native review: product pages, category pages, key blog posts.
• Machine only, spot checked: long tail blog archives, help articles, low traffic pages.

WooCommerce: Multi-Currency and Multilingual Checkout

A multilingual store is a bigger job than a multilingual brochure site, because translation reaches into products, variations, emails and payment.

Things to plan for:

• Product data. Titles, descriptions, attributes, variations and categories all need translating. On large catalogs, this is where most of the translation budget goes.
• Transactional emails. Order confirmations and shipping notices should arrive in the customer's language. WPML's WooCommerce Multilingual and Polylang's WooCommerce add-on handle this, but custom email templates may need extra work.
• Multi-currency. Showing prices in euros or pounds is not only a display setting. Decide whether to use automatic exchange rates or set fixed prices per currency (fixed prices avoid awkward numbers like 23.47). Also confirm your payment gateway supports charging in each currency, not just displaying it.
• Taxes and shipping. Different countries often need their own tax settings and shipping zones, which is WooCommerce configuration, not translation.
• Stock sync. With WPML and Polylang, translated products should share inventory with the original. Test this before launch by placing orders in each language.

For stores selling into several countries, our ecommerce development team usually audits the store setup before any translation begins.

Workflow: How Content Gets Published After Launch

Launching translated pages is a project. Keeping them in sync is a permanent process.

Questions to answer before choosing:

1. Who publishes new content, and in which language first? Most teams write in one source language and translate from it.
2. What happens when the source page changes? WPML and TranslatePress flag outdated translations. With Polylang, you usually need your own checklist.
3. Do translated pages ever need different content? A promotion only for Germany, or different images for Japan, is easier with post-per-language plugins (WPML, Polylang).
4. Who approves translations? If a regional partner reviews content, give them an editor role limited to their language.

If nobody owns translation updates, the second language will be out of date within months. Assign an owner.

What a Multilingual WordPress Site Costs

Costs depend heavily on page count, the number of languages and how much is human translated. Typical ranges from our projects, for adding languages to an existing, well-built site:

• Small brochure site (10 to 30 pages, one or two new languages): setup and configuration roughly $800 to $2,500, plus translation.
• Content-heavy business site or blog (100+ pages): roughly $2,500 to $6,000 for setup, SEO configuration and template fixes.
• WooCommerce store with multi-currency: often $4,000 to $12,000 or more, depending on catalog size, custom features and payment setup.

Ongoing costs include plugin licenses or subscriptions (estimate your word count before choosing Weglot), translation credits, human translation (typically per word, varying by language pair) and maintenance time to keep languages in sync.

If your site already has theme or plugin problems, fixing them first is usually cheaper than translating a broken foundation. Our WordPress development services cover both the cleanup and the multilingual build, so the site is ready for new markets rather than patched for them.

How to Choose

A quick decision guide:

• Choose WPML for large sites, complex page builders, WooCommerce with multiple currencies, or a translation agency workflow.
• Choose Polylang for lean sites where your team translates manually and wants low overhead.
• Choose TranslatePress when non-technical editors will do the translating and visual editing matters most.
• Choose Weglot when speed matters more than long-term cost, or you need the same translation layer across several platforms.

Whatever you pick, test on a staging copy with your real theme and plugins first.

FAQ

Can I switch from one translation plugin to another later?

Yes, but it is rarely clean. WPML to Polylang (or the reverse) is most manageable since both store translations as posts. Leaving TranslatePress or Weglot usually means exporting translations and adding redirects.

Does machine translation hurt SEO?

Search engines focus on whether content helps readers, not how it was produced. Unreviewed, low quality translation can still underperform, so review high value pages.

How many languages should I start with?

Start with the one or two markets where you already see traffic or sales. Each language adds ongoing maintenance, so it is better to do two well than five poorly.

Will a translation plugin slow down my site?

Any plugin adds some overhead, but with good hosting and caching the impact is usually small. Test speed on translated pages too, since caching is sometimes configured only for the main language.

If you are planning to take your WordPress site into new languages or markets, book a free 1-hour strategy call through our contact page and we will help you pick the right setup.