gTLD

What a gTLD is

A gTLD (generic top-level domain) is a domain ending not tied to any country — .com, .org, .net, plus the newer wave like .shop, .app, and .dev. For international SEO the defining property is neutrality: a gTLD tells Google nothing about which country you're targeting, which means you have to say it through other signals.

That neutrality is a feature and a chore. Feature: one .com can credibly serve forty markets from subdirectories, pooling every backlink into one domain. Chore: without explicit targeting work, Google guesses your audience from whatever evidence it finds — and it guesses conservatively.

How Google treats gTLDs

Google's multi-regional documentation is plain about it: gTLDs carry no inherent geotargeting. Historically you could set a target country per property in Search Console's International Targeting report; that report was deprecated (country setting retired in 2022, hreflang report later), so today geotargeting a gTLD is done entirely through hreflang annotations and on-page locale evidence — currency, addresses, phone formats, local-language content, and links from in-country sites. Server location, per the same doc, is no longer a meaningful signal thanks to CDNs.

Note the mirror-image gotcha from the ccTLD world: Google treats a set of two-letter domains people use generically — .io, .ai, .co, .me, .tv — as gTLDs. Your .ai startup domain is effectively a gTLD in Google's eyes, with all the same targeting obligations.

Geotargeting levers on a gTLD

gTLD vs ccTLD, the short version

A gTLD with subdirectories concentrates authority: every link to any market strengthens all markets. ccTLDs buy a stronger per-country signal at the price of starting each domain from zero. For most teams the gTLD route wins until per-country operations justify the ccTLD overhead — we walk through a real decision in the ccTLD vs gTLD case study, and the architecture options are compared in International SEO Site Structure.

Do the new "meaningful" gTLDs help? Google has said repeatedly that keyword TLDs (.shop, .lawyer) confer no ranking advantage. Pick them for branding if you like them; don't pick them for SEO.

One honest caveat on cheap new gTLDs

While Google scores no TLD higher or lower by policy, some bargain-bin new gTLDs have attracted enough spam registrations that their neighborhoods are rough — email deliverability filters and some corporate firewalls treat them with suspicion, and users hesitate to click unfamiliar endings. That's a trust and conversion problem, not a rankings problem, but it lands on the same bottom line. If the domain will carry a serious commercial site, weigh the reputation of the ending, not just its price.

How to check gTLD geotargeting

1. Inventory your locale sections and confirm each has hreflang annotations — validate reciprocity with the hreflang validator (or generate clean tags with the generator).
2. In Search Console, segment the Performance report by country per section (URL-prefix properties per locale folder make this painless). Each section should win its own market's queries.
3. Spot-check on-page locale evidence: does /fr/ show euros, French dates, a French address? If it's English content with a French URL, no signal exists.
4. Test SERPs per market with &gl= country overrides and confirm the intended section surfaces.
5. Check for forced IP redirects — they blind US-crawling Googlebot to your non-US sections. Banners, not redirects.

Common mistakes and fixes

• Assuming a .com "targets the US." It targets nothing; US dominance in your traffic is your content and links, not the TLD. Fix: add explicit signals for every market you want.
• Hreflang as the only lever. Tags on unlocalized content match versions that don't differ. Fix: localize first.
• Region-only hreflang codes. hreflang="uk" is invalid (and uk isn't even the ISO code — gb is). Fix: language, optionally plus region: en-gb.
• Splitting locales across subdomains without a reason. Fix: default to subdirectories unless infrastructure genuinely demands otherwise — background in the international SEO entry.
• Planning around the deprecated Search Console country setting. Fix: it's gone; hreflang plus locale evidence is the whole playbook now.

FAQ

Does .com rank better than other gTLDs?

No inherent advantage. .com correlates with age and links because it's had a forty-year head start, but Google doesn't score the TLD itself. A strong .dev beats a weak .com.

Can one gTLD target multiple countries at once?

Yes — that's its core strength. Separate localized sections plus hreflang let one domain hold distinct versions for the UK, Australia, and Canada, each surfacing in its own market.

Is .io good or bad for SEO?

Neutral. Google treats it as generic, so it behaves like a gTLD. The risks are non-SEO: pricing, registry stability, and the fact that its territorial status has been under review since the Chagos Islands handover.

How do I target a single country with a gTLD?

Localized content with unambiguous locale evidence, hreflang with the region code, and local links. That combination approximates most of what a ccTLD gives you, without abandoning your domain authority.

gTLD or ccTLD for a new international site?

Default to gTLD + subdirectories; graduate to ccTLDs only when per-country operations and budgets justify independent domains.