The Best Multilingual Tools for WordPress

Multilingual sites look simple in the proposal: “Add a Spanish version.” Then the real questions show up. Is it a translation of the same content, or different content per country? What happens to SEO? Who keeps the translations updated? What does it cost a year from now?

The answers in this thread leaned on a few familiar names, but the most useful parts were the gotchas, so we’ve given them their own section.

This post is a summary of a Tuesday Toolbox discussion inside The Admin Bar community, where agency owners shared the multilingual solutions they use and what they like about them.

The Most Mentioned Multilingual Tools

These came up repeatedly in the discussion:

• WPML
• Polylang
• TranslatePress
• Weglot
• DIY

A number of other tools came up as well (we’ll get to those).

Why Agencies Choose These Multilingual Tools

WPML

The most-mentioned option, and the one people reach for when things get complicated.

WPML came up more than any other tool in the thread. The pattern was clear: it’s the pick for complex builds, and compatibility is the reason.

“WPML is the gold standard.”

Paul Sallaway

Melbod Salimzadeh called it the safest plugin because almost all other plugins are compatible with it. Irene Koukia likes that it’s compatible with almost everything and that she can export data easily for translation and localization. Satoshi Fujita put the dividing line clearly: WPML is the only option when you need a complex setup, while Polylang or TranslatePress are enough for simple ones. Jean-Francois Arseneault’s team uses it mainly for complex eCommerce needs.

A few members are there partly because of history. Todd Edelman has been on it since the lifetime license was offered many years ago and “kinda just stuck it out.” Mario Marquez Tagliaferro said the lifetime deal was a great one.

Not everyone is thrilled. Priscilla Morris said she’s used it “but I hate it at the same time,” and has since moved to Polylang for what she needs.

Best fit: complex multilingual builds, especially eCommerce, where plugin compatibility and structured translation workflows matter more than simplicity.

Polylang

The lighter option, and the favorite for smaller projects.

Polylang was the second most-mentioned plugin, usually recommended as the simpler alternative to WPML.

“PolyLang does what I need without the bloat.”

Tro Bakerdjian

Jean Werk said that if you only need two languages, the free version is perfect. Irene Koukia agreed: Polylang free is fine for bilingual sites where the client doesn’t want to pay for a plugin, though she still prefers WPML overall. Melbod called it the lighter option for small projects. Patrik Kekäläinen and Satoshi Fujita also named it for simple setups.

Best fit: small or bilingual sites where the budget is tight and the structure is straightforward.

TranslatePress

Easy to use, with a caveat on SEO.

Linus Ahimsa chose it for his workplace because of its simplicity and compatibility with most plugins. Sebastián Bórquez uses it, though he wants to try Clonable. Patrik Kekäläinen lists it alongside Polylang.

Jean-Francois Arseneault shared the main gotcha: his team tried TranslatePress, but even for a static site they had to hack things to get proper SEO support, which is why they went to WPML.

Best fit: simple sites where visual, front-end translation is a priority and SEO requirements are modest. Test your SEO needs before committing.

Weglot

Quick to set up, with a pricing model that put some people off.

Weglot came up from two members. Dan Stramer recommended trying it, but Jean-Francois Arseneault said the pricing was a deal-breaker for his team: you keep paying for translated content over time.

Best fit: agencies who want a hosted, fast-to-launch translation layer and have reviewed how the ongoing cost scales with content.

DIY

No plugin at all: ACF, custom post types, and hand-built links.

Luis PW’s setup was the most detailed comment in the thread. For a bilingual site (English and Spanish), he skipped translation plugins entirely, using ACF and Breakdance.

Every piece of content exists twice, as a Spanish post and an English one. Posts are a separate custom post type, and English pages live under /en/. A small ACF field group links each pair with a language field, the URL of the twin, and a repeater for hreflang tags, which a small snippet prints in the head. Categories get the same treatment. Breakdance handles separate headers per language and a switcher that reads the twin’s URL.

What he likes:

• Zero plugin overhead, no lock-in, a clean database, and full control over slugs
• Hand-picked slugs for each language, rather than literal translations, which can help SEO

What could be better:

• Change a slug and the pair breaks silently, because the links are stored as absolute URLs, so you have to fix both sides
• WordPress still outputs lang="es" on English pages, since it only knows one site language. He fixed it with a small filter on language_attributes and the SEO plugin’s og:locale
• Translation is entirely on you, with no auto-sync

His verdict: for a two-language content site it’s been rock solid, but with five or more languages he’d probably go with a plugin. He added that using Claude or ChatGPT for the grunt work (creating the twin, filling in fields, checking pairs) makes it easier to maintain than when he built it by hand.

Austin Siewert has a similar philosophy from a different platform: Craft CMS handles this “with its site and localization feature,” managing content at the entry level.

Best fit: two-language content sites where you’re already writing both versions by hand and want total control over URLs and SEO.

Notable Mentions

These also came up in the thread:

