Skip to content

Guides · Site structure

Multilingual website structure for international patients: URLs, hreflang and page list

URL design per language, hreflang setup, the 12 page types each language needs, and writing with local search terms for clinics serving patients from Japan, Taiwan, English-speaking countries and Thailand.

By
OSKIT team (Afformation)
Updated
2 min read
On this page
  1. 01Steps
  2. 02The short answer
  3. 03URL options
  4. 04The 12 page types per language
  5. 05Write with local search terms
  6. 06hreflang
  7. 07One entity
  8. 08Inquiry channels
  9. 09In OSKIT

Summary

  • Use a subfolder per language (/ja/, /zh-tw/) and tie versions together with hreflang.
  • Each language needs treatment, price, doctor, directions and inquiry pages. A translated home page alone gives search nothing to rank.
  • Write titles and first paragraphs in the phrases patients in that country actually search.

Steps

  1. 1

    Fix target countries and language codes

    Pick languages from patient volume and inquiry channels. Use ISO codes such as ja, zh-TW, en and th.

  2. 2

    Set URL rules per language

    Use subfolders (/ja/, /zh-tw/) with the same path structure in every language.

  3. 3

    List pages per language

    Home, treatment list, treatment detail, prices, doctors, directions, international patient info, review policy, FAQ, inquiry, blog and about: 12 types per language.

  4. 4

    Research local search terms

    Find treatment and area terms per language and use them in titles and first paragraphs.

  5. 5

    Set hreflang and x-default

    Make language versions reference each other, set x-default, and mirror the pairs in the sitemap.

  6. 6

    Connect inquiry channels per language

    Show the messenger each market uses, such as LINE for Japan and Taiwan and WhatsApp for English speakers.

The short answer

Give each language its own subfolder (/ja/, /zh-tw/, /en/, /th/), build the same 12 page types in each, and tie them together with hreflang. A site with only a translated home page has one page to rank. International patients search with specific phrases such as “city + treatment + price”, so treatment and price pages must exist in every language.

URL options

OptionExampleProsCons
Subfolderexample.com/ja/Signals stay on one domain, one site to runCountry targeting via hreflang
Subdomainja.example.comEasy to separate serversSignals split
Country domainexample.jpClear country signalCost multiplies per language
Parameterexample.com/?lang=jaEasy to buildHard for search engines to treat as a language version

Subfolders are the default for clinics. Use the same path in every language, such as /ja/treatments/ultherapy and /en/treatments/ultherapy.

The 12 page types per language

PageContentStructured data
HomeName, location, 3–5 main treatments, inquiry buttonMedicalClinic + WebSite
Treatment listCategories and linksBreadcrumbList
Treatment detailDescription, duration, recovery, price rangeMedicalProcedure
PricesPrice or range, inclusions, payment methods–
DoctorsName, specialty, career, languagesPhysician
DirectionsAddress, nearest station, time from the airportMedicalClinic
International patientsInterpreters, payment, tax refund, accommodation–
Review policyPosting rules, medical advertising notes–
FAQCountry-specific questionsFAQPage (optional)
InquiryMessenger per language, response time–
BlogPosts on local search termsBlogPosting
AboutFounding, certifications, contactMedicalClinic

Write with local search terms

Japanese patients use Japanese common names for treatments. Taiwanese patients write in Traditional Chinese and add the country name. A direct translation of Korean text misses these phrases. Build a term list per language, put the main term in the title and H1, state what, where and how long with numbers in the first paragraph, and have a native speaker review.

hreflang

Every version lists all versions, itself included.

html
<link rel="alternate" hreflang="ko" href="https://example.com/treatments/ultherapy" />
<link rel="alternate" hreflang="ja" href="https://example.com/ja/treatments/ultherapy" />
<link rel="alternate" hreflang="en" href="https://example.com/en/treatments/ultherapy" />
<link rel="alternate" hreflang="x-default" href="https://example.com/en/treatments/ultherapy" />

x-default is the fallback, often the English page. Mirror the pairs in the sitemap. Leave untranslated pages out of the set.

One entity

Fix the official clinic name per language and use it everywhere. Use the same MedicalClinic @id on every language version and list inquiry languages in availableLanguage.

Inquiry channels

MarketMain messenger
JapanLINE
TaiwanLINE
English-speakingWhatsApp, email
ThailandLINE

One messenger button converts more easily than a long form. Track button clicks as conversion events.

In OSKIT

Site Engine generates language subfolders, hreflang, x-default and per-language sitemaps. Afformation’s blog engine already publishes in 7 languages: English, Japanese, Traditional Chinese, Thai, Indonesian, Russian and Mongolian.

Sources

  1. [1]Google Search Central — Localized versions of your pageshttps://developers.google.com/search/docs/specialty/international/localized-versions
  2. [2]schema.org — MedicalClinichttps://schema.org/MedicalClinic
  3. [3]Google Search Central — AI features and your websitehttps://developers.google.com/search/docs/appearance/ai-features

Summarize in an AI chat

Only the page URL is sent.

A free check shows your search and AI answer visibility

Enter your website address and see search engine and AI bot access and index status right away.

3 minutes · Free · No contract