main-site.webflow.io
, guide-site.webflow.io
)./guides/*
traffic to the Guide site and all other traffic to the main site using fetch-and-rewrite logic.example.com/*
), and update DNS with proxy enabled to route all traffic through the Worker.You're trying to host a separate Webflow CMS site (a "Guide" section) as a standalone instance because your main Webflow site hit the page limit, and you want to combine both sites via Cloudflare Workers with custom routing.
Here’s how to configure this using Cloudflare Workers and then point your domain properly.
main-site.webflow.io
, guide-site.webflow.io
).Use Cloudflare Workers to create a reverse proxy that maps specific routes (e.g., /guides/**
) to your secondary Webflow CMS site.
export default { async fetch(request, env, ctx) { const url = new URL(request.url) if (url.pathname.startsWith('/guides')) { const newPath = url.pathname.replace('/guides', '') || '/' const targetURL = `https://your-guide-site.webflow.io${newPath}${url.search}` return fetch(targetURL, request) } // Default to main Webflow site const targetURL = `https://your-main-site.webflow.io${url.pathname}${url.search}` return fetch(targetURL, request) }}
your-guide-site.webflow.io
and your-main-site.webflow.io
with your actual Webflow subdomains or custom domains.example.com/*
To fully route traffic through your Worker at Cloudflare:
To serve a Guide section from a second Webflow site, use a Cloudflare Worker as a reverse proxy, routing URLs like /guides/...
to your second Webflow instance. Then, point your domain to Cloudflare, map all paths through a Worker route (e.g., example.com/*
), and let the Worker split traffic between your main and Guide sites.