Multilingual website SEO doesn't begin with translation, but with clean information architecture , dedicated keyword research for each language , and correct technical markup. If you first have content translated word for word into German, Italian, and English, and only then think about hreflang , navigation , canonical tags , and indexing , you'll often end up with incorrect rankings, duplicate content , and unnecessary maintenance.
I've been seeing this exact mistake for many years with SMEs in South Tyrol , Italy , and the DACH region (Germany, Austria, Switzerland). The website is often technically online, the language versions are set up, but the structure doesn't follow any market logic. Then the German site competes with the Italian one, the English version remains invisible, and nobody can accurately measure which language generates which inquiries.
A multilingual website is not a translation project. A multilingual website is a system of market logic, URLs, content, and search signals.
This is especially important for small teams. Three language versions don't simply mean three text packages. Three language versions also mean three sets of URLs, page titles, meta data, internal linking, search intent, and technical mapping. Twenty core pages quickly become 60 indexable URLs for German, Italian, and English versions. Without prioritization, this becomes expensive, slow, and prone to errors.
Multilingual website SEO: structure first, then content
The key sequence is: define the market , establish the structure , research keywords for each language , correctly tag the technology , and prioritize and roll out content . Reversing this order usually results in a beautiful surface with a weak foundation.
Google Search Central recommends separate URLs for each language or country version of multilingual websites . This isn't a minor detail. Without a separate URL for each language, implementing hreflang, canonical tags, and proper indexing is difficult.
Translation is not the same as localization.
A German term, an Italian term, and an English term rarely convey exactly the same search intent. This is precisely where multilingual website SEO most often fails. A simple translation conveys words. Good SEO conveys search intent.
- Translation conveys the content linguistically.
- Localization adapts terms, tone, and examples to the target market.
- Market adjustment decides which content is even meaningful in which language.
A South Tyrolean SME often doesn't need the same level of content depth in all language versions. For many companies, German and Italian are their core operational markets. English isn't mandatory on every page, but rather a targeted tool for building trust or for sales purposes, particularly for international inquiries, recruitment, or export.
The right information architecture for DE, IT and EN
Information architecture determines how search engines and people understand your language versions . A good structure clearly answers four questions: What language is this? For which market is the page intended? What is the corresponding page in another language? And how can a user quickly find the appropriate version from any page?
In practice, four URL models are usually relevant for SMEs. Not every model is equally useful.
| Model | Example | SEO signal | maintenance effort | Assessment for SMEs |
|---|---|---|---|---|
| ccTLD | example.de / example.it | Strong national signal | High | Useful when dealing with clearly separated national strategies, separate Budgetand enough resources |
| Subdomain | de.example.com / it.example.com | Clear separation possible | medium to high | Useful when there is a technical separation, multiple teams, or different systems. |
| Subdirectory | example.com/de/ / example.com/it/ | Strong bundling of domain signals | Low to medium | For most SMEs, the most pragmatic solution |
| Parameter | example.com?page=home&lang=de | Weaker and more prone to errors | Medium | Only in exceptional cases, usually not the first choice |
My recommendation for small and medium-sized businesses is, in many cases, to use a subdirectory . A subdirectory is technically manageable, consolidates authority on a single domain, and remains easier to maintain in daily operations than a distributed structure with subdomains or ccTLDs . A subdomain is only useful when systems or teams truly operate separately. A ccTLD is usually only worthwhile when the country, product offerings, legal aspects, and marketing differ significantly.
This is what a clean structure looks like.
- Each language has its own permanent URL.
- The URL logic is consistent across all language versions.
- The navigation always leads to the respective language alternative.
- Language selection is possible manually and not only automatically controlled.
- The German, Italian, and English versions of a page are clearly identifiable as belonging together.
For companies in South Tyrol, it's also important to note that German in Italy is not automatically the same as German for the entire DACH market. If content, offerings, or search terms differ significantly, a more refined market analysis may be necessary. If content is practically identical, a well-maintained German main version is often sufficient.
Keyword research per language: why a one-to-one approach rarely works
Keyword research for each language is essential. Not because search engines demand it, but because people search differently. Simply translating German search terms into Italian or English often results in the wrong priorities being applied to the wrong market.
I've seen this time and again with SMEs: The German site ranks well, the Italian site remains weak, even though the text has been translated correctly. The reason is almost never grammar. The reason is almost always the search logic. A term can be technically correct and still not be the term that real users in Italy or the English-speaking world would enter.
What you need to check for each language
- Search volumeIs the topic even being searched for in the language?
- Search intentionIs the user looking for information, comparison, or a direct inquiry?
- Variants of the termAre there regional or industry-specific differences?
- Competition: Who is already ranking in the respective language?
- Business valueWhich terms generate inquiries, not just clicks?
For a company located between South Tyrol, Italy, and the DACH region (Germany, Austria, Switzerland), this often means that the same service requires not only three language versions but also three different priorities. Some service pages need to be fully developed in German and Italian, while the English version focuses only on the most important offerings. This approach saves resources and improves quality.
A practical mapping solution for small teams
- First, create a list of all core pages.
- Assign one main keyword and two to three secondary keywords to each core page in each language.
- Determine which pages in DE, IT and EN truly serve the same purpose.
- Highlight pages that are strategically needed only in one language.
- Only then should you create text, page titles, meta descriptions, and internal links.
This sounds simple, but it prevents a costly mistake: blindly cloning the same navigation structure and content to all language versions.
Technical setup: hreflang, canonical tag and indexing
Once the structure is in place, the technical aspects come next. Three elements are crucial: hreflang , canonical tag , and proper indexing . Improperly setting any one of these weakens the entire multilingual website.
What hreflang really does
hreflang tells search engines which language or country version belongs to which page. hreflang is not a ranking trick. hreflang is a mapping aid. It helps search engines deliver the right version to the right user.
- The German site refers to the Italian and English alternatives.
- The Italian site refers back to the German and English alternatives.
- The English page also redirects back.
- All pages in the hreflang cluster must be reachable and indexable.
For South Tyrol, regional tagging can also be relevant. If a German page is specifically intended for users in Italy, `de-IT` might be appropriate. If an English version isn't assigned to a specific country, ` en` is often sufficient . The code must follow the market strategy, not just the language on paper.
What the Canonical Tag should and should not achieve
The canonical tag doesn't assign a language. It tells search engines which URL is the preferred version of a page with very similar content. On truly multilingual pages, the canonical tag usually points to itself . So, the German page typically canonizes to the German URL, the Italian to the Italian URL, and the English to the English URL.
A common mistake is to set all language versions to the original German page using canonical tags. This effectively tells search engines that only the German version is the main page and the rest is interchangeable. This sabotages the visibility of the other language versions.
Keep indexing clean
- Each language page needs its own URL and should be accessible server-side.
- Language content should not be switched solely via JavaScript.
- Incomplete translations should not be indexable.
- XML sitemaps should contain the correct URLs of the language versions.
- Every indexed page needs sufficient independent, usable content.
It's also important to distinguish between problematic and duplicate content . Multilingual pages aren't automatically problematic simply because they present the same content in different languages. Problems arise when the same language is displayed almost identically across multiple URLs, or when language versions aren't technically assigned correctly.
Navigation and internal linking in language versions
Navigation is not just a UX issue, but also an SEO issue. Good navigation helps search engines understand the structure and helps users switch seamlessly to the correct language.
The most important rules for navigation
- The language switcher must be visible on every relevant page.
- The language switcher should ideally lead to the corresponding page, not always just to the homepage.
- The main navigation may remain similar in its basic logic, but it does not have to be equally deep in every language.
- Automatic language switching via browser or IP address should not lock users in.
- Internal links should remain consistent within a language version.
Automatic redirects are particularly problematic. If a user in Italy wants to access the German version, the website must not force them to redirect to Italian. It becomes even more problematic if search engine crawlers only ever see one default language. This makes indexing more difficult and disrupts user navigation.
Content prioritization for DE, IT and EN
A realistic German-Italian-English (DE-IT-EN) setup for SMEs requires prioritization. Many small teams try to immediately build every subpage in three languages. This sounds decent, but is often the most expensive and weakest solution. A phased rollout is better.
My practice setup for small teams
- Phase 1: Homepage, main service pages, About Us, Contact, Directions or Location page, central trust elements in Germany and IT.
- Phase 2: EN is only for pages with a clear business objective, such as international services, recruiting or export.
- Phase 3: Only roll out the blog, guides and case studies once the core pages are technically and content-wise functioning properly.
- Phase 4: Evaluate search data for each language and then expand upon it, don't produce everything beforehand.
That, for me, is what strategic work means: not publishing as many pages as possible, but prioritizing those that deliver the most business results and search engine optimization. At Berger+Team, we deliberately work leanly on such projects, often with a small network of experts instead of cumbersome handovers. This is particularly helpful for owner-managed companies because the structure remains maintainable and doesn't collapse under its own complexity.
Which language should be developed first and to what extent
- DE: often the core language for South Tyrol and parts of the DACH market
- IT: operationally central for Italy, often crucial for local visibility
- ENselectively on pages with international relevance, not automatically consistently in full depth
The right priority doesn't depend on habit, but on inquiries, revenue potential, and internal maintenance. If your team only has two hours per week for website content, a focused setup is more effective than a theoretically complete German-Italian-English system with half-finished pages.
Typical mistakes on multilingual websites
- 1:1 keyword transfer from the German version without research in the target market
- German, Italian and English on the same URL via a switch instead of separate URLs
- Missing or incomplete hreflang-References
- Falscher Canonical Day, which combines all language versions into one original language
- Automatic language switching based on browser language without free user choice
- Meta titles and meta descriptions only partially translated
- In the Navigation Language options are missing on subpages.
- Empty or very thin language versions will still be indexed.
- Mixed menus, slugs or breadcrumbs in different languages
- EN is being built, although DE and IT are not yet working properly.
The best multilingual website is not the one with the most language versions. The best multilingual website is the one whose structure, content, and technology can be reliably maintained on a daily basis.
Conclusion: Multilingualism requires strategy, not just translation.
If you're planning a multilingual website, start with the structure. First, determine which markets you're actually serving, which language versions are relevant to business, and how the URL logic, navigation, and indexing should work. Only then should you focus on text and translations.
After over 20 years in web development, branding, and search strategy, I can tell you: Most problems don't arise in the code, but in the lack of order in which things are done. Those who... Information architecture, the Keyword research per language and setting up the technical configuration correctly early on saves a huge amount of time later, Budget and correction loops.
If you want to approach the topic in a structured way, three building blocks are usually crucial: a strategic website structure, a sound search strategy, and linguistically appropriate content development. That's precisely why we consciously integrate website concept, SEO, and text.
Frequently asked questions about multilingual website SEO
Is it enough to simply translate my German website into Italian and English?
No. A translation without market logic ignores search intent, term variations, and priorities in each language. If you want to build clean, multilingual content, you need structure and SEO in addition to textual work; that's precisely why linguistic quality and strategic adaptation go hand in hand in texts and translations.
What is usually better for SMEs: subdirectory, subdomain or ccTLD?
For many SMEs, a subdirectory is the most sensible solution because maintenance, technology, and authority are better aligned on a single domain. A subdomain or ccTLD is usually only worthwhile for clearly separated markets, teams, or systems; this decision should be made early in the technical planning of a website.
Do I really need hreflang?
Yes, hreflang is very important as soon as multiple language versions of the same page type are available in different languages . hreflang helps search engines deliver the correct language version and reduces misunderstandings between German, Italian, and English.
Does every subpage need to be available in all language versions?
No. Each language version should serve the business objective, not the desire for completeness. For many companies in South Tyrol and Italy, German (DE) and Italian (IT) are fully relevant, while English (EN) only offers real benefits on selected pages.
What does a realistic SEO setup look like for a small team?
Start with the most important pages, a clean URL structure, keyword assignment per language, and correct technical markup. Once the foundation is in place, you can systematically expand your content; in marketing strategy, this prioritization is often the difference between predictable growth and perpetual chaos.
