Introducing the CacheBoost Warmer WordPress Plugin

The problem we kept hearing about

Every time someone told us they were using CacheBoost, the conversation eventually landed on the same frustration: "I love the warming, but I have to remember to trigger it."

A nightly cron takes care of the basics. An API call in your deploy script covers deployments. But what about the post you publish at 2pm? The plugin update your hosting provider applies at 4am? The WooCommerce product you edit right before a flash sale?

These events happen constantly, outside any schedule, and every one of them leaves your cache cold.

We built the CacheBoost Warmer plugin to close that gap.

What the plugin does

Install it, connect your CacheBoost account with an API key, and forget about it. From that point on, the plugin watches every WordPress and WooCommerce event that purges your cache, and triggers the right warm-up automatically.

Content events:

• Post, page, or custom post type published or updated
• Category or tag modified
• Menu changed
• Homepage and archive pages invalidated by any of the above

System events:

• Plugin or theme activated, deactivated, or updated
• WordPress core auto-update completed
• Theme switch

WooCommerce events:

• Product saved or stock level changed
• Product category modified
• Shop page invalidated

Cache plugin hooks: The plugin auto-detects WP Rocket, W3 Total Cache, LiteSpeed Cache, and WP Super Cache, and hooks into their native purge events, so even manual cache flushes from those plugins trigger a warm-up.

Smart mode: warm only what was purged

A naive approach would flush and re-warm the entire site on every event. That's expensive and slow.

The CacheBoost Warmer plugin resolves the exact URLs that were invalidated by each event (the post permalink, its category pages, the author archive, the homepage) and warms only those. A product update on a 5,000-item WooCommerce store triggers a warm of 4–6 URLs, not 5,000.

For events that do require a full warm (core update, full cache flush), the plugin triggers a full boost run automatically.

Non-blocking, always

The warm-up call is fired with wp_remote_post() using blocking => false. This means the API call is dispatched and forgotten before WordPress finishes rendering the current page. Your editors never notice any delay.

If multiple events fire in the same request (common during bulk operations), the plugin deduplicates them and sends a single API call on shutdown instead of one per event.

Multilingual sites

WPML, Polylang, and TranslatePress sites work natively. The plugin discovers per-language URLs from your sitemap and warms all language variants of an updated page, not just the default language.

Requirements and installation

Requirements: WordPress 6.0+, PHP 8.0+, a CacheBoost account (free plan available).

Installation:

1. Search for "CacheBoost Warmer" in your WordPress plugin directory, or download it from WordPress.org
2. Activate the plugin
3. Go to Settings → CacheBoost, paste your API key (found in your CacheBoost dashboard), and save
4. Select which boost to use for full-site events (plugin updates, core updates)

That's it. The plugin starts listening to events immediately.

Open source, MIT license

The CacheBoost Warmer plugin is open source under the MIT license. The source is available on GitHub. Contributions, bug reports, and feature requests are welcome.

What this means for API users

Nothing changes for teams using the API directly. The plugin is the easiest path (install and forget), but the REST API remains available for custom integrations, mu-plugins, deploy scripts, and any other workflow where you need programmatic control.

If you're currently calling the API manually on post save or from a cron job, the plugin is a drop-in replacement that handles more events with less code on your end.

Get started

The plugin is free to install. It connects to your CacheBoost account: the free plan covers up to 500 URL warm-ups per month, which is enough to get started on most sites.