How can you effectively target multiple countries with a single domain without losing your local SEO?

Why does Google allow multiple geographic targets on the same domain?

John Mueller's statement addresses a common issue: how to structure a multilingual or multi-country site without multiplying domains. Historically, many SEOs believed that a domain could only target one country via Search Console.

In reality, Google accepts differentiated geographic targeting at the subfolder and subdomain levels. The homepage can target one country, while /fr/, /de/, /us/ target respectively France, Germany, and the United States. The engine always prioritizes the most precise signal available.

What exactly is the “most specific targeting”?

Google applies a hierarchy of specificity in geographic signals. If you configure example.com to target the UK and example.com/fr/ for France, the French URLs will inherit the France targeting — not the UK targeting from the root.

This logic also applies to subdomains: fr.example.com can target France while de.example.com targets Germany. The most granular level always takes precedence in the geolocation algorithm.

Why does this method exclude ccTLDs?

A ccTLD like .fr or .co.uk already carries an inherent geographic signal that Google reads by default. It's impossible to bypass this marker by adding a different targeting in Search Console.

If you own example.fr, all URLs will be interpreted as French, even with a /us/ or a subdomain us.example.fr. The ccTLD overrides all other targeting parameters. This is a technical constraint of the algorithm, not a bug.

• A generic domain (.com, .net, .org) allows multiple targeting through subfolders or subdomains
• Google always prioritizes the most precise geographic signal available in the URL hierarchy
• ccTLDs block any alternative targeting: the TLD imposes its default geolocation
• Configuration is done in Search Console at the property level (root domain, subfolder, subdomain)
• This strategy requires consistent hreflang tagging to avoid signal conflicts

Does this statement align with the field observations of SEOs?

Yes, overall. Practitioners have observed for years that Google handles multiple targeting correctly on a .com or .net. International e-commerce sites structuring their country versions in /fr/, /uk/, /de/ achieve distinct local rankings without contamination.

However, the quality of targeting heavily depends on the hreflang tagging. Without correct annotations, Google may mix versions or ignore the Search Console targeting. [To be checked]: the relative impact of Search Console targeting versus hreflang remains unclear in the official documentation — Mueller does not specify which takes precedence in case of conflict.

What nuances should be considered about ccTLDs?

The rule “ccTLD = locked targeting” has exceptions. The .co, .io, .ai, or .tv are technically ccTLDs but treated as gTLDs by Google for years. They thus allow for customized Search Console targeting.

Another subtlety: some .fr sites achieve rankings in other countries if their authority and content signals (language, hreflang, local backlinks) are strong enough. This is not the norm, but it happens with premium domains that have a solid history.

What risks does this multi-targeting strategy pose?

The main pitfall: creating inconsistencies between Search Console targeting, hreflang, content language, and backlinks. If example.com/fr/ targets France but publishes content in English with hreflang pointing to German URLs, Google ignores everything.

The second risk: cross-country cannibalization. If two subfolders target close markets (France and French-speaking Belgium), without rigorous hreflang, the URLs may compete in the SERPs. I’ve seen cases where /fr/ and /be/ were competing for the same queries in France.

How do you properly set up multi-country targeting on a generic domain?

First step: structure the site in dedicated subfolders or subdomains. Example: example.com for the main market (let's say the USA), example.com/fr/ for France, example.com/de/ for Germany. Avoid hybrid structures like /fr-FR/ or /fr-fr/ — keep it simple.

In Search Console, add each subfolder or subdomain as a distinct property. You can then define specific geographic targeting for each in the settings. Google will read this signal as a priority for the relevant URLs.

What technical parameters should accompany Search Console targeting?

The hreflang is non-negotiable. Every page of each country version must point to its linguistic and geographical equivalents with correct hreflang tags (lang="fr-FR", lang="de-DE", lang="en-US", etc.). Without this, Search Console targeting remains a weak signal.

Also consider localized content: native translations, currencies, local phone numbers, adapted legal notices. Google cross-references signals. If example.com/fr/ displays prices in dollars and a footer in English, the France targeting won’t hold much weight.

Should ccTLDs be avoided for international use?

Not necessarily. ccTLDs remain the strongest geographic signal for a single market. If you only target France, a .fr often outperforms a .com/fr/ due to local trust and TLD signal.

However, if your international expansion is likely or already planned, starting with a .com and multi-country architecture offers more flexibility. You avoid domain multiplication, authority dilution, and the complexity of managing multiple properties.

• Use a generic domain (.com, .net, .org) to allow for multiple targeting
• Structure your site in subfolders (/fr/, /de/, /us/) or subdomains (fr.example.com, de.example.com)
• Declare each subfolder or subdomain as a distinct property in Search Console and configure its geographic targeting
• Implement rigorous hreflang tagging on all pages with their linguistic and geographic variants
• Truly localize content: language, currencies, contact information, legal notices, UX adapted to the target market
• Obtain backlinks from local sites to strengthen the geographic signal of each country version