Building a multilingual website for the German market: what to decide first

A multilingual website for the German market lets buyers in Germany, Austria and Switzerland find you in their own language and meet a company they are willing to trust. Translating your existing pages is not enough: German needs its own addresses, text that is written in German rather than converted into it, and the information German buyers look for before they get in touch. Below are the decisions to make first, what drives the cost and the questions to ask your agency.

Do you need a German-language website?

You need one if your customers decide in German. Three typical situations:

• You sell to German companies, or want to. A buyer you meet at a trade fair will look at your website the same evening. If it is English only, it signals that you have not really arrived in their market yet.
• German buyers should be able to find you. A company in Munich or Vienna searching for what you offer searches in German. If your site has no German version, you are not part of that search.
• You are expanding across the DACH region. Germany, Austria and German-speaking Switzerland share a language but not every expectation, and your website is often the first place where that difference shows.

If you only work with a few large international accounts that buy in English, a short German company page may be enough for now. A full German site that nobody maintains does more harm than good.

Germany, Austria, Switzerland: one version or three?

For German-speaking buyers, a single German version is often enough, but not always. What matters is whether anything actually differs for the customer.

• One version is enough when prices, contacts, delivery terms and offer are the same in all three countries. Three near-identical versions would mostly mean three times the maintenance.
• Separate country pages pay off when you invoice Swiss customers in francs, have different delivery times or legal terms, or offer a different range.
• Switzerland is not only German. French- and Italian-speaking Switzerland need their own language versions. Swiss German spelling also omits the letter "ß", so text written specifically for Swiss customers should follow that.

On our own website we deliberately use the spelling that is standard in Germany, because Germany is our main market. It is a small decision, but it should be a decision rather than an accident.

Translate, or write in German?

This is the decision that most determines whether a German website brings in business. A translation carries over what your English text says. A German buyer, however, is not looking for your English text; they are looking for the answer to their own question.

A real example from our own site: in English, the usual term for what we offer is "ecommerce development". Translated literally into German, you get a phrase that German buyers rarely search for. German buyers search for "Onlineshop erstellen lassen", roughly "have an online shop built", and our German page is titled around exactly that. The literal translation would be correct, and almost nobody would find it.

Machine translation is useful as a first draft and often surprisingly good. The problem is text that nobody who writes German properly has reviewed. Google lists automatically translated pages that add no value among its examples of scaled content abuse. Our own rule: no text goes live in any language until someone who writes that language like a native speaker has read and approved it.

German business writing also has a register of its own. Customers are addressed formally ("Sie"), claims are expected to be specific rather than enthusiastic, and superlatives that sound confident in English can read as unserious in German.

What German buyers check before they trust you

Before taking a supplier seriously, German buyers look for a few things. Some of them are about trust; some are legal requirements.

• Legal notice (Impressum). Commercial digital services in Germany must make certain information easily accessible: company name, address, legal form, representatives, contact details including email and, where applicable, trade register and VAT numbers (Digitale-Dienste-Gesetz, section 5). German buyers look for this page in the footer. If it is missing, many will not take you seriously.
• Privacy notice (Datenschutzerklärung). If your site uses a contact form, cookies or analytics, you need to explain what data you process and why, in line with the GDPR. A translated privacy policy from another market is rarely enough; it has to describe the tools your site actually uses.
• Complete contact details. A full address, phone number, email and business hours. A contact form on its own often looks less transparent to German buyers.
• Formal address. Texts that address the customer informally can feel friendly in English and unprofessional in German.

This section is not legal advice; obligations depend on your company and set-up. But a German site that leaves these points out loses the first impression before it has started.

What drives the cost of a multilingual website?

The price depends less on the number of languages than on the amount of text per language. Design and technical foundations are built once; every language adds its own text and upkeep. When comparing quotes, look at these points:

