A multilingual website is worth building when a meaningful share of your buyers genuinely prefers another language, and a maintenance liability when it is built for vanity. Two languages means two sites to keep true forever, so the decision deserves the same honesty as any scope decision. Here is when it pays and how to do it properly.
When translation actually pays
The signals: analytics showing real traffic from another language region, sales conversations already happening in that language, or expansion plans with budget behind them. Serving EU markets from an English-only site leaves money with local competitors, trust rises sharply in a buyer’s own language, and in some sectors and regions, local language is effectively mandatory for credibility. Absent those signals, a better English site beats a mediocre bilingual one every time.
Machine, human, or the honest hybrid
Raw machine translation embarrasses brands in exactly the trust-sensitive places that matter: headlines, idioms, legal pages. Full human translation is best and priced accordingly. The defensible middle for most businesses: machine translation as the draft, native-speaker review for everything customer-facing, and human-first treatment for the money pages, home, pricing, contact, and proof. What cannot be outsourced is nuance decisions: product names, tone, and what stays untranslated.
The technical layer, briefly
Three rules carry most of multilingual SEO. Each language lives at its own crawlable URL (a /de/ folder or subdomain, never a JavaScript toggle that swaps text in place). Hreflang tags tell Google which page serves which language so searchers land on their version, structured data included per language. And the language switcher stays visible, human-labeled (“Deutsch”, not a flag, flags are countries, not languages), and takes visitors to the same page they were reading, not the foreign homepage.
Design consequences nobody warns about
Translated text runs long, German famously so, which breaks buttons, navigation, and tight layouts designed on English lengths; test layouts with the longest language early. Dates, currencies, and forms need locale treatment (name order, address fields, phone formats). And content operations double: every article, price change, and legal update now happens twice, which is where a structured content setup earns its keep and ad-hoc page editing collapses.
The staged path that works
Translate the money pages first, measure whether the new language earns traffic and inquiries, then expand to content. Committing the whole site on day one is how businesses end up with a stale second language quietly undermining the trust it was meant to build.
Weighing markets and languages for your site? hello@beconfidency.agency, we will scope the staged version honestly.
Choosing the right platform and building on it properly is the core of our web development service.