International Structure for Medical Tourism: ccTLD, Subfolder or Subdomain

This post is for the marketing or digital lead at an Indian hospital or hospital group that wants to attract patients from Africa, the CIS countries and the Gulf, and has to decide how the website should be structured to do it. It compares country-code domains, subfolders and subdomains, and gives decision rules you can apply to your own market mix.

The question is usually framed as "which one does Google prefer?" Google does not prefer one. Its documentation on multi-regional and multilingual sites lists the options with pros and cons and leaves the choice to the site owner. The differences that matter are operational: cost, maintenance, how signals consolidate, how clearly users understand the target, and how easily you can run separate content teams.

For medical tourism the answer is more specific than the generic advice, because the audiences are defined more by language than by country, the content is expensive to produce, and most international enquiries are driven by a small number of high-intent pages.

The three options, in Google's own terms

Google's guidance summarises the trade-offs as follows.

URL parameters (for example ?loc=ng) are listed as not recommended.

Read the table with a hospital in mind. A ccTLD for Nigeria, one for Kenya, one for Ghana, one for Iraq and one for Uzbekistan is five registrations, five sets of hosting configuration and five content teams. That only makes sense if each country will have a distinct commercial operation, local phone numbers, local payment options and local content.

Start from the audience, not the country

Indian hospitals rarely serve one country with one language. A typical pattern looks like this:

• Arabic-speaking patients in Iraq, Oman, Yemen and the wider Gulf, who share a language but differ in dialect, visa path and referral channels.
• Russian-speaking patients across several CIS countries, who share a language and often use the same search engines and messaging apps.
• English-speaking patients in East and West Africa, where the same page may serve several countries.
• French-speaking patients in parts of West and Central Africa, who need French pages and cannot be served by English ones.

If the language is the audience, the folder should be the language. If the commercial offer differs by country (visa support, flight routes, payment, local representatives), add a country layer beneath it.

That suggests a hybrid structure for most hospitals:

• /ar/, /ru/, /fr/, /en/ as language folders for core treatment content.
• Country pages beneath the relevant language only where the offer genuinely differs, such as /ru/uzbekistan/ or /en/nigeria/.
• A shared set of doctor, department and technology pages that exist once per language, not once per country.

Our broader medical tourism SEO piece covers which queries to chase. This article is only about where the pages live.

Decision rules

Apply these in order.

1. Do you have fewer than three languages and no country-specific operation? Use subfolders on the main domain. It is the lowest-cost option and consolidates everything on one host.
2. Will a market require its own legal entity, local representative, or locally hosted data? Consider a country-specific domain or subdomain for that market only, and keep it limited to the market-specific commercial content.
3. Do you need a different CMS, tech stack or content team for a language? A subdomain can make that separation clean, at the cost of managing it as a separate property.
4. Is the local audience likely to trust only a local domain? In some markets, patients and facilitators may trust a local extension. Treat that as a hypothesis to test with enquiry quality, not an assumption.
5. Otherwise use subfolders and revisit when evidence says you need to split.

For most Indian hospitals targeting Africa, CIS and the GCC from a single base, rules 1 and 5 apply.

How the three behave in practice

Link equity and consolidation

Links earned by pages on one host help the whole host. Subfolders keep every earned link, media mention and directory profile working for all language versions. Google can crawl and evaluate subdomains and separate domains as part of one site, but you should plan as though each is a separate property that has to earn its own signals, because link-building, internal linking and reporting are operated that way.

For a hospital whose strongest links come from a few Indian medical and media sources, subfolders mean the Russian or Arabic pages inherit the benefit of the English pages' links, as long as internal links connect them.

Hosting location

Google's table states that with a ccTLD server location is irrelevant, and that subdomains allow different server locations while subfolders imply a single one. For search, the practical issue is page speed for the user. A site hosted in Mumbai serving users in Lagos or Tashkent can be slow, which affects conversion more than ranking. A content delivery network usually solves this for subfolders. Hosting in a specific country for data-residency reasons is a separate legal question for your counsel, not an SEO decision.

