Multilingual Websites: What You Really Need to Know

“Just make an English version” is the most common phrase when it comes to internationalizing websites. And it’s the first step toward chaos. Multilingual websites are more than just translations. They’re a strategic, technical, and editorial challenge.

Three Questions Before You Get Started

The first is: Which languages, really? Not every language makes sense, and “We should definitely include English” is usually not a decision, but rather a way of avoiding one.

Second: Which markets? Language and market are not the same thing. English for everyone is something entirely different from one version for the United Kingdom and a second for the United States, with different references and different prices.

The third is the most difficult: Who will maintain it? A multilingual website requires ongoing editorial work—not just once at launch, but every week. If you can’t answer this question, you shouldn’t even ask the other two.

Translation, Localization, Transcreation

Translation is a word-for-word rendering. It’s cheap, fast, and almost always unsuitable for marketing texts.

Localization adapts content to the target market by using different references, examples, lines of reasoning, and imagery. It’s more expensive, but it works—and without a content strategy tailored to each market, it can’t be managed effectively.

Transcreation goes one step further by completely rewriting content so that it resonates culturally and achieves the same goal.

For B2B websites of small and medium-sized businesses, translation with minimal localization is usually sufficient. For brand websites and consumer goods, transcreation is the standard.

The Technical Models

There are four ways to learn a second language, and one of them is almost always the right one.

Subfolders such as `example.com/de/` and `example.com/en/` are recommended in most cases. A single domain, a clear structure, search engines understand it well, and web development remains manageable.

Subdomains such as `de.example.com` are technically possible, but search engines treat them as separate websites. This is only worthwhile if there are genuine market differences.

Dedicated country-code domains such as `example.de` and `example.fr` offer the strongest localization and the highest SEO value for each country. However, they require the most maintenance because each domain must build its own authority.

Parameters like `example.com?lang=en` are the worst possible solution. They’re bad for SEO, hard to share, and almost no one can read the URL aloud.

SEO for Multilingual Websites

hreflang tags are required and are part of technical SEO. They tell Google which language or country version a page is intended for:

<link rel="alternate" hreflang="de" href="https://example.com/de/" />
<link rel="alternate" hreflang="en" href="https://example.com/en/" />
<link rel="alternate" hreflang="x-default" href="https://example.com/en/" />

The `x-default` entry specifies which version is considered the default. Three rules apply: Each page must link to all language versions of itself; the links must be reciprocal; and the canonical tag is set for each language version individually, not across versions.

These errors recur with astonishing regularity. Automatic redirects based on IP address cause the Google bot from the U.S. to see only the English version, while the rest of the site is indexed poorly. If hreflang tags are missing entirely, Google advises… Incorrect language codes like “en-uk” simply don’t exist; the correct one would be “en-GB.” And if you don’t translate the URLs as well and use `/en/webdesign/` instead of `/en/web-design/`, you’ll lose the rankings you already had.

If you want to strategically build a multilingual website: We plan the structure, technology, and content workflows as part of our web development services.

The CMS decides that in advance

With WordPress, you can choose between Polylang and WPML; WPML offers more features, while Polylang remains more streamlined. TYPO3 comes with multilingual support built in and is very robust in this regard. Headless systems such as Storyblok, Contentful, and Sanity are natively multilingual anyway, as is Craft CMS.

It is not so much the choice itself that matters as the timing of that choice. Adding a second language to a system that was not designed for it after the fact is painful and expensive.

The workflow determines the half-life

There are four questions that need to be answered before the launch. Who will do the translation—an in-house team, an external agency, or AI with proofreading? Who will provide native-speaker proofreading? Who will update the content when a language version changes? And how will you prevent the English version from consistently lagging behind the German one?

Without answers to these questions, a language version becomes outdated within a few months, and then it does more harm than good.

AI Translation: Good, but Not Everywhere

AI translations will be good by 2026. DeepL, ChatGPT, and Claude will provide useful results for first drafts, supporting text, product descriptions, and internal documents.

They fall short whenever nuances matter: in marketing headlines, in brand-related copy, in technical texts with industry jargon, and in legal documents. The rule of thumb is: AI creates the rough draft; humans polish it.

The Language Selector

It belongs in the main navigation or the header. Hiding it in the footer is bad for usability because it’s exactly the users who don’t understand anything right now who are looking for it.

Flags are unsuitable as language symbols because languages are not countries. Spanish is not Spain. Abbreviations such as DE, EN, and FR—or the full name of the language—are better. You may detect the browser language and display a suggestion, but you should never switch it automatically.

Don’t forget the legal stuff

The privacy policy must be available in every language, tailored to the respective legal framework. The legal notice is mandatory in Germany and is typically included in translations of international versions. The terms and conditions must be translated and then reviewed by legal counsel, and the cookie banner must be displayed in the respective language.

Conclusion: Multilingualism means taking multiple approaches

Multilingual websites are not simply a matter of translation. They are a strategic decision with editorial, technical, and organizational implications.

If you plan it right, you’ll tap into new markets. If you approach it halfheartedly, you’ll end up with yet another problem to deal with. This decision should never be made on the fly.