Should you choose hreflang language only or language+country for your international versions?

What is the difference between hreflang language only and language+country?

The hreflang tag accepts two levels of granularity: the ISO 639-1 language code alone (two letters, like "pt" for Portuguese) or the language-country combination in the format ISO 639-1 + ISO 3166-1 Alpha 2 ("pt-BR" for Brazilian Portuguese, "pt-PT" for Portuguese from Portugal).

The first format targets all users speaking that language, regardless of their country. The second restricts targeting to a specific geographic area. Specifically: if you have a unique Portuguese version designed for Brazil, Angola, and Portugal, use "pt". If you create a version specifically tailored to the Brazilian market with prices in reais, local references, and Brazilian turns of phrase, then "pt-BR" becomes relevant.

Why does Google allow these two approaches?

The engine aims to serve the linguistically and geographically most relevant version. When a user in Lisbon searches for a product, Google will analyze geolocated signals and hreflang tags to determine whether the generic "pt" version or the specific "pt-PT" fits better.

This flexibility allows small sites not to create 5 distinct Portuguese versions if they lack the resources to adapt content and offers. Conversely, large e-commerce sites can benefit from country granularity to customize prices, stock, currencies, and editorial content according to each Portuguese-speaking market.

When should one approach be favored over the other?

If your content, prices, currencies, or offers do not vary by country within the same language, the language only version is more than sufficient. This way, you avoid unnecessarily duplicating tags and complicating your hreflang sitemap.

On the other hand, as soon as you offer prices in local currency, specific legal notices (GDPR vs. Brazilian laws), or editorial content tailored to the cultural realities of a country, the language+country combination becomes necessary. It explicitly signals to Google that this page targets a specific geographic subset.

• Use hreflang="pt" if your Portuguese content is addressed indiscriminately to all Portuguese speakers without geographic distinction
• Opt for hreflang="pt-BR" and "pt-PT" if you have distinct versions with prices in BRL/EUR, localized content, and specific offers
• Avoid mixing the two approaches for the same language: either remain generic, or segment all concerned countries
• Document your choice in your international SEO specifications to maintain coherence during future developments
• Plan a gradual migration if you move from a generic approach to country segmentation (do not switch abruptly without redirection or testing phase)

Is this statement consistent with field observations?

Absolutely. Tests on multilingual sites show that Google correctly interprets both formats for years. A site using only "pt" for its Portuguese version appears well in Brazilian, Portuguese, and Angolan results if the content remains relevant.

However, a common pitfall: some SEOs use "pt-BR" by default even for generic content, thinking it better targets the Brazilian market (the largest Portuguese-speaking pool). As a result: Google may under-serve this page to Portuguese or French-speaking African users, especially if a competitor offers a generic "pt" version or a specific "pt-PT" version.

What nuances should be added to this recommendation?

Mueller’s statement remains deliberately simple, but it overlooks a crucial point: Google’s geographic detection does not solely rely on hreflang. The engine cross-references declared language, user IP location, browser language settings, and on-page signals (currency, addresses, legal mentions).

If you use "pt" but your page only displays prices in euros with mentions like "Delivery to Portugal", Google will implicitly understand that you are targeting Portugal, even without "pt-PT". The reverse is true: a hreflang="pt-BR" with prices in dollars and European references will send contradictory signals that harm ranking.

In what cases can this rule cause problems?

Imagine a French-speaking media site with a joint editorial team for France, Belgium, Switzerland, and Canada. Using "fr" seems logical. However, Canada has strong cultural specificities (North American references, sometimes different spelling), and local advertisers want to target only the Canadian market.

In this case, keeping "fr" dilutes advertising targeting and makes it difficult to analyze performance by market. Switching to "fr-CA", "fr-FR", "fr-BE" becomes necessary—even if the editorial content remains identical—to segment audiences and monetization. [To be verified] Google rarely states how it arbiters when a site mixes generic "fr" and specific "fr-CA" on nearly identical content. Observations suggest that it favors the country version if the user is geolocated in that country, but no official documentation details this fallback algorithm.

How to audit your current hreflang implementation?

Start by extracting all your hreflang tags via a Screaming Frog or OnCrawl crawl. Check that each page correctly declares all alternatives, including itself. A missing tag breaks reciprocity, and Google ignores the entire hreflang cluster.

Then, control the language/country consistency: if you use "pt-BR" on a page, ensure that the content displays Brazilian reais, local addresses, and Brazilian turns of phrase. A misalignment between hreflang declaration and on-page reality triggers contradictory signals that obscure targeting.

Should you migrate from a generic approach to language+country?

Only if you have the resources to create and maintain content that is genuinely differentiated by country. Switching from "pt" to "pt-BR" + "pt-PT" without adapting prices, currencies, legal mentions, and editorial content delivers no benefit—and unnecessarily complicates your maintenance.

If you decide on this migration, proceed gradually: first deploy the prioritized country version (often the largest market), test performance and indexing for 4-6 weeks, then expand to other countries. Document each step and monitor Search Console to quickly detect hreflang errors or visibility drops.

What critical mistakes should be avoided during implementation?

Never mix language-only and language+country formats for the same language without clear logic. If you have "pt-BR" and "pt-PT", do not add a generic "pt" that would enter into direct competition with your country versions.

Avoid declaring hreflang solely in the XML sitemap without including it in the HTML (tags <link rel="alternate"> or HTTP headers). Google recommends redundancy to maximize detection reliability, especially on large sites where the sitemap may be partially crawled.

• Audit your current hreflang tags to check reciprocity and language/country consistency
• If you only have one version per language, simplify by using the language code alone ("pt", "es", "fr")
• As soon as you create differentiated content/prices by country, switch to language+country and declare all variants
• Test your tags with Google Search Console (International Targeting report) and immediately correct any reported errors
• Always systematically add a hreflang="x-default" tag pointing to the language selection page or main version
• Document your hreflang strategy in a centralized repository accessible to development, SEO, and content teams