The Multilingual Website Myth Costing Irish Businesses Customers

You have probably been told that making your website work in a second language is a big job. A developer. An agency. A translation project, and a few thousand euro before a single word of German or French appears on the screen. I heard a version of it again last week, from a trade-catalogue customer who assumed adding a French section meant starting his whole site over.

It does not. That belief is one of the more expensive misunderstandings in Irish small business right now, and it is wrong on almost every count. Let me take it apart, piece by piece.

The myth is built on a picture of WordPress from a decade ago

Years ago, a second language genuinely did mean custom development. Somebody had to wire up the language switching by hand, duplicate templates, and maintain the lot. That picture has stuck in people's heads. The reality moved on.

Today, a second language on a WordPress site is a plugin you install, not code you commission. The most popular free option, Polylang, sits past 800,000 active installs on the official WordPress plugin directory, holding a 4.7 rating across nearly three thousand reviews. The paid market leader, WPML, runs on well over a million sites. These are mature, battle-tested tools used by an enormous number of businesses.

Here is what that means at street level. A gift shop in Killarney that wants a German version of its opening-hours and online-order pages does not hire anyone. The owner installs the plugin, duplicates the page, drops the German text in, and a language switcher appears in the menu. The customer browsing on their phone taps a flag-free toggle and reads the site in their own language. That is the whole job for a small site.

The reason this is possible at all is that proper WordPress hosting gives you the entire plugin ecosystem, not a curated shortlist. This is the practical difference between a real platform and a walled garden, and I have written before about why the managed WordPress walled garden is a myth worth understanding. When you have full WordPress, multilingual is just one more thing you are allowed to do.

"It costs thousands" is the agency price, not the real one

The thousands-of-euro figure is real, but it describes the old model, not the work. Brief a stranger to translate, build, and maintain your pages in four languages, and you are into agency territory: weeks of lead time, a project fee, and then change requests billed by the hour every time you tweak a price or a paragraph. That is where the number comes from. It is the cost of having someone else stand between you and your own site.

Self-serving the same capability changes the maths completely. With managed WordPress, the language plugin is free or a modest one-off, and the hosting that runs it is already paid for. On Web60's €60-a-year all-inclusive hosting, multilingual is not a per-feature upgrade or a tier you climb to. It is included in the simple fact that you are running full WordPress on infrastructure that handles the heavy lifting.

There is one cost that does not disappear, and I would be lying if I told you otherwise. Good translation of the pages that actually earn you money is worth paying a human for. More on that below. But the platform cost of going multilingual, the part that used to be the barrier, has effectively collapsed.

"Only big exporters need this" ignores who is actually reading

This is the line I hear most, and the data does not support it.

Start with the web itself. W3Techs, which tracks this monthly, reported in June 2026 that English appears on only around half the websites it can identify a language for, roughly 49 to 50 percent. That measure counts sites rather than people and leans English-heavy by its own admission, so treat it loosely. Even so, the headline holds. Half the web is not in English. Your customers are not all in English either.

Then there is buying behaviour. Common Sense Advisory's much-cited Can't Read, Won't Buy study found that roughly seven in ten consumers spend most of their time on websites in their own language, and about four in ten will not buy at all from a site in a language they do not read. That research is well over a decade old now and was run across non-English-speaking markets, so I would not treat the exact percentages as gospel. The direction, though, has not shifted. People trust, and spend, in their own language.

Now bring it home. Ireland drew somewhere around six million overseas visitors in 2025, by the Irish Tourism Industry Confederation's year-end count, spending in the region of five billion euro. France and Germany are among the larger Continental markets. Picture the Friday of a bank holiday in tourist season. A French family lands on a Killarney shop's site to check whether it opens Sunday and whether they can reserve something before they drive down. The page is English-only. They are not going to puzzle through it. They tap back and try the next result. You never knew they were there, and you never knew you lost them.

That is the cost of the myth. Not a dramatic outage. A quiet, invisible leak of customers who could not read the page.

"A drag-and-drop builder does this just as well" is where it gets expensive

This is the part that catches people out. The walled-garden builders advertise multilingual support, and on the surface it looks comparable. Underneath, you are renting a feature on someone else's terms, with the limits and the lock-in that come with it.

The honest comparison is about control. On full WordPress you own the language setup, you choose the plugin, and you can move the whole site, translations included, to another host whenever you like. On a closed builder, the multilingual feature is whatever the vendor decided to give you, priced however they decide, and it does not travel if you leave. I have walked through the broader version of this trade-off in the Wix versus WordPress performance reality check, and language is one more place the same pattern shows up.

