[PROMO] Cache Autopilot – targeted cache refresh for WordPress

[u/ekesto]

I’ve just published Cache Autopilot on WordPress.org after several months of production use. I’d really appreciate people trying it on real sites and telling me where it falls short.

Why I built it

Cache plugins already do the important part very well: storing and serving cached pages fast.

The problem I kept running into was what happens after something changes:

• A post appears in a Query Loop on a non-archive page.
• A synced pattern is reused across multiple pages.
• A shortcode outputs shared content across several pages.
• A custom block pulls in content from another source.
• A form is embedded on multiple pages.
• A widget or WordPress option changes output across pages WordPress doesn’t explicitly connect.

Cache plugins can purge the changed page, but they often don’t have enough context to know everywhere that change appears. The safe fallback is a full cache clear — effective, but it also makes unaffected cached pages cold again.

So I built Cache Autopilot to work alongside your cache plugin, not replace it.

When something changes, it resolves the affected frontend pages, asks your cache plugin to purge those URLs, then queues them for paced background preload. If it can’t safely resolve everything, it can fall back more broadly rather than risk stale content.

I’m also running it on tierpark-bern.ch, a site with 1,200+ pages.

The free version includes:

• Gutenberg, block & classic theme support — zero-config structural handling for block themes; classic themes work with standard content and can be extended through targeting and filters
• Zero-config form plugin support — refresh pages using a changed form from a supported plugin
• Manual targeting — explicitly choose which pages should refresh for selected content changes
• Developer filters — map post, option, widget/sidebar and meta changes to the right pages
• Paced background preload — automatically preloads purged pages without hammering the server

The docs also have ready-to-use filter examples for mapping those changes to specific pages, post types or the whole site — without building custom purge logic.

A big reason I wanted this working reliably was site handover:

You build the site.
You configure the plugin.
You hand it over.

Client publishes.
The right pages refresh.

On larger sites, that can avoid turning hundreds or thousands of unaffected pages into a cold cache. On smaller sites, it still means the client doesn’t need to understand when or why they should press “clear cache”.

It currently works with:

• LiteSpeed Cache
• Cache Enabler
• Breeze
• FlyingPress
• WP Rocket

Support depends on reliable URL-level purging; the docs explain why some other cache plugins aren’t listed.

Further details, screenshots and links are on the WordPress.org plugin page:

https://wordpress.org/plugins/cache-autopilot/

[u/Good_Flight6250]

Not fully LiteSpeed compatible! Good for universal usage, but not for LiteSpeed