If you came looking for the country targeting gsc control — the dropdown in Search Console where you told Google “this site is for Australia” — stop looking. It doesn’t exist anymore. Google retired the International Targeting report’s country setting in 2022, and the option was quietly deprecated long before that. Most guides on this topic still walk you to a menu that isn’t there. The useful question isn’t “where is the setting” but “if Google no longer takes my word for which country a page targets, what signals is it reading instead — and how do I get those right?”
The Country Setting Really Is Retired — Not Moved
This trips people up because deprecations in Search Console are usually reshuffles: a report moves tabs, gets renamed, hides under “Legacy tools.” Country targeting in GSC is different. Google announced in August 2022 that it was removing the country-targeting portion of the International Targeting report entirely, and it followed through. There is no replacement toggle buried elsewhere in the interface. The reason Google gave was blunt and worth internalizing: the setting was rarely used correctly, and the geotargeting signals it was meant to supplement had matured to the point where a manual override caused more harm than help.
So the honest starting point for any international SEO plan today is that you no longer declare your target country to Google. You signal it — through your domain, your markup, and your links — and Google infers the rest. That shift from declaration to inference is the whole story, and it changes what you should spend your time on.
What the Old International Targeting Report Actually Did
The retired setting only ever applied to generic top-level domains — .com, .net, .org, .info and the like. If your site ran on a country-code TLD (.co.uk, .com.au, .sg), the setting was greyed out because a ccTLD already carries an unambiguous geographic signal. For everyone on a gTLD, the report let you pin the whole property, or a specific subdirectory or subdomain you’d registered separately, to one country. It was a tie-breaker: a way to tell Google that yourdomain.com/au/ was meant for Australian searchers when nothing else on the page made that obvious.
Critically, it was never a ranking booster. It didn’t push you up in the target country; it only helped Google decide which market a page belonged to when the other signals were ambiguous. Once hreflang adoption spread and Google’s location inference improved, that tie-breaker became redundant — and, in the hands of people who set it wrong, actively misleading.
How Google Geotargets Your Pages Now
With the manual control gone, geotargeting runs entirely on inferred signals. Google combines several, and no single one is a magic switch:
- ccTLD — the strongest automatic signal. A .de domain reads as German-market by default, no configuration required.
- hreflang annotations — the primary way a gTLD site tells Google which language-and-region version to serve to which searcher.
- Server and CDN location — a weak, secondary hint; largely moot now that most sites sit behind global CDNs.
- Local signals — links from in-country sites, a local address and phone number, currency and language on the page, and a Google Business Profile for physical locations.
- On-page language — genuinely writing in the market’s language (and dialect) does more work than any tag.
The practical takeaway: the effort you’d have spent flipping a toggle now goes into structure and markup that Google can actually verify. That’s harder to fake, which is exactly why Google prefers it.
What Search Console Still Gives International Sites
Losing the country setting doesn’t mean Search Console is useless for global sites — the reporting is still where you diagnose problems. The Performance report lets you filter clicks and impressions by country, which is how you confirm whether your German pages are actually reaching German searchers or leaking into Austrian and Swiss results. The Pages and Sitemaps reports show you which localized URLs are indexed. And while the standalone hreflang error report was folded away, hreflang mistakes still surface in coverage and enhancement data. Search console country data is a measurement tool now, not a control panel — read it to catch drift, not to steer.
ccTLD vs Subdirectory vs Subdomain: The Real Trade-Off
Because you can no longer force country targeting after the fact, your URL structure carries more weight than it used to. There is no universally correct answer — it depends on how many markets you run, your engineering resources, and how much link authority you can afford to split.
- ccTLD (example.de): the strongest geo-signal and the cleanest user trust, but every domain is a separate site in Google’s eyes. You build authority from scratch per market and pay for, secure, and maintain each domain. Right for well-resourced brands committed long-term to a few countries.
- Subdirectory (example.com/de/): all markets inherit the root domain’s authority, and it’s the easiest to deploy and maintain. The trade-off is a weaker inherent geo-signal, so hreflang has to do the heavy lifting. For most businesses this is the pragmatic winner — one strong domain beats five weak ones.
- Subdomain (de.example.com): a middle ground. Easier geo-separation than a subfolder, but Google often treats subdomains as semi-distinct, so authority sharing is inconsistent. Choose it when technical constraints make a subfolder impractical.
If you’re deciding today, default to subdirectories unless you have a specific reason not to — you keep your authority consolidated and let hreflang handle the geo-routing.
Hreflang: The Real Replacement for Country Targeting
Hreflang is now the closest thing to the old country targeting gsc setting, and it’s the tag most sites implement wrong. It tells Google which language-and-region version to show which searcher. The rules are strict:
- Use correct codes. Language is ISO 639-1 (
en,es,zh); the optional region is ISO 3166-1 Alpha-2 (en-gb,es-mx,en-au). The classic error isen-uk— “uk” isn’t the country code for the United Kingdom;gbis. Region without a language is invalid too. - Be reciprocal. If page A points to page B as its German alternate, page B must point back to A. Non-reciprocal annotations are ignored.
- Include an
x-defaultfor searchers who don’t match any listed version — usually your global or language-picker page. - Pick one delivery method. HTML
<link>tags in the head, an HTTP header (for PDFs and non-HTML files), or XML sitemap entries. Choose one — you don’t need all three, and mixing them inconsistently causes conflicts.
Region codes are optional and often should be omitted. If you have one Spanish page for all Spanish speakers, use es, not es-es — the bare language code serves every Spanish market. Only add a region when you genuinely maintain a market-specific version (say, Mexican Spanish with local pricing).
The Auto-Redirect Trap
A tempting shortcut is to auto-redirect visitors by IP address or browser language — send anyone with a French IP to /fr/ automatically. Don’t. Googlebot crawls predominantly from US-based IPs, so IP redirection can trap the crawler on your US version and prevent it from ever seeing — and indexing — your other language pages. You end up invisible in the markets you were trying to serve. The correct pattern is a suggestion, not a forced redirect: show a dismissible banner (“Looks like you’re in France — visit our French site?”) and let both the user and Googlebot reach any version by URL. This preserves crawlability while still nudging humans to the right place.
Beyond Google: Baidu, Yandex, and Naver
If your markets include China, Russia, or South Korea, Google isn’t the whole picture — and these engines don’t read Google’s signals. Baidu dominates China, favors simplified-Chinese content, ideally on infrastructure inside or near China, and has its own webmaster tools and content rules (plus the reality of the Great Firewall). Yandex leads in Russia and weights local relevance and its own Webmaster verification. Naver is South Korea’s default, blends search with its own portal content, and rewards presence in its ecosystem over classic backlinks. Treat each as a separate project with its own submission tools and ranking logic — porting a Google-optimized page over and hoping is how international expansions stall.
A Workflow That Replaces the Missing Toggle
Without a single setting to flip, international SEO becomes a per-market discipline: research, structure, verify, monitor. This is where SEO Rocket fits — it runs keyword research on real Ahrefs data with a per-country market selector, so you see actual German search volume for German terms rather than guessing from US numbers. Its rank tracking follows positions country by country, which is how you confirm a localized page is landing in the right market now that no toggle vouches for it. The real-crawler site audit catches the errors that quietly break global sites — non-reciprocal hreflang, wrong region codes, duplicate content across near-identical language versions — and competitor gap analysis runs per market, because the ranking opportunity in Singapore rarely matches the one in the UK. It’s an SEO measurement and workflow layer, not a translation service; you still need real localized copy. As a Singapore consultant working across English, Chinese, Malay, and Tamil markets, the founder built this on a playbook proven across 1,000,000+ ranking pages — multi-market SEO is the native problem, not an afterthought.
Frequently Asked Questions
Where is the country targeting setting in Google Search Console?
It no longer exists. Google removed the country-targeting option from the International Targeting report in 2022. There is no replacement toggle in the interface — geotargeting now relies on your ccTLD, hreflang annotations, and local signals rather than a manual declaration.
How do I target a specific country without the GSC setting?
Use the signals Google actually reads: a country-code TLD for an unambiguous single-market signal, or a gTLD with correct hreflang tags for multi-market sites. Reinforce with in-country links, local language and currency, and a Google Business Profile if you have a physical presence. There’s no shortcut toggle anymore.
Does GSC still show country data?
Yes. The Performance report filters clicks and impressions by country, letting you verify whether each localized version reaches its intended market. Search Console country data is now for measurement and diagnosis, not for setting a target.
Do I still need hreflang if I use a ccTLD?
If you run a single ccTLD for one market, hreflang is optional. But the moment you serve multiple languages or regions — even across several ccTLDs — hreflang tells Google how those versions relate, so it shows the right one to each searcher and doesn’t treat them as duplicates.