WordPress earns its position here for a boring, durable reason. It runs more than four in ten websites worldwide, a touch under 42 percent by W3Techs' June 2026 count, because it does not box you in. Multilingual is a feature of that openness, not a paid extra bolted onto a cage.

The honest limits nobody mentions

Here is the part the plugin marketing skips, and it matters more than any feature list.

Machine translation is not enough for the pages that earn you money. It is genuinely useful for a first draft and for low-stakes content, but auto-translated pricing, booking, and product copy reads as subtly wrong to a native speaker. That wrongness lands at the exact moment you need trust. I learned this the slightly embarrassing way once, trusting an auto-translate setup on a German page for a project and assuming it was fine. A native-speaking colleague read it and winced. The grammar was clumsy enough to undercut the whole pitch. The lesson stuck: machine-translate the draft, have a human verify anything that asks for money or a commitment.

The second limit is maintenance. Two languages means two versions to keep in step. Change your prices on the English page and forget the German one, and you now have a customer reading a number you no longer honour. The discipline is simple but real: when you update one, you update the other. Build the new pages on a staging environment, verify the switcher and the translations, then deploy. Do not edit live and hope.

And the strategic concession, because it would be dishonest to pretend WordPress is always the answer. If your business is large enough that you want a professional service to translate, proof, and maintain every page across four languages with zero involvement from you, a dedicated translation-management service genuinely does that better than self-serving it. That is a real workload with a real budget behind it. Equally, if every customer you will ever serve reads English, a second language is effort you do not need. Build one clean English site and stop there. The point is not that everyone should go multilingual. It is that the ones who should are being scared off by a price tag that no longer exists.

Where a second language actually pays off

Not every business needs this. A few feel it sharply.

• Tourism and hospitality. If overseas visitors book, browse, or buy from you, an English-only site quietly sends a share of them to whoever translated theirs. This is the clearest case in Ireland and the easiest to measure.
• Exporters and trade suppliers. A Waterford manufacturer with a trade-catalogue site selling into Germany or France is asking buyers to evaluate a serious purchase in a foreign language. A native-language product section is not a nicety there, it is table stakes.
• Services with non-English-speaking clients. Clinics, solicitors, and advisers serving migrant communities at home win trust the moment a worried person can read the page in their own language.

If you are none of these, you have your answer, and it is a single good English site.

What this actually means for your site

The skills barrier that made a second language a developer's job is gone. What used to demand custom code is now a click, and what used to demand an agency retainer is now a plugin and a translator you call when it counts. The expensive part was never the technology. It was being locked out of your own site.

So the decision in front of you is no longer technical. It is commercial. Look honestly at who is landing on your pages and failing to read them, and decide whether reaching those people is worth a translator's afternoon and a little ongoing care. If the answer is yes, the platform is no longer the thing standing in your way.

Frequently Asked Questions

Do I really need a multilingual website for a small Irish business?

Only if you actually serve people who do not read English. If every customer you will ever deal with speaks English, one clean English site is the right call. But if you sell to overseas visitors, export to the Continent, or serve a non-English-speaking community here at home, a second language often pays for itself in bookings and enquiries you would otherwise lose.

How do you make a WordPress website multilingual?

You add a translation plugin such as Polylang or WPML, then create a translated version of each page and menu. The plugin handles the language switcher and tells Google which page is which. Because full WordPress gives you the entire plugin ecosystem, nothing about this requires custom development.

Is Google Translate enough for my business website?

Machine translation is fine for understanding the gist of a page, but it is not enough for the pages that earn you money. Auto-translated pricing, booking, and product copy reads as slightly off to a native speaker, and that erodes trust at the exact moment you want it. Use machine translation as a first draft, then have a human check the pages that matter.

Will adding a second language hurt my Google ranking?

Done properly it helps, because you appear for searches in both languages. The key is that each language version has its own clean URL and the correct hreflang tags, which the established multilingual plugins handle for you. Problems only arise when you bolt translation on badly, with duplicate content and no language signals.

Can I add a second language later, after my site is already built?

Yes. Because it is full WordPress, you can launch in English now and add another language whenever the need is real. Build the translated pages on a staging environment first, verify the language switcher works, then deploy. There is no need to rebuild anything you already have.

Sources

W3Techs, Usage statistics of content languages for websites, June 2026

W3Techs, Usage statistics and market share of WordPress, June 2026

Polylang, official WordPress plugin directory listing

Common Sense Advisory, Can't Read, Won't Buy: Why Language Matters

Irish Tourism Industry Confederation, Year End Review 2025 and Outlook 2026