Swedish, Danish, Norwegian and Finnish: why machine translation brings no links or traffic

Translating Nordic content “once and done” does not work. Readers notice at once when a text does not speak to their market, and publishers do not link to text that was not written for them.

Four languages, four contexts

• Sweden (sv-SE): the largest market, strong media, users compare licence and Spelpaus information
• Denmark (da-DK): separate regulation and dates that change in 2026–2027 with the advertising bill
• Norway (nb-NO): two written standards, Bokmål and Nynorsk; most web content is in Bokmål
• Finland (fi-FI): Finnish is structurally entirely unlike Swedish or Danish, and Swedish is also an official language there

Danish and Norwegian are close, but not interchangeable. A Dane notices a Norwegian “translation” into Danish and vice versa.

What Google says about hreflang

• Reciprocal links: if two pages do not point to each other, the tags are ignored
• Each version lists itself and all other language versions
• URLs must be fully qualified, with the protocol (https://...)
• The language code is ISO 639-1 and the region ISO 3166-1 Alpha 2; a country code cannot be used alone
• x-default points to a fallback page for users whose language is not supported
• There are three methods (HTML link, HTTP header, sitemap) and you do not need to combine them

Example: a page exists in Swedish and Danish. The Swedish version declares link rel=alternate hreflang=sv-SE (itself), hreflang=da-DK (the Danish version) and x-default. The Danish version declares exactly the same three lines. If the Danish page fails to reference the Swedish one, Google ignores both annotations.

Why machine translation does not earn links

Links go to pages where a local author adds something the original does not have: a reference to local law, the name of a local operator, local examples. Machine translation is not a bad start, but it is not enough alone. Google’s spam policy covers mass low-value content, and the risk grows when hundreds of translated pages exist and nobody has reviewed them.

A practical workflow

1. Write the original in one language and decide which pages really need a local version
2. Have a local author or editor rewrite the text, not just proofread it
3. Add the local regulator, legislation, examples and numbers
4. Set up hreflang in both directions and check that URLs are fully qualified
5. Build links in local publications, not as a global package
6. Measure in Search Console by country and language separately

Typical mistakes

• Hreflang points one way only
• Wrong language code (for example “se” for Sweden instead of “sv”, or “dk” for Danish instead of “da”)
• Every version is canonical to one page, so Google does not index the others
• An untranslated menu and footer on a translated page

A checklist before publishing

• The text was written or rewritten by a local author
• The menu, footer and forms are translated
• Hreflang is reciprocal and URLs are fully qualified
• The canonical link points to the same language version, not another
• The local regulator and legislation are named in the text

Three questions

Is x-default required?

No, but it is useful: x-default points to a fallback page (for example a language selector) for users whose language is not supported.

Can I declare hreflang in several ways at once?

Google treats HTML links, the HTTP header and the sitemap as equivalent, and using several adds no value. Pick one and keep it correct.

Which language code for Norway?

The language code follows ISO 639-1, optionally with a country. A country code cannot be used alone. Choose the code that matches your page’s actual language and use it consistently.

Sources

• Google Search Central: Tell Google about localized versions of your page
• Google Search Central: How x-default can help you
• Google Search Central: spam policies