
A company registered in Germany does not always run in German. A logistics firm near Kaiserslautern with Dutch owners. A consultancy in Pirmasens selling into the UK. A practice that serves the American community around Ramstein and the German one the rest of the week. All of them hit the same wall the moment a website is discussed: the people paying the invoice and the people writing the text do not share a working language.
I work in that gap, so this is what it looks like from the inside, and what to check before you hand anyone money.
Where the language actually bites
Design decisions are cheap to argue about in a second language, because nobody is quite sure what was agreed. The expensive misunderstandings are never about colour. They are about scope and about who is responsible for what.
Three examples that come up constantly:
- Content. A studio in Germany will usually expect you to supply text. If your working language is English and your customers read German, somebody has to write twice, and a translator who has never seen the page will produce something accurate and unusable.
- Legal text. An Impressum and a Datenschutzerklärung are German documents governed by German rules, whatever language the rest of the site is in. § 5 DDG does not care that your board meets in English. A studio that says "we do not touch legal text" is telling you where the boundary is, which is useful. A studio that quietly copies a template and hopes is worse.
- Consent. Cookie banners are read by both audiences. If the banner only appears on the German pages, the consent setup is broken, because the English pages are usually the ones loading the extra scripts.
What to ask before you sign
These questions separate a studio that can work across languages from one that merely tolerates it.
- Who writes the German copy, and is it written for the page or translated after the fact?
- Which legal pages do you set up, and which do you hand to a lawyer?
- Does the site run on one content structure with two language versions, or two separate sites that drift apart?
- Who holds the domain, the hosting account and the administration login after launch?
- What happens to the site if we stop working together, and can we edit it without you?
Question four matters more than it sounds. International clients are the group most often locked out, because the local agency held everything and nobody thought to ask.
Two languages, one site
A bilingual site has to be built as one structure with two trees, not one page with a button that swaps the words around. The URLs mirror each other, the German version sits under its own path, and every page declares which language it is in so a search engine sends each audience to the version it will actually read.
Get that wrong and you pay twice. Google sees two near-identical pages, picks one to rank, and quietly throws away the traffic from the other. The visible symptom is a site that appears in one language's results and nowhere in the other, which is usually discovered months later by whoever is unlucky enough to be asked about it.
Two things I insist on. The language switcher labels each option in its own language, because a person who does not read German cannot tell which button to press. And the choice is remembered, so clicking the logo from an English pricing page lands on the English home page rather than dumping you back into German.
What it costs and how long it takes
The build itself is not the expensive part of a bilingual site. A Starter Site is €300 for ten pages and a Business Site is €500 for up to thirty, and a second language tree is more pages rather than a different project, priced at €15 per extra page.
What costs real money is writing. Every page exists twice, the legal layer has to be checked on both sides, and a sentence that is vague in English stays vague when translated. That is why the timeline is anchored to your content, not to my calendar. From the moment text and images are ready, a build runs five to seven working days, with a rush option in one to two days for an additional €120.
If you supply nothing and expect the studio to invent it, you get a site that describes a company nobody recognises. That is the failure mode I see most often with international clients, and it is not a design problem.
Send me your current site and the three things you need it to do, and I will tell you which of these problems you already have.
Send me your URL and I will tell you, in writing, what a fixed-price build covers and what it does not. The plans and the numbers are on the pricing page.
