Google Search Console for International SEO: A Practical Guide

If your site targets audiences in more than one country or language, Google Search Console is your ground truth for international SEO. It surfaces hreflang errors before they tank your rankings, shows you exactly which countries are finding your pages, and lets you set a geographic target for country-specific subdirectories or subdomains.

This guide walks through every international SEO task GSC can help you with, from initial geo-targeting setup to diagnosing hreflang mismatches that Google has already caught.

Why International SEO Is Easy to Get Wrong

Serving the right page to the right user sounds simple, but Google has to infer your intent from signals you set. When those signals contradict each other — a hreflang tag pointing to a URL that returns a 404, or a ccTLD with the wrong x-default — Google ignores your instructions and guesses. The result is the wrong language ranking in the wrong country.

Google Search Console shows you when this is happening. The International Targeting report (under Legacy Tools and Reports) and the Enhancements reports both surface these mismatches as errors you can act on. Left unaddressed, they suppress the impressions and clicks you should be getting from your target markets.

Setting Geographic Targeting in GSC

GSC lets you tell Google which country a property is intended for. This is most useful for generic top-level domains (.com, .net, .io) with a country-specific subdirectory or subdomain, like example.com/de/ or de.example.com.

Country code top-level domains like .de or .fr already carry an implicit geographic signal, so setting a target in GSC is redundant but harmless.

To set geo-targeting:

Open Google Search Console and select your property.
In the left sidebar, go to Legacy Tools and Reports, then International Targeting.
Click the Country tab.
Check "Target users in" and select the country from the dropdown.
Click Save.

What this does not do: Geo-targeting in GSC is a soft signal, not a hard redirect. It biases ranking toward the selected country but does not replace hreflang tags or IP-based redirects. For multi-country sites, hreflang is still required.

One property at a time: Each GSC property (each subdomain or subdirectory) needs its own geo-targeting setting. If you have example.com/de/, example.com/fr/, and example.com/es/, you need three separate GSC properties and set each one independently.

Understanding the Hreflang Report

The hreflang report lives under International Targeting > Language. It shows Google's view of your hreflang implementation: how many URLs it found hreflang annotations for, how many have errors, and what the errors are.

GSC checks hreflang when it crawls your pages. The report reflects the last crawl, not real time. If you just fixed an error, give it a few days before expecting the report to clear.

Common Hreflang Errors in GSC

No return tag: This is the most common error. If example.com/en/page has a hreflang pointing to example.com/de/page, the German page must also have a hreflang pointing back to the English page. Without the return tag, Google treats the annotation as incomplete and may ignore both.

The fix: make sure every URL in your hreflang cluster links back to every other URL in the cluster, including itself.

Missing x-default: The x-default tag tells Google which URL to serve when no other language matches the user's preference. Without it, Google picks a URL — usually the wrong one.

Add an x-default tag to your hreflang cluster pointing to your global default or language-selector page:

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

Incorrect language or region code: Hreflang uses IETF language tags. en is English. en-US is American English. en-GB is British English. pt is Portuguese. pt-BR is Brazilian Portuguese. Using en-us (lowercase) or en_US (underscore) invalidates the tag.

Redirect chains: If a URL in your hreflang cluster redirects to another URL, Google may not follow the chain or may treat the annotation as broken. Use canonical destination URLs in hreflang, not redirect intermediaries.

URL not indexed: A URL referenced in hreflang must be accessible to Googlebot and return a 200. If the target URL is blocked in robots.txt, noindexed, or returns a 404, GSC logs it as an error.

Analyzing Performance by Country

The Performance report in GSC lets you filter by country. This is how you find out which markets are finding you, which queries they use, and where your international pages fall short.

How to view performance by country:

Open the Performance report (Search Results).
Click the Country filter tab (or add a New type filter and select Country).
Select the country you want to analyze.

You can also click the Countries tab in the Performance report to see a breakdown of impressions and clicks across all countries without prefiltering.

What to look for:

High impressions, low clicks in a target country: Your pages are showing up but users aren't clicking. This often means your title and meta description aren't localized — they're in the wrong language or don't match the intent of that country's search query.
Missing impressions in a target country: If you have translated pages for a market but GSC shows near-zero impressions from it, hreflang is probably broken or Google is not indexing the localized pages.
Unexpected country traffic: If you're getting significant traffic from a country you don't target, those users may be landing on content that doesn't serve them. Consider adding a localized version or at least a geo-aware redirect.

