Title: Cache Watch – Clear Cache Everywhere
Author: FCB Digital Ltd
Published: October 30, 2026
Last modified: October 30, 2026
---
Search plugins
# Cache Watch – Clear Cache Everywhere
By [FCB Digital Ltd](https://profiles.wordpress.org/beginwpuk/)
[Download](https://downloads.wordpress.org/plugin/fcb-cache-watch.1.0.1.zip)
* [Details](https://wordpress.org/plugins/fcb-cache-watch/#description)
* [Reviews](https://wordpress.org/plugins/fcb-cache-watch/#reviews)
* [Installation](https://wordpress.org/plugins/fcb-cache-watch/#installation)
* [Development](https://wordpress.org/plugins/fcb-cache-watch/#developers)
[Support](https://wordpress.org/support/plugin/fcb-cache-watch/)
## Description
**Cache Watch clears every cache on your WordPress site from one place, at the right
time, then warms it back up.**
Most WordPress sites have three or four caches stacked on top of each other: a cache
plugin, the host’s server cache, a CDN like Cloudflare and the object cache. You
update a page, menu or theme file, and visitors still see the old version, because
one of those layers didn’t get cleared.
Cache Watch fixes that. It notices when something on your site changes, tells you(
or just deals with it), purges every cache layer it finds, then preloads the cache
so visitors never hit a slow page.
It works alongside the cache plugin you already have. It doesn’t replace it.
**Why people use Cache Watch**
* **One button clears everything**: cache plugin, host cache, Cloudflare, Bunny
CDN, Varnish, Redis / Memcached object cache and page builder CSS
* **Catches changes other plugins miss**: menus, widgets, Customizer, block theme
templates, global styles, and even theme files uploaded by FTP or deployed with
git
* **Smart purging**: edit one post and only the affected pages are cleared, so
the rest of your site stays fast
* **Cache warming**: purged pages are revisited in the background so the next visitor
gets a cached page
* **Auto-detects your setup**: 12 cache plugins, 9 managed hosts and the major
CDNs, with no configuration needed for most sites
* **Built for developers**: WP-CLI commands, a deploy webhook, an activity log
and hooks
* **Private by design**: no analytics, no telemetry, no account needed
#### Knows when your site has changed
* Posts, pages, WooCommerce products and custom post types published, updated,
unpublished or deleted
* Slug changes (the old URL is purged too)
* Block theme templates, template parts, global styles, patterns and navigation
* Menus, widgets, Customizer, site title, tagline, homepage and permalink settings
* Categories, tags and other public taxonomies
* Theme switches, plugin activations, and core, plugin and theme updates
* Approved comments, WooCommerce stock changes and ACF options pages
* **Changes WordPress never sees**: an hourly scan of theme and plugin files catches
FTP uploads, git deploys and file editor changes
#### You choose what happens
* **Notify me**: an admin notice, a status dot in the admin bar, a dashboard widget
and an optional email summary with a link to flush
* **Flush automatically**: purge the cache the moment a change is saved
* **Scheduled flush**: clear the cache every 1, 3, 6 or 12 hours, daily or weekly.
It can skip the flush when nothing has changed.
#### Smart purging
Editing one post doesn’t need to wipe your whole cache. Cache Watch purges only
that post, the home page, its categories and tags, the author, date archives and
the feed, so the rest of the site stays fast. Menus, themes and settings changes
still flush everything.
#### Clears every cache layer
**Cache plugins:** WP Rocket, W3 Total Cache, WP Super Cache, LiteSpeed Cache, WP
Fastest Cache, WP-Optimize, FlyingPress, Cache Enabler, Hummingbird, Swift Performance,
Comet Cache, Autoptimize
**Managed hosting:** Kinsta, WP Engine, SiteGround, Cloudways (Breeze), Pantheon,
GoDaddy Managed WordPress, Pagely, SpinupWP, Pressable / WordPress VIP (Batcache)
**CDN and server cache:** Cloudflare, Bunny CDN, Varnish (direct HTTP PURGE or Proxy
Cache Purge), Nginx Helper
**Page builders:** Elementor, Divi and Beaver Builder generated CSS
**WordPress:** the object cache, including Redis and Memcached
#### Cache warming and preload
After a purge, Cache Watch visits the affected pages in the background, five at
a time, so the next real visitor gets a fast, cached page instead of a slow one.
#### For developers and agencies
* **WP-CLI**: `wp fcb-cache-watch flush`, `flush `, `flush --post=`, `
status`, `integrations`, `scan`, `preload`
* **Deploy webhook**: one secret URL to clear the cache from GitHub Actions, a
deploy script or Zapier, with optional per-URL purging
* **Purge buttons** in the admin bar (“Purge this page”) and in post lists
* **Activity log** of every change, purge, email and error
* **Hooks** to add your own cache layer, change which URLs are purged, or run code
after a flush
### External services
Cache Watch does not send analytics or telemetry. Cloudflare and Bunny CDN are contacted
only when you enable the integration and provide its credentials on the Integrations
tab. Varnish requests are sent only when you enable it and configure a server.
Cache Watch stores its settings, change status, activity log and cache-warming queue
in this WordPress site’s database. API credentials are stored in the plugin settings.
These options are removed when the plugin is deleted. Optional email summaries are
sent to the addresses you configure using this site’s WordPress mail service. Cache
warming makes requests to this site’s own pages.
#### Cloudflare
Used to purge your Cloudflare cache. When Cache Watch flushes, it sends your API
token and either a “purge everything” request or the list of page URLs to purge
to the Cloudflare API (api.cloudflare.com). When you test the connection, or haven’t
entered a Zone ID, it also sends your domain name to look up the zone.
* [Cloudflare Terms of Use](https://www.cloudflare.com/website-terms/)
* [Cloudflare Privacy Policy](https://www.cloudflare.com/privacypolicy/)
#### Bunny CDN
Used to purge your Bunny CDN pull zone. When Cache Watch flushes, it sends your
API key and either your pull zone ID or the page URLs to purge to the Bunny API (
api.bunny.net).
* [Bunny Terms of Service](https://bunny.net/tos/)
* [Bunny Privacy Policy](https://bunny.net/privacy/)
Varnish purges and cache warming only send requests to your own server.
## Screenshots
[⌊Dashboard: see at a glance whether the cache is stale, what changed and which
cache layers are being cleared.⌉⌊Dashboard: see at a glance whether the cache is
stale, what changed and which cache layers are being cleared.⌉[
Dashboard: see at a glance whether the cache is stale, what changed and which cache
layers are being cleared.
[⌊Settings: choose to be notified or clear the cache automatically, set a schedule
and turn on cache warming.⌉⌊Settings: choose to be notified or clear the cache automatically,
set a schedule and turn on cache warming.⌉[
Settings: choose to be notified or clear the cache automatically, set a schedule
and turn on cache warming.
[⌊Integrations: detected cache plugins and hosts, plus Cloudflare, Bunny CDN and
Varnish.⌉⌊Integrations: detected cache plugins and hosts, plus Cloudflare, Bunny
CDN and Varnish.⌉[
Integrations: detected cache plugins and hosts, plus Cloudflare, Bunny CDN and Varnish.
[⌊Tools: quick actions, WP-CLI commands, the deploy webhook and the activity log.⌉⌊
Tools: quick actions, WP-CLI commands, the deploy webhook and the activity log.⌉[
Tools: quick actions, WP-CLI commands, the deploy webhook and the activity log.
[⌊Admin bar: clear all caches or purge the page you're looking at.⌉⌊Admin bar: clear
all caches or purge the page you're looking at.⌉[
Admin bar: clear all caches or purge the page you’re looking at.
## Installation
1. Install from Plugins > Add New (search for “Cache Watch”), or upload the `fcb-cache-
watch` folder to `/wp-content/plugins/`.
2. Activate the plugin.
3. Go to **Settings > Cache Watch**. Your cache plugin and host are detected automatically.
4. Choose **Notify me** or **Flush automatically**, and set a schedule if you want
one.
5. If you use Cloudflare, Bunny CDN or Varnish, add the details on the **Integrations**
tab and click **Test connection**.
## FAQ
### Is this a caching plugin?
No. Cache Watch doesn’t cache anything itself. It works with the cache plugin, host
and CDN you already have, and makes sure they’re cleared at the right time.
### My cache plugin already clears the cache when I update a post. Why do I need this?
Most cache plugins only clear the post you edited. They often miss menus, widgets,
Customizer changes, theme files uploaded by FTP, and the other layers above them,
like your host’s server cache and Cloudflare. Cache Watch covers all of those, in
one place.
### Why am I still seeing old content after clearing my cache?
Usually because another cache layer is still serving the old page, often Cloudflare,
Varnish or your host’s server cache. Cache Watch clears every layer it detects together,
so nothing is left behind.
### How do I clear the Cloudflare cache automatically from WordPress?
Add a Cloudflare API token on the **Integrations** tab and choose **Flush automatically**.
Cache Watch will purge the changed URLs from Cloudflare whenever you update your
site, or purge everything when a site-wide change is made.
### Does it work with WP Rocket, LiteSpeed Cache and W3 Total Cache?
Yes. These and nine other cache plugins are detected and cleared automatically.
See the full list above.
### Does it work with WooCommerce?
Yes. Product updates and stock changes are detected, and the affected product and
archive pages are purged.
### Will flushing the cache slow my site down?
Briefly, because pages have to be rebuilt. That’s why Cache Watch uses smart purging(
only clearing what changed) and warms the cache afterwards.
### What permissions does the Cloudflare API token need?
Zone · Cache Purge · Purge. If you want Cache Watch to find your Zone ID automatically,
also add Zone · Zone · Read. Restrict the token to the zone for this site.
### The scheduled flush doesn’t run on time.
WordPress runs scheduled tasks when someone visits the site, so on quiet sites they
can run late. For exact timing, add `define( 'DISABLE_WP_CRON', true );` to wp-config.
php and set up a real cron job on your server to request `https://yoursite.com/wp-
cron.php` every 5 to 15 minutes.
### Can I clear the cache from a deploy or CI pipeline?
Yes. Use the deploy webhook on the **Tools** tab from GitHub Actions, a deploy script
or Zapier, or run `wp fcb-cache-watch flush` with WP-CLI.
### Can I add my own cache layer?
Yes. Extend `FCB_Cache_Watch_Integration` and register your class with the `fcb_cache_watch_integrations`
filter. Or, for a simple case, hook into `fcb_cache_watch_flush`:
```
add_action( 'fcb_cache_watch_flush', function ( $source, $result ) { /* purge something */ }, 10, 2 );
```
### Which hooks are available?
* `fcb_cache_watch_integrations` (filter): add or remove cache layers
* `fcb_cache_watch_post_urls` (filter): URLs purged when a post changes
* `fcb_cache_watch_preload_urls` (filter): URLs warmed after a full flush
* `fcb_cache_watch_watched_options` (filter): settings that count as a site-wide
change
* `fcb_cache_watch_ignored_post_types` (filter): post types to ignore
* `fcb_cache_watch_fingerprint_dirs` and `fcb_cache_watch_fingerprint_extensions`(
filters): what the file scan looks at
* `fcb_cache_watch_capability` (filter): who can manage Cache Watch (default `manage_options`)
* `fcb_cache_watch_flush` (action): after a full flush
* `fcb_cache_watch_purge_urls` (action): after a targeted purge
* `fcb_cache_watch_changes_pending` (action): when changes are waiting for a flush
## Reviews
There are no reviews for this plugin.
## Contributors & Developers
“Cache Watch – Clear Cache Everywhere” is open source software. The following people
have contributed to this plugin.
Contributors
* [ FCB Digital Ltd ](https://profiles.wordpress.org/beginwpuk/)
[Translate “Cache Watch – Clear Cache Everywhere” into your language.](https://translate.wordpress.org/projects/wp-plugins/fcb-cache-watch)
### Interested in development?
[Browse the code](https://plugins.trac.wordpress.org/browser/fcb-cache-watch/),
check out the [SVN repository](https://plugins.svn.wordpress.org/fcb-cache-watch/),
or subscribe to the [development log](https://plugins.trac.wordpress.org/log/fcb-cache-watch/)
by [RSS](https://plugins.trac.wordpress.org/log/fcb-cache-watch/?limit=100&mode=stop_on_copy&format=rss).
## Changelog
#### 1.0.1
* Renamed to FCB Cache Watch. The plugin folder is now fcb-cache-watch. Settings,
activity log and schedules move across automatically and the old Cache Watch
plugin is switched off, so you can delete it.
* The deploy webhook is now /wp-json/fcb-cache-watch/v1/flush with the X-FCB-Cache-
Watch-Key header. The old URL and header keep working.
#### 1.0.0
* First release.
## Meta
* Version **1.0.1**
* Last updated **1 day ago**
* Active installations **Fewer than 10**
* WordPress version ** 6.2 or higher **
* Tested up to **7.1.4**
* PHP version ** 7.4 or higher **
* Tags
* [cache](https://wordpress.org/plugins/tags/cache/)[cache preload](https://wordpress.org/plugins/tags/cache-preload/)
[clear cache](https://wordpress.org/plugins/tags/clear-cache/)[cloudflare](https://wordpress.org/plugins/tags/cloudflare/)
[purge cache](https://wordpress.org/plugins/tags/purge-cache/)
* [Advanced View](https://wordpress.org/plugins/fcb-cache-watch/advanced/)
## Ratings
No reviews have been submitted yet.
[Your review](https://wordpress.org/support/plugin/fcb-cache-watch/reviews/#new-post)
[See all reviews](https://wordpress.org/support/plugin/fcb-cache-watch/reviews/)
## Contributors
* [ FCB Digital Ltd ](https://profiles.wordpress.org/beginwpuk/)
## Support
Got something to say? Need help?
[View support forum](https://wordpress.org/support/plugin/fcb-cache-watch/)