Geotargeting in Google Search Console

Geotargeting in Google Search Console tells Google which country a section of your site is intended for. It is a direct signal that helps Google serve the right version of your content to the right audience. But it has specific limitations, and it is not always the right tool for the job.

This guide covers when geotargeting works, when it does not, how to set it up, and what to use instead when it falls short. For the full international SEO picture, see our hreflang guide.

What Geotargeting Does

When you set a target country for a Search Console property, you are telling Google: "This content is primarily intended for users in this country." Google uses this as one signal among many when deciding which version of your content to show in search results for users in different locations.

It does not force Google to only show your content to users in that country. It does not block users from other countries from seeing your pages. It is a preference signal, not a restriction.

When You Need It (and When You Do Not)

You need geotargeting if:

You are using a generic top-level domain (gTLD) like .com, .org, or .net with subdirectories or subdomains for different countries. Google cannot tell from example.com/fr/ alone that the content targets France. The geotargeting setting provides that signal.

You do not need geotargeting if:

You are using ccTLDs. Google already knows that example.fr targets France and example.de targets Germany. Setting geotargeting for a ccTLD is redundant. Google ignores it.

You are targeting a language, not a country. Geotargeting is country-level. If you have a Spanish-language section that targets all Spanish-speaking countries, geotargeting to Spain would be wrong. Use hreflang tags to handle language targeting instead.

You are using hreflang tags comprehensively. Hreflang tags provide more granular language-and-region targeting than geotargeting. If your hreflang implementation is solid, geotargeting in Search Console adds a secondary signal but is not strictly necessary. That said, using both is fine and recommended.

Setting Up Geotargeting

Step 1: Add the right property type

For subdirectory-based international sites (like example.com/fr/), you need to add each subdirectory as a separate URL-prefix property in Search Console. The Domain property covers everything under the domain and cannot be geotargeted to a single country.

Add these as separate properties:

• https://example.com/fr/
• https://example.com/de/
• https://example.com/es/

For subdomain-based sites, add each subdomain as its own property:

• https://fr.example.com
• https://de.example.com

Step 2: Verify each property

Each property needs to be verified independently. If you have already verified the parent domain, some properties may auto-verify. Otherwise, use any standard verification method: DNS record, HTML file, meta tag, Google Analytics, or Google Tag Manager.

Step 3: Set the target country

In each property, go to Settings (the gear icon or the Settings menu in the left sidebar). Look for "International Targeting" or the country targeting section. Select the target country from the dropdown.

That is it. Google will start using this signal immediately, though it may take time for search results to reflect the change.

The One-Country Limitation

This is the biggest limitation of geotargeting in Search Console: you can only set one target country per property. If your /fr/ section targets both France and Belgium (both French-speaking), you have to pick one.

This is where hreflang tags fill the gap. With hreflang, you can specify fr-FR for France and fr-BE for Belgium, pointing to the same or different pages as appropriate. Geotargeting handles the broad signal; hreflang handles the nuance.

If you must pick one country for geotargeting, pick the primary market for that section. Use hreflang for the rest.

What Geotargeting Cannot Do

It cannot target by language

Geotargeting is country-level only. There is no way to say "this property targets French speakers worldwide." For language-level targeting, use hreflang with language-only codes (like fr instead of fr-FR). See our hreflang best practices for guidance.

It cannot override user location

If a user in Germany searches for something and your site is geotargeted to France, Google may still show your French content if it is the best match. Geotargeting influences results; it does not restrict them.

It cannot fix content problems

If your French content is just machine-translated English content with no localization, geotargeting will not save it. Google evaluates content quality independently. A geotargeting signal on poor content does not make it rank better in the target country.

It cannot work on subpages individually

You cannot geotarget example.com/fr/page-1 to France and example.com/fr/page-2 to Belgium. The setting applies to the entire property. For page-level targeting, use hreflang.

Alternatives and Complements to Geotargeting

Hreflang tags

The most flexible option for international targeting. Hreflang lets you specify language, region, or both at the page level. It works across ccTLDs, subdomains, and subdirectories. It handles complex scenarios like a single page serving multiple regions. See how to implement hreflang for the technical details.

Server-side geo detection

Some sites detect user location via IP address and serve different content or redirect users to the appropriate version. This works for user experience but creates problems for SEO if not handled carefully. Googlebot crawls primarily from the US, so it may only see your US content unless you configure things properly.

If you use geo-based redirects, make sure Googlebot can access all versions. Use hreflang to tell Google about the alternate versions, and do not redirect Googlebot based on its IP address. Google explicitly advises against this.

ccTLDs

If you use country-code top-level domains, the domain itself is the geotargeting signal. No Search Console configuration needed. See our ccTLD vs subdomain vs subdirectory comparison for help choosing.

Common Mistakes

Setting geotargeting on a ccTLD

This is harmless but pointless. Google already knows .fr targets France. Do not spend time configuring it.

Geotargeting your entire .com to one country

If you set your root example.com property to target the United States, and you also have international subdirectories, the signals may conflict. Only geotarget the specific subdirectory or subdomain properties, not the parent domain property.

Forgetting to add subdirectory properties

Geotargeting requires a URL-prefix property for each section. If you only have a Domain property, you cannot set country-level targeting. Add URL-prefix properties for each international subdirectory.

Using geotargeting as your only signal

Geotargeting is one signal. It works best when combined with hreflang tags, localized content, local backlinks, and proper URL structure. Relying on it alone is insufficient for competitive international markets.

Geotargeting a language section to a country

If your /es/ section is Spanish content for all Spanish-speaking countries, do not geotarget it to Spain. Either leave it untargeted or pick the primary market and use hreflang for the rest.

Checking Your Current Geotargeting Settings

If you inherited an international site or want to audit the current setup:

1. Log into Google Search Console
2. Check each property in your account
3. For each property, go to Settings and check the International Targeting section
4. Document what each property is currently targeted to
5. Compare against your intended targeting strategy

Misconfigurations here are surprisingly common, especially on sites that have changed their international strategy over time. A subdirectory that was once targeted to Germany might still carry that setting even after the content changed.

Recommended Setup

For most international sites using subdirectories on a gTLD:

1. Add a URL-prefix property for each international subdirectory
2. Set the target country for each property
3. Implement hreflang tags on every page, covering all language and region variants
4. Submit sitemaps for each property
5. Monitor the International Targeting report and search performance per property

This belt-and-suspenders approach gives Google every signal it needs to serve the right content to the right users.

---

References

• Google Search Central: Managing Multi-Regional and Multilingual Sites
• Google Search Console: International Targeting Report
• Google Search Central: Localized Versions