--- title: "Multilingual Web and Content | Sağlık Ajansı" description: "A multilingual content structure built on localisation rather than translation, aligned with hreflang and real team language capacity." canonical: https://saglikajansi.com.tr/en/services/multilingual-web-and-content.html language: en last_modified: 2026-08-22 alternates: - en: https://saglikajansi.com.tr/en/services/multilingual-web-and-content.html - tr: https://saglikajansi.com.tr/hizmetler/cok-dilli-web-ve-icerik.html publisher: "Sağlık Ajansı — Marka Studio Dijital Reklam Tasarım Ajansı" note: "Bu dosya, kanonik HTML sayfasının makine-okunur alternatifidir. Kanonik kaynak yukarıdaki canonical URL'dir." --- *Medical-tourism agency service* # Multilingual Website and Content A multilingual structure is not the translation of existing pages. Because each market asks different questions and carries a different decision process, content is rebuilt in that language. The number of languages is bounded by the institution's ability to answer in them. An institution with pages in eight languages and answers in three loses patients in five. The first decision in multilingual work is not which language to add but which language not to add. > Multilingual content structure planned around target markets and team language capacity ## Translation versus localisation Translation carries a Turkish sentence into the target language. Localisation starts from the question the patient in that market asks and, where necessary, adds a section the Turkish page never had. In Germany, insurance and invoicing questions are decisive; in the Gulf, companion and accommodation arrangements come first. The difference produces measurable results: directly translated pages show low engagement and high exit rates in the destination market, while localised pages bring more enquiries from fewer visitors. ## Technical language infrastructure The relationship between language versions is established with hreflang tags: every page references itself and its counterparts, and x-default is defined. Incorrect hreflang leads search engines to show the wrong-language page and lands a visitor on something they cannot read. URL structure must also be decided upfront. Directory changes made later produce redirect chains and lost pages. Checks in a language setup - Self-referencing and reciprocal hreflang on every page - x-default pointing to the correct language - The language switcher taking the user to the same content, not the homepage - Forms, consent texts and error messages working in that language - Date, currency and telephone formats appropriate to the market ## Maintenance costs more than translation Adding a language is not a one-off task but a standing obligation. When the Turkish page updates, the others must follow; otherwise an information gap opens between languages and turns into a loss of trust. So the language decision is taken with content-maintenance capacity in view. Managing two languages well beats leaving five half-finished. Capacity rule Before opening a page in a language, answer three questions: who will reply in it, during which hours, and who will refresh the translation when content changes? ### Market logic Each language version is built around that market's question, not translated word for word. ### Technical accuracy hreflang, URL structure and the language switcher built correctly from the start. ### Maintenance plan Update responsibility and rhythm written before a language is added. *Working sequence* ## How we move, step by step 1. 01**Language decision**Target market and team capacity compared; the language list is bounded. 2. 02**Content gap analysis**Sections that must differ from the Turkish page identified per language. 3. 03**Localised production**Content written for that market's question with subject-matter editors. 4. 04**Technical setup**hreflang, URL structure, form and message languages configured. 5. 05**Maintenance hand-over**Update flow and responsibility transferred to the institution in writing. *Frequently asked questions* ## What institutions ask most about this ### Can we use machine translation? We advise against raw machine output. In health communication a wrong phrase creates both trust and compliance exposure. Machine translation can serve as a draft but must be edited by someone with subject knowledge. ### Which languages should we start with? English is usually the mandatory base; the second language follows the target market — German or Arabic most often. The decision depends on your capacity to answer in it. ### Should every page be translated? No. Institutional identity, treatment information and contact pages come first. Content specific to the Turkish market may be unnecessary in other languages. ### Does Arabic need right-to-left layout? Yes. Text translated into a layout that was never adapted becomes hard to read and signals inexperience. ### Subdomain or subdirectory? For most medical tourism institutions a subdirectory structure (/en/, /de/) is more efficient for management and authority accumulation. The decision depends on your platform and team. ### Does adding languages hurt SEO? Not when done correctly. Harm comes from incorrect hreflang, duplicate content and half-finished language versions. *Next step* ## Raise answer quality, not language count Share your target markets and team language capacity and we will draw a realistic language plan. *Related topics* ## Continue with the next relevant topic --- Kanonik sayfa / Canonical page: https://saglikajansi.com.tr/en/services/multilingual-web-and-content.html Site haritası / Site map: https://saglikajansi.com.tr/llms.txt