The geotargeting setting in GSC that overrides your hreflang intent

The geotargeting setting in GSC that overrides your hreflang intent

A configuration mistake that lives outside your code: a Search Console geotargeting setting that contradicts your hreflang strategy.

Background. For ccTLDs, country association is automatic and not user-settable — .de targets Germany inherently. For generic TLDs on subfolders or subdomains, the legacy International Targeting report let you assign a single country to a property. That setting and hreflang answer different questions, and people conflate them.

The conflicts we find:

— A whole gTLD property pinned to one country in GSC, while hreflang tries to serve a dozen locales — the property-level country signal pulls against the per-page intent
— A site that should target a language globally (one es for all Spanish speakers) but is geo-pinned to Spain, suppressing relevance in Latin America
— Teams still relying on the country-targeting setting, unaware Google has been deprecating the manual control

The fix:

— For multi-country sites on a gTLD, prefer hreflang plus subfolders and avoid a single property-level country lock
— Let language-only targeting stay language-only — don't bolt a country onto a globally-relevant language

Limitation, stated plainly: Google has shifted away from the manual geotargeting control, and behavior here has changed over time, so verify the current state of your property rather than trusting old screenshots. The durable principle survives the UI churn — page-level hreflang and property-level country must not encode contradictory intent.