Introduction

Cloudflare APO can make WordPress feel fast until visitors keep seeing an old version of a page that you already updated. Posts stay outdated, logged-out users miss recent changes, and cache purges appear inconsistent. In most cases APO is not broken by itself. The stale content comes from purge failures, cache bypass rules, or another cache layer underneath it. The fix is to trace where the old response is being kept and whether WordPress is telling Cloudflare to purge the right page.

Symptoms

  • Edited WordPress pages still show old content to visitors
  • Manual Cloudflare purges seem to help only temporarily
  • Logged-in users see updates, but public visitors do not
  • The issue started after enabling APO or changing cache plugins
  • Some URLs refresh correctly while others stay stale

Common Causes

  • The Cloudflare WordPress integration is not purging the affected URLs correctly
  • A page cache plugin or host cache keeps serving old content behind APO
  • APO bypass or cookie rules are misconfigured for the affected paths
  • The origin sends cache headers that conflict with the intended refresh behavior
  • A CDN purge was run for one URL while stale variants still exist elsewhere

Step-by-Step Fix

  1. Confirm which exact URL is stale and whether the problem affects only logged-out visitors, because APO targets the public cache path.
  2. Check whether the Cloudflare WordPress plugin or integration is active and still connected to the correct site and zone.
  3. Purge the affected URL specifically and then compare the result with a broader cache purge to see whether invalidation is reaching APO.
  4. Review any WordPress cache plugins, host-level caching, or reverse proxies that may still serve an older page before Cloudflare even gets a fresh copy.
  5. Verify cache bypass rules for admin paths, preview URLs, login cookies, and dynamic sections so APO is not caching pages that should be excluded.
  6. Inspect origin cache headers and page rules to make sure they do not encourage a longer cache life than your update workflow expects.
  7. Re-test from a private browser session and from multiple regions if possible, because stale variants can persist unevenly across cached paths.
  8. Confirm that theme, plugin, or builder updates trigger the same purge behavior as normal post edits.
  9. Keep Cloudflare APO, WordPress caching, and hosting cache settings aligned so one cache layer does not hide stale content behind another.