Emilytics

GSC International Targeting: Setting Up Hreflang and Geotargeting

Emily RedmondData Analyst, EmilyticsApril 18, 2026

GSC International Targeting: Setting Up Hreflang and Geotargeting

By Emily Redmond, Data Analyst at Emilytics · April 2026

TL;DR: Use hreflang tags to tell Google which page is for which language/region. Set geotargeting in GSC to specify target countries. Without these, Google might rank the wrong version in the wrong country, tanking your visibility in multiple regions.

You serve multiple countries or languages. Great—bigger market. But Google needs to know which version is for which audience.

Hreflang tags and geotargeting tell Google. Set them up wrong, and you lose traffic in most of your markets.

The Problem: Multiple Versions, One Search Result

Imagine you have:

  • /en/ (English)
  • /es/ (Spanish)
  • /fr/ (French)
  • /de/ (German)

Someone in Spain searches for your keyword. Which version should Google show?

Without hreflang: Google guesses. Might show the English version (wrong). User bounces.

With hreflang: Google shows the Spanish version. User gets content in their language. Win.

What Is Hreflang?

Hreflang is a link tag that tells Google: "This page has alternate versions in other languages/regions."

Example:

On your English page (/en/product), you add:

<link rel="alternate" hreflang="en" href="https://example.com/en/product" />
<link rel="alternate" hreflang="es" href="https://example.com/es/product" />
<link rel="alternate" hreflang="fr" href="https://example.com/fr/product" />
<link rel="alternate" hreflang="x-default" href="https://example.com/en/product" />

This tells Google: "I have versions in English, Spanish, and French. Here they are."

The x-default version is the fallback for people in countries you don't specifically target.

Setting Up Hreflang: Three Methods

Method 1: HTML Link Tags (Easiest for WordPress)

Add hreflang in the <head> of each page.

WordPress with Yoast SEO:

  1. Edit a page
  2. Go to the Yoast SEO settings
  3. Find "Multisite" or "Canonical URL" section
  4. Enable hreflang if available (Yoast adds it automatically for translated pages)

WordPress with Polylang or WPML:

  1. Install the plugin
  2. Translate your pages into multiple languages
  3. The plugin adds hreflang automatically

Manual HTML:

  1. Add the link tags above to your page's <head>
  2. Deploy

Method 2: Sitemap-based Hreflang

If you have separate sitemaps for each language, you can use sitemaps instead of link tags.

In your sitemap.xml:

<url>
  <loc>https://example.com/en/product</loc>
  <xhtml:link rel="alternate" hreflang="es" href="https://example.com/es/product" />
  <xhtml:link rel="alternate" hreflang="fr" href="https://example.com/fr/product" />
  <xhtml:link rel="alternate" hreflang="x-default" href="https://example.com/en/product" />
</url>

Submit this sitemap to GSC.

Method 3: HTTP Headers (For Dynamic Sites)

If your site changes content based on user region (one URL, different content), you can use HTTP headers instead of HTML tags.

This is advanced (requires developer work). Skip unless you know you need it.

💡 Emily's take: Hreflang is one of those things that seems complex but is actually straightforward once you understand it. The biggest mistake I see: people implement it halfway. Like they set it up on English pages but forget on the Spanish pages. Then Google gets confused. Make sure every page has hreflang pointing to all versions (not just other languages, but itself too).

Setting Geotargeting in GSC

Hreflang tells Google which language/region. Geotargeting in GSC tells Google your target country.

Go to Settings → Geographic targeting (left menu).

You'll see a dropdown for "Primary Country." Select your main target country.

Example: You have /en/ (English) and /es/ (Spanish). Your company is in Mexico.

  • Set primary country to Mexico
  • Google will prioritize showing your site to Mexican users

This is optional if you're using hreflang correctly (hreflang alone is enough). But it helps, especially for ambiguous cases.

Validating Your Hreflang Setup

You want to make sure hreflang is working.

In GSC

  1. Go to Enhancements → International targeting (if available)
  2. See if GSC recognizes your hreflang tags
  3. It'll show you all the language versions it detected

