Questo plugin non è stato testato con le ultime 3 versioni principali (major releases) di WordPress. Potrebbe non essere più mantenuto, o supportato, e potrebbe presentare problemi di compatibilità se utilizzato con versioni più recenti di WordPress.



What this plugin can do for you

One-click WordPress-optimized settings

The easiest way to setup Cloudflare for your WordPress site.

Web application firewall (WAF) rulesets

Available on all of Cloudflare’s paid plans, the WAF has built-in rulesets, including rules that mitigate WordPress specific threats and vulnerabilities. These security rules are always kept up-to-date, once the WAF is enabled, you can rest easy knowing your site is protected from even the latest threats.

Automatic cache purge

Occurs when you change the appearance of your website. This means that you can focus on your website, while we ensure that the latest content is always available to your visitors.
(Note: By default, Cloudflare does not cache HTML, and a cache purge is not required on updating HTML content such as publishing a new blog entry).

Additional features

  • Header rewrite to prevent a redirect loop when Cloudflare’s Universal SSL is enabled

  • Change Cloudflare settings from within the plugin itself without needing to navigate to the dashboard. You can change settings for cache purge, security level, Always Online, and image optimization

  • View analytics such as total visitors, bandwidth saved, and threats blocked

  • Support for HTTP2/Server Push

Screenshot (schermate di esempio)

  • Cloudflare Plugin



Make sure your PHP version is 5.3.10 or higher.

From your WordPress Dashboard

  1. Visit “Plugins” → Add New
  2. Search for Cloudflare
  3. Activate Cloudflare from your Plugins page.


  1. Download Cloudflare
  2. Upload the “cloudflare” directory to your “/wp-content/plugins/” directory, using ftp, sftp, scp etc.
  3. Activate Cloudflare from your Plugins page.

Once Activated

  1. Go to
  2. Login with your cloudflare account. (If you don’t have a Cloudflare account first sign up for Cloudflare)
  3. Press your account name on top right corner and select “My Settings”
  4. Scorri verso il basso fino a “API Key” > “Global API Key” > Vedi API Key
  5. Copia la API key
  6. Torna indietro alla pagina del Plugin Cloudflare di WordPress
  7. Inserisci il tuo indirizzo mail e incolla la tua API key
  8. Premi Login.


Mi serve un account Cloudflare per usare questo plugin?

