Should you really prioritize NO-NO over NO-NB for Norwegian hreflang?

Why this recommendation on the Norwegian language code?

Norwegian has two official written forms: bokmål (which is the majority, around 85-90% of speakers) and nynorsk. The ISO 639-1 codes designate NO as the generic code, NB for bokmål, and NN for nynorsk.

Google simplifies things by recommending NO for both aspects of the hreflang tag: language AND region. This prevents webmasters from having to choose between NB and NN, especially when the content is not specifically written in either variant. This minimalist approach reduces the risk of implementation errors.

What happens if I use NO, NB instead of NO, NO?

Mueller clarifies that this setup works, which means that Google correctly interprets hreflang tags with NO, NB. The key is consistency: if you choose NO, NB on one URL, all other URLs in the hreflang cluster must follow the same logic.

Conflicting signals (sometimes NO, NO, sometimes NO, NB) may confuse Google’s geographic targeting algorithm. The engine might then partially or completely ignore your hreflang annotations, which defeats the initial purpose: directing Norwegian users to the correct language version.

What’s the tangible difference between NO and NB for Google?

Technically, Google treats NO as a generic code covering the whole territory and the Norwegian language variants. NB explicitly targets bokmål, which may seem more precise but offers no measurable advantage in practice for most sites.

The recommendation of NO, NO is based on the observation that Google does not refine its targeting based on the bokmål/nynorsk distinction in its SERPs. Norwegian users will see the Norwegian version regardless of the code used, as long as the language and region match. In other words, the extra granularity of NB does not change the algorithm’s behavior.

• NO, NO : Google's official recommendation, maximum simplicity, no ambiguity.
• NO, NB : functional if consistently applied across the site, but without observable SEO benefits.
• Consistency : number one criterion — mixing conventions undermines the effectiveness of hreflang.
• Bokmål vs nynorsk : a linguistic distinction that Google doesn't value in its regional targeting algorithm.
• Crawl impact : inconsistent hreflang tags slow down interpretation and can generate errors in the Search Console.

Is this statement consistent with observed practices on the ground?

Absolutely. Hreflang audits show that sites using NO, NO and sites using NO, NB correctly index their Norwegian versions, with no performance difference in Norwegian SERPs. Google displays no algorithmic preference for either configuration.

However, errors mainly arise in hybrid implementations: a page with hreflang="no-no" linking to another with hreflang="no-nb" creates a chain break. The Search Console then raises "No return tag" alerts, indicating that Google cannot loop back the hreflang cluster. Consistency outweighs linguistic precision.

What nuances should be added to this recommendation?

If your content is explicitly written in nynorsk (NN) for editorial or institutional reasons, it would make sense to use NO, NN rather than NO, NO. However, Mueller does not mention this variant, suggesting that Google views the case as marginal and does not provide specific guidance.

Additionally, some CMS or frameworks automatically generate hreflang tags with the complete ISO codes (no-nb, no-nn). Modifying these values to NO, NO may require custom development. If the cost outweighs the benefit (no measurable SEO impact), keeping NO, NB remains a viable option as long as consistency is guaranteed.

When does this rule not apply?

If you manage a multilingual site with distinct versions for Denmark (DA, DK) and Norway (NO, NO), the hreflang tags must clearly separate the two markets. The risk of confusion is low as the codes are different, but the issue arises for Scandinavian sites that sometimes combine multiple closely related languages.

Another edge case involves sites with separate geographical subdomains or directories (/no/ for Norway, /se/ for Sweden). If the regional code remains consistent (NO for all Norwegian URLs), the choice between NO, NO and NO, NB becomes even less critical. The URL structure already carries the main geographic signal.

What should be done practically on an existing site?

Start with a comprehensive audit of your current hreflang tags. Export all Norwegian URLs and check the codes used: NO, NO or NO, NB. If you notice a mix of both, normalize to NO, NO to follow Google's recommendation and simplify future maintenance.

Use the Search Console to identify existing hreflang errors (missing return tags, language/region conflicts). These alerts often indicate inconsistencies in the codes. Prioritize correcting them, as they block international targeting. A single broken link in the hreflang cluster can invalidate the whole.

What errors should be avoided during implementation?

Never mix NO, NO and NO, NB on pages that are supposed to belong to the same hreflang cluster. Google interprets these codes as two distinct configurations and does not automatically link them. As a result, your Norwegian versions may cannibalize each other in SERPs instead of reinforcing each other.

Also, avoid using NB or NN as isolated language codes without specifying the region (hreflang="nb" instead of hreflang="no-no"). Google expects a language-region format for hreflang, except for x-default. An incomplete code generates validation errors and may be ignored by the algorithm.

How can I check if my implementation is compliant?

Test a sample of Norwegian URLs with an hreflang validator (tools like hreflang.org or browser extensions). Ensure that each page correctly points to its equivalents in other languages, and that all return tags are present. Symmetry is mandatory: if A points to B, B must point back to A.

Monitor the Search Console in the "International targeting" section. Google reports hreflang errors detected during crawling here. A clean site should show no alerts after a few weeks of stabilization. If errors persist, it indicates that consistency is lacking.

• Audit all Norwegian hreflang tags and identify the codes used (NO, NO vs NO, NB).
• Normalize to NO, NO if a mix is detected, to follow the official Google recommendation.
• Check the symmetry of return tags among all language versions of the cluster.
• Test with an hreflang validator to identify syntax or logic errors.
• Monitor the Search Console for 4-6 weeks after modification to confirm the absence of alerts.
• Document the chosen convention in an internal guide to ensure consistency during future updates.