Cloudflare

If your domain’s DNS runs through Cloudflare, a Framer or Webflow site works with it. The records just need to follow the platform’s instructions, and someone needs access on launch day.

What Cloudflare is

Cloudflare is a network that sits between visitors and websites. Its services include DNS, a content delivery network, security and bot protection, domain registration, and Workers, which run code close to the visitor. Many companies use it to manage their domain’s records in one place.

How it fits on your site

Framer and Webflow both host your site on their own infrastructure, with SSL and a CDN included. On a site built with either, Cloudflare’s role is usually narrower.

DNS. This is the most common setup. You add the records Framer or Webflow gives you in Cloudflare’s DNS settings. Each platform publishes its own steps, and both currently say to set those records to DNS only.

The rest of your domain. Cloudflare keeps your other records in one place, such as email routing and the authentication records your email tools need.

Shared domains. When the marketing site and your docs or app need to share one domain, a subdomain such as docs.yourcompany.com is the simplest route. Serving them under one path, such as yourcompany.com/docs, needs a proxy setup, often with a Cloudflare Worker, and each platform has its own rules and plan requirements for it.

Where the scope includes it, we connect your domain at launch, working with whoever manages your Cloudflare account.

What you get

  • DNS records for the new site, added and checked at launch

  • A note of every record added or changed, and why

  • The domain and SSL checked live before the launch is announced

What to watch out for

Proxy settings

Turning on Cloudflare’s proxy for records that point at Framer or Webflow can cause SSL errors. Follow the platform’s current guidance for each record.

Caching twice

Both platforms already cache your pages. Extra caching rules in Cloudflare can keep serving old pages after you publish.

Email records

Changing the website’s records should leave MX and email authentication records alone. Note what’s there before changing anything.

Account access

DNS changes need someone with access to your Cloudflare account. Agree who that is before launch day.

Questions about Cloudflare

Daniel G. Bright, founder of BrightStudios

Daniel G. Bright

Founder, BrightStudios

Still have a question?

Book a call with me to talk through your project and agree the next step.

Tell us what your site connects to

Share your product and the tools your team uses. We’ll recommend a scope and the simplest way to connect each one.

Tel Aviv
Your time