HubSpot Multi-Language Websites: Routing Visitors to the Right Language

TL;DR

HubSpot's multi-language tools create and link language variants (/de, /fr) but don't reliably send visitors to them. The standard pattern: keep HubSpot's language variants + hreflang for SEO, and add a geo-redirect rule per market so live visitors land on the right version automatically.

Content Hub does the authoring side of multilingual well: language variants, linked translations, automatic hreflang between variants, a language switcher module. What it leaves open is the routing question — when someone from Oslo types your .com address or clicks a LinkedIn ad, who makes sure they end up on the Norwegian pages?

One rule per market: visitors are routed to their language folder; everyone else stays on the default.

The three-layer setup that works

Layer 1 — Structure: language folders

Use HubSpot's multi-language page management so each page has variants under a language slug (/de/preise, /no/priser). Folders on one domain consolidate SEO authority and are the easiest structure to maintain.

Layer 2 — SEO: hreflang

HubSpot generates hreflang tags between linked variants automatically. Verify them (View Source → look for rel="alternate" hreflang) and make sure every variant is linked to its siblings, including x-default for your fallback version. This is what makes Google show German searchers the German result directly.

Layer 3 — Visitors: geo-redirects

Hreflang only helps visitors who arrive via search. Everyone else — ads, social, email, direct — lands wherever the link pointed. A geo-redirect layer catches them: one rule per market, e.g. "Norway → /no", "DACH → /de", applied site-wide. Good implementations redirect once per session and never redirect someone who is already on a language path, so a German visitor can still deliberately browse your English pages.

Redirect or suggest?

Auto-redirecting is right when markets map cleanly to countries (pricing, legal, language all differ). If your versions differ only in language, consider redirecting only the homepage, or showing a suggestion banner instead — heavy-handed routing of bilingual visitors is a common complaint.

Common mistakes

Redirecting every page to one homepage — send /pricing visitors to /de/preise if it exists, or at minimum preserve the path structure where you can.
Forgetting query parameters — losing UTM tags in the redirect silently destroys campaign attribution.
No escape hatch — always keep a visible language switcher so a mis-located visitor (VPNs, travelers) can self-correct.

Geo-redirects on your HubSpot site in 5 minutes

One script tag, no code, no DNS changes. Free plan included.

Start free

Frequently asked questions

Doesn't HubSpot automatically show the right language version?

Only partially. HubSpot can match the visitor's browser language on some page types, but it doesn't reliably route by location, doesn't cover external domains, and many international teams find visitors landing on the wrong version daily.

Should I redirect by browser language or by country?

Country is usually the better business signal — it matches pricing, legal entities, and sales regions. Browser language is better for purely linguistic routing. Many teams combine them: country for the market, with a visible language switcher for individual preference.

Do I still need hreflang tags if I use geo-redirects?

Yes. Hreflang tells search engines which version to index for which audience; redirects handle live visitors. They're complementary, not alternatives — use both.