GSC for international sites

Structure properties and analyze countries, languages, canonicals, and regional directories.

Directional evidence Partially automatable Advanced

Search Console can show which canonical pages receive visibility in each searcher's country, but it does not provide a complete hreflang report, a language dimension, or a setting that proves regional targeting is correct. International diagnosis therefore combines property scope, URL patterns, country data, canonical evidence, crawling, and an external hreflang validator.

Design the property structure around decisions

Use a Domain property for the complete domain across protocols and subdomains. Add URL-prefix properties when regional teams need a stable subdomain or directory scope, for example:

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

A URL-prefix property matches the exact prefix, including protocol and host. A Domain property cannot isolate a folder. Keep the broad property so cross-locale canonicalization and migrations remain visible even when local teams use narrower views.

Country-code domains require separate properties because each is a different domain. Keep property naming, owner groups, and exports consistent across markets.

Understand the evidence dimensions

Evidence	What it means	What it does not mean
Country dimension	Country where Google estimates the search originated	Page language, user nationality, or intended market
Page URL or path	Locale implied by the site's URL convention	Language Google detected from content
Query	Exposed search text for the result	Complete demand; rare queries are hidden
Canonical in URL Inspection	Google's selected representative for that inspected URL	Validation of the entire locale cluster
`hreflang` in source/sitemap	Site-declared alternate relationship	Confirmation Google accepted every annotation

Create an explicit locale-by-country matrix outside Search Console. For each canonical URL segment, compare clicks, impressions, CTR, and position by relevant countries. Add business eligibility—shipping, legal availability, language support, currency, and conversions—before labeling a market an opportunity.

International implementation principles

Google recommends different URLs for different language versions rather than serving locale variants from cookies or browser settings. Use visible, crawlable links so people and Googlebot can switch versions.

Google primarily determines language from visible page content, not the lang attribute or URL alone. Keep navigation and main content consistently translated; changing boilerplate while leaving the primary content in another language can create a poor experience.

Avoid automatic redirects based solely on IP or assumed language. Googlebot commonly crawls from the United States and does not normally send Accept-Language, so locale-adaptive variants can remain undiscovered. Offer a choice and preserve access to every locale URL.

`hreflang` and canonical relationships

For each equivalent locale page:

Use a stable, indexable URL.
Declare the page's own canonical unless it is truly a duplicate that should consolidate elsewhere.
Include every equivalent alternate, including a self-reference.
Make relationships reciprocal.
Use valid language and optional region codes.
Add x-default for a selector or fallback when appropriate.
Keep HTML, HTTP-header, or sitemap implementations internally consistent.

Do not canonicalize translated pages to one language merely because their subject is equivalent. Canonical and hreflang solve different problems: canonical selects a representative among duplicates; hreflang connects legitimate locale alternatives.

Search Console does not expose an authoritative list of accepted hreflang pairs. Crawl the site and validate annotations independently, then use URL Inspection samples to check whether Google chose an unexpected cross-locale canonical.

Diagnose wrong-market visibility

Locale URL receives impressions in an unexpected country

This can be legitimate: travelers, expatriates, multilingual users, or globally relevant content can search from any country. Look for a persistent pattern before treating it as an error.

Check:

whether the expected locale URL is indexed and canonical;
reciprocal hreflang and self-references;
visible language, currency, address, availability, and local links;
automatic redirects or blocked locale variants;
whether multiple locale pages compete for the same queries;
whether the query itself expresses a different regional intent.

Expected country has weak impressions

Search Console cannot distinguish low market demand from low eligibility by itself. Compare Google Trends, query research, local competition, indexation, internal links, and whether the offering actually serves the country.

Country CTR is low

Control for query, device, position, and result appearance. Then inspect whether the title, snippet, language, currency, or promise is appropriate for that market. A country-wide CTR average can be driven by a different query mix.

URL architecture tradeoffs

Structure	Useful characteristic	Operational cost
ccTLD, `example.de`	Strong country signal and clear separation	Multiple domains, infrastructure, authority, and governance
Subdomain, `de.example.com`	Operational separation on a generic domain	Users may not infer whether code means language or country
Subdirectory, `example.com/de/`	Lower maintenance and easy shared-domain management	Less infrastructure separation
Parameter, `?loc=de`	Quick to implement	Google does not recommend it for geotargeting; hard to segment and communicate

Architecture alone does not fix localization. Google also considers hreflang, visible local details, currency, local links, and other signals. Server location is not definitive, particularly with CDNs.

Reporting and automation

Use the API or BigQuery to maintain a daily matrix of canonical URL locale × searcher country × device. Keep language and intended market as first-party URL metadata, not inferred from the Country dimension.

Report:

each locale's clicks and impressions in intended countries;
unexpected cross-market exposure as a diagnostic rate, not automatically an error;
pages where Google selects a different locale canonical;
locale-level indexing and sitemap trends;
conversions and availability from first-party systems;
known migrations, launches, and hreflang releases.

Top-row and privacy limits still apply. Small markets are especially vulnerable to hidden queries and low-volume sampling, so avoid precise conclusions from missing rows.

International review checklist

Confirm the broad and local property scopes.
Validate locale URL inventory and status codes.
Crawl canonical, hreflang, language-switcher, and sitemap relationships.
Inspect representative URLs from each template and locale.
Compare the locale-by-country matrix over equivalent periods.
Join market eligibility and conversions.
Test automatic redirects from several locations and user agents.
Annotate launches and migrations.
Preserve access for regional teams without making agencies or vendors permanent owners.