Can you really target different countries on the same domain without using subdomains?

What is the real difference between gTLDs and ccTLDs for geographic targeting?

A gTLD (generic Top-Level Domain) like .com, .org, or .net sends no geographic signal by default. You decide the targeting using Search Console. In contrast, a ccTLD (country code Top-Level Domain) like .fr, .de, or .co.uk already carries an intrinsic geographic signal: Google automatically associates it with the corresponding country.

Mueller's statement clarifies that you can set a country targeting for the root domain on a gTLD, and then another for a subdirectory. For example: example.com targeted to the United States, example.com/uk/ targeted to the United Kingdom. The most specific parameter wins — here, /uk/ will override the root targeting.

Why is this granularity not available on ccTLDs?

Because the ccTLD already enforces country targeting at the domain level. You cannot tell Google that a .fr targets Germany or that .fr/uk/ targets the United Kingdom: the national extension overrides any manual configuration.

This structural limitation explains why many multilingual strategies prefer gTLDs with subdirectories rather than multiple ccTLDs. The flexibility is incomparably superior, especially when managing secondary markets or regional tests.

How does Search Console apply the “most specific parameter” principle?

Search Console lets you define a geographic targeting at the root domain level, then override it at the level of each subdirectory. If you set example.com for the USA and example.com/fr/ for France, Google will use the /fr/ configuration for everything under that branch.

Note: this granularity stops at the subdirectory level. You cannot target an isolated page or a sub-subdirectory differently from its immediate parent. The hierarchy must remain consistent — otherwise, you send conflicting signals that dilute your local relevance.

• gTLD + subdirectories: flexible and section-configurable country targeting
• ccTLD: fixed and unmodifiable country targeting at the subdirectory level
• Priority: the setting defined on the most specific path always prevails
• Limitation: no targeting at the page or isolated sub-subdirectory level
• Use case: multilingual sites, SaaS platforms, international e-commerce on a single infrastructure

Is this statement consistent with observed practices in the field?

Yes, and it’s even a long-documented feature. Field tests show that Google does indeed respect the targeting at the subdirectory level on gTLDs, as long as the on-page signals (hreflang, content language, currencies, local contact information) are consistent.

Where it gets tricky: many SEOs underestimate the importance of secondary signals. Search Console targeting is an indicator, not an absolute override. If your /fr/ displays content in English, prices in dollars, and US addresses, Google will completely ignore you — and rightly so.

What practical limitations does Mueller not mention?

The first limitation: the granularity stops at the first-level subdirectory. You cannot target example.com/blog/uk/ differently from example.com/blog/ if the latter already has a defined targeting. The hierarchy imposes its rules.

Second limitation: geographic targeting absolutely does not guarantee a preferential ranking in the targeted country. It’s an eligibility filter, not a boost. If your /fr/ content is mediocre compared to well-optimized local .fr sites, you won’t gain anything. [To be verified]: Google has never communicated the exact weight of this signal against other local relevance factors (local backlinks, mentions in regional media, user behavior).

In what cases can this setup backfire?

Classic mistake: targeting too finely when your content is not truly localized. If you’ve merely translated US content into French without adapting examples, units, or cultural references, geographic targeting will only expose your shortcomings.

Another trap: mixing ccTLDs and subdirectories in a hybrid architecture. I've seen sites with example.fr for France AND example.com/fr/ for “testing”. Result: total cannibalization, conflicting signals, ranking plummeting. Choose a strategy and stick to it.

How to correctly set geographic targeting on a multi-market gTLD?

First step: in Search Console, add each subdirectory as a separate property. You need to create a property for example.com/, one for example.com/fr/, one for example.com/de/, etc. Without this, you cannot set granular targeting.

Next, for each property, go to Settings → International Targeting → Country, and select the target country. Ensure that the root targeting does not contradict your subdirectories — if example.com is targeted “United States” and you want a /uk/, it’s consistent. If the root is “not targeted,” even better to avoid any ambiguity.

What on-page signals should you strengthen for Google to respect your targeting?

Search Console targeting is a signal among others. You must reinforce it with tangible elements: content written in the local language (not just translated), prices displayed in the local currency, local phone numbers and addresses, mentions of relevant cities or regions.

And most importantly: implement hreflang correctly. Each page must point to its language and regional variants with hreflang tags in the header or in the XML sitemap. This is the precision layer that prevents Google from mixing your UK and US versions in the SERPs.

What mistakes should you absolutely avoid in a multi-market configuration?

Never leave a subdirectory without a defined targeting if you have set one on others. Google might interpret this void as a contradiction and ignore your settings. Be thorough.

Also avoid targeting a country that does not correspond to the language or actual audience of the subdirectory. If /es/ displays content for Spain but you target it at Mexico, you create a cognitive dissonance that harms user experience and relevance signals.

• Create a separate Search Console property for each geolocated subdirectory
• Set a clear country targeting for each property, in line with the content
• Implement hreflang on all affected pages (tag or XML sitemap)
• Truly localize the content: language, currency, cultural references, contact information
• Regularly audit the logs to ensure Googlebot is crawling each localized version correctly
• Monitor positions and traffic by country to detect any targeting anomalies