A‑Vintage Digital
Why translating your website is not enough
Many international businesses make the same mistake: they translate their website, publish it, and wait for traffic from that new market. Nothing happens. The problem is that translation without SEO produces a page that search engines cannot properly index, attribute, or rank for the target language audience.
True multilingual SEO requires translation plus: per-language keyword research, hreflang implementation, independent Google Search Console configuration for each language, multilingual sitemap structure, and ongoing content optimisation.
Understanding hreflang — the foundation of multilingual SEO
Hreflang is an HTML attribute that communicates to Google which language and country a specific page is intended for, and how each version relates to the others. It is the single most technically critical element of multilingual SEO.
Without it, Google sees three similar pages and often ranks or suppresses them arbitrarily — or triggers duplicate content issues across all three versions.
Three site architecture options for multilingual websites
Option 1: Subdirectories (Recommended)
example.com/de/ for German, example.com/it/ for Italian. Consolidates domain authority into one root domain. Easiest for Google to process and audit, and the most common choice for businesses expanding into new language markets.
Option 2: Subdomains
de.example.com for German. Acceptable, but technically split from the root domain's authority in some contexts.
Option 3: Country-Code Top-Level Domains (ccTLDs)
example.de for Germany. The strongest geo-targeting signal — but requires building domain authority independently for each domain.
Per-language keyword research: why you cannot translate English keywords
Search behaviour differs not just by language but by market. German users searching for "digital marketing agency" do not search for a direct translation of those words. They use different phrases, different qualifiers, and different intent patterns.
Effective multilingual keyword research requires native-language research conducted in each target market — using that market's search tools, trending queries, and competitive data.
Google Search Console setup for multilingual sites
Each language version of your website should be configured as a separate property in Google Search Console — allowing you to monitor crawl health, indexing status, and performance independently for each language version. Submit language-specific sitemaps to each property.
Frequently Asked Questions
What is hreflang and why does it matter for multilingual SEO?
Hreflang is an HTML attribute that tells search engines which language version of a page to show to which user in which country. Without correct hreflang, a translated website creates duplicate content issues where search engines cannot determine which version to rank for which audience. With correct hreflang, each language version ranks independently in its target market.
Should I use subdirectories or subdomains for multilingual websites?
For most websites, subdirectories (example.com/de/ for German) are recommended — they consolidate domain authority and are easiest for Google to process. Subdomains (de.example.com) are acceptable but split authority. Country-code top-level domains (example.de) provide the strongest geo-targeting signal but require building domain authority separately for each domain.
Can I just translate keywords from English into other languages?
No — this is one of the most common and costly mistakes in multilingual SEO. Search behaviour differs significantly by language and market. Users in Germany, Italy, or France search with different phrases, different intent, and different vocabulary than English speakers — even for the same products or services. Keyword research must be conducted natively in each target language.
How do I set up Google Search Console for a multilingual website?
Each language version of your website should be added as a separate property in Google Search Console. For subdirectory sites, add each subdirectory as a property prefix (e.g., example.com/de/). Submit a language-specific XML sitemap to each property. Monitor crawl coverage, indexing, and performance independently for each language version.
