Multi Lingual SEO

I start with the URL structure. For most multilingual sites, I prefer subdirectories over subdomains or ccTLDs because they consolidate link equity and simplify management. For example, /fr/ for French and /de/ for German. I then set up hreflang tags page-level, not just in sitemaps. Each page gets a self-referencing hreflang tag plus references to all alternate language versions. I use ISO 639-1 language codes and optionally ISO 3166-1 Alpha 2 regional codes. For a recent client selling software, I chose subdirectories /fr/ and /de/. I did keyword research separately for each language using Ahrefs and native speakers. The top French keyword "logiciel de comptabilité" had a search volume 5x higher than the German equivalent, so I prioritised French. I localised the content, not just translated it — the French page focused on features, while the German page emphasised compliance. After implementing hreflang and fixing a few errors flagged in Google Search Console, French organic traffic jumped 30% in two months. I also use the x-default tag to catch untargeted languages. I never rely on automatic redirects based on IP; Google recommends against that. I check hreflang with a tool like Merkle's checker before deploying. The key is to validate with one language-market pair before scaling. Once the setup is clean, expanding to other languages is straightforward. I also ensure that each page has a canonical tag pointing to itself, especially if the same content appears in multiple languages.

The most common mistake I see is missing return tags in hreflang. If page A links to page B, page B must link back to page A. I once audited a site where 60% of hreflang annotations were incomplete — Google ignores them. Another gotcha is using the wrong language code. For example, using 'en' for both UK and US pages without a regional code causes cannibalisation. I use 'en-gb' and 'en-us' when the content differs. Also, avoid using browser language detection to redirect users. Google's [international SEO](/international-seo/) guidance explicitly warns against this. It can trap users and create duplicate content issues. Another watch-out is treating translation as localisation. I have seen pages rank poorly because the translated text did not match the search intent. For example, the Spanish query "reserva de hotel" is more transactional, while a literal translation of "hotel booking" might be informational. You need to analyse the SERP for each language. I also see sites neglect the x-default tag. Without it, Google may show the wrong language version to users from regions you do not target. [Localisation SEO](/localization-seo/) is about more than words — it is about currency, date formats, and cultural references. Finally, monitor Search Console for the hreflang report. Errors like "no matching return tags" are common. I fix them immediately because they can block your pages from appearing in the correct language SERPs.

I used to believe that adding hreflang tags was the hard part. I would set them up, test them, and call it done. But I learned the hard way that hreflang is only a signal — it does not guarantee that Google will show the right version. I once had a client with German and Austrian pages. I used 'de-DE' and 'de-AT' correctly, but the content was identical. Google saw duplicate content and chose one version for both markets, killing the Austrian page's traffic. I had to localise the Austrian page to differentiate it. Another mistake: I assumed that keyword research could be done once and translated. For a travel site, I optimised for "hotel booking" in Spanish, but the Spanish keyword "reserva de hotel" had a different intent — users were looking for booking forms, not information. My page had high impressions but low CTR. I now do separate [international SEO keyword research](/international-seo-keyword-research/) for each language. Also, I forgot to include the x-default tag on one project. Google showed the French version to users in the UK who had French language settings, but they expected English. The bounce rate was terrible. I now always include x-default pointing to the generic English page. Finally, I used to rely on sitemaps alone for hreflang. I moved to page-level annotations because they are easier to maintain and less error-prone. These mistakes cost me months of traffic, but they taught me that [multilingual SEO](/multilingual-seo/) is a continuous process of testing and localisation.