ccTLD vs. Subdomain vs. Subdirectory for International SEO

The three URL structures for targeting different countries — ccTLD (example.de), subdomain (de.example.com), subdirectory (example.com/de/). Google has no ranking preference, but only ccTLDs carry an automatic geo-signal. Here's how to choose.

First published: Jul 2, 2026 · Last updated: Jul 18, 2026 · Advanced
demand #2 in Architecture & Targeting#16 in International SEO#381 on the site

For serving different countries or languages you have three URL structures: a ccTLD (example.de), a subdomain on a gTLD (de.example.com), or a subdirectory on a gTLD (example.com/de/). Google has said it has no ranking preference among them — but the choice is not neutral. A ccTLD carries an automatic, unambiguous country signal (no manual geotargeting needed), which the other two don't get for free. The tradeoff: ccTLDs split your domain authority and backlink equity across separate domains and cost more to run. Subdirectories consolidate everything on one domain and are the easiest to operate, but since Google removed the International Targeting report in Search Console (September 2022) there's no way to explicitly declare a subfolder's country anymore — you're left with hreflang. Subdomains sit in the middle. My advice: default to subdirectories unless you have a strong reason (an existing ccTLD, legal/trust requirements, or genuine infrastructure separation) to do otherwise.

TL;DR — For country/language targeting you’re choosing among a ccTLDCountry-code top-level domain like .de or .co.uk — a strong geotargeting signal. (example.de), a gTLD subdomain (de.example.com), and a gTLD subdirectory (example.com/de/). Google documents all three as usable structures with different tradeoffs. The real differentiator is the geoGenerative Engine Optimization (GEO) is the practice of optimizing content and brand presence so AI-powered search engines and assistants — Google AI Overviews, ChatGPT, Perplexity — cite, recommend, or mention you when generating answers. Google's position is that it's still SEO.-signal: a ccTLD carries an automatic, unambiguous country signal that the other two don’t get for free. The cost of that signal is fragmentation — separate domains split link equityPageRank is Google's original recursive link-graph algorithm: a page's score depends on the scores of the pages linking to it, and in the published model each page's score is split across its outbound links (the simplified version: links are weighted votes). Google says it's evolved since launch but still part of its core ranking systems., multiply infrastructure, and make hreflangHreflang is an annotation (in HTML, HTTP headers, or XML sitemaps) that tells search engines which language and optional region a page targets, and which alternate versions exist. It only works when every page in the cluster references all the others. harder to manage across properties. Subdirectories consolidate authority on one domain and are the cheapest to run, but since Google removed the International Targeting report in Search Console (September 2022) there is no longer any way to explicitly declare a subfolder’s target country — use hreflangHreflang is an annotation (in HTML, HTTP headers, or XML sitemaps) that tells search engines which language and optional region a page targets, and which alternate versions exist. It only works when every page in the cluster references all the others. alongside visible locale content and other local signals. Subdomains sit in the middle: a separate hostname that can be hosted in-country but otherwise needs the same manual signals a subdirectory does. Ownership, registrant eligibility, governance, and cost matter as much as the signal — and switching structures later is a full URL migration (redirectsA redirect sends browsers and crawlers from a requested URL to a different one. An HTTP redirect specifically is a 3xx status code paired with a Location header; meta refresh and JavaScript redirects achieve a similar navigation without being a 3xx response themselves. Permanent redirects (301/308) are Google's signal the target should be canonical; temporary ones (302/303/307) aren't., canonicals, hreflang, sitemapsA sitemap is a file that lists the pages, images, videos, and other files on your site so search engines can discover them. It helps discovery, but submitting a sitemap doesn't guarantee crawling or indexing., monitoring), not a quick fix. My default: subdirectories, unless an existing ccTLD, a trust/legal requirement, or genuine infrastructure separation pushes you elsewhere. This is the international decision — the general dot-vs-slash architecture question is a separate topic (see below).

Evidence for this claim Google documents ccTLD, gTLD subdomain, and gTLD subdirectory structures as usable locale-specific URL options, with different operational tradeoffs. Scope: Google Search international URL-structure guidance; the documentation does not promise equal ranking outcomes. Confidence: high · Verified: Google: Locale-specific URL structures Evidence for this claim Google calls ccTLDs a strong country signal and also lists hreflang, server location, local contact details, currency, local links, and Business Profile signals among its locale inputs. Scope: Google Search target-locale signals; no single signal guarantees a chosen result. Confidence: high · Verified: Google: How target locale is determined

The three structures, precisely

StructureExampleCountry signalAuthorityOperational cost
ccTLDexample.deAutomatic (Google + users)Split across separate domainsHighest (registration, hosting, hreflang across properties)
Subdomainde.example.comExplicit and contextual signalsSeparate hostname; per-site evaluationMedium
Subdirectoryexample.com/de/Explicit and contextual signalsConsolidated on one domainLowest

A ccTLD is a country-code top-level domain — .de, .fr, .co.uk, .jp. Google treats it as a strong geotargeting signal by defaultHreflang is an annotation (in HTML, HTTP headers, or XML sitemaps) that tells search engines which language and optional region a page targets, and which alternate versions exist. It only works when every page in the cluster references all the others.: it maps the domain to a country automatically, and you cannot (and don’t need to) override that with a manual setting. A gTLD (generic TLD like .com, .org, .net) carries no country meaning on its own, so a subdomain or subdirectory on a gTLD has to earn its geotargetingConfiguring a site or URL to target users in a specific country. some other way.

What Google actually says

Google’s Managing multi-regional and multilingual sites documentation lists these as the URL structuresURL structure is how the parts of a web address — scheme, domain, path, query string, and fragment — are organized and formatted. It mostly affects crawling, usability, and how engines understand a page, not rankings directly. for country targeting, with their tradeoffs:

  • Country-specific domain (ccTLD) — pro: clear geotargeting, clear server location by convention, easy separation of sites. Con: expensive, can have limited availability, needs more infrastructure.
  • Subdomain with gTLD — pro: easy to set up and allows different server locations. Con: users might not recognize geotargeting from the URL alone.
  • Subdirectory with gTLD — pro: easy to set up, low maintenance (same host). Con: users might not recognize geotargeting from the URL, single server location.
  • URL parametersThe `?key=value` data tacked onto the end of a URL after a question mark — used for tracking, sessions, filtering, sorting, and search — and one of the biggest sources of duplicate URLs and wasted crawling in SEO. (example.com?country=de) — not recommended for country targeting; hard to segment and users can’t recognize the geoGenerative Engine Optimization — visibility inside AI answer engines. from the URL.

Notice what’s not in that list: any claim that one ranks better. Google’s consistent position, repeated in its URL structure guidance and the general site-structure docs, is that it has no indexingStoring a crawled page in the search index so it can appear in results. Crawled is not the same as indexed — Google selects what to keep, and indexing isn't guaranteed. or ranking preference — you should pick what’s easiest to organize and manage. The structural choice is about operations and signals, not a ranking lever.

The key differentiator: automatic vs. manual geo-signal

This is the whole point of the decision, and it’s what separates this from the generic subdomain-vs-subdirectory debate.

A ccTLD gives you the country signal for free. example.de is understood as targeting Germany the moment Google sees it. You do nothing. Users see it too — the .de in the address bar is a trust and relevance cue no .com/de/ path can match.

A subdomain or subdirectory on a gTLD does not get that automatically. The .com says nothing about country. So how do you tell Google that example.com/de/ is for German-speaking users in Germany?

For years, the answer had two parts: hreflang and Search ConsoleGoogle's free tool for monitoring crawling, indexing, and search performance.’s International Targeting report, which let you manually set the target country for a whole gTLD property — including, when you used a URL-prefix property, a specific subdirectory like example.com/de/. That manual country setting was the one way to explicitly geotarget a subfolder.

The change most articles miss: International Targeting is gone

Google removed the International Targeting report from Search Console in September 2022 (Google’s own deprecation notice; also covered by Search Engine Land). The report had two tabs — an hreflang-error checker and the country-targeting setting. Google’s stated reasoning was that the value of the manual country setting had decreased over time and hreflang had matured.

The practical consequence is specific and important: there is no longer any way to explicitly declare a subdirectory’s (or subdomain’s) target country to Google. The manual override is gone. What’s left for a gTLD subfolder or subdomain is:

  • hreflang — the reciprocal language-region annotations that tell Google which version to serve which user (see hreflangHreflang is an annotation (in HTML, HTTP headers, or XML sitemaps) that tells search engines which language and optional region a page targets, and which alternate versions exist. It only works when every page in the cluster references all the others. and x-defaultx-default is the reserved hreflang value that points to a fallback URL — the page Google shows when a user's locale doesn't match any of your other hreflang tags. It is optional and does not mean \"English.\").
  • Signals Google infers on its own — server/CDN location, local language and currency, local address and phone details, links from in-country sites.

None of those is a hard “this folder targets Germany” declaration the way the old setting was. hreflang is a hint about which version to show, not a country assignment. So the subdirectory route now leans entirely on getting hreflang right — which, in my study of 374,756 hreflang-using domains, over 67% got at least partly wrong. That’s the real cost of the “easiest to run” option: the geo-signal is all on you, with less margin for error.

A ccTLD sidesteps this entirely. It never needed the International Targeting setting, so losing that report didn’t change anything for it. That asymmetry — ccTLDs were never dependent on a manual tool, subfolders were — is the strongest single argument for a ccTLD when the geo-signal genuinely matters.

The cost of a ccTLD: fragmentation

If ccTLDs give the cleanest signal, why not use them everywhere? Because the signal comes bundled with real costs:

  • Split authority. Each ccTLD is a separate domain. Backlinks to example.de build the authority of example.de, not of example.com. You’re starting each country’s reputation from close to zero instead of pooling it on one strong domain. For a site whose strength is concentrated on one gTLD, that fragmentation can hurt more than the clean geo-signal helps.
  • Multiplied infrastructure. More domains to register and renew, more hosting or CDN configuration, more certificates, more of everything. Some ccTLDs also require a local presence or local address to register at all (.com.au, historically some EU ccTLDs), which is a legal/administrative hurdle, not just a technical one.
  • Harder hreflang. hreflang across a single domain is fiddly; hreflang across a dozen separate properties — each needing to reference all the others reciprocally — is where large international sites most often break. Every ccTLD you add is another node every other node has to point at correctly.

Subdirectories invert all of this: one domain, one property, one hosting setup, all authority consolidated, hreflang contained within a single site. That’s why they’re the practical default for most global sites — the operational simplicity is real, even though the geo-signal is weaker.

Subdomains: the middle ground

A gTLD subdomain (de.example.com) is a genuine middle option, but understand why it’s in the middle:

  • Like a subdirectory, it’s on a gTLD, so it gets no automatic country signal — it needs the same hreflang and inferred signals a subfolder does.
  • Unlike a subdirectory, it’s a separate hostname, so it can trivially be hosted on a different server or in a different country, and it can be split out to a different team or stack. Google’s docs specifically note subdomains “allow different server locations.”
  • Whether Google treats the subdomain as part of your main site (so authority flows) or as a separate site is decided per-site based on integration — the same per-site evaluation that governs the general subdomain-vs-subdirectory question.

So a subdomain buys you hosting flexibility without buying a separate domain, at the price of the same manual geo-signaling a subdirectory needs. For most people, if you don’t specifically need the separate host, a subdirectory does the same job with less overhead.

What about the correlation studies?

You’ll see studies showing ccTLDs dominating international SERPs — for example SE Ranking’s analysis of 20,000 keywords across 15 markets found ccTLDs holding the lion’s share of top-three positions, subdirectories a distant second, and subdomains a small fraction. Take that at face value and you’d conclude ccTLDs “win.”

I’d be careful. Those numbers are correlational, not causal. In competitive local markets, the sites on ccTLDs tend to be the established local players — long-standing local brands, local businesses, national retailers — who would rank well regardless of URL shape. The .de isn’t causing the ranking; being a strong, locally-relevant, well-linked site is, and those sites happen to sit on ccTLDs by convention. The clean geo-signal helps at the margin, but it doesn’t manufacture authority you haven’t earned. Don’t read “ccTLDs rank higher” as “switch to a ccTLD and rank higher.”

Where the general (non-international) tradeoffs live

Everything above is the international-targeting angle. There’s a separate, non-international question — is a subdomain functionally equivalent to a subdirectory for SEO in general (a blog, a help center, docs), how per-site treatment works, and why most subdomain→subdirectory migration “wins” are confounded by simultaneous changes. I cover that in depth in the general subdomain vs subdirectoryA subdomain (blog.example.com) is a separate hostname; a subdirectory (example.com/blog/) is a path on the same hostname. Google has no blanket ranking preference — it decides per site whether a subdomain is treated as part of the site, based on integration signals. article in the website-structure cluster, including the case studies (Pink Cake Box, IWantMyName), Google’s per-site integration signals, and the reverse-proxy workaround. If your question is “where should my blog live,” start there. If your question is “how do I serve different countries,” you’re in the right place.

Ownership, governance, and cost belong in the decision too

Google’s guidance frames this as a tradeoff, not a ranking contest, and the tradeoffs go beyond the geo-signal:

  • Ownership and availability. You have to actually be able to buy and keep the ccTLD you want. Some country registries restrict who can register — a local business presence, a local contact, or a local address (historically true for some EU and .com.au-style ccTLDs). A handful of ccTLDs are marketed and treated more like generic vanity domains than country signals (.io, .co), so don’t assume every cc ending behaves the same way in Google’s eyes.
  • Governance and deployment isolation. A separate ccTLD or subdomain can be run by a different team, on a different stack, with independent deploys — genuinely useful if a local market needs its own release cadence. That isolation is also a cost: more properties to secure, monitor, and keep consistent, and more surface area for one market’s mistake (a broken hreflang tag, an expired certificate) to go unnoticed by the team running the others.
  • Cost. Registration, renewal, hosting, and certificates scale with the number of properties. A ccTLD-per-market strategy multiplies all of that; a subdirectory strategy keeps it to one domain.

None of this changes the core answer — match the structure to your market scope, who owns and can maintain each property, and how much local trust actually matters in that sector — but skip straight to “which one ranks better” and you’ll miss the constraints that decide it in practice.

Migration risk

Changing structures later — ccTLD to subdirectory, subdomain to ccTLD, or any other direction — is not a copy-paste. It’s a URL migration, with the same mechanics and the same risk as any other one:

  • Redirects. Every old URL needs a 1:1 redirect to its new equivalent, not a blanket redirect to the homepage.
  • Canonical tagsA rel=\"canonical\" annotation — in the HTML <head> or an HTTP Link header — that tells search engines which URL is the preferred version of duplicate or near-duplicate content.. Update canonicals to point at the new URLs; where you still have same-language regional duplicates, Google recommends a preferred canonical plus hreflang rather than leaving them to compete.
  • hreflang. Every locale’s reciprocal hreflangIf page A lists page B as an alternate, B must list A back — or Google ignores the pair. set needs to reference the new URLs — across every property, not just the one you moved.
  • Internal linksAn internal link is a hyperlink from one page on a website to another page on the same website. Internal links help search engines discover your pages and pass ranking signals (PageRank and anchor-text context) between them. and sitemapsA sitemap is a file that lists the pages, images, videos, and other files on your site so search engines can discover them. It helps discovery, but submitting a sitemap doesn't guarantee crawling or indexing.. Update internal links to the new URLs and refresh XML sitemapsAn XML sitemap is a UTF-8 file listing the canonical URLs on your site (with optional lastmod) so search engines can discover and prioritize them. It's a discovery and diagnostic aid, not a guarantee of indexing — and Google ignores its priority and changefreq tags. so crawlersA crawler — also called a spider or bot — is an automated program that fetches web pages, extracts their links, and queues new URLs to visit. Search engines use crawlers to discover and download content for their index. find the new structure quickly.
  • Host verification. A ccTLD or subdomain is a new property in Search Console/Bing Webmaster ToolsMicrosoft's free portal for monitoring and improving how a site appears in Bing search — the peer to Google Search Console, plus IndexNow instant indexing, richer backlink data, and keyword volumes. Because Bing's index also feeds Microsoft Copilot, it doubles as a window into AI-search visibility.; verify it before you need the data, not after something breaks.
  • Monitoring. Watch indexingStoring a crawled page in the search index so it can appear in results. Crawled is not the same as indexed — Google selects what to keep, and indexing isn't guaranteed., traffic, and rankings through the transition. If you’re comparing before/after numbers, remember the migration itself is a confounding variable — you can’t attribute a change to the new URL shape without controlling for everything else that moved at the same time (redirects, content refreshes, link changes).

Don’t migrate structures purely chasing a ranking bump — Google has no stated preference among them, and the migration itself carries more risk than the structure change is likely to fix.

My recommendation

  • Default to subdirectories (example.com/de/). Cheapest to run, authority stays consolidated, and for most sites the weaker geo-signal is a fine trade for the simplicity. Just commit to getting hreflang right, because since 2022 that’s your only explicit lever.
  • Choose ccTLDs when the geo-signal genuinely matters and you can afford the fragmentation: you already own the country domains, you’re in a sector where a local address drives trust (finance, health, big retail, government-adjacent), or a market has legal/registration requirements that push you onto its domain. Confirm you can actually register and govern the domains you want before you commit. Go in knowing each domain builds its own authority.
  • Choose subdomains mainly for infrastructure reasons — you need each country on a separate host or stack but don’t want (or need) separate domains. You still owe the same manual geo-signaling a subdirectory does.
  • Never mix haphazardly. Picking a structure and applying it consistently across all markets matters more than which structure you pick. Consistency is what keeps hreflang and crawlingCrawling is how search engines use automated bots (like Googlebot and Bingbot) to discover URLs and download pages. A page has to be crawlable to be indexed, but crawling on its own isn't a ranking factor. sane at scale.
  • Never migrate structures without a plan. If you do move, treat it as a full URL migration — redirects, canonicals, hreflang, internal links, sitemaps, host verification, monitoring — not a quick fix for a ranking problem.

Where this fits

Siblings in this cluster cover the broader international basics — an international SEOInternational SEO is the practice of optimizing a site so search engines understand which countries and/or languages it targets, and serve the right version to each user. It spans URL structure, hreflang, and on-page localization. audit, an implementation checklist, keyword research across markets, and the translation-vs-localizationLocalization is adapting content for a specific target market — not just translating the words, but adjusting currency, formats, idioms, cultural references, local search terms, and trust signals so the experience feels native. decision. The tag-level mechanics live in hreflang and x-defaultx-default is the reserved hreflang value that points to a fallback URL — the page Google shows when a user's locale doesn't match any of your other hreflang tags. It is optional and does not mean \"English.\". And the deciding factor once you’ve chosen a structure is almost always hreflang correctness, not the structure itself.

Add an expert note

Pin an expert quote

New person? Create their unclaimed profile at /admin/experts/ → Pin a quote first.