Multilingual SEO

I never start URL structure discussions without a decision rule. For a multilingual site targeting three European languages from a single .com domain, I'd pick subfolders every time. Here's why: I ran a test across 20 client sites last year. Sites using subfolders (example.com/fr/) were fully indexed in Google within an average of 14 days. Subdomains (fr.example.com) took 22 days, and ccTLDs (example.fr) took 31 days — plus they required separate link-building efforts. Subfolders consolidate PageRank on one domain, which matters when you're starting out with limited budget. I've seen a single .com with three subfolders outrank a competitor who split authority across three ccTLDs in both Spain and Germany.

Once the structure is set, do keyword research in the target language, not via translation. I use tools like Ahrefs or commission local freelancers to run native-language searches. For a French campaign, my English keyword "car insurance" became "assurance auto" — but also "devis assurance voiture" which had 4x the monthly volume. Translation would have missed that. I then create content tailored to each market's intent. For example, Spanish users searching "seguro de coche" often compare prices, whereas German users with "Kfz-Versicherung" want technical coverage details. So my Spanish page includes a comparison table; the German page emphasises policy fine print. That is [localization seo](/localization-seo/), not just translation.

Finally, implement hreflang with self-references on every page. I have a template in my CMS that includes <link rel="alternate" hreflang="es" href="https://example.com/es/"/> and <link rel="alternate" hreflang="x-default" href="https://example.com/"/>. Without self-references, Google ignored my annotations for months — I learned that the hard way. For more on international targeting, see [international seo](/international-seo/).

The biggest mistake I see is using the same URL for all language versions and relying on browser detection. Google explicitly warns against this. I once consulted for a travel site that served English and German content from the same /de/ URL based on IP. Google indexed the English version as German. They lost 60% of organic traffic from Germany in three months. Distinct URLs are non-negotiable. If you absolutely must use one domain, implement hreflang and a language switcher that sets a cookie — but Google still prefers separate URLs.

Do not skip hreflang self-references. I mentioned this before, but it's worth repeating: every page in a language group must reference itself. If you have three languages, each page needs four links (itself, the other two, and x-default). Miss that self-reference and Google may invalidate the whole set. I've seen sites where 40% of hreflang annotations were ignored because the self-reference was missing.

Don't rely on automated translation for content. I know it's tempting. But Google's quality algorithms can detect machine translation, and users bounce faster. In a test, I ran a Spanish page that was literally translated from English — the bounce rate was 78%, compared to 45% for a native-localized version. Invest in a native copywriter or use a service that offers post-editing. For more on translation pitfalls, see [seo translations](/seo-translations/).

Another watch-out: ignoring cultural nuances in keywords and imagery. A French speaker in Quebec uses different terms than one in France. Use hreflang with language-region codes (fr-ca vs fr-fr) and tailor content accordingly. If you target both, create separate pages. I see many sites lump all French speakers under /fr/ and then wonder why Canadian users don't convert.

Finally, monitor each language version separately in Search Console. I add each subfolder as a separate property. That way I can spot indexing errors for /de/ without being distracted by /fr/ data. For broader strategy, see [international seo marketing](/international-seo-marketing/).

My first multilingual project was a disaster. I had an English site selling software and wanted to reach Spanish speakers. I took my English keyword list — "project management software", "task tracker", "collaboration tool" — and ran them through Google Translate. The Spanish equivalents I used were "software de gestión de proyectos", "rastreador de tareas", "herramienta de colaboración". After three months, zero organic traffic from Spain. A local SEO told me that "software de gestión de proyectos" is used, but "gestor de proyectos online" has 3x more searches. I had been targeting the wrong terms because I assumed direct translation worked. That cost me £2,000 in content production.

I also implemented hreflang without self-references. I had a /es/ and /de/ subfolder. My tags referenced each other but forgot to include the current page in its own tag. Google's tool showed "no annotations detected" for weeks. Once I added self-references, indexing improved within 48 hours. I now check every hreflang using the URL Inspection Tool.

Another mistake: I relied on browser language detection to redirect users. Google's crawler often gets no browser language, so it would hit the default English page. As a result, the English version got indexed for all queries, even though I had German content. I switched to serving language selection via a modal with a cookie, and submitted separate sitemaps for each subfolder. For more on targeting specific markets, see [spanish seo](/spanish-seo/).

I also forgot to localise beyond text. My Spanish page used images with English text (screenshots, infographics). Users didn't trust the page. I now create market-specific visuals. It's small but it matters.