Can Framer redirect visitors by browser language?

Not natively. Framer Localization creates translated pages but does not route visitors to them by language. The Router plugin reads the visitor's language server-side and sends or suggests the matching page.

Should I redirect by country or by language?

Language is usually the better signal for choosing a language version: a French speaker in Canada wants French, not the Canadian-English page. Country is better for pricing, currency and regional stores. Router can combine both.

Do language redirects hurt SEO?

Forced automatic redirects can. Google recommends letting users and crawlers reach any version and suggesting the better one, which a dismissible banner does without blocking crawling.

Framer guide

How to send Framer visitors to the right language version

You built French, German and Spanish versions of your Framer site. But everyone still lands on the English one. Framer translates pages; it doesn't route visitors to them. Here's how to close that gap by browser language, without wrecking your SEO.

By the Vanssay team. We build Router, the plugin used below. This is an explainer, not a hard sell.

Updated July 2026 · 4 min read

Works on any Framer site No code · no DNS changes

Country or language: which signal?

They answer different questions. Language is the right signal for choosing a language version: a French speaker in Canada wants French, and a German expat in Spain wants German, regardless of where their IP sits. Country is the right signal for pricing, currency and regional stores. The browser sends an Accept-Language preference on every request, which is exactly what you want for language routing, and you can combine it with country when you need both.

Why not the JavaScript version

The copy-paste approach reads navigator.language and redirects with JavaScript. It flashes the wrong page first, and forced client-side redirects are what Google's internationalization guidance warns against. Googlebot crawls mostly from US, English-preferring requests; if it always gets bounced, your other language versions may not get crawled well.

The SEO-safe setup with Router

Framer has no language-routing setting, so this comes from a plugin. Router reads the visitor's language server-side and acts on it:

Install Router from the Framer marketplace.
Add language rules: fr → /fr, de → /de, es → /es. Combine with country if needed.
Choose suggest or redirect. A dismissible banner offers the matching page and auto-translates into the visitor's language, so it's readable even before they switch. The choice is remembered so they're never asked twice.
Publish. Detection runs server-side, so there's no flash of the wrong page and no API keys in your source.

The Router plugin's Redirect rules panel in the Framer editor: rules matching language and country, sending visitors to locale paths, first match wins — Add language rules in Router's Redirect rules panel; combine with country when you need both.

Tip: keep every language version reachable by a stable URL and let crawlers see all of them. Pair this with hreflang tags so search engines index the right version per language, then use Router to guide humans to it.

Router, route by language, country and device for Framer, with SEO-safe suggestion banners. Free plan available.

View Router on Framer

Common questions

Does this work with Framer Localization?

Yes. Router just sends or suggests whichever locale URL you specify, including Framer's own localized paths.

Can I combine language and country?

Yes. Rules can match language, country, region, device or VPN status, alone or combined, and the first matching rule wins.

What if the visitor's language isn't one I support?

They fall through to your default page. Only visitors whose language matches a rule are routed or shown a banner.

Sources: Google Search Central: locale-adaptive pages · Framer help.