A Cloudflare Webflow proxy and sitemap Worker for ShapesLab

SoFlow built a Cloudflare Worker that proxies a Webflow origin for shapeslab.xyz, normalizes the public host, and can generate sitemap routes from configured static and CMS sources.
ShapesLab Worker
Client
ShapesLab Worker
Timeline
Private draft
Services
No items found.
About

A Cloudflare Webflow proxy and sitemap Worker for ShapesLab

This is a specific Worker implementation, but it needs client/project approval before public use. The useful public angle is Webflow proxying, canonical host control, and Worker-generated sitemap behavior.
Challenge

The challenge behind the build

A Webflow site may need canonical host normalization, public sitemap control, and CMS-route discovery that is easier to manage at the edge.

Goal

The implementation goal

SoFlow built a Cloudflare Worker that redirects www to the apex host, proxies requests to the Webflow origin, generates XML/HTML sitemap responses, and can fetch Webflow collection items for route lists.

Result

SoFlow built a Cloudflare Worker that proxies a Webflow origin for shapeslab.xyz, normalizes the public host, and can generate sitemap routes from configured static an...

This is a good private proof item for Cloudflare/Webflow routing work, pending approval to name the project publicly.

Stack
Cloudflare Workers, Webflow origin proxy, Webflow CMS API, sitemap generation
Systems
Webflow, Cloudflare Workers
Category
Custom Solutions
This is some text inside of a div block.

The brief was to put a Cloudflare Worker in front of a Webflow-hosted ShapesLab site so route and sitemap behavior could be controlled outside Webflow alone.

This is some text inside of a div block.

A Webflow site may need canonical host normalization, public sitemap control, and CMS-route discovery that is easier to manage at the edge.

This is some text inside of a div block.

The project belongs to a separate domain and needs permission before naming or publishing. Keep private until approved.

This is some text inside of a div block.

SoFlow built a Cloudflare Worker that redirects www to the apex host, proxies requests to the Webflow origin, generates XML/HTML sitemap responses, and can fetch Webflow collection items for route lists.

This is some text inside of a div block.

Requests reach Cloudflare first. The Worker normalizes the host, serves sitemap routes when requested, fetches Webflow CMS item slugs through the Webflow API when configured, and proxies normal page requests to the Webflow origin.

This is some text inside of a div block.
  • Canonical www to apex redirect
  • Webflow origin proxying
  • XML and HTML sitemap generation
  • Configured static routes plus Webflow collection routes
  • Public-host URL normalization
This is some text inside of a div block.

This is a good private proof item for Cloudflare/Webflow routing work, pending approval to name the project publicly.

This is some text inside of a div block.
  • wrangler config names shapeslab.xyz as public host
  • Worker source includes sitemap XML/HTML responses and Webflow collection route fetching
This is some text inside of a div block.

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 permission to name the project and capture public-safe route/sitemap proof.

This is some text inside of a div block.

This work proves that SoFlow can use Cloudflare Workers to add technical routing and discovery controls around a Webflow site.

This is some text inside of a div block.

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?

This is some text inside of a div block.

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

  1. Item 1
  2. Item 2
  3. Item 3

Unordered list

  • Item A
  • Item B
  • Item C

Text link

Bold text

Emphasis

Superscript

Subscript

This is some text inside of a div block.

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

  1. Item 1
  2. Item 2
  3. Item 3

Unordered list

  • Item A
  • Item B
  • Item C

Text link

Bold text

Emphasis

Superscript

Subscript

This is some text inside of a div block.
This is some text inside of a div block.
Before

The Webflow origin did not own the whole domain-edge routing and sitemap behavior.

After

The Worker gives the domain a controlled proxy and sitemap layer in front of Webflow.

This is some text inside of a div block.

Webflow page settings do not fully own edge redirects, proxy behavior, or a Worker-generated sitemap built from multiple route sources.

Let's talk

Ready to elevate your business?