Language-Based Content Routing

The scenario

You have content available in multiple languages — a help center, a product page, a terms of service page — and you want visitors to land on the right version automatically. Instead of showing a language picker or relying on browser-based redirects on your own site, you want a single link that detects the visitor's language and routes them to the correct page.

How to set it up

1. Create a Redirect by Language link

Go to the Redirect by Language tool and map each language to its localized page:

• English → example.com/en/help
• Spanish → example.com/es/ayuda
• French → example.com/fr/aide
• Default → example.com/en/help (fallback for when the visitor's language doesn't match any of your selections)

The tool reads the visitor's browser language setting and redirects to the matching destination.

2. Set a custom URL

Give it a clean slug like nimble.li/help or use a custom domain. This is the only URL you share — it works for everyone regardless of their language.

3. Use it everywhere

Share the link in contexts where your audience is multilingual:

• Global email campaigns — One link in the email, each recipient lands on their language.
• International support pages — A single "Help" link that routes to the right docs.
• Multi-language QR codes — Print one QR code on packaging that serves content in the scanner's language.

What you get

• No language picker — Visitors go straight to their language version. No extra step, no dropdown.
• One link for all languages — Simpler to manage and share than maintaining separate URLs per language.
• Language breakdown in analytics — The Destinations chart shows how many visitors went to each language version, which helps you understand your audience mix.

Variations

Language vs. country

Redirect by Country routes by geographic location; Redirect by Language routes by browser language setting. These can differ — someone in Germany might have their browser set to English. Choose the one that matches your content structure: if your pages are organized by language (/en/, /es/, /fr/), use language routing. If they're organized by region (/us/, /de/, /jp/), use country routing.

Combining language and country

For more precise routing, stack a Redirect by Country link with Redirect by Language links per region. For example, visitors from Canada get routed by language (English or French), while visitors from other countries get their regional page directly.

Passing language context

Enable parameter forwarding and your destination can receive additional context. Some CMS platforms use URL parameters to override language settings, so the forwarded params can reinforce the language selection.