Cache Watch – Clear Cache Everywhere

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.

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.

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.

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.

Yes. These and nine other cache plugins are detected and cleared automatically. See the full list above.

Yes. Product updates and stock changes are detected, and the affected product and archive pages are purged.

Briefly, because pages have to be rebuilt. That's why Cache Watch uses smart purging (only clearing what changed) and warms the cache afterwards.

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.

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.

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.

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 );

• 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