O que este plugin pode fazer por você

Automatic Platform Optimization (APO)

Speed up your WordPress site by up to 300% with Cloudflare’s Automatic Platform Optimization (APO) plugin. APO allows Cloudflare to serve your entire WordPress site from our edge network of over 250+ data centers worldwide ensuring fast & reliable performance for your visitors no matter where they are.

Optimizing your WordPress site with multiple plugins can be overwhelming. Take your WordPress site’s performance to the next level by switching to a single plugin for CDN, intelligent caching, and other key WordPress optimizations with Cloudflare (APO). Visit our announcement blog to learn more about APO.

What makes APO different from other caching plugins?

The key differentiating factor between Cloudflare APO and other traditional page caching and CDN solutions is its ability to directly cache static HTML at Cloudflare’s edge. Every other plugin and CDN will cache your static assets (images, javascript, CSS), but none help you cache the actual content on your site (the HTML) using a massive edge network like Cloudflare’s.

APO intelligently caches your HTML pages and will automatically purge content from the cache that you update, so users will always see the latest content without compromising the performance of pages that haven’t been recently updated

What you get with Cloudflare APO

APO is a $5 add-on with Cloudflare’s free plan and comes with an unlimited amount of subdomains. With APO you also get to leverage many of the other benefits of Cloudflare such as Free DNS, Free Automated SSL Certificates, Free DDoS Mitigation, and more. APO is free for all paid plan users so if you have Cloudflare Pro or Business already you can just turn it on. You can compare all our plans here.

Protect your WordPress site with Cloudflare’s Web Application Firewall (WAF)

Cloudflare’s WAF is available on all our paid plans and comes with built-in rulesets, specifically tailored to mitigate WordPress threats and vulnerabilities. These security rules are regularly updated by our team of experts. At the flip of a switch, you’ll have your WAF up and running without any difficult adjustments to your site. With over 26 million internet properties under our protection, you can sleep easy knowing Cloudflare has your back.

Recursos adicionais

  • Reescrita do cabeçalho para evitar um loop de redirecionamento quando o SSL Universal do Cloudflare está ativo

  • Altere as configurações do Cloudflare de dentro do próprio plugin, sem precisar navegar até o painel em Você pode alterar as configurações de eliminação do cache, nível de segurança, Sempre Online e otimização de imagem

  • Ver análises como total de visitantes, largura de banda economizada e ameaças bloqueadas

  • Suporte ao HTTP2/Server Push

Imagens de tela



Make sure your PHP version is 7.2 or higher.

Speed Up Your WordPress Site with Cloudflare APO

Getting Started

Setting up Cloudflare APO

If you’re currently utilizing Cloudflare’s free plan you can add APO to your plan for just $5/month. If you are on Cloudflare’s Pro Plan Cloudflare APO is already included in your subscription. We recommend you start with our APO developer documentation which includes all the information you need to get APO up and running.

How to check if APO is working
Using Uptrends you can verify if Cloudflare APO is working by checking to see if APO response headers are present. You can follow along in this video.

APO Support Resource can be found here

Get Started with Cloudflare SSL here

View our Cloudflare APO blog post here


Preciso de uma conta do Cloudflare para usar o plugin?

