What does the configuration of Cloudflare Workers look like to set up a separate Guide section as another Webflow site using the CMS system in Webflow when the main site has reached the max page limit? After setting up the configuration, how do I point my main domain at the provided Routes URL from Cloudflare?

If your main Webflow site has reached the max page limit, you can use Cloudflare Workers to serve a separate Webflow CMS-driven Guide section from another Webflow project under a shared domain. Here's the setup process:

1. Configure Cloudflare Worker for Routing

You need to create a Cloudflare Worker that forwards requests to your separate Webflow site.

• Go to the Cloudflare Dashboard and navigate to Workers & Pages > Manage Workers.

• Create a new Worker and add a script that proxies requests from /guide/* (or another subpath) to the secondary Webflow project.

• Use the following logic inside your Worker:

• Capture incoming requests to /guide/*.

• Modify and forward them to the Webflow-hosted Guide CMS site.

• Return the response to users seamlessly.

2. Deploy the Cloudflare Worker

Once you've added the script:

• Save and Deploy the Worker.
• Test the Worker by manually fetching content from the separate Webflow site.
• Ensure CSP (Content Security Policy) and CORS (Cross-Origin Resource Sharing) settings allow proper access.

3. Update Cloudflare Workers Routes

Now, direct traffic using the Worker:

• Go to Cloudflare > Workers & Pages > Triggers.
• Set up a Route matching your desired guide path, e.g., example.com/guide/*.
• Assign it to your deployed Worker.

4. Update DNS for Main Domain

Now, configure your main domain (e.g., example.com) to point to Cloudflare so it correctly handles routing.

• If your domain isn’t already using Cloudflare, add your domain to Cloudflare and update your Nameservers per their instructions.
• Ensure Webflow’s root domain is proxied through Cloudflare by updating your A records or CNAME settings in Cloudflare:
• A records: Use Webflow’s default IPs: (a) 75.2.70.75, (b) 99.83.190.102.
• CNAME (for subdomains like "www"): Point www to Webflow’s proxy-ssl.webflow.com.
• Confirm the Cloudflare Proxy (Orange Cloud) is enabled to allow routing through Workers.

5. Test and Verify Integration

• Open a browser and check example.com/guide/ - it should load content from your second Webflow project.
• Debug issues using Cloudflare Logs and Webflow’s publishing settings.

Summary

To extend your Webflow CMS limit, use a Cloudflare Worker to forward /guide/* traffic to a second Webflow project. Then, configure DNS to route everything through Cloudflare and verify correct proxying settings. This allows both sites to function under one domain.