Question architecture
Pages follow the patient's question, not the organisation chart.
Medical-tourism guide
Website and SEO Guides
Search visibility for medical tourism sites rests on three foundations: an information architecture built around the patient's question, a technically crawlable platform and a correctly configured multilingual structure. Keyword placement is secondary to all three.
The most common problem we see in healthcare institution sites is structural rather than technical: pages organised around the org chart rather than around what patients ask.
How to build information architecture
Patients search with questions: how many days does an implant take, when can I fly after a hair transplant, is IVF legal in Türkiye. The site needs a page or section answering each.
That does not mean endless pages. When every treatment page sits on the same skeleton — definition, suitability, process, duration, preparation, follow-up, FAQ — most questions are already covered.
Technical checklist
- A unique title under 60 characters and a description of 140–155 on every page
- One H1 per page and no skipped heading levels
- A self-referencing canonical tag
- hreflang: reciprocal, self-referencing and with x-default defined
- Descriptive alt text, dimensions and lazy loading on images
- A mobile-first, fast-loading page structure
- Organization, Service, FAQPage and BreadcrumbList schema
The most common multilingual mistakes
The three most frequent: hreflang tags that are not reciprocal, a missing x-default definition and a language switcher that dumps users on the homepage. All three cause search engines to serve the wrong-language page.
A fourth is subtler: content divergence between language versions. When the Turkish page is updated and the others are not, inconsistency appears for both users and search engines.
Depth or page count?
In healthcare, a small number of comprehensive pages outperforms many shallow ones. Answering every question about a treatment on one page beats splitting the topic across five thin pages.
The exception is market and institution-type pages. Where they genuinely carry different content they should be separate; copies with only the location name changed count as doorway pages and cause harm.
A shared skeleton
When treatment pages share a structure, most questions get answered automatically.
Depth over count
One comprehensive page beats five shallow ones.
Working sequence
How we move, step by step
- 01Question inventory
Questions asked in the target market extracted by language.
- 02Architecture build
The page map reorganised around those questions.
- 03Template standard
A shared skeleton established for treatment and market pages.
- 04Technical correction
Meta, canonical, hreflang and schema layers fixed.
- 05Measurement
Entry points and enquiry-producing pages tracked.
Frequently asked questions
What institutions ask most about this
Do we have to run a blog?
Not necessarily. Durable information pages generally outperform dated blog posts. What matters is the format less than whether the question is answered.
Should we open a page per city?
No. Pages with identical content and only the location changed count as doorway pages and cause harm.
What keyword density should we target?
There is no target density and forcing one creates risk. Answering the question fully and covering the topic with related concepts is enough.
How important is site speed?
Page speed directly costs enquiries in markets with slower mobile connections, where most medical tourism traffic originates.
Is schema markup essential?
Not essential, but it markedly improves entity recognition in search and answer engines — provided it matches visible content exactly.
Should we delete old pages?
Merging and redirecting is usually better than deleting; deleted pages lose their link value too.
Next step
Let us build your site around the patient's question
Share your current page structure and we will start with an information architecture audit.