Every cache purge leaves your pages “cold”: the first visitor after a purge pays the full origin render time. CacheBoost Warmer closes that gap. Whenever a purge or invalidation occurs in WordPress, it tells the CacheBoost API to re-warm the affected pages, so your cache stays hot and every visitor hits a fast, cached response.

Features:

Smart warming — resolves purged post/term URLs and triggers a targeted warm (only the affected pages).
Full warming — triggers a full site warming on global events (theme switch, plugin upgrade, full cache purge).
Deduplication — multiple purge events within the same HTTP request produce a single API call.
Non-blocking — uses wp_remote_post() with blocking => false; never delays a WordPress request.
WooCommerce — warms product and category pages on save; optional stock-change warming.
Cache plugin integrations — WP Rocket, W3 Total Cache, LiteSpeed Cache, WP Super Cache.
Multisite — each sub-site has its own settings and API key.

Configuration

Step 1 — Get your API key

Log in to app.cache-boost.com.
Go to your profile and click New API key.
Select the scopes: sites:read, sites:write, boosts:read, boosts:write, runs:read.
Copy the generated key (format cb_live_…).

Step 2 — Configure the plugin

Go to the CacheBoost menu:

Enable — master on/off switch.
API Key — paste your cb_live_... key.
Warming triggers — Smart (targeted URLs) and/or Full (entire site), each can be toggled independently.
Stock Warming — (WooCommerce only) warm product pages after stock changes.
Test Connection — validate your API key without leaving the admin. If your domain is not yet validated in CacheBoost, the plugin validates it automatically (requires the sites:write scope).

Cache plugin support

WP Rocket, W3 Total Cache, LiteSpeed Cache, WP Super Cache

External Services

This plugin sends data to the CacheBoost API (https://api.cache-boost.com) to trigger cache warming jobs after a purge event. Data transmitted includes the site URL, the list of page URLs to warm and a timestamp. No personal user data is sent.

Requests are only made when:
– The plugin is enabled in the CacheBoost settings
– A valid API key (format: cb_live_…) has been configured

CacheBoost Terms of Service: https://www.cache-boost.com/terms