Note that Googlebot generally crawls from the United States, and Google warns that it does not set an Accept-Language header on requests. That matters for the next section.

Language folders and the geo-redirect trap

Google recommends separate URLs for each language version rather than changing content by cookie or browser setting, and notes that sites which reroute users by language or location may leave variations undiscovered, because crawlers do not behave like local users. Its page on locale-adaptive pages explains this in more detail.

The practical rule is that every language version must have its own URL that can be reached without a redirect based on IP address or browser language. You may suggest a language to a visitor with a banner. Do not force it.

Hreflang

Hreflang tells Google which URL to show for which language and region. The rules are in Google's guide on localized versions. The ones that cause most breakage:

• Each version must list itself and every other version. Links must be reciprocal, or the annotations may be ignored.
• URLs must be fully qualified, including protocol.
• Use x-default for the page that should show when no language matches, usually the English home page or a language selector.
• Google does not use hreflang or the HTML lang attribute to detect the language of a page. It uses its own algorithms, so the page content must actually be in the stated language.
• You can place annotations in the head, in HTTP headers, or in the XML sitemap. For large sets of pages, sitemap annotations are easier to maintain.

Use language-only codes (ar, ru, fr, en) when you serve one page per language. Use language-region codes (en-ng, ar-iq) only when two pages in the same language differ by country, such as different contact details and logistics.

Worked example, hypothetical

A 500-bed hospital in Delhi wants to grow patient enquiries from Iraq, Nigeria and Uzbekistan. It has an English site only.

• Languages needed: Arabic, Russian (for Uzbek enquiries, along with Uzbek later if justified), English.
• Country-specific content: visa letter process, typical travel routes and a local representative contact for each market.

A defensible structure: hospital.com/ar/, /ru/ and existing English pages, each with its own treatment pages. Country pages under each, such as /ar/iraq/, hold logistics and local contacts. Hreflang annotations are generated in the sitemap from a table that maps each treatment page to its language versions.

Nothing needs a new domain. If the hospital later opens a representative office in Lagos with its own phone numbers and a local content person, a Nigeria-specific subfolder is still likely enough. A separate domain should wait until a business reason exists.

How to measure whether the structure works

Do not wait for rankings. Build measurement into the structure.

1. Verify each folder as its own Search Console property (URL-prefix properties for /ar/, /ru/ and so on), alongside the domain property. This gives per-language impressions, clicks and queries.
2. Segment by country in the Performance report to see whether Arabic pages are shown to the countries you expect.
3. Track enquiry source by language folder in analytics and in your CRM, so a chat or form submission records which folder it came from.
4. Review hreflang errors through a crawler monthly, since broken return links are the most common problem.
5. Check indexation by folder using the page indexing report, filtered through the folder property.

Failure modes to avoid

• Machine-translated pages published unreviewed. Medical text needs clinical and native-language review. Poor translation costs trust, and Google's spam policies address scaled content created without review.
• Canonical tags pointing across languages. Each language page should canonicalise to itself.
• Country sites duplicating the same English text. Two near-identical English pages for Nigeria and Kenya compete with each other. Use one English page with a country-specific logistics block unless the offer is truly different.
• A language selector that is a JavaScript dropdown without crawlable links.
• Hosting every market on a subdomain by default, then discovering that the Russian subdomain has no inbound links of its own.
• Moving structure later without redirects. A switch from subdomains to subfolders is a site move. Google's site move guidance applies in full.

Where to start

• List the languages your patients actually use, with source data from enquiries and Search Console.
• Choose subfolders unless one of the decision rules above forces another structure.
• Create a single mapping table: treatment, language, URL, hreflang set, owner.
• Set up per-folder Search Console properties before launch.
• Brief translators and reviewers with clinical terminology lists.
• Publish a language only when it has full content on the pages that matter, not empty shells.
• Plan the internal links between languages so the folders reinforce each other.

Closely related reading: our guides to attracting international patients and the medical tourism marketing guide cover the commercial side. For implementation, see our multilingual SEO service.