TL;DR
Webflow teams hit the geo wall from two directions: a multi-market brand site needing country routing, or Webflow Localization adopters discovering that translated locales don't route anyone by themselves. Both end at the same setup.
Step 1 — Rules first
Create a site in Easy Redirects for your Webflow domain and add rules — e.g. DACH → /de, Nordics → /no, or cross-domain to yourbrand.de. Country presets, path scoping, and priorities work identically to every other platform.
Step 2 — Paste into Webflow
- Webflow Designer → Site Settings → Custom Code
- Paste the snippet into Head Code
- Save and publish — unlike HubSpot's header HTML, Webflow custom code ships on the next publish, so this one needs the publish button
The snippet then runs on every page of the published site, including CMS collection pages. Rule changes after this point are live immediately — no republish needed; only snippet installation is tied to publishing.
Step 3 — Test
Same drill as anywhere: a temporary rule targeting your own country, a fresh private window, then verify ?no_redirect=1 keeps editors un-redirected. One Webflow-specific check: confirm you published to the custom domain, not just the .webflow.io staging domain — staging and production have separate publish states.
SEO note for Localization users
Webflow Localization generates hreflang for localized pages — keep it on, and let redirects handle live visitors. The combination (hreflang for search arrival + once-per-session geo-redirects for everyone else) is the same best-practice pattern we recommend for every platform.Geo-redirects on your HubSpot site in 5 minutes
One script tag, no code, no DNS changes. Free plan included.
Start freeFrequently asked questions
Does Webflow have native geo-targeting or geo-redirects?
No — Webflow ships URL redirects (301s) but nothing location-aware, and its Localization product translates content rather than routing visitors across pages or domains. Location-based routing on Webflow is done with a script tag.
Do I need a paid Webflow plan?
You need a site plan that allows custom code (any paid site plan does). The free staging tier doesn't support custom head code on a custom domain.
Does this work with Webflow Localization?
Yes, and they pair well: Localization creates the locale subdirectories (/de, /fr) and handles hreflang; a geo-redirect rule per market routes first-time visitors into the right locale. Webflow localizes content; the redirect layer localizes arrival.