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.
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 — If you want to serve different versions of your site to different countries, you have three URL shapes to choose from: a country domain like
example.de, a subdomain likede.example.com, or a folder likeexample.com/de/. Google documents all three as usable structures. One important difference: a country domain (.de,.fr,.co.uk) strongly signals to search engines and users which country it’s for automatically. The folder version is the easiest to run, so it’s the sensible default for most sites.
The three options
Say you’re a US company expanding into Germany. Where does the German version of your site live? Three choices:
- ccTLDCountry-code top-level domain like .de or .co.uk — a strong geotargeting signal. — a country-code top-level domain:
example.de. The.deis Germany’s own domain ending, the way.fris France’s and.co.ukis the UK’s. You’re buying a separate domain for each country. - Subdomain — a prefix on your main domain:
de.example.com. Same main domain, a “de.” bolted on the front. - Subdirectory (or subfolder) — a path on your main domain:
example.com/de/. Same domain, everything sits in one place, just organized into folders.
Does one rank better?
Google does not document one structure as universally best. Its guidance presents different pros, cons, and locale signals, so the decision should fit the audience and operating model rather than assume a guaranteed ranking outcome.
But that doesn’t mean they’re interchangeable. Here’s the one difference that actually matters for a beginner to understand:
A ccTLD announces its country automatically. When Google sees example.de, it
already knows that site is aimed at Germany — no extra setup required. Users get the
same signal: a German shopper trusts a .de address more than a generic .com.
With a subdomain or a subdirectory, that country signal isn’t automatic. You have to establish the intended audience through explicit signals such as 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., locale-specific content, local details, and local links.
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 determinedSo which should you pick?
A simple rule of thumb:
- Use a subdirectory (
example.com/de/) if you’re not sure. It’s the cheapest and simplest to run — one domain, one hosting setup, one place to manage everything — and all your site’s “strength” stays on a single domain. - Use a ccTLD (
example.de) if you already own the country domains, if trust in a local address really matters (common for banks, government, big retail), or if a country has legal reasons you need to be on its domain. - Use a subdomain (
de.example.com) mainly when you have a technical reason to keep each country on a separate host but don’t want to buy separate domains.
The thing most people get wrong
Don’t buy a ccTLD for every country thinking it’ll rank better. It won’t — and you’ll split your site’s authority across a dozen separate domains, each of which has to earn its own links and reputation from scratch. That’s a real cost, not a free win. Want the full tradeoff, what Google actually says, and how the removal of Search ConsoleA free Google service that reports how a site performs in Google Search and surfaces problems with how Google crawls, indexes, and serves it. It's first-party data straight from Google — but you don't need it to appear in results.’s geotargetingConfiguring a site or URL to target users in a specific country. tool changed things? Switch to the Advanced tab.
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 determinedTL;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).
The three structures, precisely
| Structure | Example | Country signal | Authority | Operational cost |
|---|---|---|---|---|
| ccTLD | example.de | Automatic (Google + users) | Split across separate domains | Highest (registration, hosting, hreflang across properties) |
| Subdomain | de.example.com | Explicit and contextual signals | Separate hostname; per-site evaluation | Medium |
| Subdirectory | example.com/de/ | Explicit and contextual signals | Consolidated on one domain | Lowest |
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-regionannotations 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.debuild the authority ofexample.de, not ofexample.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 everyccending 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.
AI summary
A condensed take on the Advanced version:
- Three structures for country targeting: ccTLDCountry-code top-level domain like .de or .co.uk — a strong geotargeting signal. (
example.de), gTLD subdomain (de.example.com), gTLD subdirectory (example.com/de/). - Google has no ranking preference among them (stated in its multi-regional and URL-structure docs). The choice is about signals and operations, not rank.
- Key differentiator — 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 to both Google and users, with no manual setup. A subdomain or subdirectory on a gTLD gets no automatic country signal and must rely on 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. plus inferred signals (server location, language, currency, local links).
- International Targeting removed (Sept 2022). Google removed the Search ConsoleA free Google service that reports how a site performs in Google Search and surfaces problems with how Google crawls, indexes, and serves it. It's first-party data straight from Google — but you don't need it to appear in results. report that let you manually set a gTLD property’s (including a subdirectory’s) target country. There is no longer an explicit way to declare a subfolder’s country — 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. is the only remaining lever.
- ccTLD cost = 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. (each builds its own authority), multiply infrastructure, and make cross-property hreflang harder.
- Subdirectory = cheapest, authority consolidated on one domain, but leans entirely on hreflang for geoGenerative Engine Optimization — visibility inside AI answer engines.-signaling.
- Subdomain = middle ground: separate hostname (flexible hosting/server location) but still needs the same manual geo-signals a subdirectory does; treated as part of the site or separate on a per-site basis.
- Correlation caveat: studies showing ccTLDs dominating international SERPs (e.g. SE Ranking’s 20K-keyword study) are correlational — established local brands sit on ccTLDs by convention; the domain isn’t causing the rank.
- Ownership, governance, cost. Some ccTLDs restrict who can register (local presence/address requirements); a few are treated as generic vanity domains rather than country signals. More properties means more governance overhead and more cost (registration, hosting, certificates) regardless of the geo-signal.
- Migration risk. 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, 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., 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., host verification, monitoring — and any before/after ranking comparison is confounded by everything else that changed in the move. Don’t migrate purely chasing a ranking bump.
- Patrick’s default: subdirectories, unless an existing ccTLD, a trust/legal requirement, or genuine infrastructure separation pushes otherwise. Consistency across markets matters more than the pick.
Which structure should you use?
Work top to bottom — the first “yes” that fits usually settles it.
1. Do you already own, or is your business already established on, country
domains (example.de, example.fr)?
→ Use ccTLDsCountry-code top-level domain like .de or .co.uk — a strong geotargeting signal.. You’ve already paid the fragmentation cost and built local
authority; don’t throw that away to consolidate. Keep them, and wire up 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.
across the properties.
2. Does a market legally require a local domain, or is local trust mission-critical (finance, health, government-adjacent, big national retail)? → Use a ccTLD for that market. The automatic 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 and the trust cue of a local address are worth the extra domain here. (You can run ccTLDs for some markets and subdirectories for others, but keep each market internally consistent.)
3. Do you need each country on a genuinely separate server, stack, or team, but
don’t want to buy separate domains?
→ Use a subdomain (de.example.com). You get the hosting/location flexibility
without a separate domain — just remember you still owe 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.; the subdomain
doesn’t geotarget itself.
4. None of the above — you’re a mostly-.com site expanding into new
languages/countries and want the simplest thing that works?
→ Use subdirectories (example.com/de/). Authority stays consolidated on one
domain, one hosting setup, one Search ConsoleA free Google service that reports how a site performs in Google Search and surfaces problems with how Google crawls, indexes, and serves it. It's first-party data straight from Google — but you don't need it to appear in results. property. Commit to correct hreflang,
because since September 2022 there’s no manual country-targeting setting left to fall
back on.
Two rules that override the tree:
- Consistency beats the “perfect” pick. One structure applied cleanly across all markets outperforms a mix chosen per-market on a hunch.
- Never migrate structures purely for a ranking bump. Google has no preference; the migration risk (see the general subdomain-vs-subdirectory article) usually outweighs a signal you can get with hreflang.
Official documentation
Primary-source documentation from the search engines.
- Managing multi-regional and multilingual sites — the three 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 (ccTLDCountry-code top-level domain like .de or .co.uk — a strong geotargeting signal., subdomain, subdirectory), their pros and cons, and the recommendation to use different URLs per version rather than cookies/browser-based serving.
- URL structure best practices — recommends ccTLDs or subdirectories for geotargetingConfiguring a site or URL to target users in a specific country.; no stated ranking preference.
- Tell Google about localized versions of your page (hreflang) — the reciprocal 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. rules that are the only explicit 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 left for gTLD subdomains and subdirectories, alongside the inferred signals (server location, local content, local links) Google reads on its own.
- Crawling and indexing multilingual sites — how Google discoversGoogle Discover is a personalized, mobile-first content feed built into the Google app, Chrome's mobile New Tab page, and google.com that surfaces articles and videos based on a user's interests and activity — not a response to a search query. There's nothing to 'rank' for in the traditional sense; eligibility is governed by Discover's content policies plus the same helpful-content, image, and page-experience signals Google Search already uses. and serves the right locale version.
Bing / Microsoft
- How To Tell Bing Your Website’s Country and Language (Bing Webmaster Blog) — Bing’s guidance on multi-country/multi-language sites; note Bing leans more on the
content-languagemeta/header signal than on 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.. - Bing Webmaster Guidelines — general guidance; no prescriptive preference among ccTLD, subdomain, or subdirectory for legitimate sites.
Quotes from the source
On-the-record statements and documented positions. Where a page supports it, the link is a deep link to the passage; where the brief relayed a claim without a verified verbatim substring, it’s paraphrased without quotation marks.
Google — no ranking preference among structures
- Paraphrased: Google’s documentation states you should choose whatever is easiest to organize and manage, and that from an 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. and ranking perspective it doesn’t have a preference among 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.. URL structure docs
Google — the three international structures and their tradeoffs
- Paraphrased from the multi-regional docs: a country-code top-level domain gives clear geotargetingConfiguring a site or URL to target users in a specific country. and easy site separation but is expensive and needs more infrastructure; a gTLD subdomain is easy to set up and allows different server locations but users may not recognize the geotargeting; a gTLD subdirectory is easy to set up and low-maintenance on a single host but, again, users may not recognize the geotargeting. Managing multi-regional and multilingual sites
Google — International Targeting report removal (September 2022)
- Paraphrased from Google’s Search ConsoleA free Google service that reports how a site performs in Google Search and surfaces problems with how Google crawls, indexes, and serves it. It's first-party data straight from Google — but you don't need it to appear in results. announcement, as reported: the International Targeting report was retired because the value of the manual country-targeting setting had decreased over time as 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. matured — leaving 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. as the mechanism to signal localized versions. Google’s deprecation notice
Common mistakes (and what to do instead)
Myth 1: “A ccTLDCountry-code top-level domain like .de or .co.uk — a strong geotargeting signal. ranks better, so buy one for every country.” Why it’s wrong: Google has no ranking preference among the structures, and every ccTLD is a separate domain that builds its own authority from near zero and adds infrastructure and 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. complexity. The ranking studies showing ccTLDs on top are correlational — established local brands sit on ccTLDs by convention. Do instead: use ccTLDs only where the automatic 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 or local trust genuinely justifies the fragmentation; otherwise consolidate on subdirectories.
Myth 2: “Subdirectories are just as good, so I don’t need 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..” Why it’s wrong: a subdirectory on a gTLD gets no automatic country signal, and since Google removed the International Targeting report (Sept 2022) there’s no manual country-targeting setting left. Without hreflang you’ve told Google nothing about who each version is for. Do instead: implement reciprocal, self-referential hreflang across all your locale folders — it’s now the only explicit lever you have.
Myth 3: “Set the target country in Search ConsoleA free Google service that reports how a site performs in Google Search and surfaces problems with how Google crawls, indexes, and serves it. It's first-party data straight from Google — but you don't need it to appear in results. for my /de/ folder.”
Why it’s wrong: that setting (International Targeting) no longer exists — it was
removed in September 2022. You cannot explicitly declare a subfolder’s country
anymore.
Do instead: rely on hreflang plus inferred signals (server/CDN location, local
language and currency, local address, in-country links).
Myth 4: “Subdomains geotarget themselves because they’re a separate hostname.”
Why it’s wrong: a gTLD subdomain (de.example.com) carries no country meaning from
the .com; it needs the same hreflang and inferred signals a subdirectory does. The
separate hostname buys hosting flexibility, not an automatic geoGenerative Engine Optimization — visibility inside AI answer engines.-signal.
Do instead: treat a subdomain’s geotargetingConfiguring a site or URL to target users in a specific country. exactly like a subdirectory’s — hreflang
first — and use the subdomain only for its infrastructure benefits.
Myth 5: “Migrate to a ccTLD (or subfolder) to fix weak international rankings.” Why it’s wrong: a structure migration is risk without a guaranteed reward — Google has no preference, and the general subdomain-vs-subdirectory case studies show most migration “wins” are confounded by simultaneous changes. You rarely fix authority or relevance problems by moving URLs. Do instead: fix the underlying signals (hreflang correctness, local content quality, in-country links) before touching the URL structureURL 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..
Myth 6: “Mix structures per market — whatever’s convenient each time.” Why it’s wrong: an inconsistent mix makes hreflang clusters, 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., and authority harder to reason about and easier to break at scale. Do instead: pick a primary structure and apply it consistently; only deviate for a specific, justified reason (an existing ccTLD, a legal requirement).
Choosing an international URL structure — checklist
Before you pick
- Confirm you actually need country/language targeting (different content per market), not just translation of one global site.
- List your target markets and note any with legal/registration requirements for a local domain.
- Check whether you already own relevant ccTLDsCountry-code top-level domain like .de or .co.uk — a strong geotargeting signal. or already rank on any.
- Decide how much local trust matters in your sector (finance/health/retail lean toward ccTLDs; SaaS/content often fine on subdirectories).
Deciding
- Established on ccTLDs already, or legal/trust-critical? → ccTLD.
- Need separate hosting/server location per country but not separate domains? → subdomain.
- Otherwise, want simplest to run with consolidated authority? → subdirectory (the default).
- Whatever you pick, plan to apply it consistently across all markets.
After you pick (any gTLD structure — subdomain or subdirectory)
- Remember there is no manual country-targeting setting in Search ConsoleA free Google service that reports how a site performs in Google Search and surfaces problems with how Google crawls, indexes, and serves it. It's first-party data straight from Google — but you don't need it to appear in results. anymore (removed Sept 2022).
- Implement reciprocal, self-referential 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. across all versions.
- Add an 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.\" for the fallback/ selector page.
- Reinforce with inferred signals: server/CDN location, local language and currency, local address/phone, links from in-country sites.
- Don’t migrate an existing, working structure purely for a ranking bump.
If you go ccTLD
- Budget for separate registration, renewal, hosting, and certificates per domain.
- Plan 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. across separate properties (every ccTLD referencing every other, reciprocally).
- Accept that each domain builds its own authority — don’t expect 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. to pool.
If you’re migrating between structures
- RedirectA 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. every old URL 1:1 to its new equivalent — no blanket redirects to the homepage.
- Update 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. to the new URLs; keep a preferred canonical plus hreflang for any same-language regional duplicates.
- Rebuild reciprocal hreflangIf page A lists page B as an alternate, B must list A back — or Google ignores the pair. across every property, referencing the new URLs.
- Update 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 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..
- Verify the new host/property in Search ConsoleGoogle's free tool for monitoring crawling, indexing, and search performance. and 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. before you need the data.
- Monitor 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 — and remember the migration itself is a confounding variable in any before/after comparison.
The mental models
1. Signal vs. authority — the core trade. A ccTLDCountry-code top-level domain like .de or .co.uk — a strong geotargeting signal. maximizes 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 (automatic, unambiguous) but fragments authority (separate domains). A subdirectory maximizes authority (consolidated on one domain) but minimizes the automatic geoGenerative Engine Optimization — visibility inside AI answer engines.-signal (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. only). A subdomain sits between them. Almost every decision here is a point on that signal-vs-authority line.
2. Automatic vs. manual geo-signal. Only a ccTLD gives you the country signal for free. Everything on a gTLD — subdomain or subdirectory — has a manual signal you’re responsible for. And since Sept 2022, “manual” means 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., not a Search ConsoleA free Google service that reports how a site performs in Google Search and surfaces problems with how Google crawls, indexes, and serves it. It's first-party data straight from Google — but you don't need it to appear in results. setting. If you pick a gTLD structure, you are signing up to run hreflang correctly.
3. Structure is not a ranking lever. Google has no preference. You do not rank better by picking a shape. You rank better by being relevant, trusted, and well-linked in a market — the structure only changes how cleanly you signal which market. Kill the “which ranks better” question first; it’s the wrong question.
4. Consistency beats optimization. One structure applied cleanly across all markets is worth more than a per-market mix chosen on hunches. Consistency is what keeps hreflang clusters 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. tractable at scale.
5. Separate the international question from the general one. “Where should my blog live?” (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. in general) and “how do I serve different countries?” are different decisions with different deciding factors. The general one turns on integration and migration risk; the international one turns on the geo-signal. Don’t import the answer from one into the other.
Test yourself: ccTLD vs. Subdomain vs. Subdirectory
Five quick questions on choosing an international URL structureURL 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.. Pick an answer for each, then check.
Resources worth your time
My related writing
- Hreflang: The Easy Guide for Beginners — the mechanics you’ll depend on for any gTLD subdomain or subdirectory, plus my study of 374,756 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.-using domains showing how often 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. breaks (over 67% had an issue).
- The Beginner’s Guide to Technical SEO — where international URL-structure decisions fit in the bigger picture.
- Subdomain vs Subdirectory: Subdirectories Are Not Better Than Subdomains For SEO — my general (non-international) case that the two are functionally equivalent and most migration “wins” are confounded; read this for the “where should my blog live” version of the question.
My speaking
- How Search Works (SlideShare) — my walkthrough of 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., renderingTurning HTML, CSS, and JavaScript into the final visual page and DOM., 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., and ranking; useful background for why signals (not URL shape) drive results. (Standing disclaimer applies: “This is my understanding of systems… not going to be 100% complete or accurate.”)
From around the industry
- Managing multi-regional and multilingual sites (Google Search Central) — the source list of the three structures and their documented pros and cons.
- The International Targeting report is deprecated (Google Search ConsoleA free Google service that reports how a site performs in Google Search and surfaces problems with how Google crawls, indexes, and serves it. It's first-party data straight from Google — but you don't need it to appear in results. Help) — the September 2022 removal and what it means for declaring a subfolder’s country.
- URL structure best practices (Google Search Central) — the geotargetingConfiguring a site or URL to target users in a specific country. guidance and the no-preference position.
- Subdomains vs Subdirectories Research: 20K Keywords Analysed (SE Ranking) — the transparent correlational study across 15 markets showing ccTLDsCountry-code top-level domain like .de or .co.uk — a strong geotargeting signal. dominating international SERPs (read it as correlation, not causation).
- SEO Best Practices with Cloudflare Workers, Part 1: Subdomain vs. Subdirectory (Cloudflare) — the reverse-proxy workaround if you’re locked into a subdomain but want a subdirectory URL.
Geotargeting
Configuring a site or URL to target users in a specific country.
Related: ccTLD, Hreflang
Geotargeting
Configuring a site or URL to target users in a specific country. Done via ccTLDCountry-code top-level domain like .de or .co.uk — a strong geotargeting signal., subdirectory, or (weakest) subdomain + Search ConsoleA free Google service that reports how a site performs in Google Search and surfaces problems with how Google crawls, indexes, and serves it. It's first-party data straight from Google — but you don't need it to appear in results. geotargeting setting.
Related: ccTLD, Hreflang
Build-time retrieval analysis plus live signals for this exact article. The automatic chunk report includes a deterministic readiness score and is ready without a model download.
Search Console
sampleGA4 traffic (28d)
sampleCloudflare traffic (7d)
sampledCrUX field data (28d, phone)
sampleGoogle NLP entities
localChangelog
Updated Jul 18, 2026.
Editorial summary and recorded change details.Summary
Added ownership/governance/cost factors to the architecture decision and a migration-risk checklist, and softened an overstated hreflang-hierarchy claim.
Change details
-
Added an Ownership, governance, and cost section and a Migration risk section (redirects, canonicals, hreflang, links, sitemaps, host verification, monitoring) to the Advanced lens, plus a matching migration checklist.
Full comparison unavailable — no prior snapshot was archived for this revision.