Geotargeting in Google Search Console

Last updated

Geotargeting in Google Search Console is the mechanism by which you tell Google which country a subdomain or subdirectory is intended to serve. It is one of several geo-signals Google uses alongside URL structure, hreflang annotations, content language, and the origin of inbound links.

What geotargeting does

When you set country targeting for a Search Console property, you give Google an explicit hint that the content in that property is primarily intended for users in the specified country. Google weighs this alongside other signals; it is a hint, not a directive, and may be overridden by stronger conflicting signals.

What geotargeting does not do

It is worth being clear about what geotargeting in Search Console does not do:

  • It does not redirect users to the geo-targeted version automatically.
  • It does not prevent the page from appearing in other countries.
  • It does not replace hreflang. Both signals should be used together for international sites.
  • It does not affect ccTLD properties, which are automatically associated with their country.

Which properties can be geo-targeted

ccTLDs (.co.uk, .de, .fr): automatically associated with their country by Google. The International Targeting panel shows the country but does not allow you to change it.

Subdomains (uk.example.com, de.example.com): can be geo-targeted to a specific country. Each subdomain requires a separate Search Console property, with country targeting applied independently to each one.

Subdirectories (example.com/uk/, example.com/de/): geo-targeting is applied per-subdirectory. Set up each subdirectory as a Search Console property using the URL prefix method, then apply country targeting to each independently.

Root domains on generic TLDs (.com, .co, .io): treated as global by default. Applying country targeting to the root domain tells Google the entire domain targets one country, which is almost never appropriate for a multi-market site.

How to set country targeting

  1. Open Google Search Console and select the property for the subdomain or subdirectory you want to target.
  2. Go to Settings > International Targeting.
  3. In the Country tab, select the target country from the dropdown.
  4. Save the setting.

The setting takes effect over the following days as Google recrawls the property.

The International Targeting report

Search Console’s International Targeting section has two tabs:

Country tab: where you set geo-targeting and view the current setting for the property.

Language tab: shows detected hreflang usage and any errors found during crawl. This is the fastest way to identify hreflang problems at scale. Common errors reported include:

  • Return tags missing (non-reciprocal hreflang)
  • Alternate pages returning errors (404, 500, or redirect chains)
  • No-return tag on alternates

Check this report after any site changes that affect page <head> elements or the XML sitemap, as hreflang errors commonly appear after template updates.

When not to apply geotargeting

Global products or services: if your content is relevant to users in multiple countries, do not geo-target the root domain or a cross-market subdirectory to one country. You will reduce visibility in every other market.

Cross-market sections: a /blog/ or /resources/ directory containing content relevant to all markets should not be geo-targeted to a single country unless the content is genuinely country-specific.

Fallback or global pages: pages intended as the x-default in hreflang sets serve all non-matched users. Applying country targeting to these pages conflicts with their intended function.

Monitoring international performance by country

The Search Console Performance report can be filtered by country to track impressions, clicks, and average position per market:

  1. Open the Performance report.
  2. Click + New and select Country.
  3. Add the target countries as separate filters to compare markets.

For large international sites, exporting this data and tracking it over time in a spreadsheet is more efficient than manual monitoring. Sudden drops in visibility for a specific country often indicate a hreflang error affecting that region, a geo-targeting misconfiguration, or a ranking shift in that market.

Geo-targeting and hreflang together

Geo-targeting in Search Console and hreflang serve complementary but distinct functions:

  • Geo-targeting declares the country intent of a property at the domain/subdirectory level.
  • Hreflang declares the language and regional intent at the individual page level and maps equivalents across markets.

Neither replaces the other. A subdirectory property geo-targeted to Germany without hreflang lacks page-level language signals. Hreflang without geo-targeting on subdirectory properties misses the property-level geo-signal. Both should be set up consistently.

Frequently asked questions

Does geo-targeting in Search Console improve rankings? It is a geo-targeting hint, not a ranking factor. Combined with hreflang, correct URL structure, and localised content, it helps Google understand your intended audience. It does not independently boost rankings.

What happens if I geo-target a property to the wrong country? You signal to Google that your content targets a country other than the one you intend. This can suppress visibility in the correct market and inflate impressions in the wrong one. Change the setting and monitor the effect over the following weeks.

Should I set geo-targeting before or after implementing hreflang? Ideally at the same time. Both are geo-signals and should be consistent with one another and with the URL structure and content language of the site.