Most WordPress sites are built in one language and never revisited. That’s fine until your analytics start showing a steady trickle of visitors from countries where English isn’t the first language — people who land on a page, can’t quite follow it, and leave within seconds. You don’t need to hire a translator or rewrite every post by hand to fix this. In most sites I build for clients with any international audience, adding AI-powered translation is one of the highest-value, lowest-effort changes available, and it pairs naturally with anyone who has already used AI tools to build a WordPress site faster.
What’s changed is how cheap this has become. A few years ago, multilingual WordPress meant either paying a translator by the word or accepting the reputational risk of an obviously robotic auto-translate widget. Neither is really true anymore — modern translation plugins call the same neural machine translation engines (DeepL, Google Translate, or a provider’s own model) that power Gmail’s inline translation, and the output is good enough that a light human review pass, not a full rewrite, is usually all a page needs.
Three Real Paths, and What Each Actually Costs
There are three genuinely different approaches, and the right one depends on how much control you want versus how fast you want it live.
| Polylang | WPML | Weglot | |
|---|---|---|---|
| How it works | Stores each translation as its own WordPress post; you (or a linked machine-translation add-on) fill it in | Built-in AI translation by default, plus a translation management workflow | Sits in front of your site and auto-translates on the fly, no duplicate posts to manage |
| Free tier | Yes — full manual multilingual support at no cost | No free tier | Free trial only, then paid |
| Entry price | Free; Polylang Pro (machine translation, slug translation) is roughly €99/year | Multilingual Blog tier around $39/year; the more commonly used CMS tier around $99/year | Starter plans begin around €15/month, scaling with total translated word count |
| WooCommerce | Separate add-on purchase, no built-in multi-currency | Integrated multilingual WooCommerce support | Supported, product-by-product |
| Best fit | Content sites that want free multilingual support and don’t mind translating manually or paying once for automation | Stores or content sites that want AI translation and full editorial workflow built in from day one | Anyone who wants a live multilingual site today with the least setup, at an ongoing subscription cost |
For a first attempt at multilingual content on a site with modest traffic, Polylang’s free tier is usually the better starting point — there’s no recurring cost while you find out whether international visitors actually convert. If your budget supports it and you’d rather not manage per-post translation manually, WPML or Weglot both remove that overhead in exchange for a subscription.
Setting It Up
Go to Plugins → Add New and install your chosen plugin. Run its setup wizard, select your site’s default language plus the languages you want to add, and choose a URL structure for translated pages — a subdirectory such as /fr/ or /de/ is the most SEO-friendly option and what most plugins default to, since it lets Google’s hreflang tags point searchers to the correct language version of the same page automatically.
Don’t try to translate the entire site on day one. Start with the homepage, your main service or product pages, and anything in the checkout flow if you run WooCommerce — these are the pages where a confusing or badly translated sentence costs the most. Review the machine translation for these pages manually before publishing; even a few small corrections make the page feel far more trustworthy. Add a language switcher to your header or footer, then test the experience yourself: switch languages, confirm navigation menus and buttons are translated (not just body text), and check that prices, currency symbols, and date formats display correctly for each language on a store.
The Risk Nobody Mentions: Google Treats Bulk Auto-Translation as a Spam Signal
This is the part most translation guides skip, and it matters more than any setup step. Google’s own spam policies for Search list “creating pages by automatically translating content without human review or localization” as a specific example of scaled content abuse — the same policy category used against AI content farms and auto-generated doorway pages. This doesn’t mean AI translation itself is banned; Google’s guidance and public comments (including on large sites like Reddit that translate at scale) are explicit that intent and value are what’s judged, not the use of machine translation as a tool.
What it does mean in practice: publishing hundreds of raw, unreviewed machine-translated pages purely to rank in another language, with no human check and no localisation of things like currency, idioms, or local context, is exactly the pattern the policy targets. The fix is the same discipline covered elsewhere on this site for AI content generally — review before publishing, especially on your highest-traffic pages, rather than flipping on auto-translate and walking away.
Practical Tips
- Keep machine translation switched on for new content, but schedule a periodic pass to tidy up whichever pages get the most international traffic — check this by country in your analytics after launch, since it usually points straight at which language to prioritise next.
- Translate image alt text and metadata too, not just visible page content — both affect how a page performs for international searchers, and both get skipped by default in most setups.
- A high bounce rate concentrated in a handful of non-English-speaking countries is usually a language problem rather than a content or design one, and it’s often the clearest signal that translation will pay off before you spend time on anything else.
Common Mistakes
- Auto-redirecting visitors based on browser language with no way to switch back — this frustrates people who deliberately prefer to read in a second language.
- Leaving machine-translated checkout and pricing pages unreviewed, where a mistranslated word can cause real confusion about cost or delivery.
- Publishing raw machine translations at scale with zero human review, which is the exact pattern Google’s scaled content abuse policy is written to catch.
When Translation Is Worth Adding
AI translation earns its keep once you have real, measurable international traffic and want to serve it without hiring a translator for every post. If your audience is genuinely local and single-language, skip it — it’s added complexity with no upside. For sites with serious volume in one specific foreign market, human translation of your top-performing pages, layered on top of AI translation for everything else, usually gives the best balance of quality and cost. If you’re still working through the step-by-step guide to building a WordPress website, get your core pages right first, then add translation once you have traffic worth translating for — and once you do, the same review discipline applies to AI-drafted blog posts in any language.
Start with one plugin, one extra language, and your highest-traffic pages, review them by hand before publishing, and expand once you see how visitors actually respond.
Etienne Basson works with website systems, SEO-driven site architecture, and technical implementation. He writes practical guides on building, structuring, and optimizing websites for long-term growth.