--- title: "International URL Structure" description: "How to choose between ccTLDs, subdomains, and subdirectories for international SEO, and what each structure means for geo-targeting and link equity." tldr: "The three main international URL structures are ccTLDs (example.co.uk), subdomains (uk.example.com) and subdirectories (example.com/uk/). Subdirectories are the recommended default, consolidating link equity on a single domain and being easiest to maintain. ccTLDs give a strong automatic geo-targeting signal but target one country each, require building authority on every domain, and do not apply to the roughly twenty vanity ccTLDs Google treats as generic, including .io, .co, .ai and .me. Whichever you choose, do not redirect users automatically by IP or language header, because Googlebot may then never see your other versions." publishDate: 2026-04-29 updatedDate: 2026-10-09 author: "Liam Hayward" --- Where an international site puts each market's pages, on a separate country domain, a subdomain or a folder of one domain, is one of the first technical decisions in international SEO. It decides how Google reads your regional targeting, whether link equity builds on one domain or splits across several, and how much maintenance each new market adds. Subdirectories are the recommended default for most sites because they keep everything on one domain; the sections below set out when a country domain or subdomain is worth its cost, and why URL parameters are not. For general URL conventions (slugs, hyphens, path depth), see [URL Structure](/on-page-seo/url-structure/). ## The four options **Country-code top-level domains (ccTLDs)** Each country gets its own domain: `example.co.uk` for the UK, `example.de` for Germany, `example.fr` for France. Google describes ccTLDs as providing "a strong signal to both users and search engines that your site is explicitly intended for a certain country".[^2] The signal comes from the domain itself, so no additional configuration is needed. One important exception before you buy a domain on this basis. Not every country-code domain counts as a country signal: Google states that it "treats some ccTLDs (such as .tv and .me) as gTLDs, as we've found that users and website owners frequently see these more generic than country-targeted".[^2] The list runs to around twenty and includes several domains commonly bought for branding rather than geography: `.ad`, `.ai`, `.as`, `.bz`, `.cc`, `.cd`, `.co`, `.dj`, `.fm`, `.io`, `.la`, `.me`, `.ms`, `.nu`, `.sc`, `.sr`, `.su`, `.tv`, `.tk` and `.ws`, with `.eu` and `.asia` treated as generic regional domains.[^2] A `.io` or `.co` domain buys you no automatic country association at all. Note also Google's stated limit on the approach: a ccTLD "can only target a single country",[^2] which makes it a poor fit where one language serves several markets. The tradeoff is authority. Each ccTLD is a separate domain, which means a separate crawl budget, a separate link profile, and a separate Search Console property. A backlink to `example.co.uk` does not benefit `example.de`. For businesses entering a new market, starting from zero authority on a new ccTLD is a significant disadvantage against established local competitors. ccTLDs make sense when: - Legal or regulatory requirements mandate a distinct local domain - The brand operates under different names or identities in each country - The business can sustain separate SEO programmes for each domain **Subdomains** Each market gets a subdomain: `uk.example.com`, `de.example.com`. Google treats subdomains as separate properties and each can be set up as a distinct Search Console property, but they do not receive the automatic country association that ccTLDs do. With the International Targeting setting removed in 2022,[^1] geo-targeting for subdomains rests on the other signals Google reads automatically, chiefly hreflang, the visible language of the content, and the market signals covered below. Google documents no difference between how links to a subdomain and links to a subdirectory count. Its ranking systems guide says the site diversity system "generally treats subdomains as part of a root domain", while noting that "sometimes subdomains are treated as separate sites",[^4] and its SEO Starter Guide lists subdomains versus subdirectories among the things it believes you shouldn't focus on.[^5] For most sites, subdomains offer no SEO advantage over subdirectories at higher operational cost. They are not without merit, though, and there is one real edge: Google's own comparison lists "allows different server locations" among the subdomain pros, against "single server location" as a subdirectory con.[^2] Since Google also names server location among its geotargeting signals, that is a genuine, if minor, international advantage. Subdomains are a reasonable choice where technical or organisational constraints make subdirectories impractical. **Subdirectories** All markets live under a single domain: `example.com/uk/`, `example.com/de/`. This is the recommended approach for most sites. Advantages: - Link equity accumulates on a single domain. A link to any page on `example.com` benefits every international variant. - A single domain means one hosting setup, one SSL certificate, and one primary Search Console property. - Lower operational overhead as markets scale. The main disadvantage is a weaker automatic geo-targeting signal compared to ccTLDs, mitigated by implementing hreflang correctly and by the other market signals below. **URL parameters** `example.com/?lang=de` or `example.com/?country=uk`. Google marks this approach "not recommended",[^2] and it should be avoided for all new builds. Google's stated objections are that URL-based segmentation becomes difficult and that "users might not recognize geotargeting from the URL alone".[^2] In practice the URLs are also poor for sharing and analysis. If you encounter an existing site using parameters for internationalisation, migrating to subdirectories is a worthwhile investment. ## What geotargeting signals does Google actually use? Since the manual Search Console setting is gone, Google documents four groups of signals for determining a page's target locale: ccTLDs (subject to the vanity-domain exception above), hreflang statements, server location, and market signals such as local addresses, currency and links from local sites.[^2] [Geotargeting](/international-seo/geotargeting/) covers how each behaves and which shortcuts Google ignores. The point for this page is that URL structure is one input among several, and not the decisive one. A subdirectory site with localised content, local currency, local contact details and local links is sending several of these signals at once. ## Don't redirect users automatically Whichever structure you choose, a common way it gets broken in practice is automatic redirection based on a guess about the visitor. Google's guidance is explicit: "avoid automatically redirecting users from one language version of a site to a different language version of a site. For example, don't redirect based on what you think the user's language may be. These redirections could prevent users (and search engines) from viewing all the versions of your site."[^2] The workable pattern is to give every version its own URL, let users land where they asked to land, and offer a visible way to switch. Google's own recommendation is "using different URLs for each language version of a page rather than using cookies or browser settings to adjust the content language on the page",[^2] and it suggests "adding hyperlinks to other language versions of a page".[^2] A banner suggesting a different version is fine; a forced redirect is not. Why the failure is usually invisible, why switching to `Accept-Language` sniffing does not fix it, and how to test whether your redirects fire for Googlebot are covered under [common international SEO mistakes](/international-seo/international-seo-mistakes/). ## How do you choose the right international URL structure?
| Structure | Geo-targeting strength | Link equity | Maintenance burden | |---|---|---|---| | ccTLDs | Very strong (automatic) | Fragmented | High | | Subdomains | Moderate | No documented split | Moderate | | Subdirectories | Moderate (declared) | Consolidated | Low | | URL parameters | Weak | Consolidated | Not recommended |
For most organisations: use subdirectories. The link equity benefit is significant, especially for sites in competitive markets where accumulating authority takes years. Consolidating that authority on a single domain rather than splitting it across multiple ccTLDs makes each individual page more competitive. Use ccTLDs when distinct local domains are required by legal or compliance obligations, or by brand architecture. Not because they feel more local to your audience. ## URL structure and hreflang Whichever URL structure you choose, it must be implemented consistently before hreflang annotations are added. Hreflang references specific URLs; if those URLs later change (for example, from subdomains to subdirectories), all hreflang annotations need updating simultaneously. Retrofitting a URL migration and a hreflang update at the same time increases the risk of errors considerably. ## URL naming conventions When using subdirectories, there are two main conventions: **Country codes**: `/uk/`, `/de/`, `/fr/`. Clear for regional targeting. Use when one language per country. **Language codes**: `/en/`, `/de/`, `/fr/`. Better when one language serves multiple countries (English for the UK, Australia, and Canada). Combine with hreflang to specify regional targeting. **Combined codes**: `/en-gb/`, `/de-de/`, `/fr-fr/`. Most explicit; best for large sites with both language and regional variants. ## How do you migrate between international URL structures? Changing international URL structure is one of the harder SEO migrations to execute cleanly, with real ranking risk; treat the initial choice as a long-term commitment. If moving from subdomains or URL parameters to subdirectories: 1. Set up the new URL structure and test it before redirecting any traffic. 2. Implement 301 redirects from every old URL to its new equivalent. 3. Update hreflang annotations to use the new URLs. 4. Update the XML sitemap. 5. Update internal links throughout the site. 6. Monitor Search Console for crawl errors and ranking changes for several weeks after migration. ## Frequently asked questions ### Can I mix URL structures across markets? Technically yes, but it creates maintenance complexity and makes hreflang harder to implement correctly. Consistency across all markets is strongly preferable. Note that hreflang itself is not the obstacle: Google states that alternate URLs "do not need to be in the same domain",[^3] so a ccTLD in one market and a subdirectory in another can still be annotated as versions of each other. ### Does URL structure affect whether I appear in AI answers? There is no evidence that it does, and no platform has documented a mechanism. Structure determines which URL Google serves to which user in classic search. Treat a well-formed international URL structure as necessary hygiene for search rather than as a lever for AI visibility. What appears to matter more is whether each market's pages say something different, which is covered in hreflang best practices. ### Does Google ever ignore the URL structure signal? URL structure is one signal among many. A well-optimised subdirectory with strong local links and correct hreflang will outperform a neglected ccTLD. The structure sets the stage; content and authority determine rankings. ### Should I buy all relevant ccTLDs even if I use subdirectories? Buying defensive ccTLDs to prevent brand squatting can be sensible depending on your market. Using them for SEO alongside a subdirectory strategy creates confusion and is unnecessary. [^1]: [The International Targeting report is deprecated — Google Search Console Help](https://support.google.com/webmasters/answer/12474899) [^2]: [Managing multi-regional and multilingual sites — Google Search Central](https://developers.google.com/search/docs/specialty/international/managing-multi-regional-sites) [^3]: [Tell Google about localized versions of your page — Google Search Central](https://developers.google.com/search/docs/specialty/international/localized-versions) [^4]: [A guide to Google Search ranking systems — Google Search Central](https://developers.google.com/search/docs/appearance/ranking-systems-guide), "Site diversity system" section. [^5]: [SEO Starter Guide — Google Search Central](https://developers.google.com/search/docs/fundamentals/seo-starter-guide), "Things we believe you shouldn't focus on" section.