Si, dopo l’installazione e attivazione del plugin, la prima volta agli utenti verrà chiesto di inserire il loro indirizzo mail (usato per il registrare un account su e la loro API key dell’utente. Questo per ottenere tutte le caratteristiche offerte dal plugin.

Che impostazioni sono applicate quando clicco su “Applica impostazioni di default” nel plugin Cloudflare di WordPress?

Puoi recensire le configurazioni raccomandate che sono state applicate qui.

Il plugin funziona se io ho Varnish abilitato?

Si, Cloudflare funziona con, e aiuta a velocizzare il tuo sito ancora di più, se hai Varnish abilitato.


Simple and Useful

Thanks CloudFlare for the services. This plugin is useful, especially when updating content to WordPress blog, it does purge cache automatically so I don't need to go to CloudFlare dashboard. For initial setting, I'd recommend to go to CloudFlare dashboard, keep the plugin as simple as this.

Love Cloudflare

We love Cloudflare and always recommend it's services. It's a shame this plugin doesn't have an option for Server Push in it, that has to be enabled via wp-config, otherwise I'd have gladly given it 5 stars.

It has basically no features

Purging cache on website change is ok, so 2 stars, but I'm not going to keep it only for this. I can change everything on Cloudflare website. I will be honest, I downloaded this plugin ONLY for HTTP2 server push. And I am completely disappointed. I had to google how to set it up, because it is not an option in this plugin, nor it is even mentioned. So I entered this magic line in wp-config.php file. I even managed to see initiator server push in Chrome dev tools for some files sometimes, but usually index.php is an initiator even if I purge cache and speed testing tools don't see any difference. I don't know what files / types of files are supposed to be pushed as a rule. HTTP2 is out since a long time and server push support in this plugin is in some ice age of development. Also when plugin is installed, you get this infinite processing wheel, I though I need to wait because something is being processed, but no, 15 minutes later the same. Simply needed to click any menu icon, because this processing indicator is broken. Not too important, but pretty much sums up quality of this plugin.

Works fine

I install this plugin just so the Cloudflare cache will get purged automatically when anyone makes a content change. Seems to work fine on WP 5.x and PHP 7.2. We have it running on many sites.
Leggi tutte le recensioni di 111

Crediti e riconoscimenti

“Cloudflare” è un software open source. Le persone che hanno contribuito allo sviluppo di questo plugin sono indicate di seguito.


Traduci “Cloudflare” nella tua lingua.

Ti interessa lo sviluppo?

Esplora il Codice segui il Repository SVN iscriviti al Log delle Modifiche. Puoi farlo tramite RSS con un lettore di feed.

Changelog (registro delle modifiche)

3.3.3 – 2019-3-6


  • Bug in Hooks.php causing errors in PHP 7+
  • Bug preventing Autoptimize plugin’s optimized asset urls from being used when present and when Cloudflare HTTP/2 Push was enabled

3.3.2 – 2017-12-12


  • Bug in cf-ip-rewrite


  • Added a new filter cloudflare_purge_by_url allowing users to have better control on automatically purged urls.

3.3.1 – 2017-6-29


  • Potential bug by using $_GET.

3.3.0 – 2017-6-29


  • Added a new Splash Screen
  • Added userConfig.js file allowing custom configurations.
  • Added logs in debug mode for Automatic Cache Purge.
  • Added logs for oversized Server Push HTTP headers.


  • Automatic Cache Purge now purges Autoptimize by everything rather than by URL.
  • Updated IP Ranges


  • Bug where domains which had capital letters not working.
  • Bug where Automatic Cache Purge couldn’t purge front page.
  • Bug related to work with IWP.
  • Bug where if PHP is compiled with ipv6-disable flag, it crashed the site.

3.2.1 – 2017-3-14


  • Bug where accounts which had more than 20 zones would not show up correctly.

3.2.0 – 2017-3-1


  • Bypass Cache By Cookie functionality.
  • HTTP/2 Server Push functionality (disabled by default).


  • Lowered the plugin size.
  • Automatic Cache Management feature includes purging taxonomies.
  • Automatic Cache Management feature supports sites which use both HTTP and HTTPS.


  • Admin bar disappearing from the plugin.
  • Bug where spinner was loading forever.
  • Bug where the backend errors where not being shown in the frontend.
  • Issues where IE11 was not working properly.

3.1.1 – 2016-11-17


  • Moved Admin Bar behind Automatic Cache Purge toggle.

3.1.0 – 2016-11-17


  • Added ability to automatically purge cache when a post is published, edited or deleted. (Thanks to brandomeniconi and mike503)
  • Added ability to work with WordPress MU Domain Mapping plugin. (Thanks to brandomeniconi)


  • Changed the UI to look more like dashboard.
  • Changed plugin description.
  • Disabled showing WordPress Admin Bar and Edit Post Link to avoid caching problems for users using HTML Caching.


  • Fixed bug where require vendor folders was not working.
  • Fixed bug where static files were cached which caused issues updating the plugin.
  • Fixed dependencies which caused issues with PHP Compatibility Checker plugin.

3.0.6 – 2016-10-6


  • Added ability to toggle Development Mode.


  • Fixed bug where active zone dropdown was not working properly.


  • Compressed resources to lower plugin size.
  • Updated Cloudflare logo.

3.0.5 – 2016-09-28


  • Fixed bug where refactored Flexible SSL fix was causing the settings page hook not to load.

3.0.4 – 2016-09-27


  • Ability for users to toggle Automatic HTTPS Rewrites (enabled by default, solves for most mixed content errors).


  • Fixed an issue where low PHP version where getting syntax error.
  • Fixed issue where some users using Flexible SSL where not able to login to wp-admin .
  • Fixed a bug where the active zone selector was not paginating through the whole zone list.
  • Fixed an issue where the setting for Image Optimization was being displayed incorrectly.
  • Fixed a bug in Analytics where the  Uniques Visitors data was not displaying accurately.


  • Compressed assets to lower plugin size.
  • Hooks loading logic refactored to make it more simple and readable.

3.0.3 – 2016-09-21


  • Fixed an issue where some domains were being incorrectly propagated to the domain selector dropdown
  • Fixed an issue where the Web Application Firewall was accidentally triggering RFI Attack Rules
  • Fixed an issue where image optimization was not being enabled for Pro and higher Cloudflare plans

3.0.2 – 2016-09-16


  • Disabled HTTP/2 Server Push which was leading to 520 and 502 errors for some websites.

3.0.1 – 2016-09-16


  • Fixed HTTP/2 Server Push exceeding the header limit Cloudflare has which caused 520 errors.
  • Fixed warning message in HTTP/2 Server Push.

3.0.0 – 2016-09-15


  • Added one-click application oft WordPress specific recommended settings
  • Added ability to purge the Cloudflare cache
  • Integrated with WordPress cache management to automatically clear the Cloudflare cache on updating site appearance
  • Added ability to change Cloudflare settings (Always Online mode, I’m Under Attack, Image Optimization, Security Level, Web Application Firewall)
  • Added Analytics showing Cached Requests, bandwidth used, unique visitors, threats blocked
  • Added Header rewrite to prevent a redirect loop when Cloudflare’s Universal SSL is enabled
  • Added HTTP/2 Server Push support
  • Added Support for PHP 5.3+


  • Removed HTTPS Protocol Rewriting
  • Removed submission of spam comments
  • Removed ability to toggle Development Mode On/Off


  • Updated user interface
  • Started to support WordPress 3.4+ instead of 2.8+ because we depend on the WordPress Options API