Translating a WordPress site: automatic plugins or real translations?

You want to open your site to foreign customers and you're facing the classic fork in the road: translate a WordPress site with an automatic plugin that does everything by itself, or invest in curated translations by someone who actually speaks the language? We have offices in Italy and Malta and manage multilingual sites every week: the honest answer is that it depends on what you sell and how much each individual page weighs. Let's look at the options with their real trade-offs.

The three paths to a multilingual WordPress

Simplifying, the solutions on the market fall into three families:

• On-the-fly machine translation: a service translates pages automatically and serves them in the visitor's language. Set up in a few hours, low cost, but control over the text is limited and the quality is the machine's, taken as is.
• Multilingual plugin with managed content: every page exists in every language as separate content inside WordPress. You can start from an automatic draft and correct it, or insert professional translations. More work, total control.
• Separate sites per language: one installation (or one network site) per market, with content that can even differ between them. It makes sense when markets require different offers, prices or communication, not just different languages.

For most SMEs the second path is the sweet spot: it costs more than on-the-fly translation, but it leaves you in control of your texts and your SEO.

What machine translation gets wrong (and where it's actually enough)

Modern machine translators produce fluent text, and that is both their strength and their trap: the errors aren't visible at a glance. The points where they stumble most often are industry terminology (the technical term translated with the wrong synonym), product and service names that shouldn't be translated at all, idioms rendered literally, and the brand's tone of voice, which flattens into a neutral register. On legal pages, terms of sale and texts that create obligations, an automatic error can cost you dearly.

That said, machine translation has a legitimate place: on large, low-risk archives (old blog articles, secondary pages) a quickly reviewed automatic draft is a sensible compromise. The criterion we recommend to clients: the closer a page is to the purchase decision, the more its translation deserves a competent human eye.

Multilingual SEO: where markets are won and lost

Translating the texts is half the job; the other half is making the structure clear to Google. The technical points to watch:

• Correct hreflang tags between language versions, so Google shows each user the right language and doesn't treat the versions as duplicate content.
• Dedicated URLs per language (directories like /en/, subdomains or separate domains): each version needs its own indexable address.
• Translated meta titles, descriptions and slugs: they're your storefront in the SERP and plugins often forget them, leaving Italian titles on English pages.
• Keyword research for each market: people don't search for the literal translation of Italian terms; they search with the words of their own market. A faithful translation of the wrong keyword ranks for searches nobody makes.

This is why "translating the site" and "opening a foreign market" are not the same thing: the second includes the first, plus the SEO work in the target language.

The quality workflow we recommend

In the multilingual projects we manage, the workflow that balances cost and quality works like this. First you define the scope: which pages get translated right away (home, main services or products, contacts, legal pages) and which can wait. Then you produce a draft, automatic or human depending on the budget. Then the review: sales pages and legal pages go through a native speaker or someone who knows the industry in the target language; secondary pages get a lighter review. Finally, the technical check inside WordPress: hreflang, translated meta, menus, forms and automatic emails in the right language, because a form that replies in Italian to a German customer undoes everything else. One last thing: multilingual is a permanent commitment. Every new page will need translating, so choose a number of languages you'll be able to keep up with.

Want a multilingual site built to sell, not just translated?

If you're thinking about taking your site to other markets, the choice of tools and translation workflow needs to be made beforehand, because fixing it afterwards costs twice as much. We build multilingual websites and eCommerce, from the technical structure to the SEO for each language. Book a free call: tell us which markets you want to enter and we'll propose the solution with the best quality-to-budget ratio for your case.