WordPress website translation: WPML, Polylang, and the script-tag option (2026)

Option 1: WPML (WP Multilingual Plugin)

WPML is the most established WordPress multilingual plugin, with over 1 million active installations. It creates separate post/page copies per language, manages per-language URLs (/fr/about/), and integrates with most themes and page builders.

When WPML is the right choice

• •You need per-language SEO URLs for every post and page
• •You have a team of human translators who will maintain each language version
• •Your content strategy is language-specific (different posts per market)
• •You're building a long-term multilingual publication and SEO is critical

WPML downsides

• ✗Annual editions vary by feature; verify current vendor pricing
• ✗Significant setup time — URL configuration, language switcher placement, theme compatibility
• ✗Duplicate content management overhead — every update requires updating each language version
• ✗Machine translation is a paid add-on, not included

Option 2: Polylang

Polylang offers core and paid editions. Verify current vendor packaging; the paid edition adds WooCommerce support and some advanced features. The architecture is similar to WPML — language-specific posts, per-language URL structure — but the workflow is simpler.

When Polylang makes sense

• •You want the CMS localization approach but WPML's price is a barrier
• •You're comfortable with a less polished setup experience
• •You don't need WooCommerce (free plan) or can justify the Pro price

Polylang downsides

• ✗Still requires managing separate content per language
• ✗No built-in machine translation — you translate everything manually or integrate a third-party service
• ✗Less third-party plugin compatibility than WPML

Option 3: Script-tag translation widget (Lingvit)

Instead of restructuring your WordPress content, Lingvit translates your existing site in place. One plugin install (or a snippet in functions.php) and your entire site is automatically translated. No duplicate posts, no URL restructuring, no manual translation workflow.

When Lingvit is the right WordPress choice

• ✓You need multilingual support fast — days, not weeks
• ✓Your primary goal is serving existing visitors in their language, not separate-language SEO
• ✓You're running a WooCommerce store and want product pages translated immediately
• ✓You can't afford to restructure your URL scheme or manage multiple content versions
• ✓You want machine translation with an editorial override dashboard

Lingvit limitations for WordPress

• ✗Translated content is not in HTML source — search engines index the original language only
• ✗You can't have language-specific posts or different content strategies per locale

Decision guide: which approach for your WordPress site?

Scroll horizontally to view every column.