Home/Blog/Best Cloudflare Settings for WordPress 2026

Best Cloudflare Settings for WordPress 2026

Cloudflare settings for WordPress dashboard illustration

Cloudflare can make your WordPress site faster and safer for free, but only if you configure it properly. Many site owners add their domain to Cloudflare, switch the nameservers, and then never touch another setting. The result is a site that is only slightly faster and still exposed to the same attacks. The right Cloudflare settings for WordPress change that completely. In this guide, you will learn the exact settings worth changing in 2026, the ones to leave alone, and the mistakes that break WordPress sites.

Why Cloudflare Helps WordPress Sites

Cloudflare sits between your visitors and your hosting server. When someone opens your site, Cloudflare serves cached images, CSS, and JavaScript from a data centre near them instead of making every request travel to your origin server. That cuts loading time, especially for visitors far from your server. At the same time, Cloudflare filters bad traffic, absorbs DDoS attacks, and provides a free SSL certificate. If you are still setting up Cloudflare for the first time, read our step-by-step Cloudflare setup guide for WordPress before changing the advanced settings below.

Step 1: Proxy Only the Right DNS Records

After adding your domain, open DNS in the Cloudflare dashboard. Your main domain and www record should show an orange cloud, which means traffic is proxied through Cloudflare. Records for mail, FTP, and your hosting control panel should stay grey, or DNS-only. Proxying mail records breaks email delivery, and proxying control-panel subdomains can lock you out of your hosting account. This single check prevents a large share of Cloudflare setup problems.

Step 2: Set SSL to Full (Strict)

The most common Cloudflare mistake is leaving SSL on Flexible. Flexible encrypts the connection between the visitor and Cloudflare, but not between Cloudflare and your server, and it often causes redirect loops on WordPress sites. Go to SSL/TLS, then Overview, and select Full (Strict). This requires a valid certificate on your origin server, which most hosts provide free through Let’s Encrypt. Also turn on Always Use HTTPS so every visitor is redirected to the secure version of your site. If you ever see an SSL handshake error after this change, our guide to fixing Cloudflare connection errors walks through the likely causes.

Cloudflare caching and security layers protecting a WordPress website

Step 3: Caching Settings That Speed Up WordPress

Under Caching, keep the Caching Level at Standard and turn on Smart Tiered Caching, which reduces requests to your origin server. Set Browser Cache TTL to Respect Existing Headers so your WordPress caching plugin controls how long browsers keep files. After publishing or updating a post, purge the cache for that URL from the Cloudflare dashboard or the official Cloudflare plugin, otherwise visitors may keep seeing the old version. If your site still feels slow after these tweaks, check the other causes in our guide on why websites load slowly and how to fix them. For full-page caching, Cloudflare APO costs $5 per month on the free plan and caches your WordPress HTML at the edge, which is the biggest single speed win for most blogs.

Step 4: Speed Settings Worth Turning On

Under Speed, enable HTTP/3, which helps visitors on slow or mobile connections, and turn on Early Hints to start loading key resources sooner. Leave Rocket Loader off unless you test it carefully first, because it defers JavaScript and can break sliders, menus, and checkout pages. Note that Auto Minify no longer exists in the 2026 dashboard; handle CSS and JavaScript minification inside WordPress with a performance plugin instead. Test your site after every change by clicking through your homepage, a post, and your contact page.

Step 5: Security Rules Every WordPress Site Needs

Under Security, set the Security Level to Medium for a good balance between protection and usability. Turn on Browser Integrity Check to block visitors with suspicious headers. Then create two free WAF custom rules. First, block requests where the URI path contains xmlrpc.php, a legacy file attackers abuse for brute-force attacks. Second, add a rule to challenge or rate-limit repeated requests to wp-login.php. Only enable Bot Fight Mode if your site has no webhooks, APIs, or app traffic, because it can block legitimate automated requests. These rules take minutes to set up and stop a large share of automated attacks.

Mistakes to Avoid

  • Leaving SSL on Flexible, which causes redirect loops and weak encryption.
  • Proxying mail and control-panel records, which breaks email and hosting access.
  • Turning on every speed toggle at once, so you cannot tell which one broke your site.
  • Forgetting to purge the cache after updates, so visitors see outdated content.
  • Using old tutorials that mention Page Rules or Auto Minify, both retired from the dashboard.

Conclusion

The best Cloudflare settings for WordPress are not complicated: proxy only your website records, use Full (Strict) SSL, cache smartly, enable the safe speed toggles, and block the two attack paths every WordPress site faces. Apply them one at a time, test your site after each change, and you will get a faster, safer site on the free plan. Explore more guides on the KamiWeb blog and try our free website tools to keep improving your site.