Page caching (WP Rocket, LiteSpeed, W3 Total Cache)
Keep member prices correct with full-page caching — what is safe to cache, what must not be cached, and settings for the common cache plugins.
Updated November 8, 2026 · 1 min read
Logged-in customers see their own prices; guests all see the same page. So:
- Guest pages can be cached. The guest preview is the same for everyone.
- Pages for logged-in users must not be cached together. Most cache plugins skip logged-in users by default — keep it that way.
WP Rocket
Cache → User cache must be off (the default). WP Rocket then serves logged-in visitors uncached pages. Cart, checkout and My Account are excluded automatically.
LiteSpeed Cache
Cache → Cache Logged-in Users off (default), or on with private cache — LiteSpeed's private cache is per user and works with PriceKit.
W3 Total Cache
Page Cache → Don't cache pages for logged in users on (default).
CDN and server caches
Cloudflare APO, Varnish and host caches usually bypass the cache when WordPress login cookies are present. Check that your host does the same.
After changing prices
Clear the cache after changing tiers, guest mode or display settings, and on the start day of a scheduled member price.