Using the URL Inspection Tool

  1. Inspect a page in a different language
  2. Click the "Inspect URL" result
  3. Look for "Hreflang" in the details
  4. See if it shows all language versions correctly

Using Google's Mobile-Friendly Test

  1. Go to Google's Mobile-Friendly Test
  2. Paste your page URL
  3. Scroll down to "Mobile usability" section
  4. Look for hreflang warnings (if any)

Manual Testing

Search on Google in different countries/languages (use a VPN if needed) and see which version appears.

Example:

  • Search from Spain IP: Do you see Spanish version?
  • Search from France IP: Do you see French version?
  • Search from US IP: Do you see English version?

If yes to all three, hreflang is working.

Common Hreflang Mistakes

Mistake 1: Not including self-references

<!-- WRONG: Missing self-reference -->
<link rel="alternate" hreflang="es" href="https://example.com/es/product" />
<link rel="alternate" hreflang="fr" href="https://example.com/fr/product" />

<!-- RIGHT: Includes self-reference -->
<link rel="alternate" hreflang="en" href="https://example.com/en/product" />
<link rel="alternate" hreflang="es" href="https://example.com/es/product" />
<link rel="alternate" hreflang="fr" href="https://example.com/fr/product" />

Every page needs to reference itself.

Mistake 2: Using wrong language codes

Google uses ISO 639-1 language codes:

  • en = English
  • es = Spanish
  • fr = French
  • de = German
  • pt = Portuguese
  • ja = Japanese

And country codes:

  • en-US = English (United States)
  • en-GB = English (United Kingdom)
  • es-MX = Spanish (Mexico)
  • es-ES = Spanish (Spain)

Use the right codes or Google won't recognize them.

Mistake 3: Pointing to the wrong URL

<!-- WRONG: Pointing to home page instead of translated page -->
<link rel="alternate" hreflang="es" href="https://example.com/" />

<!-- RIGHT: Pointing to actual Spanish page -->
<link rel="alternate" hreflang="es" href="https://example.com/es/product" />

Each language version must point to its actual URL.

Mistake 4: Using hreflang on non-translated pages

If you only have one version, don't use hreflang. It's for when you have multiple versions.

When You Don't Need Hreflang

You don't need hreflang if:

  • You have only one language
  • You use subdomains (example.com for English, es.example.com for Spanish) and Google recognizes the difference
  • You use different domain names (example.com for English, example.es for Spanish)

But if you use subdirectories (/en/, /es/), hreflang is critical.

Tracking Hreflang in GSC

Once you set up hreflang, check GSC's International targeting report (if available in your region).

You'll see:

  • How many pages have hreflang
  • Which language versions Google detected
  • Any hreflang errors

Check monthly. If you add new languages, make sure hreflang is on all new pages.

Frequently Asked Questions

Q: Do I need hreflang for dialects (en-US vs en-GB)? A: Only if you want different content for each. Most sites use just the language code (en) and Google handles country variations automatically.

Q: What if I have hreflang errors in GSC? A: Common causes: wrong URL (404), wrong language code, inconsistent hreflang across pages. Fix the URL or code and re-check.

Q: Can hreflang help me rank in multiple countries? A: Partially. It ensures the right version shows to the right audience. But your content still needs to be good and you still need backlinks in each country for competitive keywords.

Q: Should I use hreflang on translated pages that aren't 1:1 matches? A: No. Only use hreflang when pages are actual translations of each other. If you have a /blog/ that's different in Spanish (not a translation), don't hreflang them.

Next Steps

If you serve multiple countries/languages:

  1. Audit your site: Where are the language versions? Subdirectories? Subdomains? Separate domains?
  2. Check if you already have hreflang (inspect pages, look for hreflang tags)
  3. If you don't have hreflang but need it, implement it (plugin or manual)
  4. Validate in GSC's URL Inspection tool
  5. Monitor International targeting report monthly

This is foundational infrastructure for international sites. Worth getting right.

Emily Redmond is a data analyst at Emilytics — the AI analytics agent that watches your GA4, Search Console, and Bing data around the clock. 8 years of experience. Say hi →

More from Google Search Console