• GTranslate: Alex Celeste used it on two sites that needed it but lacked the staff to support a full multilingual website, so the Google Translate integration filled the gap
• Google Translate plugins: Chris Wilcox called a Google Translate plugin the easier option versus Joomla’s native multilingual features, which he considers perhaps the “better” solution but far more work
• Bogo: Jean Werk called it “very basic but entirely free,” and uses it on a personal blog
• Loco Translate: Jean Werk suggested it for translating text strings inside plugins
• Clonable: Sebastián Bórquez wants to try it
• Nagatapress: Daniel Schiffner mentioned it with no details
• Lingocode Translation Management: Rose Newell is building her own tool, which she hasn’t released yet and is still deciding how to license. She says it uses native WordPress features, so it doesn’t slow the site down, and that it has stronger SEO and alt-text support than the alternatives. Since it’s unreleased and self-reported, treat it as something to watch, not a recommendation.

Gotchas to Avoid

The prompt asked for gotchas, and members delivered. These are the ones that came up:

• Translating strings is not the same as managing per-language content. Satoshi Fujita called this the pitfall: many solutions only translate strings and can’t create custom content per language. He almost always needs different content for each country, not just translated copies. Decide early which one the project needs.
• SEO support varies a lot. Jean-Francois Arseneault’s team had to hack TranslatePress to get proper SEO even on a static site. Luis PW’s DIY route gave him full control over slugs and hreflang, at the cost of doing it himself.
• Ongoing cost models differ. Weglot’s pricing (paying over time for translated content) was a deal-breaker for one team, while WPML’s lifetime license is part of why some members have stuck with it.
• Plugin compatibility is a real differentiator. WPML’s compatibility with almost everything is why it keeps being recommended for complex builds.
• Slugs can break silently in custom setups. If you link translations by absolute URL, changing one slug breaks the pair without warning.
• WordPress only knows one site language. Without a plugin handling it, you’ll see the wrong lang attribute and og:locale on your other-language pages.
• Someone still has to do the translating. Priscilla Morris’s comment that she can’t be bothered to translate her own site anymore is funny, but it points to the real maintenance problem. Alex Celeste’s team used Google Translate because they didn’t have the staff to maintain a full multilingual site.

Patterns We Noticed

A few things stood out across the thread:

• WPML is the complex-build default, but not an enthusiastic one. People recommend it for compatibility and structure, with the occasional “I hate it at the same time.”
• Polylang is the simple-build default. For two languages or tight budgets, it came up again and again as enough.
• Complexity decides the tool. Almost every answer split the same way: simple sites get Polylang or TranslatePress, complex ones get WPML.
• Lifetime licenses create loyalty. Several WPML users are there because of an old lifetime deal.
• Machine translation is a legitimate answer when staff time is short. GTranslate and Google Translate plugins came up for sites that need multilingual access but can’t maintain full translations.
• DIY is viable for two languages. Luis’s setup is a clear example, and he noted AI tools make it easier to maintain.
• The real question is about content, not plugins. Do you need the same content in several languages, or different content for different markets? Many of the gotchas come from answering that too late.

How to Choose the Right Multilingual Tool

These questions can help narrow it down:

• How many languages do you need, now and later?
• Is it the same content translated, or different content per language or country?
• How complex is the build? Is there eCommerce, custom post types, or lots of third-party plugins?
• How important is SEO control over slugs, hreflang, and metadata?
• Who will translate the content, and who will keep it updated?
• What will the tool cost over time, including renewals and translated-content fees?
• Does the client want to pay for a plugin license at all?

Frequently Asked Questions About Multilingual WordPress Sites

What is the best multilingual plugin for WordPress? WPML was the most mentioned, mainly for complex builds, because of its compatibility with nearly everything. Polylang was the most recommended for simpler sites, and its free version was called perfect for two languages.

WPML or Polylang? It depends on complexity. Members consistently recommended WPML for complex setups, such as eCommerce, and Polylang for simpler or bilingual sites. Polylang was described as lighter, while WPML was described as the safest for compatibility.

Is there a free multilingual plugin for WordPress? Polylang’s free version was recommended for two-language sites. Bogo is a very basic, entirely free option. Loco Translate was suggested for translating strings inside plugins.

Can I build a multilingual WordPress site without a plugin? Yes. One member built a bilingual site using ACF, a custom post type, hand-linked translations, and a small snippet for hreflang tags. It gives full control over slugs and SEO, but translation is manual, links can break when slugs change, and he’d likely use a plugin for five or more languages.

Is Google Translate good enough for a multilingual website? It can work when you don’t have the staff to maintain full translations. One member used a GTranslate-style plugin on two sites for this reason. It’s a trade-off: quicker and easier, but without the control over content and SEO that proper translated pages provide.

What are the biggest gotchas with multilingual sites? Whether the tool handles per-language content or only string translation, how well it supports SEO (slugs, hreflang, metadata), what the ongoing costs are, and who will maintain the translations. These all came up in the thread.