Free tools Windows power users keep installed
One-click scans. No signup required.
iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Antihost offers managed WordPress hosting with free migration, one-click staging and a 14-day free trial.
Cloudflare Automatic Platform Optimization (APO) is an edge-caching service for WordPress. It stores eligible HTML pages on Cloudflare’s network, so many visitors receive pages from a nearby edge location instead of waiting for your origin server. The Cloudflare WordPress plugin handles authentication, cache signaling, and purging when you publish changes.
On Cloudflare’s Free plan, APO is documented at $5 per month in 2026. It is most compelling for sites with slow or geographically distant hosting and many anonymous visitors. It is less compelling for highly personalized, logged-in, transactional, multisite, or already well-optimized sites. Measure your own site before and after enabling it; Cloudflare does not promise one universal percentage improvement.
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 minute
What Cloudflare APO changes on a WordPress site
A normal WordPress page request usually travels to the origin host, where PHP, the database, and WordPress generate HTML. A CDN can accelerate static files such as images, CSS, and JavaScript, but HTML often remains dynamic and continues to involve the origin.
APO extends edge caching to the WordPress HTML layer. Cloudflare describes it as serving an entire WordPress site from its edge network and reducing origin round trips. A visitor requesting a cacheable page can therefore receive an already generated response from an edge location. The practical result is usually more consistent time to first byte when the origin is slow, overloaded, or far from the visitor.
#1 Best Overall
The plugin is part of the system
APO is not a page builder, WordPress theme, hosting server, or local page-cache plugin. Its WordPress plugin supplies the integration Cloudflare needs to recognize WordPress requests, bypass cache for logged-in and administrator users, and purge edge content when WordPress changes are made through the dashboard. Removing or misconfiguring the plugin can leave stale pages or incorrect cache behavior.
What visitors can and cannot receive from cache
- Anonymous visitors requesting public pages are the primary APO use case.
- Logged-in and administrator sessions are bypassed so private or personalized content is not served from a public cache.
- Cart, checkout, account, membership, and other cookie-dependent responses may be bypassed or require explicit exclusions in your application.
- Publishing or editing content through WordPress can trigger edge purging through the plugin, reducing the time that old HTML remains available.
Those rules mean APO improves delivery of cacheable HTML; it does not make every request cacheable and does not remove the need to configure dynamic features safely.
Check these requirements before you start
Your DNS must be on Cloudflare
The domain must use Cloudflare DNS, which requires changing the domain’s authoritative nameservers at the registrar to the nameservers Cloudflare assigns. Merely pointing an individual record at a Cloudflare address is not the same as moving the zone to Cloudflare. Confirm that all required records, including mail and verification records, are present before changing nameservers.
Choose the correct plan and purchase state
Cloudflare documents APO at $5 per month for a Free-plan zone in 2026. APO is documented as included with paid Cloudflare plans such as Pro and Business; Cloudflare’s launch announcement also named Enterprise. Plan entitlements and billing terms can change, so check the current plan screen for your zone. Free-plan users are instructed to purchase APO before installing or activating it.
Account access and a token
You need permission to manage the Cloudflare zone and to create the WordPress API-token template token. Do not paste your global API key into the plugin. A scoped token limits the integration to the permissions Cloudflare specifies for APO.
Audit existing caching layers
List every layer that might cache HTML: a WordPress plugin, host-level page cache, reverse proxy, CDN, or security service. Cloudflare’s activation guidance recommends disabling WP Rocket, W3 Total Cache, or similar cache plugins during initial setup. You can reintroduce another cache layer later only after testing purge behavior and headers; two systems making different cache decisions are a common source of stale pages and confusing results.
Confirm whether you are running multisite
The Cloudflare APO plugin does not support WordPress multisite. A single-site installation can use the documented integration, but a network installation should not be treated as supported simply because one mapped domain appears to work. If multisite is essential, plan for a different edge-HTML strategy and test each site independently.
How to set up Cloudflare APO step by step
1. Put the domain on Cloudflare DNS
- Add the domain to your Cloudflare account and let Cloudflare scan existing DNS records.
- Compare the imported records with the authoritative records at your current DNS provider. Pay particular attention to MX, SPF, DKIM, DMARC, verification, API, and staging records.
- At your registrar, replace the old authoritative nameservers with the two Cloudflare nameservers assigned to the zone.
- Wait for the registrar and DNS changes to propagate. In Cloudflare, confirm the zone status is active before proceeding.
Do not delete the old DNS zone until mail, redirects, subdomains, and third-party integrations have been checked from outside your network.
2. Purchase APO when the zone is on the Free plan
If the zone uses Cloudflare Free, open the zone’s performance or APO settings, purchase the $5-per-month APO service, and confirm that the subscription is active. This purchase step comes before installing or activating the APO integration according to Cloudflare’s activation guidance. For a paid plan that includes APO, verify that the feature is shown as included rather than starting a second subscription.
3. Install the Cloudflare WordPress plugin
- In WordPress, open Plugins > Add New.
- Search for the official Cloudflare plugin, install it, and activate it. On a Free-plan zone, complete the APO purchase first.
- Open the plugin’s Cloudflare settings page and select the option to connect the site to your Cloudflare account.
Use the plugin on the canonical WordPress site that serves the domain. A separate plugin installation on an unrelated staging domain should not share production credentials or purge settings.
4. Create the API token from Cloudflare
- In Cloudflare, open your profile’s API-token area.
- Choose the WordPress API-token template supplied for the integration.
- Review the zone scope and permissions shown by the template, create the token, and copy it immediately if Cloudflare displays it only once.
- Paste the token into the WordPress plugin’s connection field and save.
If the connection fails, check that the token belongs to the same Cloudflare account and zone as the WordPress domain, has not expired or been revoked, and was pasted without extra spaces. Regenerate a scoped token rather than using a global key.
5. Apply the recommended plugin settings
After authentication, use the plugin’s recommended settings for APO. These settings configure the cache-control signals and purge hooks the integration expects. Leave other page-cache plugins disabled during this first pass, and clear any origin or host cache so that your verification starts from a known state.
6. Turn on Automatic Platform Optimization
- In the Cloudflare dashboard, open the zone’s APO setting.
- Enable Automatic Platform Optimization for the WordPress domain.
- Save the setting and wait for the dashboard to show it as active.
- Visit a public page in a private browser window while logged out of WordPress.
Do not use an administrator session for the first test. The plugin is designed to bypass logged-in and administrator users, so that session will not demonstrate public edge caching.
7. Handle subdomains and subdirectories correctly
Cloudflare documents support for WordPress installations on subdomains or subdirectories when the plugin is version 4.4.0 or later. Update the plugin before testing those layouts. Cloudflare also documents sending cf-edge-cache: no-cache for non-WordPress paths. That signal prevents APO from treating unrelated applications or directories as WordPress cacheable content.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problemsHow to verify that APO is actually caching pages
Do not infer success from a faster page load in one browser tab. Check the response headers on a logged-out request and repeat the request after the first visit. You can use browser developer tools, an HTTP inspection utility, or a command such as:
curl -I https://your-domain.example/Replace the example host with your own domain. Inspect the response headers for the indicators Cloudflare documents:
| Header | What to look for | How to interpret it |
|---|---|---|
cf-cache-status |
The cache state returned by Cloudflare | Compare the first request with later anonymous requests and with a deliberately bypassed request. A single response is not enough to establish a stable cache pattern. |
cf-apo-via |
An APO-related response indicator | Its presence helps show that the APO path handled the request. Record the complete value when troubleshooting. |
cf-edge-cache: cache,platform=wordpress |
The WordPress edge-cache directive | This is the cache signal Cloudflare documents for WordPress HTML. A non-WordPress path may instead use cf-edge-cache: no-cache. |
Use a repeatable verification sequence
- Log out of WordPress or open a private browsing window with no administrator cookies.
- Request a public page and save the response headers.
- Request the same URL again from the same region and save the headers again.
- Repeat with a second public URL, such as a category or article page, because one page may be excluded by a cookie or rule.
- Publish a small, safe edit, then request the edited URL and verify that the new content appears after the plugin’s purge completes.
- Check a logged-in request separately; it should not be used as proof of public cache delivery.
If the headers do not show the expected APO and edge-cache signals, inspect DNS proxy status, plugin authentication, Cloudflare rules, response cookies, and any host-level cache before judging performance.
Cache purging, edits, and freshness
APO’s WordPress integration is intended to update edge content when WordPress changes are made through the plugin’s supported hooks. A newly published post, edited page, changed menu, or updated widget can therefore trigger purge activity. Purging is not the same as rebuilding every page instantly: the next request may need to fetch fresh HTML from the origin before the edge has a new copy.
Test the exact editing workflow your team uses. A deployment that edits files directly, changes content through a separate application, or writes to the database without WordPress hooks may not trigger the same purge event. For such workflows, provide an explicit Cloudflare purge procedure and verify the affected URLs.
APO compatibility with WP Rocket and other cache plugins
Cloudflare recommends disabling WP Rocket, W3 Total Cache, and similar cache plugins during initial APO setup. This is a diagnostic step, not a claim that every combination is permanently impossible. Once APO works by itself, you can test one additional cache layer at a time.
Why overlap causes problems
- A local page cache may emit headers that conflict with Cloudflare’s WordPress cache signal.
- A plugin may serve an old HTML file even after Cloudflare has purged its edge copy.
- One system may vary on cookies while the other assumes a page is public.
- Purge hooks may clear one layer but not the other, making edits appear inconsistent.
A safe reintroduction test
- Capture baseline headers and page content with APO enabled and other HTML caches disabled.
- Enable only one additional cache plugin, leaving its CDN or HTML-edge features off initially.
- Request the same logged-out URLs, then edit a page and verify that the edit appears without manually clearing multiple caches.
- Test logged-in, cookie-bearing, search, preview, and form pages before enabling more aggressive settings.
- Keep the combination only if headers, purge timing, and private-content behavior remain correct.
Does APO support WordPress multisite?
No. Cloudflare’s activation guidance states that the APO plugin does not support multisite. That limitation applies even if one site in a network appears to cache successfully. Multisite networks often combine mapped domains, network-admin changes, shared cookies, and different paths, so a partial success can conceal incorrect caching on another site.
For a multisite network, use an edge-cache solution that explicitly documents multisite support, or configure Cloudflare rules and purge automation at the network level. Treat each mapped domain and private area as a separate test case, and never assume the single-site plugin workflow applies.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Is the $5-per-month APO charge worth it?
The price is easy to state; the value depends on how many requests can be served from the edge and how expensive an origin trip is for your audience. The strongest candidates are public WordPress sites with slow or distant hosting and a high share of anonymous page views. The weakest candidates are sites where most requests are personalized, logged in, transactional, or already delivered through a well-tuned HTML edge cache.
| Site condition | Likely APO value | Reason |
|---|---|---|
| Public magazine, documentation, or blog with distant or inconsistent hosting | Often strong | Many repeatable HTML requests can avoid the origin, improving consistency for visitors far from the server. |
| Small brochure site with reliable nearby hosting and low traffic | Possibly modest | The origin may already respond quickly, so the monthly fee may produce little measurable change. |
| Membership, account, or highly personalized site | Often limited | Logged-in and cookie-dependent responses are bypassed or excluded, leaving fewer cacheable requests. |
| WooCommerce-style transactional flow | Mixed | Public catalog pages may benefit, while cart, checkout, account, and session paths need careful bypass handling. |
| Site already using a reliable HTML edge cache | Potentially redundant | Overlapping cache layers can add cost and purge complexity without adding another useful edge copy. |
| WordPress multisite | Not supported by the APO plugin | Cloudflare documents multisite as an explicit limitation. |
Compare the full monthly cost
For a Free-plan zone, use $5 per month as the documented APO charge in 2026. For Pro, Business, or Enterprise arrangements where APO is included, compare the plan’s total price and features rather than assigning a separate APO fee. Include existing cache-plugin, hosting, and CDN costs in your calculation; replacing several overlapping services may matter more than the $5 line item.
Measure before making a decision
- Choose three to five public URLs that represent your real traffic, including a home page and a typical article or landing page.
- Record several logged-out requests before APO, from the same test locations and network conditions.
- Enable APO, allow DNS and cache changes to settle, and repeat the same requests at comparable times.
- Compare response headers, time to first byte, total load time, and origin resource usage. Keep the test conditions and URLs identical.
- Check mobile and desktop conditions separately if they produce different cookies, markup, or cache variation.
Cloudflare explains the mechanism—fewer origin trips and edge delivery—but does not guarantee a universal percentage improvement. Your own headers and repeatable measurements are the evidence for whether the subscription pays for itself.
Troubleshooting common APO setup failures
The plugin cannot authenticate
- Confirm the zone is active in the Cloudflare account associated with the token.
- Recheck that you used the WordPress API-token template rather than a global API key.
- Regenerate the token if it was copied incompletely, revoked, expired, or restricted to another zone.
- Verify that the WordPress site’s canonical domain matches the Cloudflare zone you selected.
Headers show no APO behavior
- Confirm the domain’s nameservers are Cloudflare’s and the relevant DNS record is proxied.
- Check that APO is enabled for the correct zone and that a Free-plan purchase is active.
- Test while logged out and remove cache-bypass cookies from the browser.
- Temporarily disable WP Rocket, W3 Total Cache, host page caching, and custom response-header rules.
- Inspect the exact URL for a path, query string, cookie, or rule that intentionally bypasses cache.
Edits remain stale
- Confirm the edit was made through WordPress and that the plugin remains connected.
- Check whether a second cache layer still holds the old HTML.
- Test the canonical URL, trailing-slash variant, mobile variant, and any language or subdirectory path separately.
- Use a controlled edit and record when the new content first appears at the edge; do not clear unrelated caches blindly.
Private or transactional content appears cached
Stop testing the affected path publicly. Check cookies, cache rules, and plugin exclusions, then purge the relevant edge content. Keep account, checkout, cart, preview, and other private paths outside public HTML caching unless your application and Cloudflare configuration explicitly support a safe variation model.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Subdomain or subdirectory pages behave differently
Update the Cloudflare plugin to version 4.4.0 or later as Cloudflare documents for these layouts. Confirm that the WordPress path sends the expected cache signal and that non-WordPress paths send cf-edge-cache: no-cache. A separate application sharing the same hostname should not inherit WordPress cache behavior accidentally.
When to choose another approach
APO is a good fit when you want Cloudflare-managed edge HTML caching and can operate a single-site WordPress installation on Cloudflare DNS. Consider a different design when any of the following is true:
- You must support WordPress multisite and need an integration that explicitly supports it.
- You cannot move authoritative nameservers to Cloudflare.
- Your site’s pages are mostly personalized or transaction-sensitive, leaving little public HTML to cache.
- You already have a tested edge-HTML cache with reliable purging and do not want another cache-control layer.
- Your team cannot test cookie bypasses, deployment purges, and private paths safely.
Alternatives may include managed WordPress hosting with built-in page caching, another CDN that documents edge HTML caching, or a carefully configured origin page cache. Compare them on HTML edge-cache capability, purge freshness after edits, logged-in and cookie bypass behavior, compatibility with existing plugins, multisite support, DNS requirements, verification headers, and total monthly cost.
Quick Recap
A practical go-live checklist
- Cloudflare nameservers are authoritative and all required DNS records work.
- APO is purchased or included for the selected Cloudflare plan.
- The official WordPress plugin is current, connected with a scoped API token, and not installed as an unsupported multisite integration.
- Other HTML cache plugins are disabled for the initial test.
- APO is enabled for the correct zone.
- Logged-out responses show the documented APO and edge-cache headers.
- Logged-in, administrator, preview, account, cart, checkout, form, and other private paths bypass public caching.
- A controlled WordPress edit reaches visitors after the expected purge.
- Subdomain or subdirectory installations use plugin version 4.4.0 or later, and non-WordPress paths use the documented no-cache signal.
- Before-and-after measurements show a worthwhile result on your actual URLs and audience.
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.
