Hreflang & Multilingual SEO

Brass-SEO treats this as the authoritative rulebook for hreflang implementation. Google's documentation states plainly that "if two pages don't both point to each other, the tags will be ignored" — reciprocal linking is mandatory, not advisory. It also lists three equally valid implementation methods (HTML link tags, HTTP headers, or XML sitemap entries) and names the common errors it sees: missing reciprocal links, non-ISO-639-1 language codes, and invalid region codes like "EU," "UN," or "UK." A one-directional hreflang tag is Google's most common cause of a setup that looks correct and does nothing.

Examines:

Google's official documentation on using the hreflang annotation — HTML tag, HTTP header, or sitemap entry — to signal localized page variants to Search.

Brass-SEO draws on:

The mandatory-reciprocal-link rule and the named common errors — cited when Brass-SEO diagnoses a hreflang setup that appears correctly implemented but isn't being honored.

Primary source

developers.google.com/search/docs/specialty/international/localized-versions

Brass-SEO draws on this as the formal grammar every valid hreflang value must follow. RFC 5646 (BCP 47) defines the language tag structure as language, then an optional script, then an optional region, then optional variants — in that fixed order. A tag like "en-UK" fails because it substitutes a country abbreviation for the ISO region code the spec requires, and because region subtags come after language, not before it. Hreflang values aren't arbitrary strings; they're BCP 47 tags, and most implementation errors trace back to not knowing that.

Examines:

The IETF Best Current Practice specification defining the structure and syntax of language tags — the format hreflang values must conform to.

Brass-SEO draws on:

The formal language-script-region-variant tag grammar — cited when Brass-SEO explains why a specific hreflang value is malformed rather than merely unconventional.

Primary source

rfc-editor.org/rfc/rfc5646

Brass-SEO uses this as the live, authoritative check for whether a specific language, script, or region subtag actually exists and is current. The registry, maintained per RFC 5646, enumerates every valid subtag across language, script, region, and variant categories, each with an added date and, where applicable, a deprecated-and-replaced-by field for codes that have been superseded. A hreflang audit that only checks tag format and not subtag validity will miss a deprecated code that's syntactically fine and semantically wrong.

Examines:

The single authoritative, continuously updated IANA registry of every valid language, script, region, and variant subtag usable in a BCP 47 tag.

Brass-SEO draws on:

The registry's deprecated-subtag tracking — cited when Brass-SEO flags a hreflang tag using a technically well-formed but outdated language or region code.

Primary source

iana.org/assignments/language-subtag-registry

Brass-SEO cites this when correcting the most common over-engineering mistake in hreflang tags. The W3C's guidance states subtags should only be added when needed to distinguish the language in context, and that the script subtag should be omitted entirely when the IANA registry marks it "suppressed" for that language, which it is for English and the Latin script. The correct tag is "en-US," not "en-Latn-US" — adding the script back in isn't extra precision, it's a spec violation dressed up as thoroughness.

Examines:

W3C's practical guidance on constructing a correct BCP 47 language tag, complementing the formal RFC 5646 grammar with usage recommendations.

Brass-SEO draws on:

The suppress-script rule — cited when Brass-SEO explains why a longer, more "specific-looking" hreflang tag is actually the incorrect one.

Primary source

w3.org/International/questions/qa-choosing-language-tags

Brass-SEO monitors this for hreflang adoption across the open web. The 2022 Web Almanac found hreflang tags on 9.6% of desktop home pages and 8.9% of mobile home pages, both up slightly from 9.0% and 8.4% in 2021, with English ("en") the single most common target, appearing on 5.4% of desktop home pages. Fewer than 1 in 10 sites use hreflang at all — a business that implements it correctly isn't following table stakes, it's doing something most competitors never attempt.

Examines:

HTTP Archive's crawl-based measurement of real-world hreflang and content-language adoption across millions of home pages.

Brass-SEO draws on:

The under-10% hreflang adoption rate — used to frame international SEO as a differentiator rather than baseline practice when Brass-SEO discusses expansion opportunities.

Primary source

almanac.httparchive.org/en/2022/seo

Brass-SEO draws on this to explain that hreflang alone doesn't determine regional targeting. Google's documentation states webmasters "must explicitly tell Google about any locale or language variation" and lists the signals it actually weighs: ccTLD as a "strong" standalone signal, hreflang annotations, server IP location, and secondary cues like local contact information, language, and currency — with URL parameters for geotargeting explicitly marked "not recommended." Hreflang is one input to a broader targeting decision, not a substitute for URL architecture.

Examines:

Google's official architectural guidance on URL structure (ccTLD vs. subdomain vs. subdirectory) for country/language targeting, and the signals Google uses to infer a page's locale.

Brass-SEO draws on:

The ranked list of regional-targeting signals — cited when Brass-SEO advises on URL architecture decisions that hreflang tags alone can't fix.

Primary source

developers.google.com/search/docs/specialty/international/managing-multi-regional-sites

Brass-SEO cites this to quantify the demand-side case for multilingual targeting. W3Techs' ongoing crawl-based survey finds English is the declared content language of 49.5% of measured websites, with Spanish, German, Japanese, and French each in the 4-6% range. Roughly half the web's content is already published in a language other than English — a business serving only English isn't matching the shape of the web it's competing on.

Examines:

An independent, continuously updated crawl-based measurement of declared content language across millions of live websites.

Brass-SEO draws on:

The roughly-50%-non-English content-language split — cited when Brass-SEO makes the business case for evaluating multilingual demand before assuming it doesn't exist.

Primary source

w3techs.com/technologies/overview/content_language