Using URL Inspection for International Pages

The URL Inspection tool is useful for diagnosing individual international pages. Enter the full URL of a localized page and check:

Is it indexed? If Google hasn't indexed the page, it cannot rank it, regardless of hreflang.
What canonical does Google see? If Google chose a different canonical than the one you set, the localized page is being treated as a duplicate of another page — usually the default-language version.
What hreflang does Google see? Under "Crawled Page," expand the HTML section to see what hreflang tags Googlebot read. This catches cases where your CMS outputs different hreflang on the live page than you expect.

Connecting International GSC Data to Your Optimization Workflow

Pulling performance data by country manually is slow. If you're managing more than a handful of international pages, you need to automate the analysis.

The Search Console Tools dashboard lets you filter your GSC performance data by country and query side by side, so you can spot pages with high impressions and low CTR in specific markets without exporting to a spreadsheet. Connect your GSC property and use the country filter to identify international pages that need title and description work.

For large international sites, the GSC API is the most practical route. You can run queries like this to pull impressions and clicks by country for a specific URL:

from googleapiclient.discovery import build

service = build('searchconsole', 'v1', credentials=creds)

request = {
    'startDate': '2026-09-01',
    'endDate': '2026-10-31',
    'dimensions': ['country', 'query'],
    'dimensionFilterGroups': [{
        'filters': [{
            'dimension': 'page',
            'operator': 'equals',
            'expression': 'https://example.com/de/your-page/'
        }]
    }]
}

response = service.searchanalytics().query(
    siteUrl='https://example.com',
    body=request
).execute()

This returns the queries driving impressions to that specific page, broken down by country. Run it across all your international pages to build a prioritized list of underperformers.

A Practical International SEO Audit in GSC

Here is a repeatable audit sequence using only GSC:

Check hreflang errors. Open International Targeting > Language. If error count is above zero, expand and fix each error type before doing anything else. Hreflang errors suppress the pages downstream.
Check geo-targeting. Open International Targeting > Country for each property that has a country-specific subdirectory or subdomain. Confirm the target is set correctly.
Filter performance by target countries. For each country you care about, check whether you have any impressions. Zero impressions in a target market means Google is not surfacing your localized pages at all.
Look for high impressions with low CTR by country. Filter the Performance report to your target country, sort by impressions descending, and find pages with CTR below 2%. These are your first title and description rewrites.
Inspect canonicalization on low-impression pages. Use URL Inspection to confirm that Google's chosen canonical for your international pages matches what you set. If Google is canonicalizing your German page to your English page, hreflang is broken.
Recheck the hreflang report after fixes. GSC updates on its crawl schedule. Wait 5-10 days after fixing hreflang errors before expecting the report to clear.

What GSC Cannot Do for International SEO

It is worth being direct about the limits:

GSC does not test your server-side redirects. If you redirect users by IP or Accept-Language header, GSC will not show you whether that is working. Test redirects manually or with a tool that spoofs IP or headers.
GSC does not show translated query data. If your German page ranks for a German query, you see the German query string in the Performance report. GSC does not translate it or map it to an English equivalent.
GSC does not check your CMS's hreflang output in real time. The hreflang report reflects what Googlebot saw on its last crawl. If your CMS has a template bug that outputs wrong hreflang on certain page types, the report shows it only after Googlebot re-crawls those pages.
The International Targeting report is a legacy tool. Google has not deprecated it, but it is under Legacy Tools, which signals it may not get new features. The hreflang data is still actionable, but do not expect it to expand.

Summary

Google Search Console gives you everything you need to find and fix the most common international SEO problems: hreflang errors, misconfigured geo-targeting, missing impressions in target countries, and canonicalization issues that suppress localized pages.

The workflow is straightforward. Fix hreflang errors first because they cascade. Set geo-targeting on subdirectories and subdomains. Use the Performance report country filter to find markets where you have impressions but poor CTR, then rewrite titles and descriptions for those markets. Inspect low-impression pages to confirm Google is indexing them with the right canonical.

If you are managing international GSC data at scale, use the Search Console Tools dashboard to filter performance by country across all your properties without manual exports. It surfaces the pages worth optimizing before you have to dig for them.