Are new gTLDs really changing the game for geographic targeting in SEO?

Are generic gTLDs really geographically neutral?

Unlike ccTLDs (.fr, .de, .es) that automatically signal national targeting to Google, new generic gTLDs (.tech, .shop, .blog, .agency...) are considered neutral. Google does not assign any geographical connotation to them by default.

This means that a site with a .berlin or .paris domain will not automatically be prioritized for Berlin or Paris — despite what the name suggests. These extensions operate like a .com or .net: they require manual configuration if you wish to target a specific country.

How do I configure geographic targeting in Search Console?

Search Console allows you to set geographic targeting for an entire domain, a subdomain, or a subdirectory. For a neutral gTLD, you enable this option and select the target country. Simple in theory.

But the reality is more nuanced. This manual declaration is just one signal among others. Google also takes into account hosting, content language, local backlinks, address mentions, and most importantly, user behavior. A .tech targeted for France but hosted in Canada with content in English will never be treated as a genuine French site.

Can I mix several geographic targets on a single domain?

Absolutely. This is one of the key advantages of neutral gTLDs. You can create subdomains (fr.mysite.tech, uk.mysite.tech) or subdirectories (mysite.tech/fr/, mysite.tech/uk/) and configure each one individually in Search Console.

Each entity then becomes a distinct geographic signal. This is exactly the same mechanism as with a multilingual .com. No technical difference, no penalty, no advantage either — just a neutrality that requires rigorous setup.

• New gTLDs are geographically neutral by default, just like .com or .net
• Geographic targeting is manually configured in Search Console for each verified subdomain or subdirectory
• This declaration remains a weak signal: hosting, language, backlinks, and user behavior matter just as much, if not more
• A domain can target multiple countries through distinct sub-structures, each configured individually
• No intrinsic SEO advantage of generic gTLDs — they neither boost nor penalize, they just require diligence

Is this statement consistent with real-world observations?

Yes, and it's actually one of the few subjects where Google has been consistent. Since the widespread rollout of new gTLDs, real-world feedback confirms this geographical neutrality. A .shop or .tech behaves exactly like a .com in terms of geolocation.

But there's a catch. This neutrality also means you have to manually reconstruct all signals. A ccTLD .fr benefits from a presumption of French targeting — even without configuration. With a neutral gTLD, you start from scratch. If you forget to configure Search Console or your on-page signals are weak, Google won't make any assumptions in your favor.

What nuances should be added to this statement?

First point: not all gTLDs are created equal. Google maintains an internal list of gTLDs with geographical connotations (.london, .paris, .nyc...) that it treats differently. Mueller does not mention this distinction, and it's a blind spot in his statement. [To be verified]: what proportion of new gTLDs remains genuinely neutral in Google's algorithm, versus those that carry an implicit bias?

Second nuance: Search Console configuration is not magic. If you declare targeting France but 90% of your backlinks come from the United States and your content is in American English, Google will ignore your setting. This signal is weak; it does not compensate for structural inconsistencies.

In what cases does this rule not fully apply?

If you are aiming for hyperlocal SEO — local business, home services, regional professional — neutral gTLDs are a handicap. A ccTLD .fr sends a strong and coherent signal that Google values in local results, especially when paired with a Google Business Profile.

With a .tech or .online, you need to overcompensate with other signals: extremely coherent NAP address mentions, quality local backlinks, geolocated content, Schema.org LocalBusiness structuring. This is doable, but it involves more work for equivalent results. Frankly, why complicate things if your business is purely local?

What should you concretely do if you are using a neutral gTLD?

First, check and configure each property in Search Console. Main domain, subdomains, subdirectories — each must be added and individually verified. Then, set geographic targeting for each entity aiming at a specific country.

But don’t stop there. Strengthen all other geographic signals: content language (with hreflang tags if multilingual), local address and phone mentions, backlinks from target country sites, hosting on local servers or through a performant CDN. Search Console targeting is just one building block among others.

What mistakes to avoid with new gTLDs?

The classic mistake: thinking that the domain name is enough. Buying a .london or .paris and assuming that Google will automatically understand. No. These extensions remain generic gTLDs and require explicit configuration.

Another trap: not checking sub-structures. You configure the main domain for targeting France but forget to verify and configure the subdomain en.mysite.tech aimed at the United Kingdom. Result: Google does not know what to do with this subdomain and applies default targeting — that is, none.

How to check if the configuration is working correctly?

Go to Search Console, section Settings > International targeting. Check that each property displays the desired target country correctly. If the option does not appear, it means Google considers your domain as a ccTLD or a gTLD with geographical connotation — in which case, targeting is automatic and unmodifiable.

Then, monitor performance by country in Search Console reports. If you target France but 80% of your impressions are coming from elsewhere, your geographic signals are inconsistent. Dig into backlinks, content language, search queries. The problem is structural, not just a checkbox.

• Check and configure each subdomain and subdirectory individually in Search Console
• Explicitly set geographic targeting for each property aiming at a specific country
• Enhance on-page geographic signals: language, address, phone, localized content
• Build a consistent local backlink profile aligned with the target country
• Implement hreflang tags if you manage multiple language or geographic versions
• Monitor country performance reports in Search Console to detect inconsistencies