Cost driver	Why it matters
Number of pages and products	Every page is written in every language; 10 and 500 products are different jobs
How the text is produced	Reviewed machine draft, translation agency or rewriting: three price levels
Keyword research per language	Needed to be found; missing from many quotes, so ask
Text inside images	Graphics with English text need new versions for German
Legal pages	Legal notice and privacy notice for the German market
Maintenance	Prices and products change in every language at once

One warning sign: if a quote promises "unlimited languages for a fixed fee", the texts will very probably be machine-translated only. Ask, and get the answer in writing.

Being found in German search

Most of the technical detail is your agency's job. To check that it is done properly, you only need to know three things.

First: every language has its own address. German pages live under yourdomain.com/de/, English pages under yourdomain.com/en/. Google indexes each language separately and shows German searchers the German page. For small and medium-sized companies this is the lowest-maintenance structure, and Google explicitly supports it.

Second: the addresses are written in the page's language. On our site the same service page lives at three addresses: /leistungen/webdesign-onlineshop in German, /hizmetler/web-tasarim-e-ticaret in Turkish and /services/web-ecommerce in English. Searchers see the address in the results; one in their language, containing their search term, is more likely to be clicked.

Third: the language versions point to each other. The German page tells Google where its English and Turkish equivalents are, and Google shows each person the right language. The technical term is "hreflang", and your agency sets it up. When we reviewed our own site before launch, we found these signals were being generated in two places and contradicted each other, and we fixed it. Mistakes like this are invisible on the page, which is why the questions below matter.

How a project runs, step by step

A well-run multilingual project usually follows the same order. Knowing where you are makes it easier to spot what is missing.

1. Choose markets and languages. First decide which buyers in which countries you want to reach. The languages follow from that, not from "the more, the better".
2. Research search terms per language. For each market, find out how buyers search and what they ask. Page titles, addresses and product names are chosen from that list.
3. Settle structure and addresses. Addresses, language switching and how the versions link up are decided before launch. This is the step that is most expensive to change later.
4. Finish the source text. Write a complete text in the language you describe your company best in, often English.
5. Write and review each language. Each language is adapted based on its own research and read by someone who writes it like a native speaker. Units, currency and contact details are adjusted for the market.
6. Add the legal pages. Legal notice and privacy notice are prepared for the German market and match the tools the site actually uses.
7. Publish and measure. After launch, measure which countries, languages and searches bring visitors. That data shows which language is actually bringing enquiries and where more effort will pay off.

The step most often skipped is the second. Without search research, you end up with translated pages that nobody finds.

Questions to ask your agency

Ask these in writing when you request quotes. The answers show whether your German website is being built to bring in business or just to contain translated pages.

1. Will each language have its own address, or will a plugin switch the language?
2. Who writes or translates the texts, and who reviews them as a native speaker?
3. Will there be separate keyword research for German?
4. Will the addresses be in German on the German pages?
5. Will the language versions be linked correctly for Google (hreflang)?
6. When a visitor switches language, will they land on the same page in the other language, or on the home page?
7. Will visitors be redirected to a language automatically based on their location? (Google advises against it.)
8. Will a legal notice and privacy notice be prepared for the German market?
9. Can I edit the texts in every language myself?
10. What would it take to add another language later?

If you cannot get a clear answer to any of these, revisit the scope of the quote.

Costly mistakes

Most mistakes can be fixed later. A few become expensive once the site is live.

• Changing the address structure after launch. If you change the language addresses of a live site, every old address needs a redirect and your rankings will be unsettled for a while. Get this right from the start.
• Choosing languages by flag. A flag stands for a country, not a language. German is spoken in Germany, Austria and Switzerland; English in many countries. Write the language name in the menu.
• A half-finished language. A German home page with English product pages leaves a worse impression than no German version at all.
• Forgetting forms and emails. If the page is in German but the form's error messages or the automatic confirmation email are in English, the buyer stumbles at the very first contact.
• Different information in different languages. If a price or phone number is updated on the English page but not on the German one, the buyer no longer knows which to trust.

A well-built German website is the first and longest conversation you have with a buyer you have not met yet. Holding that conversation in their language, around their questions and with the information they trust often matters as much as the quality of what you sell.