A company decides to enter the German market, orders a translation of its website, publishes it and waits for leads. Three months later, visitors from Germany are still rare. Usually the problem is neither the product nor the translation itself, but how that version is built technically and how well it matches what local customers expect.
Translation and localization are not the same
Translation carries the meaning. Localization makes the page read as if it was written for that market. German buyers search with different words, read prices and dates differently and expect other payment and contact options.
- Keywords. Research them again for German search instead of translating them. A literal translation of a query often produces a phrase nobody types.
- Formats. Prices in euros with a decimal comma: 1.490,00 €. Dates as 03.10.2026. Phone numbers with +49.
- Tone. The formal "Sie" in business copy, specifics instead of loud promises.
URL structure: one address per language
Search engines need to see every language version as a separate page. The simplest reliable setup is folders on one domain, for example site.com/de/. They inherit the authority of the main domain and are easy to maintain.
What to avoid: switching language only with JavaScript or a cookie without changing the URL. Google then often sees one version, and the rest simply does not exist for it.
Hreflang: telling search which version to show to whom
The hreflang attribute tells search engines that pages are language variants of each other. This way a user in Germany gets the German version in results, not the Ukrainian one.
- Each version links to all the others and to itself.
- Links are reciprocal: if German points to English, English must point to German.
- The x-default value sets the page for all other languages.
- Each version has its own canonical pointing to itself, not to the main language.
Hreflang mistakes do not break the site, so they can go unnoticed for months. Check the markup right after launch and every time you add a language.
Trust: what German customers check first
Buyers in Germany pay close attention to transparency. An Impressum page with company details, a clear privacy policy and GDPR-compliant cookie consent are mandatory for a commercial website there. Missing them puts customers off before they even read about your services.
Add reviews and case studies from the region if you have them, list payment methods familiar to the market and the real hours when you reply.
Speed and meta tags in every language
Each language version needs its own title and description, translated social media markup and images with captions in the right language. The site should load equally fast from Europe: if the server is far away, a CDN helps.
A short pre-launch checklist
- Keywords researched for German search.
- Each language has its own URL, such as /de/.
- Hreflang and canonical set up and validated.
- Title, description and alt written in every language.
- Impressum, privacy policy and cookie banner in place.
- Forms, currency, dates and phone numbers in local format.
- Language versions included in the sitemap.
A multilingual website pays off when each version is built for its market rather than just translated. If you plan to enter Germany or another EU country, get in touch and we will look at what your website needs.