內容簡介
Cache Autopilot 是一款協助自動清除快取的外掛，能夠在 WordPress 內容變更後，自動判斷哪些前端頁面受到影響，並安全地請求快取外掛清除這些頁面的快取，從而減少手動清除快取的需求。
【主要功能】
• 自動判斷受影響頁面
• 與快取外掛無縫整合
• 減少手動清除快取的次數
• 自動預加載被清除的頁面
• 保持未受影響頁面的快取
外掛標籤
開發者團隊
原文外掛簡介
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 supported 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.
That means:
Fewer stale-page surprises — shared content refreshes where it actually appears.
Fewer manual cache clears — no chasing individual URLs or flushing the entire cache just to be safe.
Less cold-cache traffic — unaffected pages can stay cached while purged pages are preloaded automatically.
No cache clearing to think about — configure Cache Autopilot once; normal publishing triggers the right refreshes automatically.
Where this matters
Cache plugins are excellent at storing and serving pages fast. What they can’t always see is where else your content shows up — so a single change can leave related pages stale.
Common examples:
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 does not explicitly connect.
Cache Autopilot resolves those affected frontend pages and asks your cache plugin to purge the corresponding URLs. If it cannot safely determine every affected page, it can fall back more broadly rather than risk stale content.
Built for handover
Configure it once, then hand the site off. Your client publishes normally, and Cache Autopilot handles the resolution in the background — no chasing URLs, no manual cache clearing as a routine step.
What you get with the free version
Zero-config Gutenberg & block theme support — synced patterns, template parts, templates, Navigation and global styles.
WooCommerce support — automatically refresh the Shop page, affected products, relevant categories and tags, and connected products such as variation parents, upsells and grouped products.
Classic theme support — standard content works normally; custom layouts can be mapped through targeting and developer 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 preload purged pages without hammering the server.
The documentation includes ready-to-use filter examples for mapping custom changes to specific pages, post types or the whole site — without building your own cache-purge logic.
Supported cache plugins
Cache Autopilot currently works with:
LiteSpeed Cache (Free)
WP Rocket
WP Fastest Cache (Free) – support ready, awaiting their next release
WP Optimize (Free) – setup notes
Speed Optimizer (Free) – setup notes
FlyingPress
SpeedyCache (Free)
Breeze (Free)
Cache Enabler (Free)
Support depends on reliable URL-level purging. Some widely used cache plugins are not listed because they do not expose a suitable URL-level purge API.
Read the full cache adapter explanation.
How it works
Something changes — a post update, synced pattern edit, option or widget change, form update, or structural site edit.
Cache Autopilot resolves which frontend pages are affected.
Your supported cache plugin purges those URLs.
Cache Autopilot queues them for safe, paced background preload.
Resolution happens automatically for standard content and block themes. Custom layouts, classic themes, and advanced setups can be extended through settings and developer filters.
Free features in detail
Block theme / Site Editor support — zero configuration
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.
Cache Autopilot understands Gutenberg’s structural model:
Template parts — follows references through synced patterns and Site Editor templates, with a full-site fallback when WordPress cannot determine every page that inherits the shared part.
Site Editor templates — supports archive templates, single templates, post-type-specific templates, and slug-specific templates.
Synced patterns — finds pages embedding the pattern and refreshes those pages.
Navigation blocks — refreshes affected pages after navigation changes.
Global styles — treated as a site-level design change.
Learn more about Block Theme / Site Editor support.
Post type targeting and propagation
Each configured post type can control how broadly Cache Autopilot refreshes affected content.
Target Mode
Selected pages — always refresh specific pages when this post type changes.
All pages — refresh every published page.
Purge all cache — run a full cache purge and emit broad invalidation URLs.
Additional targeting options can extend that behaviour:
Post type archive URL — include the post type archive when this post type contributes to invalidation.
Taxonomy archive URLs — include relevant category, tag, and custom taxonomy archives.
Additional Singular Post Types — always refresh all singular pages of selected post types when this post type changes, without relying on relationship detection.
Taxonomy propagation — refresh affected posts when taxonomy terms are updated or reassigned.
Tag propagation — optionally allow tags to participate in invalidation and propagation for the post type.
Additional Singular Post Types is especially useful for dynamic or unpredictable output — for example Query Loops, shortcodes, custom blocks, plugin-generated content, or WooCommerce product pages containing dynamic Related Products.
Developer filters extend targeting further for custom setups:
Post changes — refresh selected pages when a specific post type changes.
Option changes — refresh selected pages when specific WordPress options change.
Widget/sidebar changes — map widget areas or Classic theme templates to the pages that use them.
Meta changes — catch selected custom field updates from imports or integrations.
View the developer reference.
WooCommerce support
Cache Autopilot includes native WooCommerce awareness for product updates, variations, upsells, grouped products, the Shop page, and relevant product category and tag archives.
By default, refreshes stay targeted to the product pages Cache Autopilot can identify as affected.
For stores with dynamic product-page content such as WooCommerce Related Products, Cache Autopilot can refresh all product singles instead — while the rest of the site stays cached.
Learn more about WooCommerce support.
Automatic targeting for standard content
Cache Autopilot automatically resolves common WordPress targets without manual mapping:
Posts and custom post types — the changed singular page.
Archive and taxonomy pages — post type archives, paginated archives, categories, tags, and custom taxonomy archives.
Comments — refresh affected content when comments change.
Form plugin support
When a supported form is updated, Cache Autopilot finds pages embedding the changed form via shortcodes or Gutenberg blocks, then refreshes only those pages.
View Supported form plugins.
Background cache preload
Pages cleared by Cache Autopilot are queued for background preload:
Auto-paced batch execution based on past server response times.
Priority ordering so important pages warm first.
New URLs added during a run join at the current position.
Safe to deactivate — no leftover jobs or database clutter.
Debug and support logging
Debug log available from the WordPress admin.
Support Debug Mode creates a downloadable log file for troubleshooting.
Cache Autopilot PRO
Cache Autopilot PRO adds automatic handling for builders, content relationships, multilingual sites, and scheduled refreshes:
Elementor (PRO) — Elementor 4.3 ready, with support for Atomic Default Styles, Global Classes, reusable Components, Global Widgets, templates, alternate Loop Grid templates, display conditions, Theme Builder archive and single templates, nested usage, and Elementor MCP workflows. Zero configuration for standard setups.
Watch targeted cache refresh for Elementor in action
ACF relationship propagation (PRO) — follows configured ACF relationship and post object fields across multi-level content chains such as Country → Venue → Event → Pages.
Advanced content relationships (PRO) — general relationship propagation beyond ACF, configurable per post type.
Multilingual (PRO) — WPML, Polylang, and TranslatePress support for refreshing translated target URLs.
Timed cache refresh (PRO) — scheduled rules for refreshing specific pages at set times, plus automatic handling of WordPress scheduled posts.
Access control (PRO) — grant plugin access by role or user without giving full WordPress admin rights.
Pro developer filters — additional extension points for relationship, multilingual, and resolver customization.
Compare free and PRO.
What Cache Autopilot does *not* do
It does not replace your cache plugin — it works alongside it.
It does not handle cache storage or page delivery.
It cannot function without a supported cache plugin.
It does not guarantee instant background preload on every host — preload timing depends on WP-Cron and available server resources.
It does not flush the entire cache on every content change – full purges happen only as a fallback or when triggered manually.
Documentation
Official Cache Autopilot website
Getting started
Supported integrations
Developer reference
Troubleshooting
Developer extension
Cache Autopilot exposes developer filters for extending resolution with custom WordPress setups, without replacing the core targeting logic.
View developer reference.
