WordPress cache plugins are excellent at what they do: storing and serving pages fast. When content changes, deciding what to purge gets harder once the same content appears in archives, Query Loops, synced patterns, shared templates, or other pages across the site.<\/p>\n\n
Without knowing those connections, the safe choices are often either narrow \u2014 purge the page that changed \u2014 or broad \u2014 flush the entire cache. The first can leave related pages stale. The second works, but turns more of the site into a cold cache than necessary.<\/p>\n\n
Cache Autopilot works alongside your existing cache plugin and adds that missing context. It figures out which frontend pages are affected and coordinates a targeted cache refresh: the cache plugin purges those URLs, then Cache Autopilot safely preloads them in the background.<\/p>\n\n
That means fewer manual full-cache purges, fewer stale-page surprises, and less cold-cache traffic.<\/p>\n\n
Cache Autopilot requires an active, supported cache plugin with URL-level purging.<\/p>\n\n
Currently supported cache plugins:<\/p>\n\n
Some widely used cache plugins are not listed because they do not expose reliable URL-level purge APIs. Read full explanation<\/a>.<\/p>\n\n Before installing, check the full requirements<\/a>.<\/p>\n\n Resolution happens automatically for standard content and block themes. Custom layouts, classic themes, and advanced setups can be extended through settings and developer filters.<\/p>\n\n Block theme \/ Site Editor support \u2014 zero configuration<\/strong><\/p>\n\n Block themes reuse templates, template parts, synced patterns, Navigation, and Styles across the site. Cache Autopilot follows those relationships through the WordPress template hierarchy. If WordPress cannot resolve every affected page, it falls back to a full purge and site-wide preload.<\/p>\n\n Cache Autopilot understands Gutenberg's structural model:<\/p>\n\n Learn more about Block Theme \/ Site Editor support<\/a>.<\/p>\n\n Manual targeting and developer filters<\/strong><\/p>\n\n Some pages show dynamic lists or shared content outside a normal archive \u2014 a shortcode, Query Loop block, custom block, widget area, theme option output.<\/p>\n\n Settings and developer filters let you define which pages refresh when that content or setting changes.<\/p>\n\n View developer reference<\/a>.<\/p>\n\n Targeted cache clearing for standard content<\/strong><\/p>\n\n Form plugin support<\/strong><\/p>\n\n When a supported form is updated, Cache Autopilot finds pages embedding the changed form via shortcodes or Gutenberg blocks, then refreshes only those pages.<\/p>\n\n View Supported form plugins<\/a>.<\/p>\n\n Background preload \u2014 Cache Warmup<\/strong><\/p>\n\n Pages cleared by Cache Autopilot are queued for background preload:<\/p>\n\n Debug and support logging<\/strong><\/p>\n\n https:\/\/www.youtube.com\/watch?v=oe0o5mSb1BY<\/p>\n\n Cache Autopilot PRO adds automatic handling for builders, ecommerce, content relationships, multilingual sites, and scheduled refreshes:<\/p>\n\n Elementor (PRO)<\/a><\/strong> \u2014 templates, global widgets, reusable components, display conditions, Theme Builder archive and single templates, and full nesting chain handling. Zero configuration for standard setups.<\/p><\/li>\n WooCommerce (PRO)<\/a><\/strong> \u2014 product pages, shop page, product archives, variations, grouped products, upsells, and cross-sells.<\/p><\/li>\n ACF relationship propagation (PRO)<\/a><\/strong> \u2014 follows configured ACF relationship and post object fields across multi-level content chains such as Country \u2192 Venue \u2192 Event \u2192 Pages.<\/p><\/li>\n Advanced content relationships (PRO)<\/a><\/strong> \u2014 general relationship propagation beyond ACF, configurable per post type.<\/p><\/li>\n Multilingual (PRO)<\/a><\/strong> \u2014 WPML, Polylang, and TranslatePress support for refreshing translated target URLs.<\/p><\/li>\n Timed cache refresh (PRO)<\/a><\/strong> \u2014 scheduled rules for refreshing specific pages at set times, plus automatic handling of WordPress scheduled posts.<\/p><\/li>\n Access control (PRO)<\/a><\/strong> \u2014 grant plugin access by role or user without giving full WordPress admin rights.<\/p><\/li>\n Pro developer filters<\/strong> \u2014 additional extension points for relationship, multilingual, and resolver customization.<\/p><\/li>\n<\/ul>\n\n Compare free and PRO<\/a>.<\/p>\n\n Cache Autopilot exposes filters at every major resolution decision, so developers can extend which pages refresh without touching plugin code.<\/p>\n\n View developer reference<\/a>.<\/p>\n\n\n More details on how to get started<\/a>.<\/p>\n\n\n No. Your cache plugin still stores and serves cached pages. Cache Autopilot decides which URLs need to be purged after a change, then queues them for background preload.<\/p><\/dd>\n LiteSpeed Cache, Cache Enabler, Breeze, FlyingPress, and WP Rocket. A supported cache plugin is required.<\/p>\n\n View supported cache adapters<\/a>.<\/p><\/dd>\n Usually not. Cache Autopilot targets affected pages where possible. A full purge is used only when triggered manually or when the affected URLs cannot be resolved safely.<\/p><\/dd>\n Cache plugins know how to store, serve, and purge cached pages efficiently, but they cannot always know everywhere changed content is reused \u2014 such as archives, Query Loops, synced patterns, templates, or custom pages.<\/p>\n\n Cache Autopilot adds that context and tells your cache plugin which affected URLs to purge.<\/p><\/dd>\n It resolves where a change can appear on the frontend. Targets can include the edited page, archives, taxonomy pages, shared block content, and configured target pages.<\/p>\n\n Those URLs are then purged through your cache plugin and queued for preload.<\/p><\/dd>\n Yes. The free version supports Site Editor templates, template parts, synced patterns, Navigation, global styles, archives, and standard WordPress content.<\/p><\/dd>\n Yes. Standard content works normally. Custom layouts can be mapped through settings and developer filters for post, option, widget, meta, and custom-hook changes.<\/p><\/dd>\n Yes. Purged URLs are preloaded in paced background batches, subject to WP-Cron and server resources.<\/p><\/dd>\n Where a complete mapping is required but cannot be resolved safely, Cache Autopilot can fall back to a broader purge and preload instead of risking stale pages.<\/p><\/dd>\n PRO adds Elementor, WooCommerce, ACF and advanced content relationships, multilingual support, timed cache refresh, and access-control options.<\/p>\n\n Compare free and PRO<\/a>.<\/p><\/dd>\n\n<\/dl>\n\n\n Note: Free and PRO packages share the same version number. Some releases may only affect PRO features, but version alignment keeps package compatibility, support, and upgrade paths consistent.<\/p>\n\n Release Date 14th August 2026<\/em><\/p>\n\n Release Date 13th August 2026<\/em><\/p>\n\n Release Date 12th August 2026<\/em><\/p>\n\n Release Date 29th July 2026<\/em><\/p>\n\n Release Date 28th July 2026<\/em><\/p>\n\n Release Date 27th July 2026<\/em><\/p>\n\n Release Date 7th July 2026<\/em><\/p>\n\n Release Date 6th July 2026<\/em><\/p>\n\n Release Date 25th June 2026<\/em><\/p>\n\n Release Date 23nd June 2026<\/em><\/p>\n\n Release Date 19th June 2026<\/em><\/p>\n\n Release Date 19th June 2026<\/em><\/p>\n\n Release Date 18th June 2026<\/em><\/p>\n\nHow it works<\/h4>\n\n
\n
What the free version includes<\/h4>\n\n
\n
\n
\n
\n
\n
Cache Autopilot PRO<\/h4>\n\n
\n
What Cache Autopilot does *not* do<\/h4>\n\n
\n
Documentation<\/h3>\n\n
\n
Developer extension<\/h3>\n\n
\n
\n
Is Cache Autopilot a WordPress caching plugin?<\/h3><\/dt>\n
Which WordPress cache plugins are supported?<\/h3><\/dt>\n
Do I need to clear the entire WordPress cache after every update?<\/h3><\/dt>\n
Why does my WordPress site still show old content after an update?<\/h3><\/dt>\n
How does Cache Autopilot know which pages to purge?<\/h3><\/dt>\n
Does Cache Autopilot work with Gutenberg and block themes?<\/h3><\/dt>\n
Does Cache Autopilot work with classic WordPress themes?<\/h3><\/dt>\n
Does Cache Autopilot preload pages after purging them?<\/h3><\/dt>\n
What happens if Cache Autopilot cannot determine which pages are affected?<\/h3><\/dt>\n
What does Cache Autopilot PRO add?<\/h3><\/dt>\n
1.1.9<\/h4>\n\n
\n
1.1.8<\/h4>\n\n
\n
1.1.7<\/h4>\n\n
\n
1.1.6<\/h4>\n\n
\n
1.1.5<\/h4>\n\n
\n
1.1.4<\/h4>\n\n
\n
1.1.3<\/h4>\n\n
\n
1.1.2<\/h4>\n\n
\n
1.1.1<\/h4>\n\n
\n
1.1.0<\/h4>\n\n
\n
1.0.2<\/h4>\n\n
\n
1.0.1<\/h4>\n\n
\n
1.0.0<\/h4>\n\n
\n