Fast. Simple. No meetings. No delays.
Home / Blog / Denmark / Multilingual Websites: Danish and English Done Properly

Multilingual Websites: Danish and English Done Properly

URL structure, hreflang, translation workflow and language switching for a Danish and English website.

Cover graphic for the article: Multilingual Websites: Danish and English Done Properly

A multilingual website Danish English visitors can both use well needs three things: separate, stable URLs for each language, hreflang tags that link the equivalent pages, and a translation process that keeps both versions current. Everything else, from the language switcher to the contact form, follows from those foundations.

One site, two audiences

Before touching URLs, decide what the English version is for. A Danish company usually has one of three reasons: reaching international customers, supporting English-speaking staff or residents in Denmark, or looking credible to foreign partners. The reason decides how much you translate.

  • Full mirror. Every page exists in both languages. Simple to explain, but doubles your maintenance.
  • Core subset. Only the pages that matter to English-speaking visitors: services, key product pages, contact. Cheaper and often wiser.
  • Different content per market. The English site has its own pages, tone and offers. Treat it as a separate editorial product.

Be honest about capacity. A half-translated English site with Danish fragments and outdated prices does more harm than a short, accurate one. Also decide who owns it: translation is an ongoing task, not a launch task.

URL structure options for a multilingual website

This is the decision that is hardest to change later, so make it deliberately. The three common options are:

OptionExample patternStrengthsTrade-offs
Subfoldersexample.dk/ and example.dk/en/One domain, one hosting setup, shared authority, easy to maintainLess obvious geographic signal; both languages share one server location
Subdomainsen.example.dkCan be hosted separatelyTreated more like a separate site; more setup and tracking work
Separate domainsexample.dk and example.comStrong market identity; different branding possibleTwo sites to maintain, secure, promote and renew

For most small and mid-sized Danish businesses, subfolders on one domain are the pragmatic choice. They keep management simple, and everything you earn in visibility benefits one site. Separate domains make sense when the English-language brand is genuinely different or aimed at one specific foreign market.

Whichever you choose, translate the URL slugs too if it suits readers (for example a Danish word in the Danish URL), but keep them stable. Changing a URL later means redirects, and redirects are easy to forget.

Hreflang and canonical tags

Hreflang is a way of telling search engines that two pages are the same content in different languages, so each visitor is shown the right one. It is also one of the most commonly misconfigured parts of multilingual SEO. The rules that matter:

  1. Every page lists all its versions, including itself. The Danish page points to the Danish and English pages; the English page does the same.
  2. The links must be reciprocal. If A points to B, B must point back to A, or the signal may be ignored.
  3. Use correct language codes. da for Danish and en for English; add a region code such as da-DK only if you have a real reason to separate regions.
  4. Add an x-default. Point it at the page you want shown when no language matches, often a language chooser or the primary version.
  5. Use absolute URLs and make sure each one actually returns a normal page, not a redirect or error.

Each language version should have a canonical tag pointing to itself. A common mistake is to canonicalise the English page to the Danish one, which tells search engines to ignore the English page entirely. Canonical and hreflang must agree. You can place hreflang in the page head, in HTTP headers, or in the XML sitemap; pick one method and generate it automatically rather than by hand.

Only link equivalent pages. If a Danish page has no English counterpart, leave it out of hreflang rather than pointing it at the English homepage.

Translation workflow and updates

Launching is easy; staying in sync is hard. Define a process before the first page is translated.

  • Choose a source language. Usually Danish. Edits start there and trigger a translation task for English.
  • Keep content in structured fields rather than hard-coded in templates, so editors can translate without a developer. Interface strings, such as button labels and form messages, belong in language files.
  • Mark translation status on each page: current, outdated or missing. A simple status column in your content system prevents silent drift.
  • Use human review. Machine translation can produce a good first draft, but names, legal wording, product claims and tone need a fluent reader to check them.
  • Handle dates, numbers and currency by locale, so that decimal separators and date formats look natural in each language.

Treat the translation of a price, delivery term or product specification as seriously as the original: errors in the English version are still your public statements.

Language switcher and defaults

A good switcher is visible, labelled in each language's own name (Dansk and English), and takes the visitor to the equivalent page, not the homepage. If no translation exists, send them to the nearest sensible page and say so.

The question of automatic redirects is where many sites go wrong. Redirecting visitors by browser language or location looks helpful, but it can lock people out: a Danish speaker travelling abroad, or search engine crawlers that fetch pages from different regions, may never see the version they need. A safer pattern is to serve each URL in one fixed language, show a dismissible banner suggesting the other language, and remember the visitor's explicit choice in a cookie or preference. Pair that with a default that makes sense for your main audience, usually Danish at the root.

Translation does not stop at page text. Walk through every interaction an English-speaking user can have:

  • Form labels, validation messages and confirmation screens.
  • Transactional emails: order confirmations, password resets and notifications should arrive in the language the user chose.
  • Cookie notices and consent text, which must be understandable to the reader.
  • Privacy policy, terms and returns information. Legal text needs a qualified person to review the translation, and you should decide which version governs if the two differ. Our piece on GDPR by design explains the privacy side; confirm current requirements with an adviser or the official source.
  • Error pages, search results and metadata such as page titles and descriptions, each unique per language.

If you run a shop, remember that checkout language also affects payments and trust; see our guide to payment methods for Danish web shops.

Testing

Test the multilingual setup as its own workstream before and after launch.

  1. Crawl the site and check that every language page returns a normal status, has a self-referencing canonical, and has reciprocal hreflang.
  2. Switch language on ten different pages by hand and confirm you land on the equivalent page each time.
  3. Complete every form and receive every email in both languages.
  4. Look for text overflow: English and Danish strings differ in length, and compound Danish words can break narrow buttons.
  5. Check the XML sitemap, character encoding for æ, ø and å, and that search engines can reach both versions without logging in.
  6. After launch, review the search engines' reporting tools for hreflang or indexing errors and fix them promptly.

A multilingual website Danish English readers trust: next step

Start with the decisions that are expensive to reverse: the URL structure and the scope of the English version. Then automate hreflang and canonical tags, set up a visible translation status, and build the language switcher around equivalent pages rather than the homepage. If you are planning a larger Nordic expansion, our guide to developing a SaaS product for the Nordic market covers related decisions, and our software development for Danish companies page explains how we support projects like this remotely.

Frequently asked questions

Subfolders or separate domains?

For most small and mid-sized Danish businesses, subfolders on one domain, such as example.dk/en/, are the pragmatic choice: one site to host, secure and maintain. Separate domains suit cases where the English brand or market is genuinely distinct, but they double the maintenance and promotion work.

Should I auto-redirect by browser language?

Usually not as the default. Automatic redirects can lock out travellers, people with unusual browser settings and search engine crawlers. Serve each URL in one fixed language, suggest the other with a dismissible banner, and remember the visitor's explicit choice in a cookie.

How do I keep translations in sync?

Pick a source language, keep content in structured fields, and give each page a translation status such as current, outdated or missing. When the source changes, flag the translation for review. Use machine translation only as a draft and have a fluent person check names, prices and legal wording.

Related articles

Web Development Tel Aviv

Startup Landing Page Launch Checklist

Everything a startup landing page needs before launch: message, speed, forms, analytics, metadata, privacy text and tracking.

6 min read

🚀 Start Now