International SEO: Country Domain, Subdirectory or Subdomain
For a site serving more than one country: a country-code domain like .co.uk, a subdirectory like /en/, or a subdomain like uk.site.com. A comparison.
rabbitclip teamPublished: 4 min read
Short answer
A site serving more than one country or language has three structural options: a country-code domain (site.co.uk), a subdirectory under the main domain (site.com/en/), or a subdomain (uk.site.com). Google Search Central states that all three are supported and that none carries an automatic ranking advantage over the others; the real deciding factor is which structure a business can actually manage well with the resources it has.
For rabbitclip's clients working across Turkey and the UK, this is usually a decision worth making early, before a second language goes live, since changing it later is possible but requires a migration project of its own because the URL structure changes.
When does a country-code domain make sense?
A ccTLD (.co.uk, .de, .fr) is the option that signals most strongly, to both users and search engines, that a site belongs to a specific country; Google Search Central notes that this structure provides automatic and clear geographic targeting. It suits a business operating in a single country, or one that wants a particularly strong local perception there.
Its downside is needing to buy and manage a separate domain for every country; a business operating across five or six countries finds this turns into a genuinely complex structure fast.
When is a subdirectory (/en/, /tr/) the better fit?
A subdirectory keeps several language or country versions under one domain. Google Search Central notes that this setup is relatively easy and that all versions benefit directly from the authority, backlinks, brand recognition, the main domain has already built.
For a London-based service business also serving the Turkish market, this is usually the most practical option: one hosting setup, one admin panel, two language versions. Its weak point is not being able to use a different server location per country, which in some cases carries a speed advantage.
When does a subdomain (uk.site.com) become necessary?
A subdomain sits technically close to a subdirectory but can sometimes be treated by Google as a somewhat separate site; Google Search Central notes that a subdomain can also serve geographic targeting, though it requires a bit more technical setup to manage than a subdirectory.
This option tends to get chosen when different countries genuinely need separate technical infrastructure, a different server, payment system, or legal requirement; an e-commerce site using a distinct payment provider and stock system for the UK, for instance, is a case where a subdomain makes that separation technically clear too.
What does hreflang do, and where does it go?
Hreflang is a tag that tells Google which language and country a page is prepared for. Google Search Central states that each language version needs to list itself along with every other language version, and that alternate URLs must be fully qualified, starting with https://.
Google states plainly that it does not use hreflang, or the HTML lang attribute, to detect a page's language; that gets determined by its own algorithms instead. Hreflang's actual job is not language detection, it is making sure the right version reaches the right user in search results.
Questions to ask when choosing between the three
Five questions a business can ask itself when deciding between these three structures.
- How many countries does the business currently serve, and is that number likely to grow over the next two years?
- Does each country need a different payment system, shipping process or legal requirement?
- Can the team managing content and technical maintenance realistically handle separate domains?
- Does the brand specifically want a strong local perception in one particular country?
- If the site already has traffic, does a structural change bring enough benefit to justify a migration?
The common mistake: launching a multilingual site without hreflang
A branding agency's site kept its English and Turkish versions apart with subdirectories but never added hreflang; the result was Google treating the two versions as unrelated, sometimes even as duplicate content of each other.
A few weeks after hreflang was added, the two versions started appearing separately in their own country's search results; that shows the point is less about the structure itself and more about correctly telling Google what that structure means.
There is no single right answer among a country domain, a subdirectory and a subdomain; the right one depends on how many countries a business serves, what technical separation it actually needs, and which structure it can manage. Whichever gets chosen, none of it works fully without hreflang set up correctly. A short discovery call with rabbitclip is enough to see where a site's international structure stands today.
FAQ
Does a ccTLD give a ranking advantage over other structures?
No; Google states that all three structures are supported, with no automatic ranking advantage. The real difference sits in manageability and user perception.
Is a subdirectory or a subdomain easier to manage?
A subdirectory is usually easier since it benefits directly from a single domain's authority; a subdomain gets chosen when a genuine technical separation is needed.
Does a multilingual site work without hreflang?
It works, but Google may not correctly predict which version to show which user; that usually means the wrong language version surfacing in the wrong country.
Can the structure be changed later?
It can, but changing the URL structure requires redirects and a sitemap update; that should be treated as a migration project in its own right.
