{"id":1489,"date":"2026-09-03T12:16:59","date_gmt":"2026-09-03T06:46:59","guid":{"rendered":"https:\/\/cpanelfree.com\/blog\/how-to-configure-cloudflare-page-rules-cache-everything-wordpress\/"},"modified":"2026-09-03T12:31:07","modified_gmt":"2026-09-03T07:01:07","slug":"how-to-configure-cloudflare-page-rules-cache-everything-wordpress","status":"publish","type":"post","link":"https:\/\/cpanelfree.com\/blog\/how-to-configure-cloudflare-page-rules-cache-everything-wordpress\/","title":{"rendered":"How to Configure Cloudflare Page Rules & Cache Everything for WordPress"},"content":{"rendered":"
\n

\n Quick Answer:<\/strong> By default, Cloudflare only caches static files (images, CSS, JS) and passes all HTML requests to your origin server. Configuring “Cache Everything” Page Rules \/ Cache Rules<\/strong> caches the entire generated HTML page across Cloudflare’s 300+ edge data centers, delivering instant sub-30ms TTFB worldwide<\/strong> while safely bypassing the cache for logged-in administrators and WooCommerce cart sessions.\n <\/p>\n<\/div>\n

Why Default Cloudflare Does Not Cache WordPress HTML<\/h2>\n

Cloudflare’s standard caching configuration only caches assets matching specific static file extensions (.jpg<\/code>, .css<\/code>, .js<\/code>, .webp<\/code>). Because WordPress generates dynamic HTML pages via PHP and MySQL, Cloudflare forwards every page request to your origin web server.<\/p>\n

Enabling Cache Everything<\/strong> turns Cloudflare into a global edge page cache, allowing your website to handle tens of thousands of concurrent visitors on a free shared hosting account without crashing.<\/p>\n

Step 1: Creating the WP-Admin Cache Bypass Rule (Priority 1)<\/h2>\n

Never cache administrative interfaces or preview links. In Cloudflare dashboard, navigate to Rules > Page Rules<\/strong> (or Caching > Cache Rules<\/em>) and create your first rule:<\/p>\n

URL Pattern: *yourdomain.com\/wp-admin*\nSettings:\n  - Cache Level: Bypass\n  - Security Level: High<\/pre>\n
Step 2: Creating the Preview and Login Bypass Rule (Priority 2)<\/h2>\n
URL Pattern: *yourdomain.com\/*preview=true*\nSettings:\n  - Cache Level: Bypass<\/pre>\n
Step 3: Creating the Global Cache Everything Rule (Priority 3)<\/h2>\n
Create the primary edge caching rule covering all public content:<\/p>\n
URL Pattern: *yourdomain.com\/*\nSettings:\n  - Cache Level: Cache Everything\n  - Edge Cache TTL: 7 days\n  - Browser Cache TTL: 4 hours<\/pre>\n
Bypassing Cache for Logged-In Users via Super Page Cache Plugin<\/h2>\n
To ensure logged-in users and WooCommerce shoppers see personalized cart contents without paying for Cloudflare Enterprise, install the free Super Page Cache for Cloudflare<\/strong> plugin by Optimole. This plugin hooks into WordPress authentication cookies and injects Cache-Control: no-cache<\/code> headers whenever a user logs in or adds an item to cart.<\/p>\n
Advanced Cloudflare Edge Caching: Tuning Cache Keys and Headers<\/h2>\n
To maximize your cache hit ratio without serving stale content to active eCommerce shoppers, configure custom Cache Keys<\/strong> under Caching > Cache Rules<\/em>:<\/p>\n
Expression: (http.request.uri.path matches \"^\/shop\/\" or http.request.uri.path matches \"^\/product\/\")\nAction: Cache Everything\nEdge TTL: 1 Month\nRespect Origin Cache-Control Headers: Yes<\/pre>\n
Handling WordPress Nonces and Dynamic AJAX Fragments<\/h2>\n
WordPress CSRF security nonces expire every 12 to 24 hours. If full HTML pages are cached at the edge for 7 days, visitors submitting comments or contact forms will receive “Nonce verification failed” errors. To solve this, configure contact form plugins (like WPForms or Fluent Forms) to fetch fresh nonces dynamically via asynchronous AJAX requests (\/wp-admin\/admin-ajax.php<\/code>).<\/p>\n
Verifying Edge Cache Hits with CF-Cache-Status Headers<\/h2>\n
Inspect incoming HTTP response headers in Chrome DevTools to verify caching behavior:<\/p>\n