Geotargeting and International Search Console Setup: A Step-by-Step Guide
Geotargeting and international Search Console settings help websites target specific countries and improve global search visibility. This guide explains the setup process, country targeting, and key international SEO considerations.
August 8, 2026
Quick Nav
Geotargeting no longer works through a manual Search Console setting. Google retired the International Targeting report, including the country-targeting toggle, in September 2022. Geographic relevance today comes from a combination of signals instead: your domain structure, correct hreflang implementation, server or hosting location, and on-page content signals like address, currency, and language.Setting up Search Console correctly for international sites now means configuring separate properties per region or subdirectory and monitoring hreflang health through other reports, not selecting a country from a dropdown.
Most geotargeting guides still describe a Search Console feature that no longer exists. This one covers how geographic targeting actually works now.
Search a dozen SEO blogs for “Search Console geotargeting setup” and most still describe the same thing: go to International Targeting, pick a country, done. That feature is gone. Google retired it in September 2022.
This matters more than it sounds like it should. Teams still following outdated guides are configuring a setting that doesn’t exist anymore, while missing the signals that actually control geographic relevance today.
This guide covers what geotargeting looks like now, step by step, for enterprise sites operating across multiple countries.
Why "Search Console Geotargeting Setup" Doesn't Mean What It Used To
The old International Targeting report did two things: it reported hreflang errors, and it let you manually tell Google which country a site targeted.
Google’s own Search Console Help documentation confirms the report is deprecated, stating plainly that the ability to manually set a country target had little value for the ecosystem and is no longer supported.
That’s a real shift, not a cosmetic one. There’s no manual override anymore. Google decides geographic relevance entirely from signals your site already sends, whether you configure them deliberately or not.
For enterprise sites, that makes deliberate signal design more important, not less. Nobody can fix a mistargeted country with a dropdown menu anymore.
How Google Actually Determines Geographic Relevance Now
Four signals do the work the old manual setting used to do.
Domain structure.A country-code domain like .de sends the strongest single geographic signal. Subdirectories and subdomains send a weaker, more indirect one.
Hreflang tags.These tell Google which page serves which language and region, and how different regional pages relate to each other.
Server or hosting location.A weaker signal than it once was, given how much content is served through global CDNs now, but still a factor Google considers.
On-page content signals.Local addresses, currency, phone formats, and language all reinforce which market a page is actually built for.
No single signal overrides the others. Google weighs them together, which is exactly why a single wrong hreflang tag or an ambiguous URL structure can quietly undermine everything else.
Step 1: Choose a URL Structure That Signals Geography Clearly
Before anything else, decide how your international structure is organized. Three common patterns:
- Country-code domains (example.de, example.fr), the strongest signal, highest maintenance cost
- Subdirectories (example.com/de/, example.com/fr/), moderate signal strength, easiest to maintain
- Subdomains (de.example.com), weaker signal than subdirectories, similar maintenance overhead
There’s no universally correct choice. What matters is picking one and applying it consistently, since a mixed structure, some markets on subdirectories, others on separate ccTLDs with no clear logic, confuses the signal instead of strengthening it.
Step 2: Set Up Search Console Properties Correctly for Each Region
Each distinct URL pattern needs its own Search Console property. A subdirectory structure needs a property per subdirectory, or a domain property that lets you filter by path. Separate ccTLDs each need their own property entirely, since they’re functionally different domains as far as Search Console is concerned.
This matters because performance data, indexation status, and coverage issues are all reported per property. Without properties set up correctly per region, a technical problem affecting only the French market can hide inside aggregated data that looks fine overall.
Verify every property individually. A property that was never verified won’t report data at all, and enterprise sites with dozens of regional URLs sometimes discover months later that several regions were never actually being monitored.
Step 3: Implement Hreflang Correctly
Hreflang is the single most error-prone part of international setup, and it’s worth treating as its own dedicated workstream rather than an afterthought.
The core rules are simple, even though the implementation rarely is at scale: every page needs a hreflang tag pointing to every regional and language variant of that page, including a self-referencing tag pointing to itself, and every one of those tags needs to be reciprocated on the pages it points to.
This is where most enterprise sites go wrong.Search Engine Land’s analysis found that roughly 31% of international websites contain hreflang errors, most commonly missing return tags, where page A points to page B but page B doesn’t point back.
A missing return tag doesn’t just fail quietly. It can cause Google to disregard the entire hreflang cluster for that page, effectively undoing the geographic signal the rest of the setup was built to send.
A basic hreflang set for a page with UK and French versions looks like this:
<link rel=”alternate” hreflang=”en-gb” href=”https://example.com/uk/” />
<link rel=”alternate” hreflang=”fr-fr” href=”https://example.com/fr/” />
<link rel=”alternate” hreflang=”x-default” href=”https://example.com/” />
Each regional version needs the full set, including a self-referencing tag pointing to itself, not just a link to the other versions. This is the step most enterprise implementations skip, and it’s the one that causes the “missing return tag” error described above.
Step 4: Use Server Location and Hosting Signals Deliberately
Server location carries less weight than it used to, since most enterprise sites now serve content through CDNs with edge locations in multiple countries regardless of where the origin server sits.
That doesn’t make it irrelevant. For markets where local hosting is still practical, it remains one more consistent signal reinforcing the same geographic story the URL structure and hreflang tags are already telling.
Treat it as a tiebreaker signal, not a primary one. Getting domain structure and hreflang right matters more than optimizing server location on its own.
Step 5: Verify Geotargeting Is Working
Without the old manual report, verification now happens across several places instead of one dashboard.
Check the Coverage and Indexing reports per property to confirm regional pages are being indexed as expected. Use the Performance report, filtered by country, to see which countries are actually generating impressions for each regional URL. Spot-check hreflang implementation using a crawler that validates return tags, since Search Console’s remaining reports don’t surface hreflang errors as directly as the old deprecated report did.
The absence of a single “is this working” report is genuinely a downgrade in convenience. It doesn’t mean geotargeting became unverifiable, just that verification now takes more deliberate cross-referencing.
Common Geotargeting Mistakes at Enterprise Scale
A handful of patterns account for most enterprise geotargeting problems.
Following outdated setup guides.Teams still looking for the deprecated country-targeting setting waste time searching for a feature that isn’t coming back.
Inconsistent URL structure across markets.Some countries on subdirectories, others on separate ccTLDs, with no clear logic connecting the decisions.
Missing hreflang return tags.The single most common technical error, and often invisible until a regional traffic drop forces an investigation.
Treating server location as the primary signal.It’s a minor, secondary factor now, not the deciding one.
No per-property verification.Regional Search Console properties that were never verified, silently producing no data for months.
Forgetting the x-default tag.Sites with multiple regional versions but no fallback tag leave Google to guess which version to show visitors from markets the site doesn’t explicitly target.
Duplicating content across regions without localizing it.A page translated but not otherwise adapted, same examples, same currency, same cultural references, sends a weaker geographic signal than genuinely localized content, even with perfect hreflang tags underneath it.
Original Framework: The Geographic Signal Confidence Score
Since no single dashboard confirms geotargeting health anymore, this framework fills that gap, and weights the signals rather than treating them as equally important.
| Signal | Weight | What to Confirm |
| Hreflang tags | High (30 points) | Every page has a self-reference and every cross-reference is reciprocated |
| URL structure | High (25 points) | Consistent pattern applied across every market, no mixed logic |
| On-page localization | Medium (20 points) | Address, currency, and language consistent with the target market |
| Search Console verification | Medium (15 points) | One verified property per region or subdirectory pattern |
| Server or hosting | Low (10 points) | Reasonable alignment with target markets where practical |
Score each market by adding up the points for every signal it satisfies fully, for a Geographic Signal Confidence Score out of 100. A market scoring above 80 has a strong, resilient geographic signal. A market below 50 usually has at least one high-weight gap, most often hreflang, worth fixing before anything else on the list.
Weighting the signals this way reflects how much each one actually influences Google’s geographic relevance decision, rather than presenting five checks as though they matter equally. Hreflang and URL structure carry most of the signal; hosting location carries comparatively little.
How to Apply the Score: A Worked Example
Take a hypothetical enterprise site auditing its French market page. URL structure is consistent with the rest of the site’s subdirectory pattern (25 points). Hreflang is implemented, but the return tag from the French page back to the English original is missing (0 of 30 points, since a broken reciprocal link invalidates the pair).
On-page content is fully localized, with French currency and contact details (20 points). The Search Console property for the subdirectory is verified (15 points). Hosting runs through a global CDN with no specific French edge preference (5 of 10 points).
Total score: 65 out of 100. The missing hreflang return tag is the single biggest gap, worth fixing before any other adjustment, since it’s both the highest-weighted signal and the one currently scoring zero.
That’s the practical value of weighting the signals instead of just checking them off: it tells you which fix to prioritize, not just what’s missing.
The Implementation Sequence
Applied in order, the steps above form a repeatable sequence rather than a list of unrelated tasks:
- Decide and document one URL structure pattern for all markets
- Implement hreflang across every regional variant, including self-references
- Set up and verify a Search Console property for each region or subdirectory
- Localize on-page content, not just translate it
- Align hosting or CDN configuration where practically possible
- Score the result using the Geographic Signal Confidence Score, and revisit any market scoring below 80
Most enterprise geotargeting problems trace back to steps being done out of order, most often localization attempted before hreflang and structure are settled, which means the underlying signals keep shifting under content that’s already been localized once.
Illustrative Examples
The following are illustrative, composite scenarios based on common patterns across enterprise international SEO work, not case studies of specific named clients.
A software companyexpanding into Germany and France used subdirectories for both markets but implemented hreflang only on the German pages, assuming the French pages would inherit the same logic automatically. Search visibility in France stayed flat for months until a hreflang audit found the French pages were missing entirely from the tag set.
A retail brandhad separate ccTLDs for six countries, each with its own Search Console property, but three of those properties had never been verified after the initial site launch two years earlier. Verifying the missing properties immediately surfaced indexation issues in two markets that nobody had been tracking.
A B2B services firmhad correct hreflang tags but inconsistent on-page signals, using US dollar pricing on pages meant for a UK audience. Correcting the currency and contact information, alongside the already-correct hreflang setup, improved how confidently the pages matched UK search intent.
How This Connects to Enterprise SEO Services
Getting geotargeting right without the old manual setting requires more technical discipline, not less. Every signal has to be deliberately correct, since there’s no single toggle left to compensate for a mistake elsewhere.
This is usually whereenterprise SEO servicesprovide the most value for organizations expanding internationally, auditing hreflang, structure, and Search Console configuration together rather than treating them as separate, disconnected tasks.
For the broader business case behind international expansion, how enterprise SEO services support international expansion covers the strategic side this article’s technical setup supports. And if your organization runs multiple regional teams that each handle their own international setup, managing SEO across multiple business units without losing consistency covers how to keep that technical consistency from fragmenting across teams.
Frequently Asked Questions
Is the Search Console International Targeting report really gone?
Yes. Google deprecated it in September 2022, including the manual country-targeting setting. It isn’t coming back in its previous form.
How does Google know what country a page is meant for now?
Through a combination of signals: URL structure, hreflang tags, server or hosting location, and on-page content signals like address, currency, and language, weighed together rather than set manually.
What’s the most common geotargeting mistake on enterprise sites?
Missing hreflang return tags, where one page points to another but that page doesn’t point back. Independent analysis puts hreflang error rates at roughly 31% of international sites.
Do I still need separate Search Console properties for each country?
Yes. Performance and indexation data are reported per property, so each distinct URL pattern, whether a subdirectory, subdomain, or ccTLD, needs its own verified property to be monitored properly.
Does server location still matter for geotargeting?
It’s a minor, secondary signal now, especially with most enterprise sites using global CDNs. Domain structure and hreflang implementation matter considerably more.
How do I check if my geotargeting setup is actually working, without the old report?
Cross-reference the Coverage report, the Performance report filtered by country, and a dedicated hreflang validation crawl. No single report replaces the old dashboard, so verification now takes more than one source.
Can a mixed URL structure, ccTLDs for some countries and subdirectories for others, still work?
It can, but it sends a less consistent signal than picking one pattern and applying it everywhere. If a mixed structure is unavoidable due to legacy reasons, hreflang implementation becomes even more important to get right.
Do enterprise SEO services typically audit geotargeting setup?
Yes, it’s a standard part of any international-focused technical audit, since hreflang errors and inconsistent structure are among the most common, and most quietly damaging, issues enterprise sites carry for years without noticing.
What is the x-default hreflang tag, and do I need one?
It tells Google which version to show visitors from a country or language your hreflang set doesn’t explicitly cover. Enterprise sites targeting a limited set of markets should include one to avoid Google guessing on your behalf.
Can translated content alone achieve strong geotargeting without other signals?
No. Translation without hreflang, consistent URL structure, and localized details like currency and contact information sends a weaker, less coherent signal than the same content with all four elements aligned.
If your international setup still references a Search Console feature that no longer exists, that’s usually a sign the whole geotargeting configuration is overdue for a review, and it’s exactly the kind of technical audit the team at Growzify runs as part of everyenterprise SEO servicesengagement.
