The early Worker behind SoFlow's multilingual routing playbook
The challenge behind the build
Routing multilingual traffic correctly at the edge — without breaking Webflow's native structure or SEO signals — meant testing routing and manifest logic somewhere safer than a live site.
The implementation goal
Prototype Cloudflare Worker-based multilingual routing and manifest generation for Webflow, then carry forward whatever held up into a more capable, production-ready implementation.
A prototype that earned its keep by being replaced
SoFlow built this Worker to test multilingual SEO routing patterns for Webflow. The ideas that worked were consolidated into newer, stronger proxy Workers; the ones that didn't were left behind here — which is exactly what a good prototype is supposed to do.
Our other projects
The brief was internal: find a workable pattern for multilingual SEO routing on Webflow before committing to a production architecture.
Multilingual SEO routing on Webflow has enough edge cases — locale detection, manifest generation, canonical handling — that it needed a real prototype, not just a design doc. But a prototype isn't a case study, and publishing it separately would only dilute the stronger implementations it led to.
This stays private. Anything reusable from it belongs in the SoFlow AI multilingual proxy and KST multilingual route proxy case studies, not as a duplicate page.
SoFlow built and retired this Worker as an internal reference — its useful routing and manifest patterns now live inside newer, production multilingual proxy implementations.
A Cloudflare Worker sat in front of Webflow, intercepting requests to test locale routing and generate manifest data — a lightweight, edge-side precursor to the proxy architecture used in later multilingual projects.
- Early multilingual route detection logic
- Manifest generation experiments for locale data
- Edge-side routing in front of Webflow via Cloudflare Workers
- Superseded by newer SoFlow and KST multilingual proxy Workers
A safely retired prototype whose real value now lives inside SoFlow's current multilingual proxy case studies rather than as its own page.
- No public proof needed — this was never meant to ship on its own
- Patterns validated here were reused in later production Workers
- Kept private specifically to avoid a duplicate, weaker Work entry
What was this Worker actually for?
It was an early experiment in routing multilingual traffic and generating locale manifests for Webflow sites — testing ideas before they were mature enough to ship. Several of those ideas now live inside SoFlow's newer, production-grade multilingual proxy Workers.
Why put this in Webflow if external code is involved?
Webflow is the public storytelling and CMS layer. External code should stay in the app, Worker, or integration layer where it can be versioned, secured, and tested.
What is needed before publishing?
Nothing — this one is meant to stay private. Anything worth showing publicly has already been folded into the newer SoFlow and KST multilingual proxy case studies.
This shows SoFlow treats prototypes as prototypes — testing routing ideas at the edge before committing them to production, and retiring the experiment once the real implementation exists.
What was this Worker actually for?
It was an early experiment in routing multilingual traffic and generating locale manifests for Webflow sites — testing ideas before they were mature enough to ship. Several of those ideas now live inside SoFlow's newer, production-grade multilingual proxy Workers.
Why put this in Webflow if external code is involved?
Heading 1
Heading 2
Heading 3
Heading 4
Heading 5
Heading 6
Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur.
Block quote
Ordered list
- Item 1
- Item 2
- Item 3
Unordered list
- Item A
- Item B
- Item C
Bold text
Emphasis
Superscript
Subscript
Heading 1
Heading 2
Heading 3
Heading 4
Heading 5
Heading 6
Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur.
Block quote
Ordered list
- Item 1
- Item 2
- Item 3
Unordered list
- Item A
- Item B
- Item C
Bold text
Emphasis
Superscript
Subscript
SoFlow had no tested pattern yet for handling multilingual SEO routing at the edge in front of a Webflow site.
The viable routing and manifest patterns were carried into newer, production multilingual proxy Workers, and this prototype was retired to internal reference status.
Webflow doesn't natively handle locale-aware routing and manifest generation at the edge — that logic has to run in a Worker in front of the site, which is exactly what this prototype tested.
