Multilingual Websites: More Inquiries or More Work?

Why “Just Adding English” Often Backfires

Many freelancers add “English too” to their website because it feels more international and professional. In practice, the opposite often happens: the English version sounds more generic, references are missing, forms are only half translated, and the most important claims are not as clear as in the German original.

The issue is rarely language alone. The issue is a break in trust. When someone clicks an English service page and then sees German pricing, German FAQs, or a German contact flow, they subconsciously ask: Is this really meant for me? Will collaboration work in English? Is this information current?

There is also a technical side. Google recommends separate URLs for different language versions and clear references between those versions. Google also uses visible page content to determine a page’s language. If navigation, main copy, and contact areas are mixed, users become unsure and search engines get a less clean signal.

When Multilingualism Actually Makes Sense

The sensible question is not: “Should we also have English?” The sensible question is: “Does a second language help us get to the right conversations faster?”

If your customers are almost exclusively German-speaking and you do not see regular international inquiries, a second language is usually not a lever, but extra effort. A stronger German website will often do more: clear services, understandable examples, good contact paths, and content that fits your actual target customers.

If you already receive international inquiries, work with English-speaking product teams, or operate in an industry where decision-makers use English internally, an English version can be very useful. Then it is not decoration, but reduced friction: a link can be forwarded internally, a decision-maker understands your offer without a translation loop, and contacting you feels more natural.

If you rarely change your website, multilingualism is easier to maintain. But if you regularly adjust services, add references, explain pricing, or publish blog articles, you need a process. Otherwise, you slowly create a two-tier website: one version is current, the other falls behind.

The Pragmatic Approach

In implementation, the best start is usually small. Do not translate everything immediately. Translate the pages that actually influence decisions first. For a small business website, these are usually the homepage, service page, process, one or two relevant references, and contact. For a software or consulting offer, pricing, technical requirements, or an FAQ may also be decisive.

That is not a weak compromise, but clean prioritization. A second language does not have to cover every subpage. It needs to answer the right questions so a prospect has enough trust to take the next step.

Clear language guidance matters. Each page should be consistently written in one language, including navigation, calls to action, form hints, and error messages. The language switcher should also be easy to find. W3C recommends clearly visible navigation to localized pages on every page and using the target language in its own language, for example “English” and “Deutsch”.

What Has to Be Technically Clean

A multilingual website does not necessarily need a complex system. But it does need a few clean foundations.

First: each language version should have its own URL. Google recommends not relying only on cookies, browser language, or dynamic content replacement on the same URL. Separate URLs are easier to understand for users, search engines, and internal links.

Second: the language versions should reference each other. This is what hreflang references are for. They help Google understand which pages are variants of the same content. The important part is reciprocity: if the German page points to the English page, the English page must point back to the German one.

Third: automatic redirects should be used with care. Google warns against simply redirecting users based on a presumed language because this can prevent users and search engines from accessing all versions. A visible, easy-to-use language switcher is usually more robust.

Case Study: IT Service Provider with Targeted English Addition

An IT service provider works primarily in the DACH region but increasingly receives project inquiries from product teams whose working language is English. Translating every piece of content would have been oversized. A narrower start made more sense: service page, process, two relevant references, contact page, and an English FAQ about collaboration, availability, and invoicing.

The result is not “more internationality” for its own sake. Conversations become concrete faster because decision-makers can forward a clear link internally. At the same time, maintenance stays manageable because not every blog article and every subpage has to appear in two languages immediately.

The Real Effort - Unvarnished

The initial translation is the smaller part. The real effort comes afterward. Every time you rename services, explain pricing, replace references, address a new target audience, or sharpen wording, the same question appears: does the second language need to move with it?

If the answer is often “later”, multilingualism quickly becomes a liability. Then the German page describes a new offer while the English page still describes the old scope. Or a reference is visible in one language but not the other. These differences turn an otherwise strong website into an uncertain signal.

The pragmatic solution is a simple maintenance process: every content change gets a language decision. Either both versions are updated, or only one is updated deliberately - but without pretending that the other version is fully equivalent.