THE SHORT ANSWER
Point your nameservers to Cloudflare, proxy only your website records (keep mail on DNS only), set SSL/TLS to Full (strict), and turn on Always Use HTTPS. Then add WAF custom rules that block XML-RPC and sensitive files and challenge the login page, rate limit wp-login.php, and set your security plugin to read the CF-Connecting-IP header. That covers most WordPress attacks on the Free plan.
Cloudflare is the cheapest security upgrade a WordPress site can get. The Free plan alone hides your server, absorbs DDoS attacks and stops a large share of bad traffic before PHP even starts. But it's easy to set up badly: mail breaks after the nameserver change, Flexible SSL causes redirect loops, a rule locks you out of wp-admin, or Bot Fight Mode quietly blocks your payment webhooks. This guide walks through the setup we use on agency client sites, from DNS to WAF rules, with copy-paste expressions and the fixes for the errors you're most likely to hit.
Applies to: Cloudflare Free, Pro and Business plans with WordPress 6.x and 7.x, on Apache, LiteSpeed and NGINX hosts. Last verified: November 2026.
01How Cloudflare sits in front of WordPress
Without Cloudflare, every visitor, bot and attacker talks straight to your hosting server. With Cloudflare, your domain's nameservers point to Cloudflare, your main records are proxied, and every request lands on Cloudflare's network first. Cloudflare filters it, serves what it can from cache, and only then passes the rest to your server, which we call the origin.
| Step | What happens | What it protects you from |
|---|---|---|
| 1. Visitor | Types your domain. DNS answers with a Cloudflare IP, not your server IP. | Attackers can't see your real server address in DNS. |
| 2. Cloudflare edge | Checks the request against DDoS protection, WAF rules, bot checks and rate limits. Serves cached files. | Floods, known exploits, login attacks, scrapers and traffic spikes. |
| 3. Your server | Gets only the requests that passed, over an encrypted connection. | Less load, fewer attacks reaching PHP and WordPress. |
That order matters. A security plugin such as Wordfence runs inside WordPress, so PHP has already started before it can say no. Cloudflare says no before the request ever reaches your hosting. The best setup uses both: Cloudflare at the edge, a plugin firewall at the origin.
Free, Pro or Business: what actually changes for a WordPress site
For most WordPress sites the Free plan covers the important parts. Here is what the paid plans add, based on Cloudflare's plan pages at the time of writing.
| Feature | Free | Pro | Business |
|---|---|---|---|
| Price | $0 | $20 a month billed yearly ($25 monthly) | $200 a month billed yearly ($250 monthly) |
| DDoS protection | Unmetered | Unmetered | Unmetered |
| WAF custom rules | 5 | 20 | 100 |
| Managed WAF rules | Free Managed Ruleset | Adds Cloudflare Managed Ruleset and OWASP Core Ruleset | Same as Pro |
| Rate limiting rules | 1 (10 second window, by IP) | 2 (up to 1 minute window) | 5 (up to 10 minute window) |
| Regex in rules | No | No | Yes |
| Automatic Platform Optimization (APO) | $5 a month add-on | Included | Included |
| Bot protection | Simple bots (Bot Fight Mode) | Easy to detect bots | Sophisticated bots and bot analytics |
Our rule of thumb: brochure sites and blogs run well on Free. Upgrade to Pro when a site takes payments, gets targeted attacks, or when you want the Cloudflare Managed Ruleset, which ships rules for common CMS and plugin exploits. Business makes sense for stores where downtime costs real money.
Want this set up and watched for you?
Our white label care plans include Cloudflare setup on day one, then updates, backups, security monitoring and fixes, all under your agency brand.
02Before you switch: 10 minutes that save a day
Almost every Cloudflare horror story we fix started with a rushed nameserver change. Do these first.
- Export your current DNS zone. In cPanel open Zone Editor, or ask your DNS host for a zone file. Keep a copy.
- Write down every mail record: MX, SPF (TXT starting with
v=spf1), DKIM (TXT on a selector such asdefault._domainkey), DMARC (_dmarc), and any autodiscover or mail subdomains. - Note your server IP and any other subdomains: staging, cPanel, webmail, FTP, a separate app or shop.
- Take a full backup of files and database.
- Check that your server has a valid SSL certificate. You need it for the Full (strict) mode later. Most hosts issue a free Let's Encrypt or AutoSSL certificate.
- Pick a quiet hour. Nameserver changes usually settle within an hour, but can take up to 24 to 48 hours in rare cases.
03DNS setup and moving your domain to Cloudflare
DNS is the part people skip, and it's where most problems start. Get it right once and Cloudflare is quiet for years.
Add the site and check every imported record
- Create a Cloudflare account, choose Add a domain, and enter the root domain (example.com, not www).
- Cloudflare scans your current DNS and imports what it finds. The scan is a guess, not a copy. Compare it line by line with the zone export you saved and add anything missing, especially DKIM selectors and subdomains.
- Pick a plan. You can start on Free and upgrade later without changing anything else.
- Cloudflare shows two nameservers, such as
ana.ns.cloudflare.com. Replace the current nameservers at your domain registrar with these two. Remove any old ones. - Wait for the email that says the site is active. Until then, nothing has changed for visitors.
Orange cloud or grey cloud: what to proxy
Each A, AAAA and CNAME record has a proxy switch. Proxied (orange cloud) sends traffic through Cloudflare and hides your server IP. DNS only (grey cloud) just answers with your real IP, with no protection or caching. Only A, AAAA and CNAME records can be proxied, and proxied records always use a fixed TTL of 300 seconds.
| Record | Proxy status | Why |
|---|---|---|
A example.com → server IP | Proxied | Your website. This is what Cloudflare protects. |
CNAME www → example.com | Proxied | Same site, same protection. |
MX example.com → mail server | DNS only (always) | Cloudflare can't proxy mail. MX records can't be proxied. |
A mail, webmail, smtp, imap | DNS only | Mail clients connect on ports Cloudflare doesn't proxy, and proxying hides the real mail server. |
A ftp, cpanel, whm | DNS only | FTP and some panel ports don't pass through the proxy. |
A staging | Proxied, with a block or Access rule | Keep staging private, see the security section. |
TXT SPF, DKIM, DMARC, verification | DNS only (always) | TXT records are never proxied. |
CAA | DNS only | Controls which certificate authorities can issue for your domain. |
One catch: every grey cloud record that points to the same server as your website shows the world your server IP. If mail.example.com and your site share an IP, an attacker can skip Cloudflare by hitting that IP directly. That's why the origin lock in section 07 matters, and why sending mail through a separate provider (Google Workspace, Microsoft 365, Zoho) is the cleaner setup.
Email records: SPF, DKIM and DMARC
Cloudflare doesn't touch your email, but moving DNS is the best moment to fix it. Your contact forms, WooCommerce receipts and password resets depend on these records.
- SPF lists the servers allowed to send for your domain. Keep one SPF record only. Two SPF records is an error, not a backup.
- DKIM signs your mail. Copy the exact selector records from your mail or SMTP provider.
- DMARC tells inboxes what to do with mail that fails. Start with a monitoring policy, then tighten it once reports look clean.
example.com. TXT "v=spf1 include:_spf.google.com include:spf.brevo.com ~all"
_dmarc.example.com. TXT "v=DMARC1; p=none; rua=mailto:[email protected]"Swap the include values for your own mail and SMTP providers. Cloudflare also offers a free DMARC Management tool that reads the reports for you.
DNSSEC, CAA and TTL
- DNSSEC signs your DNS answers so nobody can forge them. Turn it on under DNS, Settings, then add the DS record Cloudflare gives you at your registrar. If your domain is registered with Cloudflare, it's one click.
- CAA records say which certificate authorities may issue certificates for your domain. If you add CAA records, include the authorities Cloudflare uses for edge certificates, or certificate renewals can fail. When in doubt, leave CAA empty: Cloudflare's own certificate setup works without it.
- TTL for proxied records is fixed at Auto (300 seconds). For grey cloud records, keep Auto unless you plan a move, then lower it a day before.
Should you move the domain itself to Cloudflare Registrar?
Cloudflare Registrar sells and renews domains at cost, with no markup, and renewals happen at the registry's list price. It's a good home for client domains that keep getting surprise renewal prices elsewhere. Two things to know: the domain must use Cloudflare's nameservers, and ICANN rules block transfers for 60 days after a domain is registered or transferred. Keep the domain where it is if the client wants their registrar separate from their DNS provider.
04SSL/TLS done right: Full (strict), not Flexible
There are two connections to secure: visitor to Cloudflare, and Cloudflare to your server. Cloudflare gives you a free edge certificate for the first. The SSL/TLS encryption mode controls the second.
| Mode | Cloudflare to your server | Use it? |
|---|---|---|
| Off | No encryption | Never |
| Flexible | Plain HTTP | Avoid. WordPress sites forcing HTTPS end up in redirect loops, and the second hop is unencrypted. |
| Full | HTTPS, certificate not checked | Only as a short bridge while you fix the origin certificate. |
| Full (strict) | HTTPS with a valid certificate | Yes. This is the target for every WordPress site. |
| Strict (SSL-only origin pull) | Always HTTPS, validated, whatever the visitor used | Fine for advanced setups. |
Newer zones use Automatic SSL/TLS, where Cloudflare scans your origin and picks the most secure mode it supports. It never downgrades you. If you set the mode by hand, choose Full (strict).
Your origin certificate options
- Keep your host's free certificate (Let's Encrypt or AutoSSL). Works with Full (strict) as long as it renews. Some hosts can't renew through the proxy, so watch the first renewal.
- Install a Cloudflare Origin CA certificate. Create it under SSL/TLS, Origin Server, install it in cPanel or your host panel, and it lasts up to 15 years. Browsers don't trust it directly, but Cloudflare does, which is all that matters behind the proxy.
Edge settings to switch on
- Always Use HTTPS: on. Redirects every http request at the edge.
- Minimum TLS version: 1.2.
- Automatic HTTPS Rewrites: on. Fixes many mixed content warnings from old http links.
- HSTS: turn it on only after HTTPS works on every subdomain you use. Once browsers cache HSTS, you can't go back to http for the max-age you set. Start with a short max-age, then raise it to a year. Leave preload off unless you're sure.
05WordPress security settings on Cloudflare, step by step
This is the part most guides wave at. Here are the exact settings and rules we use, in the order we apply them.
The baseline (all plans)
- Security, WAF, Managed rules: make sure the Cloudflare Free Managed Ruleset is on. On Pro or higher, also turn on the Cloudflare Managed Ruleset and review the OWASP ruleset in log or challenge mode first.
- Security level: leave it at the default. Raise it only during an attack.
- Browser Integrity Check: on.
- Bot Fight Mode: see the warning below before you turn it on.
- Turnstile: replace reCAPTCHA on contact, login and checkout forms. It's free and invisible for most humans. Gravity Forms, WPForms, Contact Form 7 and WooCommerce all have Turnstile add-ons.
Five WAF custom rules for WordPress (fits the Free plan)
The Free plan gives you 5 custom rules, and regex isn't available below Business, so these rules use plain operators. Create them under Security, WAF, Custom rules, using Edit expression. Rules run in order, and a Block stops the rest.
Rule 1: Block XML-RPC. Old remote publishing endpoint, popular for password guessing. Skip this rule if you use Jetpack or the WordPress mobile app, which still need it. Action: Block.
(http.request.uri.path eq "/xmlrpc.php")Rule 2: Challenge the login page. Humans pass in a second, scripts don't. Action: Managed Challenge.
(http.request.uri.path eq "/wp-login.php")Rule 3: Challenge wp-admin, but not the AJAX endpoints. Front end features such as forms, filters and carts call admin-ajax.php and admin-post.php for logged-out visitors, so those must stay open. Replace the example IP with your office IP to skip the challenge for your team. After someone passes the challenge, Cloudflare remembers them for the challenge passage time (30 minutes by default, adjustable under Security settings). Action: Managed Challenge.
(starts_with(http.request.uri.path, "/wp-admin")
and http.request.uri.path ne "/wp-admin/admin-ajax.php"
and http.request.uri.path ne "/wp-admin/admin-post.php"
and not ip.src in {203.0.113.10})Rule 4: Block requests for files nobody should ask for. Config backups, environment files, Git folders, debug logs and PHP files inside uploads. Action: Block.
(http.request.uri.path contains "wp-config")
or (http.request.uri.path contains "/.env")
or (http.request.uri.path contains "/.git")
or (http.request.uri.path contains "debug.log")
or (starts_with(http.request.uri.path, "/wp-content/uploads/") and ends_with(http.request.uri.path, ".php"))Rule 5: Stop user enumeration for logged-out visitors. Bots read usernames from author archives and the REST users endpoint, then try them on the login page. The cookie check keeps the block editor working for logged-in users. Action: Block.
((http.request.uri.query contains "author=")
or starts_with(http.request.uri.path, "/wp-json/wp/v2/users"))
and not http.cookie contains "wordpress_logged_in"After saving, open each rule's events under Security, Events for a day. If a rule catches something legitimate, add an exception instead of deleting the rule.
Rate limit the login page
The Free plan includes one rate limiting rule: counted by IP, with a 10 second window and a 10 second block, and it can match on the URL path. That's enough to slow down a login flood without touching real users. Create it under Security, WAF, Rate limiting rules.
If incoming requests match: (http.request.uri.path eq "/wp-login.php")
Same characteristics: IP
When rate exceeds: 5 requests per 10 seconds
Then: Block for 10 secondsOn Pro and higher, use a longer window, such as 10 requests per minute with a one hour block. Keep Wordfence or your login plugin's lockout on too: Cloudflare slows the flood, WordPress locks the account.
Bot Fight Mode: useful, with one big catch
Bot Fight Mode on the Free plan challenges traffic that looks automated. The catch: you can't skip or bypass it with WAF rules, and Cloudflare warns it may challenge API or app traffic. On a WordPress site that can mean payment webhooks, uptime monitors, backup services or a headless app that suddenly fail. Turn it on for brochure sites and blogs. On stores and sites with integrations, leave it off and use the custom rules above instead, or upgrade to Pro, where Super Bot Fight Mode can be skipped for specific paths.
Under Attack mode
When a site is being flooded, turn on Under Attack mode from the Overview page. Every visitor gets a short check before the page loads. It's a fire extinguisher, not a setting: turn it off once the attack stops, because it also slows down every real visitor and can get in the way of services that call your site.
Put wp-admin behind Cloudflare Access (free)
Cloudflare Zero Trust has a free plan for up to 50 users. With Access, you add a self-hosted application for example.com/wp-admin and example.com/wp-login.php, and only people who pass an email one-time code or your Google login can even see the login page. Everyone else is stopped at the edge. It's the strongest free lock you can put on a WordPress dashboard. Keep /wp-admin/admin-ajax.php and /wp-admin/admin-post.php out of the protected paths, or front end features will break.
A firewall lowers the risk but does not remove it. If a site behind Cloudflare is already compromised, our guide on what to do when a WordPress site is hacked walks through containment, evidence, credential resets and cleanup in order.
06Cloudflare, Wordfence or your host firewall: who does what
People often ask which one they need. The honest answer is that each layer sees something the others can't.
| Threat | Cloudflare (edge) | Security plugin (WordPress) | Host (server) |
|---|---|---|---|
| DDoS and traffic floods | Best place to stop it | Too late, PHP is already running | Only the host network |
| Login brute force | Challenge and rate limit | Lockouts per account, 2FA | Server firewall bans |
| Known plugin exploits | Managed rules (Pro adds more) | Firewall rules tuned for WordPress | Some hosts run their own WAF |
| Malware already in files | Can't see it | Malware scan, file changes | Host malware scanner |
| Vulnerable plugin versions | Can't see it | Vulnerability alerts | Some hosts alert |
| Attacks on the real server IP | Only if the origin is locked | Still runs | Firewall allowlist |
| Backups and recovery | No | Not its job | Daily backups, off server copies |
So: Cloudflare to absorb and filter, a plugin to see inside WordPress, and a host with backups and a firewall for when everything else fails.
07Making WordPress and Cloudflare work together
Show real visitor IPs in WordPress
Behind Cloudflare, your server sees Cloudflare's IPs, not your visitors'. Your security plugin then blocks or logs the wrong addresses. Cloudflare sends the real address in the CF-Connecting-IP header.
- Wordfence: All Options, General Wordfence Options, How does Wordfence get IPs, choose the Cloudflare CF-Connecting-IP option. Check that the preview shows your own IP.
- Server logs: on Apache or LiteSpeed, ask your host to enable remote IP handling for Cloudflare. Many managed hosts do it automatically.
Lock your origin so nobody can skip Cloudflare
If someone finds your server IP (old DNS history, a grey cloud mail record, an email header), they can attack it directly and every Cloudflare rule is skipped. Close that door:
- Authenticated Origin Pulls: available on every plan. Cloudflare presents a client certificate and your server only accepts requests that carry it. Works with Full and Full (strict).
- Allow only Cloudflare IPs on ports 80 and 443 in your server firewall. Cloudflare publishes its ranges at cloudflare.com/ips. On shared hosting, ask support whether they can do this for you.
- If your server IP has been public for years, consider asking your host for a new one after you switch to Cloudflare.
Cache rules that don't break logins, carts or the builder
Cloudflare caches static files (images, CSS, JS) by default and passes HTML through. If you add HTML caching, these must always bypass the cache:
- Anything under
/wp-adminand/wp-login.php. - Requests with cookies that start with
wordpress_logged_in,wp-postpass,comment_author,woocommerce_items_in_cartorwp_woocommerce_session. - Cart, checkout and my account pages on WooCommerce.
- Page builder previews (Divi, Elementor and other builders use query strings such as
et_fb=1andelementor-preview).
APO, LiteSpeed Cache or WP Rocket: pick one page cache at the edge
APO caches your full HTML on Cloudflare's network and needs the official Cloudflare plugin. It costs $5 a month on Free and is included on Pro and Business. If your host already runs a strong server cache (LiteSpeed, NGINX FastCGI) and your visitors are mostly in one region, APO adds less than you'd think. Our rules:
- Use one system for page caching and purges. Two layers that don't purge each other leave visitors with stale pages after every edit.
- Turn off Cloudflare's own minification features and let your WordPress plugin handle it, or the other way around. Never both.
- WP Rocket works with APO from version 3.8.6. For LiteSpeed Cache, test purges carefully, or let LiteSpeed handle HTML at the origin and Cloudflare handle static files.
08Common Cloudflare errors on WordPress and how to fix them
These are the Cloudflare errors we fix most on WordPress sites. Each one has a clear cause.
ERR_TOO_MANY_REDIRECTS after turning Cloudflare on
Why it happens: SSL mode is Flexible. Cloudflare calls your site over http, WordPress redirects to https, and the loop starts.
Fix: Set SSL/TLS to Full (strict) and make sure your origin has a valid certificate. Then clear your browser cookies for the site.
Error 520: web server returned an unknown error
Why it happens: The origin sent an empty or invalid response. Common causes: PHP crashed, a security module reset the connection, or response headers are too large.
Fix: Check the server error log at the time of the error, then the PHP error log. Temporarily disable plugins that add big cookies or headers.
Error 521: web server is down
Why it happens: Cloudflare reached the server, but it refused the connection. The web server is stopped, or a firewall is blocking Cloudflare's IPs.
Fix: Ask your host whether the web server is running and whether anything is blocking Cloudflare IP ranges, including server security tools such as CSF or Imunify.
Error 522: connection timed out
Why it happens: Cloudflare couldn't finish connecting to the origin in time. The DNS record points at the wrong IP, the server is overloaded, or a firewall drops Cloudflare's packets.
Fix: Confirm the A record matches your server IP, check server load, and allowlist Cloudflare IPs at the host.
Error 524: a timeout occurred
Why it happens: The server connected but didn't answer within Cloudflare's 125 second read timeout. Typical on imports, big backups and heavy reports.
Fix: Run long jobs with WP-CLI or a cron, move them to a grey cloud subdomain, or split them into smaller batches.
Error 525 or 526: SSL handshake failed or invalid certificate
Why it happens: Full or Full (strict) is on, but the origin has no certificate on port 443 (525) or the certificate is expired, self-signed or for another domain (526).
Fix: Install a valid certificate at the host or a Cloudflare Origin CA certificate. Use plain Full only as a short bridge.
Divi, Elementor or Gutenberg won't save, or shows a 403
Why it happens: A WAF rule or the managed ruleset sees the builder's large POST request as an attack.
Fix: Open Security, Events, find the blocked request and its rule ID, then add a skip rule for logged-in users on that path instead of turning the WAF off.
Email stopped working after changing nameservers
Why it happens: The Cloudflare scan missed MX, DKIM or mail subdomain records, or a mail record was set to proxied.
Fix: Compare Cloudflare DNS with your saved zone file, add the missing records and set mail subdomains to DNS only.
You locked yourself out with a custom rule
Why it happens: A rule on wp-admin or the login page matches your own traffic.
Fix: Log in to the Cloudflare dashboard (it isn't affected), disable the rule, fix the expression, and add your IP as an exception.
Padlock missing or mixed content warnings
Why it happens: Old http links are saved in the database or theme.
Fix: Turn on Automatic HTTPS Rewrites, then run a database search and replace from http to https with WP-CLI or Better Search Replace.
More server side errors live in our hosting, PHP and cPanel errors guide.
09How we run Cloudflare on finestwebgeek.com
This site runs the same stack we set up for agency clients. Without giving away anything an attacker could use, here's the shape of it:
- DNS on Cloudflare, main records proxied, mail on DNS only with SPF, DKIM and DMARC in place.
- Edge certificate from Cloudflare, HTTPS forced at the edge, HSTS for a year, plus security headers (X-Frame-Options, nosniff, Referrer-Policy, Permissions-Policy).
- Edge rules that block requests for config files, environment files and other sensitive paths before they reach the server.
- Wordfence at the origin with its firewall on and IP detection set to
CF-Connecting-IP, so lockouts hit attackers, not Cloudflare. - LiteSpeed Cache at the origin for HTML, Cloudflare for static files, and one place to purge.
- Turnstile plus a honeypot on the contact and pilot forms, so spam bots are filtered before anyone reads a message.
- A weekly security check that confirms updates, firewall status, exposed files, SSL expiry and backups, and reports anything new.
None of this is exotic. It's a boring, repeatable setup, and boring is exactly what you want from security.
10The agency playbook: Cloudflare for 20 to 200 client sites
One site is a settings page. Fifty sites need a system. Here's ours.
- Who owns the account. The client owns their Cloudflare account and domain. Your agency is added as a member with the role you need. If the relationship ends, you leave cleanly and nothing breaks.
- Scoped API tokens, never the global API key. Create tokens limited to one zone and only the permissions a tool needs, such as cache purge for your caching plugin.
- A standard rule set. The same five custom rules and one rate limit on every site, with notes for exceptions (Jetpack, webhooks, client office IPs). Keep the expressions in your internal docs so anyone on the team can apply them in five minutes.
- An onboarding checklist: zone export saved, records checked, mail tested, Full (strict) on, origin certificate checked, real IP set in the security plugin, rules applied, Turnstile on forms, origin locked.
- Notifications on. Turn on alerts for DDoS attacks, SSL certificate issues and origin errors, and send them to a shared inbox, not one person.
- A monthly review. Check Security, Events for new patterns, review rules that never fire, and confirm the plan still fits the site.
This is part of every white label care plan we run for agencies: Cloudflare setup on day one, then monitoring, updates, backups and fixes under your brand.
11Quick setup checklist
Print this or paste it into your project tool. It's the order we follow on every new site.
- Zone exported, mail records noted, backup taken.
- Domain added to Cloudflare, imported records checked against the export.
- Nameservers changed at the registrar, site shows Active.
- Website records proxied, mail, FTP and panel records on DNS only.
- SPF, DKIM and DMARC checked, test email sent from every form.
- SSL/TLS on Full (strict), valid origin certificate, Always Use HTTPS on, minimum TLS 1.2.
- Managed rules on, the five custom rules added, login rate limit added.
- Turnstile on forms, Bot Fight Mode decided based on integrations.
- Security plugin reads
CF-Connecting-IP. - Origin locked with Authenticated Origin Pulls or a Cloudflare only firewall.
- Cache bypass for admin, logged-in users, carts and builder previews. One page cache, one minifier.
- DNSSEC on, notifications on, HSTS on after a week without issues.
Need the full list? See our WordPress errors fix guide and the hosting, PHP and cPanel errors guide.
Fixes for related errors
12FAQ
Is Cloudflare free plan enough for WordPress security?
For most blogs and brochure sites, yes. The Free plan includes unmetered DDoS protection, a free managed ruleset, 5 custom WAF rules, 1 rate limiting rule, Turnstile and a free edge certificate. Upgrade to Pro when the site takes payments or gets targeted attacks.
Do I still need Wordfence or another security plugin with Cloudflare?
Yes. Cloudflare filters traffic at the edge, but it can't see inside WordPress: malware in files, weak passwords, vulnerable plugins or a compromised admin account. Use both, and set the plugin to read the CF-Connecting-IP header.
Which SSL mode should I use for WordPress on Cloudflare?
Full (strict). It encrypts the connection to your server and checks the certificate. Flexible causes redirect loops on WordPress and leaves the second connection unencrypted.
Will changing nameservers to Cloudflare break my email?
Only if records are missing or set wrong. Export your zone first, check that every MX, SPF, DKIM, DMARC and mail subdomain record is in Cloudflare, and keep mail records on DNS only.
Should I block xmlrpc.php with Cloudflare?
Yes, unless you use Jetpack or the WordPress mobile app, which still rely on it. Blocking it at the edge stops a common password guessing route before it reaches PHP.
Does Cloudflare slow down the WordPress admin or page builders?
No, as long as wp-admin, logged-in users and builder previews bypass the cache. If a builder won't save, find the blocked request in Security, Events and add a skip rule for that path.
Do I need Cloudflare APO if my host uses LiteSpeed?
Usually not at first. LiteSpeed already caches HTML at the server. APO helps most when visitors are spread across continents. Pick one page cache system so purges stay in sync.
How do I fix Cloudflare error 522 on WordPress?
Check that the A record points to your current server IP, that the server isn't overloaded, and that the host's firewall allows Cloudflare's IP ranges.
SOURCES
- Cloudflare Docs: Encryption modes
- Cloudflare Docs: WAF custom rules
- Cloudflare Docs: Rate limiting rules
- Cloudflare Docs: WAF managed rules
- Cloudflare Docs: Bot Fight Mode
- Cloudflare Docs: Proxy status
- Cloudflare Docs: Authenticated Origin Pulls
- Cloudflare Docs: Error 524
- Cloudflare Docs: Automatic Platform Optimization
- Cloudflare: Plans
- Cloudflare Blog: Zero Trust free plan for up to 50 users
- Wordfence Help: Global options (How does Wordfence get IPs)