Yes, on install and activation of the plugin, first time users will be asked to enter their email address (used to sign-up for an account at and either an API Token or their API key. This is needed to support all the features offered by the plugin.

Quais configurações serão aplicadas quando eu clicar em “Aplicar as configurações padrão” no plugin para WordPress do Cloudflare?

Você pode revisar as configurações recomendadas que são aplicadas aqui.

What do I do if Cloudflare does not detect the WordPress plugin for use with APO (Automatic Platform Optimization)

APO works best when the WordPress plugin is used. We do not recommend using APO without the plugin installed. If you face issues with Cloudflare detecting the plugin then follow these steps:
1. Go to Cloudflare WordPress plugin
2. Disable APO in the card
3. Enable APO in the card (will set proper settings for APO feature)
4. Clear any server cache used via other plugins (WP Rocket being an example)
5. Verify that your origin starts serving response header “cf-edge-cache: cache,platform=wordpress”

You can read more about APO with WordPress here

O plugin funciona se eu tiver o Varnish habilitado?

Sim, o Cloudflare funciona com, e ajuda a acelerar o seu site ainda mais, se tiver o Varnish habilitado.


11 de janeiro de 2023
Simply put, DON'T risk installing this plugin. Even after uninstalling plugin and restoring site via backup, the Cloudflare APO plugin has left its mark. Lots of issues, but main issue is Elementor page editor no longer works. Zero support from Cloudflare. Elementor isn't able to assist.
13 de novembro de 2022
Downloaded the plugin, installed it, retrieved global api from Cloudflare (located in your CF Profile - top right of screen profile > api tokens), then a few configuration choices and bam - working! Works very well and had decreased server load and page load times. If you are experiencing issues check you do not have any plugins installed which are conflicting with the CF APO plugin....disable all and re-enable one at a time to diagnose.
10 de outubro de 2022
Salut CF people, After deep diving into this plugin on complex WP website with custom post types and non-standard URL endpoints, I finally managed it to work correctly. There was some inconsistent issue with stale cache, but upgrade to latest WordPress version magically fixed it, so I guess the stale content bug is somewhere 'in transition' between this plugin and WP core as well as possibly other things such as wp rocket/autoptimize or object cache. After all it works just fine with that stack at the moment. Version 4.11.0 (Cloudflare Pro plan), WP 6.0.2
22 de setembro de 2022
Hi, On the CloudFlare > Speed tab > Automatic Platform Optimization for WordPress section; Written: Note: The WordPress plugin was not detected on I installed official plugin, but Cloudflare can not detected it. Maybe I should write new API. But there is no any API interface on panel of plugin. I deleted the plugin and after I reinstall again, but it not ask API. Probably remember old API, so no ask again. How can I logout account on Wordpress plugin? Automatic Platform Optimization not working.
22 de setembro de 2022
The plugin normally works, but when it doesn't, good luck with getting support from Cloudflare. There are occasional issues with APO (not clearing the cache on post update, caching incorrectly, etc.) in new versions of the plugin. In fact, most new versions of the plugin have had pretty serious bugs (plugin-specific, nothing wrong with the Cloudflare CDN/WAF). Issues are never answered by anyone from Cloudflare. It's a shame because the Cloudflare tech is great, it generally works really well. But the Cloudflare WP Plugin is not up to the standards of the rest of the stack.
18 de agosto de 2022
You need to understand how Cloudflare works, but when configured right, it works great. A few things to note: 1. APO does not play nice with Siteground. 2. It's annoying, but the Cloudflare plugin does not seem to invalidate the cache for all page changes. We are in the habit of manually clearing the cache after updates. A recommendation to the Cloudflare team if you read this: 1. Put an indicator in the top admin bar that shows the last time the cache was cleared for a page, or for the whole site. It is hard to tell if the CF plugin cleared a page. 2. I beg you, please put a button to clear the cache in the top menu bar. I feel rage whenever I go digging into the settings to purge the cache. If the plugin cleared the cache more often after updates, this wouldn't be an issue, but it doesn't, especially with the Oxygen framework.
Leia todas as 157 avaliações

Colaboradores e desenvolvedores

“Cloudflare” é um software com código aberto. As seguintes pessoas contribuíram para este plugin.


Registro de alterações

4.11.0 – 2022-07-27

  • Restrict access to sensitive files using .htaccess configuration.
  • Added cloudflare_use_cache hook to determine when to cache.
  • Allow arrays with url keys to be passed into cache purge requests.
  • Handle getZoneSettings not returning a key and throwing an unset array key error.

4.10.1 – 2022-06-06

  • Fix logic for ignoring cache purge operations.

4.10.0 – 2022-06-03

  • Ignore feed URLs in cache purge operations unless a cache override is in place.

4.9.1 – 2022-05-04

  • Handle empty URL arrays for purging.
  • Swap publicly_queryable for is_post_type_viewable when determining if the post is public.
  • Update always_use_https check to work with the API lacking a “value” for the key.
  • purgeCacheByRelevantURLs now accepts either an array or single ID

4.8.3 – 2022-03-22

  • When a zone has “Always Use HTTPS” enabled, only send HTTPS based URLs. HTTP URLs will never be hit and never present in the cache.

4.8.2 – 2022-03-18

  • Retag 4.8.1 with correct version in user agent

4.8.1 – 2022-03-18

  • Loosen domain check for cache purge calls to allow subdomains

4.8.0 – 2022-03-15

  • Updated supported WordPress version to 5.9
  • Replace Guzzle with wp_remote_request for remote calls
  • Update cache purge logic to improve efficiency of what we send to the remote service

4.7.0 – 2021-10-28

  • Merge cloudflare-plugin-backend into Cloudflare-WordPress repository

4.6.0 – 2021-10-11

  • Make frontend use native await/async
  • Purge cache on mobile if APO Cache By Device Type

4.5.1 – 2021-06-03

  • Rewrite PHP 8 bootstrap files for symfony/polyfill to be PHP 7 compatible

4.5.0 – 2021-06-02

  • Document unintuitive transition_post_status WP hook behavior
  • Only purge public taxonomies while clearing any empty values from the list
  • Better handling of cases where wp_get_attachment_image_src is false and not a usable array
  • Support activation of IDN domains
  • Improve development experience by shipping a Docker Compose file with more tooling and documentation

4.4.0 – 2021-03-23

  • Purge posts when transitioning to or from the ‘published’ state
  • Remove conditional logic for subdomain, allow to activate APO feature on the subdomain
  • Further work to autocorrect APO settings

4.3.0 – 2021-03-19

  • Sanitise sensitive HTTP header logs
  • Stop sending cfCRSFToken to remote API
  • Add warnings for incorrectly configured Automatic Platform Optimization
  • Purge posts that go from public to private
  • Purge pagination for first 3 pages

4.2.2 – 2021-03-08

  • Fix warning for file_get_contents of composer.json

4.2.1 – 2021-03-05

  • Deprecate REST dashboard analytics

4.2.0 – 2021-03-02

  • Allow configuration of Cloudflare credentials via environment variables
  • Prevent purging of cache before comments have been moderated
  • Remove unnecessary symfony/yaml dependency

4.1.0 – 2021-02-11

  • Removed development dependencies from vendor directory
  • Update CLOUDFLARE_MIN_PHP_VERSION to match the plugin requirements

4.0.0 – 2021-02-09

  • Drop support for PHP 5.6, 7.0 and 7.1

3.8.10 – 2021-01-29

  • Add Jacob to maintainers list

3.8.9 – 2021-01-14

  • Revert Add pagination purging

3.8.8 – 2021-01-13

  • Add pagination purging

3.8.7 – 2020-12-07

  • Purge taxonomy feed URLs
  • Fix changing APO settings (cf, wordpress, plugin) when running on subdomain
  • Fix setting hostname override

3.8.6 – 2020-11-19

  • Add subdomain support for APO card

3.8.5 – 2020-10-15

  • Added automatic purge cache on new comment

3.8.4 – 2020-10-13

  • Added composer’s type=wordpress-plugin for Bedrock users
  • Fixed typo in readme.txt
  • Fix modify header exception thrown during wp-cron
  1. Cloudflare Plugin= 3.8.3 – 2020-10-05 =
  • Fixed setting all APO values properly for correct dashboard rendering

3.8.2 – 2020-10-02

  • re-relase broken version, no changes

3.8.1 – 2020-10-02

  • Fixed typo in config.js(on) that resulted in warning #292
  • Check for array indicies are set before using #278

3.8.0 – 2020-10-01

  • Added APO support
  • Renamed Automatic Cache Management card to Auto Purge Content On Update

3.7.0 – 2020-09-25

  • Bump cloudflare-plugin-backend v2.3.0 and cloudflare-plugin-frontend v3.1.0 #283

3.6.0 – 2020-09-17

  • Bump cloudflare-plugin-backend #276

3.5.1 – 2020-07-02


  • Fixed Cache Purges failing #266

3.5.0 – 2020-06-26


  • Disable HTTP/2 Push on wp-admin pages #214
  • Fix PHP 7.4 notice #256


  • Purge attachment URLs #208
  • Purge URLs on page/post update #206
  • Turn on IPv6 by default #229
  • Add constants for better control HTTP/2 Server Push #213
  • Allow custom actions for purge url and purge everything actions #212

3.4.1 – 2019-08-29


  • Updated list of contributors.
  • Updated tested WordPress version to latest (5.2.2).

3.4.0 – 2019-08-29


  • Added support for API Token authentication.

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


  • Mudança na barra administrativa para trás d eliminação automática do cache.

3.1.0 – 2016-11-17


  • Adicionada a capacidade de automaticamente eliminar o cache quando um post é publicado, editado ou excluído. (Graças a brandomeniconi e mike503)
  • Adicionada a capacidade de trabalhar com o plugin WordPress MU Domain Mapping. (Graças a brandomeniconi)


  • Mudança na interface do usuário para se parecer mais como o painel de
  • Descrição do plugin alterada.
  • Desabilitada a exibição na barra administrativa do WordPress e ao editar links de posts para evitar problemas para os usuários usando cache de HTML


  • Corrigido o erro onde a exigência das pastas de fornecedor não estava funcionando.
  • Corrigido um bug onde os arquivos estáticos eram armazenados em cache que causou problemas para atualizar o plugin.
  • Corrigidas as dependências que causaram problemas com o plugin verificador de compatibilidade do PHP.

3.0.6 – 2016-10-6


  • Adicionada a capacidade de alternar para o modo de desenvolvimento.


  • Corrigido o erro onde o seletor de zona ativa não estava funcionando corretamente.


  • Recursos compactados para reduzir o tamanho do plugin.
  • A Logomarca do Cloudflare foi atualizado.

3.0.5 – 2016-09-28


  • Corrigido o erro onde a reescrita do SSL flexível estava impedindo o gancho de página de configurações de carregar.

3.0.4 – 2016-09-27


  • Capacidade para os usuários alternarem reescritas de HTTPS automáticas (habilitado por padrão, resolve a maioria dos dos erros mistos de conteúdo).


  • Corrigido um problema onde a versão PHP baixa estava recebendo um erro de sintaxe.
  • Corrigido o problema onde alguns usuários usando SSL flexível não conseguiam fazer login no wp-admin.
  • Corrigido um bug onde o seletor de zona ativa não paginava em toda a lista de zonas.
  • Corrigido um problema onde a configuração de otimização de imagem estava sendo exibida incorretamente.
  • Corrigido um bug no Analytics onde os dados de visitantes únicos não estava exibindo com precisão.


  • Ativos compactados para reduzir o tamanho do plugin.
  • A lógica de carregamento dos ganchos foi reescrita para torná-lo mais simples e legível.

3.0.3 – 2016-09-21


  • Corrigido um problema onde alguns domínios foram incorretamente propagados para o seletor de domínios
  • Corrigido um problema onde o Web Application Firewall acidentalmente disparava regras de ataque de RFI
  • Corrigido um problema onde otimização de imagem não estava sendo habilitada para planos de Cloudflare Pro e superiores

3.0.2 – 2016-09-16


  • Desabilitado o HTTP/2 Server Push que estava levando a erros de 520 e 502 em alguns sites.

3.0.1 – 2016-09-16


  • Corrigido o HTTP/2 Server Push que estava excedendo o limite de cabeçalho Cloudflare e causava 520 erros.
  • Corrigida a mensagem de alerta no HTTP/2 Server Push.

3.0.0 – 2016-09-15


  • Adicionada a aplicação em um clique das configurações recomendadas específicas do WordPress
  • Adicionado a capacidade de eliminar o cache do Cloudflare
  • Integrado com o gerenciamento de cache do WordPress para automaticamente limpar o cache de Cloudflare ao atualizar a aparência do site
  • Adicionada a capacidade de alterar as configurações do Cloudflare (modo Sempre Online, estou sendo atacado, nível de segurança, otimização de imagem, Web Application Firewall)
  • Adicionada a análise mostrando solicitações armazenadas em cache, largura de banda utilizada, visitantes únicos, ameaças bloqueadas
  • Adicionada a reescrita do cabeçalho para evitar um loop de redirecionamento quando Universal SSL do Cloudflare está ativado
  • Adicionado suporte a HTTP/2 Server Push
  • Adicionado o suporte ao PHP 5.3+


  • Removida a reescrita do protocolo HTTPS
  • Removido o envio de comentários de spam
  • Removida a capacidade para alternar o modo de desenvolvimento


  • A interface do usuário foi atualizada
  • Começou a oferecer suporte ao WordPress 3.4+ em vez de 2.8+ porque dependemos da API de opções do WordPress