Hreflang uses an unsupported region code
In the reportHreflang region code invalid or unsupported
hreflang_invalid_region_code · Issue
An annotation names a region outside the assigned two-letter country-code set. Correct the recorded annotation at its source.
Severity: High. The declared target is invalid or unsupported; correct the annotation.
Why it matters
Google documents assigned ISO two-letter country codes for regional targeting. Reserved codes such as UK, EU and UN, and numeric regions such as 419, do not provide the intended country targeting.
What to do
- Read the recorded value and the source channel in the finding.
- Use an assigned country code, such as
GBinen-GB. For individual countries in Latin America, use the relevant country annotations instead ofes-419. - If the alternate serves all users of a language, omit the region and keep the language, for example
es.
What we read
We read the existing HTML, HTTP Link and sitemap declarations for the page. Each annotation retains its original source channel and sitemap file.
We read the region after a valid two-letter language and optional registered script. A numeric, reserved, private-use, withdrawn or unregistered country code is reported. The region may be omitted, and x-default is valid.
All three declaration channels must have complete coverage. Missing source data, an expired reference snapshot or a resource limit gives not checked, rather than a clean result. No annotations means this check does not apply.
Example & evidence
Illustrative example of a corrected language annotation.
<link rel="alternate" hreflang="en-UK" href="https://bakery.example/en/"><link rel="alternate" hreflang="en-GB" href="https://bakery.example/en/">Confirm & check again
Check for yourself: Inspect the raw source named in the finding and check each hreflang value.
Check again: Full audit — Run another full site audit. The issue closes only when the same page is checked with sufficient declaration and reference coverage and the problem is absent. An unreadable page or missing coverage does not prove a fix.
Limits & sources
This checks the declaration, not whether Google selected a page for a particular country. The numeric-region case follows the published Google profile.
When a language declaration is malformed, region coverage remains unknown; that cannot prove an older region problem fixed.
Confidence: High The finding shows the captured annotation and failed code lookup.
Sources
- Google, Tell Google about localized versions of your page — Defines the supported language, script and region profile and explains unsupported region elements. Checked 3 October 2026.
Editorial review: 2 November 2026