Webflow and Lovable sites now get a guided setup

Webflow and Lovable both serve your custom domain from their own Cloudflare account. That is why a Worker on a Cloudflare zone you control never saw the traffic, and why the checker used to call these sites "Cloudflare, compatible" and then leave you stuck.

What changed

• The compatibility checker on the home page recognises Webflow and Lovable sites and says exactly what the one-time setup is, instead of a generic Cloudflare verdict.
• The setup wizard offers a Webflow or Lovable method, with the Cloudflare steps for that builder before the usual Worker steps: a proxied CNAME to cdn.webflow.com for Webflow, or Lovable's "Uses Cloudflare or similar proxy" setting and a proxied CNAME to your project's lovable.app hostname. Both tiles are always available to pick yourself.
• The automatic Cloudflare review names the builder and the record to create when it finds a proxied A record pointing at the builder's own Cloudflare.
• New help sections for Webflow and Lovable, including the certificate timing that causes Cloudflare's 525 error and why a Lovable A record must be replaced rather than proxied.

Once the Cloudflare layout is in place, everything else is the standard Cloudflare Worker setup, including one-click Connect Cloudflare and delegated setup links.