WordPress into Vietnamese: WPML vs Polylang vs manual
💡 For a WordPress site targeting Vietnamese readers, Polylang (free) covers routing, hreflang="vi" tags, and a language switcher at zero cost. WPML (from €39/year) is the better choice for WooCommerce and large editorial sites that need automatic translation credits. The manual route using Loco Translate handles core string translation but requires custom code for multilingual routing, making it practical only for simple brochure sites.
Key takeaways
- Polylang free: 800,000+ active installs on WordPress.org; handles Vietnamese routing, hreflang, and language switcher at no cost; WooCommerce translation requires the paid add-on (€99/year or €139/year Business Pack).
- WPML: no free tier; starts at €39/year (Multilingual Blog); Vietnamese is one of 65 pre-configured languages; WooCommerce support and automatic translation credits are included in the CMS tier (€99/year).
- TranslatePress: paid from €99/year; unique visual front-end editor; integrates Google Translate and DeepL for draft generation; WooCommerce-ready on all paid plans.
- All three plugins support directory-based Vietnamese URLs (/vi/...) and emit hreflang="vi" tags - the correct BCP 47 code for Vietnamese per the IANA Language Subtag Registry.
- The manual approach (Loco Translate for .po/.mo files) translates WordPress core strings but requires custom code for multilingual routing and hreflang, viable only for small brochure sites with infrequent updates.
Which plugin should you choose for a Vietnamese WordPress site?
The core decision is whether you need multilingual post content (separate Vietnamese and English pages at distinct URLs) or just a translated interface (menus, buttons, core WordPress strings). For the first, you need a routing plugin. For the second, Loco Translate alone may be enough.
For a content site or blog, Polylang free is the practical starting point: more than 800,000 active installs, 55+ supported locales including Vietnamese, directory-based URLs (/vi/), automatic hreflang tags, and a language switcher widget at zero cost. WPML is the better pick for e-commerce or large editorial sites needing 24/7 Vietnamese support and built-in translation credits. TranslatePress fits teams that want to translate visually, directly on the rendered page.
- Polylang free - content site routing, hreflang, language switcher; WooCommerce costs extra (€99/year add-on)
- WPML - no free tier (from €39/year); WooCommerce + auto-translation at CMS tier (€99/year); 65 languages including Vietnamese
- TranslatePress - paid from €99/year; visual front-end editor; DeepL/Google Translate integration; WooCommerce on all plans
- Manual (Loco Translate) - free; translates .po/.mo strings only; no routing or hreflang generation
What does the "manual" WordPress approach actually cover?
The manual route means using Loco Translate to manage WordPress .po and .mo translation files for your theme and plugins. This translates every core WordPress string, menu label, and plugin-generated text into Vietnamese without modifying the database schema.
What it does not cover: creating parallel Vietnamese posts or pages at separate URLs, generating hreflang tags, or routing visitors by language. For a small brochure site with three pages and no regular updates, adding hreflang manually in your theme header is manageable. For a Vietnamese e-commerce store or a news site publishing daily, the manual approach becomes a maintenance burden within weeks.
How do WPML and Polylang handle Vietnamese URLs and hreflang?
Both WPML and Polylang support three URL models: directory (/vi/tin-tuc/), subdomain (vi.yourdomain.com), and separate domain (yourdomain.vn). Directory is the most common for a site entering the Vietnam market, consolidating domain authority while making the language clear to both users and Google Search Console.
WordPress supports UTF-8 slugs natively, so Vietnamese post slugs with diacritics display correctly in modern browsers. Both plugins allow independent slugs per language: the English page at /en/english-learning/ maps to a distinct Vietnamese slug at /vi/học-tiếng-anh/ without transliteration. Hreflang tags are emitted automatically after language configuration: <link rel="alternate" hreflang="vi" href="https://example.com/vi/..."/>.
One practical note: some older server configurations may percent-encode UTF-8 slugs in HTTP responses. The fix is straightforward - set the WordPress permalink structure to %postname% and flush rewrite rules after switching language settings.
Does the free Polylang tier cover a Vietnamese content site?
For a content site, yes. Polylang free handles post and page language assignments, Vietnamese routing, a language switcher widget or shortcode, automatic hreflang for all public post types, and language-filtered navigation menus. That covers the core needs of a multilingual informational site or blog.
The gap is WooCommerce. Translating product titles, descriptions, categories, and shop pages requires the Polylang for WooCommerce paid add-on (€99/year). If you need a Vietnamese WooCommerce store with Polylang, WooCommerce support alone costs €99/year. WPML's CMS tier (€99/year) includes both WooCommerce support and automatic translation credits at the same price, which can make WPML more cost-effective for e-commerce.
Vietnamese UI strings typically run longer than English equivalents. A navigation label reading "Services" in English may expand to "Dịch vụ" or the fuller "Các dịch vụ của chúng tôi" depending on the register. Budget extra space in button and tab designs - this is a theme and CSS concern, independent of plugin choice.
In-house vs specialist: where does a native Vietnamese translator save real time?
You can handle in-house: installing Polylang or WPML, configuring language directories, generating a machine translation draft via WPML's AI credits or TranslatePress's DeepL integration, and translating static UI strings with Loco Translate.
A native Vietnamese specialist saves real time in these situations: reviewing and correcting MT-generated page content for tone and register before publishing; translating product descriptions, category names, and checkout flow strings where a wrong Sino-Vietnamese register choice loses buyers; localizing marketing landing pages where persuasion and cultural nuance matter; and providing ongoing translation as you publish new posts or product pages in Vietnamese.
The clearest workflow: use the plugin for technical routing, use MT for a first draft of bulk content, and bring in a specialist for your highest-traffic pages, checkout flow, and any content users act on directly. That keeps costs predictable and quality where it matters most.
For English and French teams building a Vietnamese WordPress store or content site, a professional Vietnamese website localization service covers content translation, Vietnamese SEO keyword research, and ongoing post-publish review.
FAQ
Is WPML free for Vietnamese?
No. WPML has no free tier. The entry plan (Multilingual Blog) starts at €39/year and supports Vietnamese among 65 pre-configured languages. The CMS tier (€99/year) adds WooCommerce support and automatic translation credits. WPML offers a 30-day money-back guarantee.
Can Polylang free handle Vietnamese hreflang for Google Search Console?
Yes. Polylang free emits hreflang="vi" tags for all public post types automatically once Vietnamese is added as an active language. This is the correct BCP 47 code for Vietnamese per the IANA Language Subtag Registry. Verify the output in Google Search Console under the International Targeting report after setting up the language.
Does WordPress support Vietnamese diacritics in URLs?
Yes. WordPress stores post slugs as UTF-8, so Vietnamese diacritics like ọ, ệ, and ữ are stored and displayed correctly in modern browsers. Some server or CDN configurations may percent-encode UTF-8 slugs in HTTP responses. Set your permalink structure to %postname% and confirm your CDN passes UTF-8 paths unchanged.
Which plugin is best for a Vietnamese WooCommerce store?
WPML CMS tier (€99/year) or Polylang Business Pack (€139/year, combines Pro and the WooCommerce add-on) are the two established choices. WPML includes automatic translation credits and formal Vietnamese support; Polylang Business Pack has a larger free-tier community. TranslatePress also supports WooCommerce from its €99/year Personal plan.
Can I use Loco Translate alongside Polylang or WPML?
Yes. Loco Translate manages .po/.mo translation files for themes and plugins, which is a separate layer from multilingual routing. You can use Loco Translate to translate plugin and theme strings into Vietnamese while Polylang or WPML handles the multilingual URL structure and post routing. The two tools do not conflict.
Official Sources
- WPML official site - pricing tiers, 65 pre-configured languages including Vietnamese, WooCommerce support, and AI translation credits. Verified October 2026.
- Polylang on WordPress.org - 800,000+ active installs, free core plugin features, Vietnamese locale support. Verified October 2026.
- Polylang Pro official site - paid tiers (Pro €99/year, Business Pack €139/year including WooCommerce), hreflang and URL structure details. Verified October 2026.
- IANA Language Subtag Registry - BCP 47 subtag "vi" registered for Vietnamese, the reference standard for hreflang values. Verified October 2026.
- DataReportal: Digital 2025 Vietnam - 79.8 million internet users (78.8% penetration) as of January 2025. Verified October 2026.
Written by Dao Huy (Lucas), Vietnamese translator & localization specialist (EN · ZH · FR → Vietnamese). See translation services →
