An AI translation and review layer for multilingual Webflow publishing
The challenge behind the build
Duplicating Webflow content across languages creates drift: source pages change, translated pages become stale, and canonical or hreflang rules become difficult to audit.
The implementation goal
SoFlow consolidated a multilingual proxy architecture that extracts English source HTML into stable translation segments, stores translation state in D1, supports draft/reviewed/published/stale/rejected states, and prepares localized route output behind a Worker.
SoFlow is building a multilingual Webflow proxy that extracts English source pages, queues AI translations for review, and serves localized routes only after review st...
The implementation gives SoFlow a serious multilingual publishing architecture, but it should remain private until storage, secrets, route ownership, and production language policy are finished.
Our other projects
The brief was to avoid managing duplicated translated Webflow pages while still preparing SoFlow for multilingual publishing across language-prefixed routes.
Duplicating Webflow content across languages creates drift: source pages change, translated pages become stale, and canonical or hreflang rules become difficult to audit.
The system is not deploy-ready. D1, KV, provider secrets, supported languages, review policy, and production route ownership still need final decisions before public use.
SoFlow consolidated a multilingual proxy architecture that extracts English source HTML into stable translation segments, stores translation state in D1, supports draft/reviewed/published/stale/rejected states, and prepares localized route output behind a Worker.
English Webflow pages remain the source. A Cloudflare Worker extracts route content, hashes segments, queues stale translation rows, uses an AI provider adapter for translation batches, stores review state in D1, and will serve localized routes with canonical and hreflang handling once the renderer is wired.
- English-source Webflow content extraction
- Source-hash based stale translation detection
- D1-backed translation review states
- Protected review and translation diagnostics endpoints
- Canonical, hreflang, sitemap, and robots groundwork
The implementation gives SoFlow a serious multilingual publishing architecture, but it should remain private until storage, secrets, route ownership, and production language policy are finished.
- Translation review module supports draft, reviewed, published, stale, and rejected states
- Protected endpoints exist for translation status, stale rows, page review, and review updates
- README explicitly marks the Worker as not deploy-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?
Finalize D1/KV bindings, provider secrets, supported language policy, route ownership, and renderer integration before public launch.
This work proves that SoFlow can design Webflow localization as a controlled publishing system, not only a page-copying workflow.
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
Multilingual publishing would have depended on duplicated Webflow content or manual translation workflows that can drift from the English source.
The project now has a clearer Worker architecture for AI-assisted multilingual publishing with review gates before translated text can become public.
A static Webflow localization setup can publish translated content, but it does not by itself track source hashes, queue stale translations, protect draft translations from rendering, or expose review state for each segment.
