Multilingual Web Design 2026: An Architecture That Holds Up
Simon HeistermannOwner
4 min readPublished on January 14, 2026Updated on September 09, 2026
This article was written with AI assistance and editorially reviewed.
Contents
A second language version is quick to set up technically and rarely thought through properly. Translate and publish without more, and you give away most of what a multilingual website can actually deliver.
A multilingual website only pays off with a clean URL structure, correct hreflang, and copy written for each market rather than merely translated into it. Miss any one of these, and the benefit falls well short of the effort.
When multilingual is worth it
A second language version pays off where a genuinely relevant audience actually searches in that language: international B2B positioning, offerings relevant to Austria or Switzerland, or brands with a clear ambition beyond German-speaking markets. For a purely local trades business with no international customers, a second language rarely delivers a measurable benefit and mostly means extra maintenance.
URL architecture: subdirectory, subdomain, or separate domain
The core technical decision comes down to three options that differ meaningfully in maintenance effort and SEO impact:
| Architecture | Example | When it makes sense |
|---|---|---|
| Subdirectory | example.com/de/ | The right choice for most cases, inherits domain authority |
| Subdomain | de.example.com | Only for content or teams that are organisationally separate |
| Separate domain | example.de | Only with a very strong, standalone presence per country |
Our own website uses a subdirectory model with /de/ and /en/, built with next-intl: every route exists under a localised path, and every language version stays part of the same domain, benefiting from its overall strength. For most multilingual small and mid-sized business sites, that is the more pragmatic solution, since it stays maintainable with a manageable technical footprint.
Getting hreflang right
Whichever architecture you choose, hreflang tags are the signal that tells Google which version is meant for which language and country. Miss that signal, or set it incorrectly, and Google can surface the wrong version in the wrong results, or the two versions end up competing against each other unintentionally. On our own site, every page is linked to its counterpart in the other language via hreflang, including x-default for visitors without a clearly matching language setting. How to get this right specifically across several German-speaking countries is covered in Hreflang for DACH.
Translation is not localisation
Translation replaces words; localisation adapts content to a market. For most small and mid-sized business sites, a clean translation with local context is enough: prices in the target market's currency, dates formatted the way that market expects, address forms matching local convention. A purely machine-translated draft without review is fine as a starting point, but it should always be checked by someone with a feel for the language before publication. Copy that reads as visibly translated rather than written costs trust at exactly the moment a visitor decides whether to keep reading or leave.
What to actually translate
- Service pages, pricing, and the contact page: always translated in full
- Frequently asked questions: translated, since they directly shape trust and decisions
- Blog content: selective by market relevance, not every article by default
- Legal pages such as imprint and privacy: adapted to the relevant jurisdiction, not just translated
- Meta titles and descriptions: written independently for each language, not carried over word for word
Concrete steps for the next 90 days
- Days 1-30: check the target market and actual demand in the second language, decide on the URL architecture
- Days 31-60: translate and localise core pages, set and test hreflang tags for every language version
- Days 61-90: set up separate Search Console and analytics reporting per language, compare early results across languages
Conclusion
Decide the URL architecture first, because it is the only one of the three points that can later be corrected solely through a full redirect chain. hreflang can be retrofitted and copy can be sharpened - a badly chosen domain or directory structure, by contrast, stays with you for the entire life of the site. How these principles connect to the rest of a website's technical foundation is covered in Web design trends 2026. Details on our own bilingual setup are on the pricing page.
Frequently asked questions
Subdirectory, subdomain, or a separate domain for each language?
A subdirectory such as /de/ and /en/ is the right call for most small and mid-sized businesses: it inherits the main domain's authority and can be maintained with one shared technical setup. Country-specific domains only pay off with a very strong localisation ambition, and subdomains usually only make sense for organisational reasons.
Is machine translation good enough?
For a first draft, yes; for publication, no. Machine-translated copy often reads unnaturally, and that costs trust and conversion exactly when it matters most. A draft from a translation tool should always be reviewed by someone with a feel for the language before it goes live.
Does every piece of content need to exist in every language?
No. Core pages such as services, pricing, and contact should be translated in full, while blog content can be chosen selectively based on market relevance. Completeness for its own sake costs more than a deliberately curated bilingual offering.
How do you measure whether the second language version is worth it?
Split by language: a separate Search Console property and analytics property per language, evaluated by organic traffic and inquiries per language. If you measure both languages together, you cannot see whether the effort actually pays off.
Related service
You might also like
Web designSeptember 12, 2026
Websites for Tiling Contractors: Trust Beyond the Master Craftsman Title
Scrapped in 2004, mandatory again since February 2020: why a master craftsman qualification alone no longer settles the quality question for tilers.
Read article
Web designSeptember 12, 2026
Websites for Scaffolding Firms: Two Clients, One Trust Anchor
Construction firms and private homeowners buy scaffolding in entirely different ways. What each needs on the website, and why the inspection record wins jobs.
Read article
Web designSeptember 12, 2026
Websites for Opticians: Sell the Eye Test, Not the Frame
No independent optician wins a price comparison against chains and online sellers, and none needs to. Why the website has to sell the examination instead.
Read article
Web designSeptember 12, 2026
Websites for Joiners and Cabinet Makers: When No One Is In A Hurry
No call-out, no urgent trigger: for a joinery business, the reference gallery does the convincing. What a configurator can do here, and where it fails.
Read article
Web designSeptember 12, 2026
Websites for Independent Garages: Put the Warranty Question First
Almost no independent garage explains its strongest argument: the EU rule securing parts access and keeping the manufacturer warranty intact.
Read article
Web designSeptember 12, 2026
Websites for Farm Shops: A Season Calendar, Not a Brochure
A farm shop website is a running schedule, not a one-off page: what is ripe this week, when you can pick your own, and what the vending machine still holds.
Read article
Get it for free
Enter your email address. You'll immediately receive a confirmation link - after clicking it the checklist is available right away.