Running a Website in 30 Languages Without Embarrassing Myself

My website is available in thirty languages. Here’s the uncomfortable truth. I can’t read most of them.

Machine translation has made “go global” almost effortless. A few clicks and your site speaks Japanese, Arabic, Finnish, Greek. Then comes the part nobody warns you about. The translation is fluent enough to look completely fine, and wrong often enough to embarrass you badly, in a language you have no way to check. You’re publishing your professional reputation in thirty languages and personally vouching for the quality of maybe two. That gap is a real trap, and here’s how I try not to fall into it.

TL;DR

• Machine translation makes 30 languages easy, and quietly dangerous.
• It’s fluent enough to look right and wrong enough to embarrass you.
• The danger is you can’t spot the mistakes in languages you don’t read.
• The fix: machine translation as a first draft, a human check on languages that matter, and honesty about the rest.
• “Technically translated” is not the same as “actually good.”

Why machine translation is a trap, not a solution

The trouble isn’t that machine translation is bad. It’s that it’s good enough to be dangerous. If it produced obvious gibberish, you’d catch it in a second. Instead it produces smooth, confident, grammatical text that’s subtly wrong: an awkward phrasing, a word with the wrong connotation, a sentence that’s technically correct and reads like a robot wrote it.

In a language you read, you catch those instantly. In a language you don’t, they sail straight through onto your live site. So you end up vouching for the quality of text you literally cannot evaluate. You’re telling Japanese visitors “this represents me” with no idea whether it makes you sound professional or absurd.

A native speaker can tell in one sentence whether text was written by a person or pushed through a machine. Your visitors in those thirty languages can tell too. First impressions don’t get a second try.

“Technically translated” and “actually good” are different things. The gap is invisible until a native speaker points at it.

The approach that keeps me honest

I don’t try to make all thirty perfect. That’s not realistic for one person, and pretending otherwise is how you get burned. Instead I treat it as tiers of confidence.

Machine translation is the first draft, never the final. It’s a starting point, not a finished product. That one reframe prevents most disasters, because it stops me treating “translated” as “done.”

The languages that matter most get a human check. For my priority markets, the places I most want to reach, I get a real native speaker to review. That’s where a bad impression costs the most. You don’t need a human pass on all thirty. You need it on the handful that actually drive your goals. Spend the effort where the stakes are.

I’m honest about the rest. For the long tail of languages I can’t vouch for, the goal is “clear and useful,” not “flawless and native.” Often a clean, simple, machine-assisted version is genuinely fine for a visitor who just needs the information. The mistake is believing it’s better than it is, then being shocked later.

How to prioritise when you can’t do everything

You can’t perfect every language, so the key is to decide deliberately instead of by accident:

1. Which languages actually drive your goals? Where are the customers, the readers, the people who matter? Those get the human check.
2. Which are nice-to-have reach? Machine-assisted is acceptable. Aim for clear and useful, and don’t oversell it to yourself.
3. Which are vanity? If a language adds nothing real, ask whether a possibly-embarrassing version is worse than no version at all. Sometimes the honest move is to not offer a language you can’t stand behind.

Match your effort to the stakes. The failure modes are neglecting everything, or chasing an impossible thirty-language perfection. Both are avoidable.

What this means for any business going international

If you’re expanding into new markets, the broader lesson is simple. Don’t mistake the ability to translate for the quality of the translation. The tools have made the first part trivial. That’s exactly what makes it dangerously easy to skip the second.

Before you put your brand in front of a new market in their language, ask one thing. Can anyone here actually vouch for how this reads to a native speaker? If the answer is no for a market that matters, you have a gap. And it’s a gap your future customers there will notice long before you do, because they’re the only ones who can read it.

What I’d do differently

I’d have prioritised the human review of my key markets sooner, instead of trusting “it’s translated” as good enough for a while. The languages I can read were always fine. It was the ones I couldn’t read that needed attention, and those are precisely the ones it’s tempting to assume are handled. Assume the opposite: the languages you can’t check are the ones most likely to be quietly letting you down.

Machine translation is a fantastic first draft and a terrible final answer. The danger isn’t that it’s wrong. It’s that it’s wrong in a way you personally can’t see, in front of an audience that absolutely can.

So if you run anything in languages you don’t speak: who’s actually vouching for how it reads? Or are you just trusting that “translated” means “good”?