Naming for a multilingual EU market: the cross-language gotchas

To avoid a name that means something bad in another EU language, test it with people rather than dictionaries: put your shortlist in front of native speakers of every market you plan to sell in, have them say each name aloud, and ask what it sounds like — slang, playground words, and near-misses included. Translation tools won’t save you, because the danger almost never lives in the dictionary definition; it lives in slang, pronunciation shifts, and false friends. Mitsubishi learned this at industrial scale: “Pajero” is vulgar Spanish slang (roughly “wanker”), which is why the SUV was sold as the Montero in Spain and the Americas and the Shogun in the UK. A car maker can swap badges per market. Your domain name can’t — which is exactly why this check has to happen before you register anything.

Why does the EU make this problem so acute?

The EU has 24 official languages inside one single market. That combination is what makes European naming harder than naming for the US or for a single country: the moment your site is live, it’s visible — and pronounceable — in Finnish, Portuguese, Greek, and everything in between, whether you’ve “launched” there or not. A Dutch customer, a German journalist, and a Spanish investor will all encounter the same name on the same domain in the same week.

Multinationals historically escaped this with per-market renaming. Mitsubishi ran Pajero, Montero, and Shogun side by side; Vicks trades as Wick in Germany and Austria. That escape hatch barely exists for an internet-first company: one product, one domain, one social handle — the name you pick is the name every language gets. The filter a car company could apply market by market, you have to apply once, up front.

The upside: this is a cheap check with a huge payoff, and it slots neatly into the testing pass of the broader naming process — if you’re still building your shortlist, start with how to name a startup and treat this article as its European extension.

Which brand names actually went wrong across languages?

Stick to documented cases — there are enough real ones.

Mitsubishi Pajero → Montero / Shogun. The canonical example above: vulgar in Spanish, renamed for Spanish-speaking markets and the UK.

Honda Fitta → Jazz / Fit. The near-miss that shows the process working. Honda was heading toward launching its small car as the “Fitta” — vulgar slang for female genitalia in Swedish, and phonetically awkward in Spanish and Italian too. Honda’s pre-launch multi-market naming review caught it, and the car shipped as the Jazz in Europe and the Fit in the US. Caught before launch, it cost a meeting; after, a rebrand.

Vicks → Wick. The subtlest one, because nothing is wrong with the word — only with how it’s pronounced. A native German reading of “Vicks” turns the V into an /f/ sound, landing uncomfortably close to a German obscenity, so the brand sells as Wick in German-speaking markets. The lesson: a name can be perfectly clean on paper and still fail out loud. Always test pronunciation, not just spelling.

Rolls-Royce Silver Mist → Silver Shadow. By the widely reported account, the car that became the Silver Shadow was headed for the name “Silver Mist” — until someone noted that Mist is German slang for manure, a poor look in a key luxury market. A textbook false friend: an evocative English word that’s an insult one border away.

Buick LaCrosse → Allure. Not an EU case, but the sharpest proof that one language isn’t one market: “LaCrosse” collides with vulgar Québécois slang, so GM sold the car as the Allure in Canada — then reverted a few years later to align with US marketing. Clearing “French” with a Parisian doesn’t clear it with a Québécois; slang is regional.

IKEA Fartfull. For levity: IKEA shipped a children’s workbench called the Fartfull in 2004 — “full of speed” in Swedish, something else entirely in English. A reminder that English is a target language too, not just the source.

Which famous naming disasters are actually myths?

The most famous story of the genre — Chevrolet supposedly flopping in Latin America because “Nova” reads as no va, “doesn’t go” — is false. The two are pronounced with different stress, no Spanish speaker would describe a broken car as “no va” (they’d say no funciona), and the Nova actually sold well in Mexico and Venezuela, beating GM’s expectations in the latter. Yet the tale still circulates in marketing textbooks decades after being debunked.

That’s worth internalizing for a practical reason, not a pedantic one: cross-language naming folklore is unreliable in both directions. Famous “disasters” turn out fine, and genuinely dangerous names sail through because nobody famous stumbled on them first. If your due-diligence process is “I skimmed a listicle of naming fails,” you’re checking your name against legends. Verify against real speakers of real languages — the same standard you’d want applied to your own name.

How do you check a name across EU languages before committing?

A workable process for a small team, in order:

1. Say it to native speakers — out loud. Not “does this word mean anything?” but “say this, then tell me what it sounds like or reminds you of.” The Vicks and Fitta problems only surface aloud or in slang; a written glance misses both.
2. Ask specifically about slang and false friends. Dictionaries flag definitions, not connotations. Prompt your reviewers for rude words, playground words, and near-homophones — and remember slang is regional, so a French check isn’t a Québécois or Walloon check.
3. Test pronunciation per language. Letters shift value across the EU: V can become /f/, J can become /y/, stress moves. A name that’s elegant in one phonology can be unsayable — or unfortunate — in another.
4. Test the full domain, not just the word. Your name will mostly be read as name.eu or name.de, and the TLD can create new word boundaries or readings. Check the exact strings you’d register, extension included.
5. Prioritize ruthlessly. You won’t exhaustively clear 24 languages, and you don’t need to. Cover your launch markets, the big EU languages, and English at native-speaker depth, and accept a truly obscure collision as survivable risk.

Five checks, a handful of coffee chats, one afternoon — cheap insurance against renaming your company in year two. And if your shortlist just got thinner, the Domain Yoga generator is built for exactly this loop: generate a fresh pool of brandable, available names, and bring the survivors back to your native speakers.