WooCommerce Cache Rules Generator

A full-page cache is one of the biggest speed wins for a WordPress store, but cart, checkout, my-account and the block-based Store API endpoint (/wp-json/wc/store, used by the cart and checkout blocks) are personal to each shopper. Cache those and one customer can see another customer's cart, or a stale checkout total. This tool builds the bypass rules for the cache layer you actually run.

Cloudflare's syntax is checked against its own Cache Rules documentation: an expression like (http.request.uri.path contains "/cart") combined with the action Bypass cache.

• Cloudflare: dashboard → Caching → Cache Rules → Create rule, paste the expression, set the action to Bypass cache.
• Nginx: add the if/set $skip_cache block above your existing fastcgi_cache_bypass or proxy_cache_bypass line, then nginx -t and reload.
• LiteSpeed Cache: LiteSpeed Cache → Cache → Excludes → "Do Not Cache URIs". LSCache already has built-in ESI support for the cart fragment, so this is mostly a backstop.
• Apache: adds a Cache-Control: no-store header on the matched paths using mod_headers, which most page-cache plugins and CDNs both respect.

• If you run a page-cache plugin (WP Rocket, W3 Total Cache, LiteSpeed Cache), check its own "never cache these pages" setting too: some caching happens inside PHP, before Cloudflare or Nginx ever see the request.
• The Nginx snippet is a widely used community pattern for pairing WordPress with fastcgi_cache or proxy_cache, not a single official Nginx page, so check it against your existing cache zone directives before reloading.
• Test by adding an item to cart in one browser and an incognito window at the same time; if the cart count or contents ever leak between them, a cache layer somewhere isn't excluding these paths.