Multilingual Websites: Structure, hreflang and Upkeep

The decision for a second language is not a matter of taste but a calculation. On the credit side sits additional revenue from a market your own language currently excludes. On the debit side sit translation, duplicated editing, duplicated legal texts, duplicated upkeep with every price change, and a second channel that wants answering as soon as enquiries arrive. Germany is an exporting country: goods worth roughly 1.56 trillion euros (Federal Statistical Office) left the country in 2024. Sales abroad are therefore real for many companies - they simply run through field sales, trade fairs and existing customers rather than through the website. That is exactly where the assessment starts.

Three signals carry weight. First, the export share: anyone already making noticeable revenue outside the German-speaking area has an audience that currently finds nothing on the website. Second, the enquiries: if English-language emails, callback requests or tenders come in regularly, demand is documented and nobody has to estimate it. Third, recruiting: companies hiring internationally need a careers page that is comprehensible without German. If all three signals are absent, a second language is usually premature. The budget is then better spent on content marketing for small and medium-sized businesses in the home market.

hreflang is the annotation with which a page reaches out to its language siblings. It tells the search engine: this page also exists in English, and here is the address. The annotation is a signal, not a directive (Google Search Central) - it influences which version a user is shown, but it does not replace good content work. It can be placed in three locations: in the head of the page, in the HTTP header for files such as PDFs, or in the XML sitemap (Google Search Central). For most websites the head of the page is the simplest option, because the annotation is then maintained together with the page and is created automatically whenever a new page is added.

The most important rule is the return link. If the German page points to the English one, the English page has to point back - and both additionally list themselves. Without the reciprocal reference, the search engine may ignore the entire annotation (Google Search Central). Then there is x-default: this entry points to the version for everyone who cannot be matched to a maintained language, typically a home page with a language choice (Google Search Central). Language codes follow ISO 639-1, the optional region follows ISO 3166-1 Alpha 2 (Google Search Central); de-AT is therefore German for Austria, while en alone is English without a region. Anyone also working with structured data and rich results carries them along per language version so that search results look complete in both markets.

Machine translation is good enough today to deliver a raw text, and rarely good enough to publish it unseen. The difference lies less in grammar than in specialist vocabulary, in the form of address and in the terms people actually search for in the target market. A service page translated word for word may name your service correctly - but not the way potential customers name it. That is why the order matters: translate by machine first, then edit professionally, then align with the search terms of the target market, just as is customary when writing SEO copy.

The effort is worth it because language carries trust. 65 percent (CSA Research 2020) of respondents prefer content in their language even when the translation quality is mediocre - which shows how strong the need is, but provides no excuse for weak copy. And 73 percent (CSA Research 2020) want to read product reviews in their own language. For shops that means user-generated content belongs in the language plan as well, not just the editorial pages. Anyone running reviews therefore decides deliberately whether they are translated, filtered or shown separately per language market. The same consideration applies to guide content created in content marketing: not every article has to appear in both languages, but every decision against it should be an actual decision.

The most expensive mistake does not happen during the build but afterwards. A price change is entered in German, the English page stays as it was. A new service appears, the counterpart is missing. After two years the two versions have drifted so far apart that reconciling them costs more than the original build. This can be prevented with one simple rule: a change is only finished when it exists in both languages or has been deliberately documented as an exception. That rule needs a place - a task list in which the second language is a step of its own and not a good intention.

A regular review comes on top. A fixed rhythm makes sense, checking three things: whether every page has its counterpart, whether the hreflang annotations run in both directions, and whether no listed address points into the void. Such checks are quickly done when they happen regularly and laborious when they are left lying around. In ongoing website care this is a fixed item, because in our experience that is the only way multilingual support holds up over years. For smaller websites a quarterly rhythm is usually enough, while shops with frequent range changes need a shorter cadence.

Multilingual support is not a translation project but a decision about structure, technology and editorial routine. Planning it in from the start produces a website that works in two markets without the upkeep hurting twice. That is exactly how we work: we build the design and structure of the website bilingually from the outset, set up online shops with separate price, shipping and legal details per language market, and use search engine optimisation to give each language market its own visibility - with one contact person and clear fixed prices.