The Cloudflare add-on connects a WordPress site to a Cloudflare account. It lets administrators manage selected Cloudflare options and view analytics from WordPress. Access to services such as Automatic Platform Optimization (APO) and the Web Application Firewall (WAF) depends on the account plan.

APO caches HTML at the edge

APO caches static HTML pages across Cloudflare’s edge network, described as having more than 250 data centers worldwide. It adds page content caching to delivery of static assets such as images, JavaScript, and CSS. When content is updated, APO automatically purges that content from cache while unchanged pages can remain cached. Cloudflare says APO can speed up a WordPress website by up to 300%.

APO is included with Cloudflare Pro and Business. On the free plan, it is a $5 per month add-on with unlimited subdomains. APO also delivers access to Cloudflare benefits such as free DNS, automated SSL certificates, and DDoS mitigation.

Plan access and security

The WAF is available on paid plans and includes rulesets tailored to WordPress threats and vulnerabilities. Cloudflare regularly updates these rules, and the WAF can be enabled without difficult site adjustments. The add-on also includes a header rewrite intended to prevent a redirect loop when Universal SSL is enabled.

Controls and analytics in WordPress

From the plugin, administrators can manage cache purges, security level, Always Online, and image optimization. Its analytics display total visitors, bandwidth saved, and threats blocked. The plugin also lists support for HTTP/2 and Server Push.

Connect the account and check APO

Before setup, make sure the site runs PHP 7.4 or higher and that you have a Cloudflare account. Install and activate the plugin in WordPress. On first use, connect the account with its sign-up email address and either an API Token or API key. Then configure the available settings and enable the plan capabilities you need.

If Cloudflare does not detect the WordPress plugin for APO, use this sequence:

1. In the plugin’s APO card, disable APO.
2. Enable APO again from the card to apply the appropriate settings.
3. Clear any server cache used by other extensions.
4. Verify that the origin serves the response header cf-edge-cache: cache,platform=wordpress.