Stop manually clearing cache after WordPress changes.

Cache Autopilot works alongside a supported cache plugin. Your cache plugin knows how to purge cached pages. Cache Autopilot adds the missing context: which frontend pages were actually affected by the change.

When content or shared site elements change, Cache Autopilot determines which pages need to refresh, asks your cache plugin to purge those URLs, and preloads them safely in the background. Unaffected pages stay cached where possible.

Configure Cache Autopilot once. Your client publishes normally. The right pages refresh.

Watch the full 2-minute overview, or jump straight to the integration demos.

The video includes examples from both Cache Autopilot Free and PRO.

Cache Autopilot helps reduce:

Stale pages after updates — shared content refreshes where it actually appears.
Manual cache clearing — no chasing individual URLs or clearing the whole cache just to be safe.
Cold-cache traffic — unaffected pages can stay cached while purged pages are preloaded in the background.

Why WordPress cache can stay stale

A cache plugin can efficiently purge a URL, but it cannot always know every other page where changed content appears.

A post may appear in a Query Loop on a non-archive page. A synced pattern, template part, shortcode, form, widget or custom block may be reused across the site. WooCommerce product data can appear on shop and taxonomy pages. A shared Elementor component or template can affect multiple frontend URLs.

Cache Autopilot resolves those connections and refreshes the affected cached pages. If the full impact cannot be determined safely, it can fall back more broadly rather than knowingly leave stale content behind.

What you get with Cache Autopilot Free

Cache Autopilot Free is fully usable on its own — it is not a trial.

Gutenberg & block theme support — Site Editor templates, template parts, synced patterns, Navigation and global styles. Learn more
WooCommerce support — products, variations, Shop, product categories and tags, grouped products, upsells and related storefront targets. Learn more
Posts and custom post types — refresh changed singular content and configured target pages.
Archive targeting & pagination — independently refresh post type, taxonomy and native Post date archives, with optional paginated archive pages. Archive settings · Pagination behavior
Form plugin support — automatically find pages using changed Contact Form 7, WPForms, Gravity Forms and Ninja Forms. Learn more
Site-wide WordPress changes — menus, widgets, Customizer changes, theme changes and relevant WordPress settings.
Classic themes and custom layouts — standard content works automatically; targeting and developer filters cover custom setups.
Manual targeting — explicitly choose pages or post types that should refresh when content changes.
Developer filters — map post, option, widget/sidebar, meta and custom changes to affected frontend pages. Developer reference
Background cache preload — purged pages are rebuilt through paced HTTP requests instead of being left cold. Warmup and pacing

Supported cache plugins

Cache Autopilot currently works with:

LiteSpeed Cache (Free)
WP Rocket
WP Fastest Cache (Free) – requires 1.5.2+
WP Optimize (Free)
Speed Optimizer (Free)
FlyingPress
SpeedyCache (Free)
Breeze (Free)
Cache Enabler (Free)

A supported cache plugin is required. Cache Autopilot depends on reliable URL-level cache purging rather than replacing your cache plugin.

See cache adapter compatibility and setup notes.

How it works

Something changes in WordPress.
Cache Autopilot determines which frontend URLs are affected.
Your supported cache plugin purges those URLs.
Cache Autopilot preloads the purged pages safely in the background.

This applies to targeted content changes as well as broader events such as shared template, navigation or presentation changes.

Archive and pagination support

Post type archives, taxonomy archives and native Post date archives can be enabled independently for each configured post type.

Optional archive pagination can refresh a bounded number of additional pages beginning with page 2. During warmup, pagination stops at the first page that does not exist instead of requesting deeper pages unnecessarily.

Date archives include affected year, month and day URLs. If a Post’s publication date changes, both the old and new date archives refresh.

See archive targeting and pagination settings.

Background cache preload

Cache Autopilot does not just purge affected pages and leave them cold. Purged URLs are queued for background preload with automatic pacing based on server response times.

Full warmups can rebuild the site after broader cache purges, while targeted warmups rebuild only the affected URLs. Important pages can be prioritized, URLs are deduplicated, and run history shows what was warmed or could not be reached.

Read about Cache Warmup · Pacing · Run history

Cache Autopilot PRO

PRO adds deeper awareness for sites where content is reused through builders, relationships or multiple languages:

Elementor — Elementor 4.3 ready. Supports reusable Components, Global Widgets, Saved Templates, Theme Builder templates, Loop Items, Popups, nested references, Display Conditions, Atomic Default Styles and Elementor MCP workflows.
- Watch targeted cache refresh for Elementor in action
ACF relationships — follow ACF relationship and post object fields to refresh connected content.
Advanced content relationships — extend refresh propagation to custom relationship models and data structures.
Multilingual — WPML, Polylang and TranslatePress support, including translated target URLs and localized post type, taxonomy, date and paginated archives.
Timed cache refresh — refresh selected content on a schedule.
Access control — grant Cache Autopilot access by role or individual user.
PRO developer extensions — additional relationship, multilingual and resolver filters.

Compare Free and PRO.

Designed to work safely alongside your cache

Cache Autopilot does not store or serve cached pages and does not replace your caching plugin. It uses the supported cache plugin to purge affected URLs, then rebuilds those pages through normal frontend HTTP requests.

Targeted refresh keeps unrelated pages cached whenever possible. When precise targeting is not safe, Cache Autopilot can broaden the refresh instead of silently leaving stale content behind.

Background preload is paced, and every run can be inspected in the Cache Warmup log. Support Debug Mode provides additional diagnostics when needed.

Cache targeting settings · Warmup diagnostics and operation

Cache Autopilot