Geotargeting in Google Search Console

Geotargeting is the country half of international wiring: telling Google which market a site section serves — and its Search Console chapter needs a present-tense correction, because the famous International Targeting report (the country dropdown veterans remember) has been deprecated: Google retired the manual country setting, leaning fully on the signals it infers. Which makes modern geotargeting a signals discipline rather than a dropdown — here's what actually sets country today, per structure, and how to verify it's working.

What sets country targeting now

1. ccTLDs — the automatic case: example.de targets Germany, inferred, always did — the structure decision's strongest signal, no configuration involved (and no override: a ccTLD can't be re-aimed at another country, which is its rigidity priced in).
2. Hreflang's region declarations — the workhorse: en-gb on the /uk/ folder is the per-page country statement the system actually reads at scale; for generic-TLD structures this is now the primary explicit signal, which upgrades hreflang correctness from important to load-bearing.
3. The on-page evidence layer: the localisation signals — currency, addresses, phone formats, local language variants, local business markup — the corroboration Google reads when inferring who a section serves.
4. The off-page evidence: links from the market's web, local mentions, local traffic patterns — country association earned the way all association is, per the neighbourhood physics.
5. What doesn't: server location (retired by CDN reality, per the hosting rules) and the deprecated dropdown — remove it from checklists and inherited documentation.

The practical setups

Generic TLD + country subfolders (the standard): hreflang with regions wired per the two laws, localisation genuine per folder, and the evidence layers accumulating — this is the whole configuration; there is no separate geotargeting step anymore. Single global site, no versions: nothing to geotarget — rank where relevance and authority reach, localise the trust basics for international buyers, and add versions when markets justify them per the matrix planning. Mixed structures (ccTLD flagship + subfolder rest): each piece follows its own rule above — coherent, common, fine.

Verifying targeting works

The instruments: per-market rank checks (location-set spot checks or tracker locales — the right version ranking in the right country's results is the definition of success), Search Console segmented per section (folder properties: each market's queries/impressions by country in the performance report — the /de/ folder earning German impressions is targeting working; earning US ones is a wiring smell), and the wrong-version symptom watch: the US page ranking in the UK signals hreflang gaps (usually return-link failures) or a thin local version losing to its stronger sibling on merit — the diagnosis fork being whether the local version competes at all.

Frequently asked questions

Google keeps showing our .com to a country we serve from a ccTLD. Why?

The .com's page is winning on merit for that query — country signals bias selection among equivalents, and a stronger non-local page beats a weaker local one. Fix the local version's competitiveness (content, links per the market programme) and ensure the pair is hreflang-linked so the systems know they're siblings.

Can one subfolder target multiple countries (e.g., /latam/)?

Regional folders work as language targets (es for the region) rather than multi-country ones — hreflang has no region-group values (no es-latam), so the pattern is language-level hreflang (es) with x-default routing, or per-country folders where countries genuinely diverge. Don't invent codes; the error files are full of them.

Does geotargeting restrict a section to its country?

Biases, never walls — a targeted section still ranks anywhere it's the best answer (the UK folder serving an Australian searcher when no AU version exists is the system working). The wiring aims; the ranking still runs on the pair every guide ends with — market-fit content and market-local authority (our compass).