Sağlık Turizmi
Multilingual SEO and hreflang for health tourism
For a clinic that wants to attract patients from abroad, having the site in several languages is unavoidable. But a multilingual site that's set up wrongly runs into duplicate content problems and confuses Google about which language version to show to whom. This guide is based on the principles in Google's own documentation.
First, the basics: translation must cover the main content
According to Google, pages where only the menu and footer (the template) are translated while the main content stays in one language aren't treated as different language versions. The body of your treatment page needs to be in the target language too. And word-for-word translation isn't enough: the words and concerns of an Arabic-speaking, German or English-speaking patient differ. Translations should be reviewed by someone who knows the treatment; in medical content a wrong translation damages both trust and accuracy.
What is hreflang?
hreflang is markup that tells Google about a page's equivalents in other languages / regions. The core rules in Google's documentation:
- Each version lists itself and the others. The same alternatives appear on every language version, including a self-reference.
- Reciprocal links are required. If page A points to B but B doesn't point back to A, the tags are ignored.
- x-default is the fallback page for users who match no language (for example a language selector page).
- URLs must be fully qualified, including the protocol.
- Language codes use ISO 639-1 and region codes ISO 3166-1 Alpha 2; a region code can't be used alone (examples:
en,en-GB,de,ar). - There are three placement methods: HTML
<link>tags, HTTP headers and XML sitemaps. Google treats them as equivalent; using all three gives no extra benefit. Pick one and manage it consistently.
Example HTML
<link rel="alternate" hreflang="tr" href="https://www.example.com/tr/dis-tedavisi/" />
<link rel="alternate" hreflang="en" href="https://www.example.com/en/dental-treatment/" />
<link rel="alternate" hreflang="de" href="https://www.example.com/de/zahnbehandlung/" />
<link rel="alternate" hreflang="x-default" href="https://www.example.com/en/dental-treatment/" />
URL structure: subfolder, subdomain or separate domain?
Google doesn't recommend a single structure; its examples include subdirectories, subdomains and country-code domains (ccTLDs), and alternate URLs don't need to be on the same domain. For most clinics, a subfolder structure under one domain (/en/, /de/) is practical because management and authority sit in one place. The decision depends on your team's capacity and target markets.
Don't confuse it with canonical
Each language version should be self-canonical. If you point a translated page's canonical at the original, Google may leave the translation out of the index. We covered the difference in our 301 vs canonical guide.
Common mistakes
- No reciprocal hreflang between language versions,
- Wrong language codes (
en-GB, noten-UK), - Untranslated pages left in Turkish inside the English folder,
- Automatic redirects based on language, which can make it hard for Google and users to reach all versions. Offer a visible language selector instead.
- Publishing bulk machine translation without human review. It carries quality and accuracy risk, especially in health content.
Checklist
- Is the main content of every treatment page translated in the target languages?
- Is hreflang reciprocal and using full URLs?
- Does each version canonicalize to itself?
- Are language alternates consistent in the sitemap?
- Is performance tracked by target country in Search Console? (Search Console guide)
To see where all this fits in a roadmap, see our health tourism SEO guide, and to run the work together, our service page.
