<b>The geotargeting setting is gone — what replaced it, and what didn't</b>

<b>The geotargeting setting is gone — what replaced it, and what didn't</b>

Google removed the country-targeting setting from <code>Search Console</code>'s International Targeting report. A common reaction was mild panic. The reality is more nuanced.

Context and methodology: we compared targeting behavior on estates that had relied heavily on the manual setting before its removal, looking at whether local rankings shifted afterward.

What we found:

— For estates with clear signals — ccTLDs, server location, local language, hreflang, and local links — removal changed nothing measurable. Those signals already determined targeting; the manual override was redundant.

— The estates that felt the loss were generic TLDs (.com) with weak local signals that had leaned on the manual setting as a crutch. They had no fallback.

— Hreflang did not replace the geotargeting setting. Hreflang controls which alternate is swapped in for a matched user; it does not declare 'this whole site is for Canada.' That distinction is frequently conflated.

Nuance: server/IP location is a weak and shrinking signal in the CDN era, so don't count on hosting to carry targeting.

Limitation: 'nothing measurable' is bounded by our instrumentation; small estates with sparse data can't rule out subtle effects.

Conclusion: the setting's removal exposed which estates were relying on a crutch. Build targeting from intrinsic signals — language, links, hreflang, structure — not a dashboard toggle that no longer exists.