Geotargeting

Long definition

Geotargeting answers a binary question: "Is this content meant for users in country X?" If yes, Google can preferentially surface it to searchers in that country and de-prioritize it elsewhere. Multiple signals contribute, in roughly decreasing strength:

ccTLD. A .es, .de, .fr domain is a hard, implicit declaration of country target. Google does not let you override it. See ccTLD vs gTLD for the trade-offs.

hreflang. The page-level signal that declares the locale (language + optional region) of a page and points to its translated/localized siblings. Doesn't itself say "rank this in country X" — it says "this is the right page for users with locale Y." Google still chooses based on relevance, but hreflang prevents the wrong locale variant from outranking the right one.

Search Console country targeting. Until November 2022, gTLD sites could declare a country target in International Targeting. Google deprecated the top-level setting, citing that algorithmic signals had become reliable enough. Sub-path targeting via the older "Set Geographic Target" feature also went away. For most gTLD sites, geotargeting now relies entirely on hreflang, on-page localization, and natural signals.

Server / IP location. Weak. Modern CDNs make server location uncorrelated with audience target, and Google has explicitly downweighted this signal. Hosting in-country has minor SEO benefit at best; hosting on a fast global CDN is usually better for both UX and rankings.

Local signals. Currency on the page, address with country, language, local phone format, links from in-country sites, mentions in local press. Algorithmically aggregated; no single one is decisive.

For multi-country sites on a gTLD, the canonical setup is:

• Subdirectories per country/locale (/es/, /de/, /mx-es/)
• Complete hreflang annotations (including x-default)
• Localized content (not just translated — local prices, contacts, regulations)
• A well-configured GSC property per section to monitor performance per country

Geotargeting is a different problem from translation. A site translated into Spanish but with no localization (still showing US prices, US toll-free phone) gets weak geotargeting signals into Spanish-speaking markets even with hreflang in place.

Common misconceptions

• "hreflang is geotargeting." Hreflang declares locale match, not country target. A page can be hreflang="es-MX" and rank in Spain if no better Spain-targeted alternative exists. Geotargeting is the broader picture.
• "Server location matters a lot for SEO." It doesn't. CDN best practice (low TTFB everywhere) trumps in-country hosting in nearly every case.
• "You still set country targeting in Search Console." Not at the top-level since November 2022. Hreflang and on-page signals do that work now.
• "Translating the content is enough." It isn't. Localization (currency, units, contacts, examples, legal) plus hreflang plus often a different URL pattern is what produces functioning multi-country SEO.