Geo-targeting (Search Console)
Also known as: GSC geo-targeting, international targeting
Geo-targeting in Google Search Console is a setting that explicitly tells Google which country you want a property to target. Available for generic top-level domains (gTLDs like .com, .net) and subdirectory/subdomain structures — not for country-code TLDs (which inherit geo-targeting from their TLD). Useful for clarifying intent when your URL structure isn't geographically explicit.
Where to find geo-targeting in Search Console
The setting moved to the new Search Console UI as “Legacy Tools” → “International Targeting” → “Country” tab. There you can:
- Select a target country for the verified property
- View hreflang errors detected across the site
- Mark the property as “unspecified” if it serves multiple regions
The setting applies at the verified property level — so if you have example.com, example.com/uk/, example.com/de/ as separate properties, each gets its own geo-target.
When to use geo-targeting
The setting matters when:
- Your domain is a gTLD (.com, .net, .io, .agency) without geographic implication
- You use subdirectories or subdomains for regions (
example.com/uk/oruk.example.com) - You don’t have hreflang fully implemented yet — geo-targeting can be a stopgap
The setting does NOT matter when:
- You use ccTLDs (
example.co.uk) — ccTLDs inherit geo-targeting from their suffix and the Search Console option is grayed out - Your site is genuinely global with no preferred country — leave it “Unspecified”
- You have rich hreflang implemented — hreflang is more granular and accurate
What geo-targeting actually does
It nudges Google’s understanding of which country the property primarily serves:
- Users in that country get the property prioritized in their local search
- Users outside that country may see it less often unless hreflang routes them otherwise
The effect is real but secondary to other signals (hreflang, content language, server location, backlinks from country).
Common mistakes
- Over-restricting to one country — if your site serves multiple regions, geo-targeting one will hurt visibility in the others
- Conflicting with hreflang — geo-targeting “US” while hreflang says fr-FR sends mixed signals; Google may pick either
- Forgetting to set when launching a regional subdirectory — common for legacy sites adding international expansion
Geo-targeting vs hreflang
| Geo-targeting (GSC) | hreflang | |
|---|---|---|
| Granularity | Whole property | Per-page |
| Languages handled | No (country only) | Yes (language + region) |
| Implementation | Search Console UI | HTML / sitemap |
| Best for | Single-country focus | Multi-region multi-language |
Use both when applicable: geo-target tells Google the property’s primary market; hreflang tells it which page version to show per locale.
Resocial perspective
For most international SEO clients we work with, hreflang is the primary tool. Geo-targeting is the supplementary nudge. We always check the GSC geo-targeting setting on intake — about 20% of clients have it set wrong (or to “Unspecified” when they should have set a country), and the correction lifts country-specific rankings modestly. See our country-domain-strategy for the broader framework.
- Resocial service →
/services/international-seo/country-domain-strategy/ - Read on the blog →
/blog/hreflang-vs-canonical/