The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Cloudflare Automatic Platform Optimization (APO) is worth $5 per month when your WordPress site serves lots of anonymous HTML pages from a slow or distant host. It places cacheable WordPress responses at Cloudflare’s edge, reducing trips to your origin server. It is a weaker investment for logged-in, personalized, checkout-heavy, or already well-cached sites. Set it up through Cloudflare’s WordPress plugin, then confirm the response headers and measure your own site before deciding.
Antihost offers managed WordPress hosting with free migration, one-click staging and a 14-day free trial.
What Cloudflare APO does for WordPress
APO is a hosted edge-cache service, not a page builder, hosting plan, or WordPress theme. Cloudflare stores eligible WordPress HTML at edge locations and serves it close to visitors. The result is fewer requests to your web host and more consistent time to first byte, especially when visitors are geographically far from the origin.
As an Amazon Associate I earn from qualifying purchases.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Repair Windows errors before they cause bigger problems3Scan for outdated or missing drivers - takes under a minuteCloudflare describes APO as serving an entire WordPress site from its edge network by intelligently caching dynamic content. In practice, “entire site” means the public, cacheable experience: static assets and anonymous HTML can be delivered from the edge, while requests that must be personalized or changed in real time are sent to the origin.
What happens when a visitor requests a page
- A visitor requests a WordPress URL through your Cloudflare-proxied DNS record.
- Cloudflare checks whether an eligible HTML response is already stored at the nearest edge location.
- On a cache hit, the edge returns the page without contacting your WordPress host.
- On a miss, Cloudflare fetches the page from the origin, stores it when the response is cacheable, and returns it to the visitor.
- When WordPress content changes, the plugin can notify Cloudflare so affected edge content is purged or refreshed instead of waiting for an arbitrary cache lifetime.
Logged-in users and administrators are normally bypassed so they see their personalized WordPress session. That bypass is essential for security: a cached response containing a user name, account data, cart, or dashboard content must never be served to another visitor.
#1 Best Overall
APO requirements and limitations
| Requirement or behavior | What it means for you |
|---|---|
| Cloudflare DNS | Your domain must use Cloudflare DNS, with the relevant records proxied through Cloudflare. Moving the domain’s nameservers is part of the initial setup. |
| WordPress plugin | The Cloudflare WordPress plugin authenticates the site, applies recommended settings, signals WordPress cacheability, and helps purge edge content after edits. |
| Free plan | APO costs $5 per month on Cloudflare’s Free plan. Cloudflare’s activation guidance says Free-plan users must purchase APO before installing or activating it. |
| Paid plans | Cloudflare documents APO as included with paid plans such as Pro and Business; a Cloudflare launch announcement also names Enterprise. Confirm the current terms for your account before budgeting. |
| Multisite | The APO plugin does not support WordPress multisite. Treat this as a hard limitation unless Cloudflare later changes its documentation. |
| Existing cache plugins | Cloudflare recommends disabling WP Rocket, W3 Total Cache, or similar cache plugins during initial APO setup. Two HTML-cache layers can otherwise conflict or make results difficult to interpret. |
| Subdomains and subdirectories | For these arrangements, Cloudflare documents plugin version 4.4.0 or later. Non-WordPress paths should send cf-edge-cache: no-cache rather than being treated as WordPress HTML. |
Prepare the site before enabling APO
Check DNS and proxy status
Confirm that the domain visitors use resolves through Cloudflare and that the web records serving WordPress are proxied. If the record is DNS-only, the request will go directly to the host and APO cannot serve that response from Cloudflare’s edge. Keep a note of the current DNS values and host IP so you can recover quickly if a nameserver change exposes a mistake.
Inventory pages that must never be cached
List login, administration, account, checkout, cart, membership, preview, and other personalized URLs. Also note plugins that set cookies or return user-specific HTML. APO’s logged-in and administrator bypasses protect the normal WordPress workflow, but custom application endpoints still need testing. A page that changes for every visitor is a poor candidate for full-page edge caching.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallCrashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minutePlan the cache-plugin transition
Record your current page-cache, minification, preload, and purge settings. Disable the existing HTML cache plugin while installing APO, as Cloudflare recommends. You can test a carefully configured combination later, but begin with one system responsible for HTML caching so a failure has one obvious cause.
How to set up Cloudflare APO step by step
1. Move the domain to Cloudflare DNS
- Add the domain to Cloudflare and review the DNS records Cloudflare detects.
- Recreate any missing records, including the record for the WordPress origin and mail-related records.
- At your registrar, replace the existing nameservers with the two Cloudflare nameservers assigned to the zone.
- Wait for Cloudflare to report the zone as active, then verify that the public site still resolves to the intended host through the proxied record.
Do not delete the old DNS zone until mail, staging hosts, verification records, and the production site have all been checked. APO depends on the active Cloudflare zone, not merely on having a Cloudflare account.
2. Install and activate the Cloudflare WordPress plugin
- In WordPress, open Plugins > Add New.
- Search for the official Cloudflare plugin, install it, and activate it.
- Open the plugin’s Cloudflare settings and start its account connection flow.
On a Free plan, purchase APO before attempting to activate the feature. A paid plan may already include APO, but the plugin still needs to be connected to the correct Cloudflare account and zone.
3. Create the WordPress API token
- Open your Cloudflare account’s API-token management screen.
- Choose the WordPress API-token template rather than creating a broadly privileged global key.
- Create the token and copy it immediately; password-manager storage is preferable because tokens should not be pasted into tickets or public notes.
The template gives the plugin the permissions it needs without making a reusable account-wide secret unnecessarily powerful. If the token is lost, revoke it and create a replacement rather than weakening the zone’s security.
4. Connect the plugin and apply recommended settings
- Paste the token into the Cloudflare plugin’s connection field.
- Select the correct Cloudflare zone when prompted.
- Apply the plugin’s recommended settings.
- Confirm that the plugin reports a successful connection and can perform a test purge.
Applying the recommendations lets the plugin add the cache signaling and purge integration APO expects. Keep a copy of any custom Cloudflare rules before accepting changes, especially if the site has security rules for an API, membership area, or staging host.
5. Turn on Automatic Platform Optimization
Enable Automatic Platform Optimization in the Cloudflare plugin or the associated Cloudflare zone control, depending on the interface presented for your account. The control should show that APO is active for the connected WordPress site. If the option is missing, check that the zone is active, the plan has APO access, and the token belongs to the same account and zone.
6. Purge old HTML and test in a private window
Run a purge after activation so an older origin response is not mistaken for the new configuration. Open the home page and several representative posts in a logged-out private browser window. Then log in to WordPress and confirm that the dashboard, previews, and personalized controls still work normally.
7. Re-enable other performance features selectively
Leave competing full-page cache plugins disabled while you establish a baseline. Asset minification, image optimization, and browser-cache features may be tested separately, but avoid enabling a second HTML edge or page-cache layer until you can identify which system owns each purge and cache rule.
Rank #3
How to verify that APO is caching pages
Do not rely on a faster-feeling browser tab. Inspect the response headers from a logged-out request. The most useful signals are:
| Header | How to interpret it |
|---|---|
cf-cache-status |
Shows Cloudflare’s cache result, such as a hit or miss. A first request can be a miss while a later request becomes a hit. |
cf-apo-via |
Indicates that the response passed through APO-related processing. |
cf-edge-cache: cache,platform=wordpress |
Signals that Cloudflare is treating the response as WordPress edge-cache content. |
cf-edge-cache: no-cache |
Expected for documented non-WordPress paths or responses that should not be cached. |
Browser method
- Open an incognito or private window while logged out of WordPress.
- Open a public page twice, waiting briefly between requests.
- Open developer tools, select the Network panel, reload the page, and inspect the document request’s response headers.
- Repeat with a post, a category or archive page, and a URL that should bypass caching.
Command-line method
From a terminal, request the page headers twice:
curl -I https://example.com/Replace the example hostname with your own domain. Compare the two responses for cf-cache-status, cf-apo-via, and cf-edge-cache. A miss followed by a hit is normal when the first request populates an empty edge cache. If every public request remains a miss, investigate cookies, cache-control headers, Cloudflare rules, origin redirects, or a plugin that marks the response private.
Measure the change, not just the header
Record a before-and-after sample from the same test locations. Use the same URLs, protocol, device class, and logged-out state. Compare time to first byte, total load time, and origin response time over several runs rather than one refresh. Cloudflare explains the mechanism but does not promise a universal percentage improvement; your host distance, page size, traffic pattern, and cacheability determine the result.
How APO handles edits, logins, and dynamic content
Publishing and updating content
The plugin can tell Cloudflare when WordPress changes are made, allowing affected edge content to be purged or refreshed. Test this with a low-risk post: publish an unmistakable title change, load the page in a logged-out window, and verify that the new title appears without waiting for a long cache expiration. Also test edits to the home page and an archive, because one content change can affect several URLs.
Logged-in and administrator traffic
Cloudflare documents bypassing cache for logged-in or administrator users. Keep your editorial workflow logged in while editing, and test the public view separately in a private window. If a custom membership plugin does not use standard WordPress login cookies, verify its account pages explicitly; APO’s normal bypass cannot infer every application’s private state.
Cookies, carts, and transactions
Shopping carts, payment steps, account pages, and dashboards should remain dynamic. Ensure those URLs and any API endpoints are excluded from caching according to the application’s requirements. A site can use APO for public guides while sending transactional paths to the origin; the goal is selective edge delivery, not forcing every response into one cache policy.
Using APO with WP Rocket or another cache plugin
Cloudflare recommends disabling WP Rocket, W3 Total Cache, or similar cache plugins during initial setup. This avoids two systems generating different HTML, purging on different schedules, or adding conflicting cache headers. Establish APO alone first, verify headers and content freshness, and then decide whether an additional plugin is needed for features APO does not provide.
When a second plugin may be reasonable
- You need local page generation or a disk cache for requests that must remain at the origin.
- You need asset optimization features that are independent of HTML caching.
- You can define one authoritative purge path and test logged-in, cookie-bearing, and preview requests.
Signs of an overlap problem
- A published edit appears for administrators but not for logged-out visitors after a purge.
- The response alternates between different cache headers on identical requests.
- One plugin purges its local cache while Cloudflare continues serving an older edge copy.
- Users receive a page with another user’s cookie-dependent content.
If any of these occurs, disable the second HTML-cache layer, purge Cloudflare, and retest before changing more settings.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
APO and WordPress multisite
The APO plugin explicitly does not support WordPress multisite. That includes networks where several sites share one WordPress installation. Do not assume that separate domains, subdomains, or mapped domains remove the limitation: the unsupported part is the multisite plugin integration and its cache-purge/authentication behavior.
A single-site WordPress installation using subdomains or subdirectories is a different case. Cloudflare documents support with plugin version 4.4.0 or later, while non-WordPress paths should return cf-edge-cache: no-cache. Check each hostname and path independently; a working main site does not prove that a media, API, or application subdomain is configured correctly.
Best Value
- Offer contains ONLY 2 titles regardless of the order quantity placed for this listing. Set of volumes may vary. Ordering in multiples will not change the volume received. Image is meant to display the type of book you will be receiving only.
- BRAIN TEASING. Perfect Puzzle Book for all ages to learn. Enjoy puzzles, maze, word search, or crosswords! This puzzle book is ideal for people on the go and will provide hours of entertainment.
- FUN & CHALLENGING. Exercise your brains long-term memory, working memory, executive functioning, attention to detail, multitasking, and processing speed. Perfect gifting item for those who love word search puzzles!
- RELAX, RECHARGE, & REFOCUS. The word find puzzle book offers an enjoyable challenge for all, from beginners to experts. Ideal for learning, practicing, and having fun time for various users.
- OFFICIALLY LICENSED. High-resolution printing. Perfect for family activities, classroom learning, or travel. Provide an engaging, educational experience with every page, making it both fun and meaningful.
Is the $5-per-month APO charge worth it?
The Free-plan price documented by Cloudflare is $5 per month. Treat that as a recurring service cost, not a one-time activation fee. APO is documented as included on some paid Cloudflare plans, including Pro and Business, and Cloudflare’s launch announcement names Enterprise; current plan terms can change, so compare the cost of upgrading with the standalone $5 charge for your account.
| Site situation | Likely value from APO | Why |
|---|---|---|
| Public blog or documentation site with many anonymous readers and a slow or distant host | High | Many HTML requests can be answered at the edge, reducing origin round trips and smoothing first-byte time. |
| Small brochure site with a nearby, fast host and light traffic | Medium to low | The origin may already be quick, so the measurable improvement can be smaller than the monthly fee. |
| Membership, community, or dashboard-heavy site | Low to medium | Logged-in and personalized requests bypass the cache; only the public portion benefits. |
| Online store or transaction-heavy application | Mixed | Public content may cache, but carts, accounts, and checkout remain dynamic and require careful exclusions. |
| WordPress multisite network | Not supported by the APO plugin | The documented plugin limitation is a blocker, regardless of potential performance gains. |
| Site with an already effective edge HTML cache | Low | APO may duplicate an existing capability while adding another purge and compatibility layer. |
A practical break-even test
- Capture a baseline for at least several representative URLs while logged out. Record origin response time and user-facing load metrics from the regions that matter to your audience.
- Enable APO without changing hosting, theme, image sizes, or other performance variables.
- Repeat the same measurements after the cache is warm and after a normal publishing cycle.
- Check freshness: publish an edit, purge or allow the plugin’s update signal to run, and measure how quickly public requests show the change.
- Compare the observed benefit with $5 per month on the Free plan, or with the incremental cost of the paid plan that includes APO.
Keep APO when it produces a meaningful improvement for your visitors or reduces origin load enough to avoid a hosting upgrade. Skip it when most requests bypass cache, the origin is already fast for your audience, or the operational complexity exceeds the measured gain.
Troubleshooting common APO problems
The APO switch is missing
- Confirm that the Cloudflare zone is active and the domain uses Cloudflare nameservers.
- Check that the Free plan has purchased APO or that the paid plan currently includes it.
- Reconnect the plugin with a token created from the WordPress API-token template.
- Make sure the token and selected zone belong to the same Cloudflare account.
Headers never show an APO cache response
- Test while logged out in a private window; logged-in cookies are intentionally bypassed.
- Inspect whether a cache plugin, security rule, origin header, or cookie marks the response private.
- Verify that the request is reaching the proxied Cloudflare record rather than a DNS-only record.
- Check that the URL is a WordPress path and not a documented non-WordPress path returning
cf-edge-cache: no-cache. - Purge once, request the page again, and compare the first and second responses.
Edits are stale for public visitors
- Confirm that the Cloudflare plugin remains active and authenticated.
- Run a manual purge, then test the public URL in a private window.
- Temporarily disable any second HTML-cache plugin and repeat the edit test.
- Check whether the edited content is assembled by a separate API or JavaScript request that has its own cache policy.
The site breaks after activation
- Disable APO in the plugin or Cloudflare control.
- Purge Cloudflare’s cache.
- Confirm that logged-in administration, previews, forms, carts, and account pages work directly from the origin.
- Re-enable APO only after identifying the URL, cookie, rule, or plugin causing the conflict.
When to choose a different architecture
APO is not the only way to deliver WordPress quickly. A managed WordPress host may provide origin-side page caching and support tailored to your installation. Another CDN with edge HTML caching may suit a site that cannot use the APO plugin, provided it supports your required purge behavior, cookie bypasses, DNS arrangement, and multisite architecture.
Compare alternatives on the capabilities that affect your site rather than on bandwidth alone:
Quick Recap
- Can it cache full HTML at edge locations, not just images, scripts, and stylesheets?
- How quickly does a WordPress edit purge or revalidate related pages?
- How are logged-in users, cookies, carts, and personalized responses bypassed?
- Will it coexist with your existing cache plugin, or should that plugin be removed?
- Does it support multisite, subdomains, and subdirectory installations?
- What DNS or nameserver changes are required?
- Which headers, logs, or dashboards let you prove that caching is active?
- What is the complete recurring monthly cost for your plan and traffic level?
Operational checklist after launch
- Verify public pages with
cf-cache-status,cf-apo-via, andcf-edge-cache: cache,platform=wordpress. - Verify that non-WordPress paths use
cf-edge-cache: no-cachewhere required. - Test an edit, an archive page, a logged-in dashboard, a preview, and every transaction flow.
- Monitor origin load and response time before and after traffic peaks.
- Keep the API token private and revoke it if it is exposed.
- Retest after changing themes, membership plugins, checkout software, DNS records, or cache rules.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
