A multilingual Webflow route proxy with sitemap and canonical control
The challenge behind the build
Localized websites need consistent route handling, canonical behavior, sitemap coverage, and fallback behavior for pages that are not ready yet.
The implementation goal
SoFlow migrated the multilingual Worker into the KST platform service structure, preserving Webflow origin proxying, localized routes, canonical routing, route manifests, protected diagnostics, and sitemap behavior.
SoFlow migrated a Webflow multilingual proxy that controls localized routes, canonical behavior, protected diagnostics, sitemap coverage, and not-ready route redirects...
This implementation creates a maintainable edge layer for multilingual Webflow sites where SEO-sensitive routing cannot be left to page settings alone.
Our other projects
The brief was to control multilingual Webflow routing and SEO behavior without turning every localized path into a brittle manual Webflow setup.
Localized websites need consistent route handling, canonical behavior, sitemap coverage, and fallback behavior for pages that are not ready yet.
The implementation includes production diagnostics, route manifests, and KST-specific route decisions. Public content should focus on the architecture, not expose protected diagnostics or stale IDs.
SoFlow migrated the multilingual Worker into the KST platform service structure, preserving Webflow origin proxying, localized routes, canonical routing, route manifests, protected diagnostics, and sitemap behavior.
A Cloudflare Worker sits in front of Webflow, reads route manifest state, applies multilingual routing and canonical decisions, protects diagnostics, excludes not-ready CMS routes from sitemap output, and redirects incomplete public paths to stable alternatives.
- Webflow origin proxying
- Localized route handling
- Canonical and SEO routing controls
- Language switcher route manifest
- Sitemap exclusions for not-ready pages
- Protected diagnostics and parity snapshots
This implementation creates a maintainable edge layer for multilingual Webflow sites where SEO-sensitive routing cannot be left to page settings alone.
- Migration status and deployed Worker version documented
- Local route parity confirmed after seeding local KV from live route manifest
- Blog, FAQ, and discipline detail routes intentionally excluded from sitemap while not ready
Can this be adapted for another business?
Yes, if the same type of workflow, integration, or decision logic exists. The implementation should be scoped around the buyer's systems and public-safety needs.
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?
Confirm which live routes are public-safe and capture a route-manifest or sitemap proof screenshot.
This work proves that SoFlow can make Webflow multilingual routing more reliable by moving route intelligence to Cloudflare.
Can this be adapted for another business?
Yes, if the same type of workflow, integration, or decision logic exists. The implementation should be scoped around the buyer's systems and public-safety needs.
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
Localized route behavior risked being spread across Webflow settings, manual links, and untracked redirects.
The site gained a Worker-owned route layer with documented parity checks and safer handling of not-ready localized routes.
Webflow page settings alone are not enough when localized routes, sitemap exclusions, not-ready redirects, origin proxying, and parity audits need to be controlled at the domain edge.
