Learning how to set up Cloudflare is one of the fastest ways to make your website quicker and safer, often in under an hour and at no cost. Cloudflare sits between your visitors and your server, caching content across a global edge network, filtering malicious traffic, and managing your DNS from one dashboard. In 2026 that matters more than ever, because page speed and security both feed directly into your Google rankings.
This guide walks you through the full setup, step by step, in plain language. You will connect your domain, configure DNS, switch on the right SSL and speed settings, and avoid the common mistakes that break email or login pages. You will also learn where Cloudflare stops helping and why your underlying hosting still decides how fast your site can truly be.
What Cloudflare Actually Does?
Before the setup, it helps to know what you are switching on. Cloudflare is three tools in one, and understanding them makes every later setting obvious.
- A CDN (content delivery network). Cloudflare caches your static content in 330 or more cities worldwide, so a visitor loads your images and files from a server near them instead of making a slow trip to your origin. This cuts latency and takes load off your server.
- A security layer. It filters traffic before it reaches you, absorbing DDoS attacks, challenging bad bots, and blocking common exploits at the edge.
- A DNS manager. Cloudflare runs the fastest authoritative DNS network, consistently ranked first by DNSPerf, with DNSSEC support to prevent spoofing. You manage all your records from one clean dashboard.
The important nuance: Cloudflare speeds up delivery, but it does not replace your hosting. Your server still generates every page. That distinction becomes the deciding factor later in this guide.
How to Set Up Cloudflare: Step by Step
Follow these steps in order. The whole process takes roughly 30 minutes of active work, plus waiting time for DNS to propagate.
Step 1: Create a Free Cloudflare Account and Add Your Domain
- Sign up for a free account at cloudflare.com. The free plan is genuinely free forever and covers unlimited bandwidth, CDN, SSL, DNS and a basic firewall, which is all most sites ever need.
- Select Add a site and enter your apex domain (for example yoursite.com, not www.yoursite.com).
- Choose the Free plan when prompted. A primary (full) DNS setup is the only option on Free and Pro, and it is the correct one for almost everyone.
Step 2: Review Your DNS Records
Cloudflare automatically scans and imports your existing DNS records. This step is critical, so do not rush it. Check that every important record came across: your A record pointing to your server IP, your CNAME for www, and especially your MX and mail records for email. Compare the imported list against your current DNS to catch anything the scan missed. A missing record here is the number one cause of a site or email going dark after setup.
| Watch out Keep your MX records and any mail subdomains (like mail.yoursite.com) set to DNS Only (the grey cloud), not Proxied (orange). Email must never route through the Cloudflare proxy, or your mail will stop working. This single rule prevents the most common Cloudflare email problem. |
Step 3: Change Your Nameservers
This is the switch that activates Cloudflare. Cloudflare shows you two nameservers, something like ada.ns.cloudflare.com. Log in to your domain registrar, find the nameserver or DNS settings, and replace your existing nameservers with the two Cloudflare gave you. Save, and you are done on the registrar side. Propagation usually completes within one to four hours, though it can take up to 48 hours in rare cases. There is no downtime during this window: some visitors hit Cloudflare and some hit your old nameservers, and both work.
Step 4: Set Up SSL the Right Way
Once your domain shows active in Cloudflare, configure encryption. Go to SSL/TLS then Overview and choose Full (strict). This encrypts traffic both from the visitor to Cloudflare and from Cloudflare to your server, and it validates your origin certificate, which prevents man-in-the-middle attacks. If your host already installs a valid certificate (most quality hosts do, via Let’s Encrypt), Full (strict) works out of the box.
| Watch out Never use Flexible SSL. It leaves the connection between Cloudflare and your server unencrypted and frequently breaks login pages and redirect loops. Full (strict) is the only setting to trust in 2026. |
Then go to SSL/TLS then Edge Certificates and switch on Always Use HTTPS, so every insecure request redirects to the secure version automatically.
Step 5: Turn On the Speed Settings That Matter
A few toggles deliver most of Cloudflare’s speed benefit. In the Speed section of your dashboard, enable these:
- HTTP/3 with QUIC. Found under Speed then Protocol Optimization. It removes handshake overhead and speeds up connections on modern browsers.
- Early Hints. Under Speed then Content Optimization. It sends a 103 Early Hints response so the browser can start preloading your hero image and critical CSS while your server is still building the page. This can shave 200 to 400 milliseconds off LCP on uncached pages.
- Brotli compression. Now on by default at the edge, Brotli compresses text assets more efficiently than the older Gzip.
For caching, Cloudflare replaced the old Page Rules system with a cleaner set of Rules in 2024. Use Cache Rules to cache static assets aggressively, and configuration rules to bypass caching on admin or checkout paths so you never serve a cached login screen.
Step 6: Set a Sensible Security Baseline
Cloudflare’s defaults are already solid, but two quick moves strengthen them. Set your Security Level to Medium for normal operation, raising it to High only during an active attack. Enable DNSSEC (under DNS then Settings) to protect your domain from spoofing, and add the DS record it generates at your registrar. Leave the free Managed Rules on for baseline protection against common exploits.
| Watch out If you enable bot-fighting features, do it carefully. Overly aggressive bot rules can block legitimate search engine crawlers and AI answer engines, which quietly harms your SEO and your visibility in AI search. Allow verified good bots. |
Where Cloudflare Stops Helping: Your Hosting Still Decides Speed
Here is the honest limit that most Cloudflare guides leave out. Cloudflare speeds up delivery, but it cannot fix a slow origin server. When a page is not cached, or when a visitor triggers dynamic content like a login, a cart, or a search, the request goes all the way back to your host. If your server’s response time is slow, Cloudflare cannot rescue it.
Time to First Byte proves the point. Google wants TTFB under 800 milliseconds, and top sites hit under 200 milliseconds. On overloaded shared hosting, TTFB can swing wildly and fail your Core Web Vitals no matter how well Cloudflare is configured. Cloudflare and your host are partners, not substitutes: Cloudflare handles the edge, your server handles the origin, and both have to be fast.
This is where the pairing gets powerful. Cloudflare’s edge caching plus server-level caching like LiteSpeed on quality hosting is one of the fastest setups available in 2026. LiteSpeed handles full-page caching on your server, delivering cached responses in the 15 to 50 millisecond range, while Cloudflare handles static assets and DDoS globally. They complement each other perfectly.
Bisup is built for exactly this pairing. Our plans run on NVMe storage with LiteSpeed servers on our own network, AS208462, so your origin responds fast before Cloudflare even caches it. You can see the technical detail on our network infrastructure page, and if slow speed is your real concern, our companion guide on why your website is slow breaks down every cause.
| Cloudflare handles the edge. We handle the engine. Bisup web hosting ships with LiteSpeed, NVMe and free migration, and it pairs cleanly with Cloudflare’s free plan. For heavier or WordPress sites, see our managed WordPress hosting and VPS plans. |
Recommended Cloudflare Settings at a Glance
| Setting | Where | Recommended value |
| SSL/TLS mode | SSL/TLS > Overview | Full (strict) |
| Always Use HTTPS | SSL/TLS > Edge Certificates | On |
| HTTP/3 (QUIC) | Speed > Protocol Optimization | On |
| Early Hints | Speed > Content Optimization | On |
| Brotli | Speed (edge default) | On |
| Security Level | Security > Settings | Medium (High during attacks) |
| DNSSEC | DNS > Settings | On, with DS record at registrar |
| MX / mail records | DNS > Records | DNS Only (grey cloud) |
Set Up Cloudflare, Then Give It a Fast Engine
Setting up Cloudflare is a genuine quick win: better speed, stronger security, and cleaner DNS, mostly for free and in about half an hour. Work through the steps above, keep your email records unproxied, use Full (strict) SSL, and switch on HTTP/3 and Early Hints. Then remember the part most guides skip: Cloudflare accelerates delivery, but your host sets the baseline. Pair it with fast, LiteSpeed-powered hosting and you get the full benefit. Explore Bisup web hosting with free migration and let Cloudflare’s edge sit in front of a server that is already quick.
Frequently Asked Questions
Yes. Cloudflare’s free plan is free forever and includes unlimited bandwidth, CDN, SSL, DNS and a basic firewall. For most websites, blogs and small stores, the free plan covers everything you need. Paid plans add advanced image, security and analytics features that only larger or high-traffic sites usually require.
Active setup takes about 30 minutes. After you change nameservers, DNS propagation typically completes within one to four hours, and occasionally up to 48 hours. There is no downtime during propagation, because visitors are served correctly whether they reach the new or old nameservers.
Not if you configure DNS correctly. The key rule is that MX records and mail subdomains must stay set to DNS Only, the grey cloud, and never route through the Cloudflare proxy. As long as those records import correctly and remain unproxied, your email keeps working normally.
No. Cloudflare is a delivery and security layer that sits in front of your host, but your server still generates every page. Cloudflare cannot fix a slow origin server, which is why fast hosting with LiteSpeed and NVMe still matters. The two work best together, not as substitutes.
Yes, and it is one of the best combinations available. LiteSpeed Cache handles full-page caching on your server for very low TTFB, while Cloudflare caches static assets globally and blocks attacks at the edge. Using both gives you fast origin responses and fast global delivery at the same time.
