Title: Cache Autopilot Author: ekesto Published: 21 de Agosto, 2026 Last modified: 14 de Setembro, 2026 --- Pesquisar plugins ![](https://ps.w.org/cache-autopilot/assets/banner-772x250.png?rev=3659465) ![](https://ps.w.org/cache-autopilot/assets/icon.svg?rev=3659465) # Cache Autopilot Por [ekesto](https://profiles.wordpress.org/ekesto/) [Baixar](https://downloads.wordpress.org/plugin/cache-autopilot.1.5.1.zip) * [Detalhes](https://pt-ao.wordpress.org/plugins/cache-autopilot/#description) * [Avaliações](https://pt-ao.wordpress.org/plugins/cache-autopilot/#reviews) * [Instalação](https://pt-ao.wordpress.org/plugins/cache-autopilot/#installation) * [Desenvolvimento](https://pt-ao.wordpress.org/plugins/cache-autopilot/#developers) [Suporte](https://wordpress.org/support/plugin/cache-autopilot/) ## Descrição **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](https://youtu.be/ExgS3oXsPbc?si=kuSqMk8xEDrkaygZ&t=51). _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](https://wpcacheautopilot.com/docs/supported-integrations/#gutenberg) * **WooCommerce support** — products, variations, Shop, product categories and tags, grouped products, upsells and related storefront targets. [Learn more](https://wpcacheautopilot.com/docs/supported-integrations/#woocommerce) * **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](https://wpcacheautopilot.com/docs/cache-invalidator/#post-type-archive)· [Pagination behavior](https://wpcacheautopilot.com/docs/cache-invalidator/#paginated-archive-warmup) * **Form plugin support** — automatically find pages using changed Contact Form 7, WPForms, Gravity Forms and Ninja Forms. [Learn more](https://wpcacheautopilot.com/docs/supported-integrations/#form-plugins-compatibility) * **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](https://wpcacheautopilot.com/docs/developer-reference/#filters) * **Background cache preload** — purged pages are rebuilt through paced HTTP requests instead of being left cold. [Warmup and pacing](https://wpcacheautopilot.com/docs/cache-warmup/#batch-execution-and-pacing) #### Supported cache plugins Cache Autopilot currently works with: * [LiteSpeed Cache](https://wordpress.org/plugins/litespeed-cache/) (Free) * [WP Rocket](https://wp-rocket.me/) * [WP Fastest Cache](https://wordpress.org/plugins/wp-fastest-cache/) (Free) – requires 1.5.2+ * [WP Optimize](https://wordpress.org/plugins/wp-optimize/) (Free) * [Speed Optimizer](https://wordpress.org/plugins/sg-cachepress/) (Free) * [FlyingPress](https://flyingpress.com/) * [SpeedyCache](https://wordpress.org/plugins/speedycache/) (Free) * [Breeze](https://wordpress.org/plugins/breeze/) (Free) * [Cache Enabler](https://wordpress.org/plugins/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](https://wpcacheautopilot.com/docs/supported-integrations/#cache-adapters). #### How it works 1. Something changes in WordPress. 2. Cache Autopilot determines which frontend URLs are affected. 3. Your supported cache plugin purges those URLs. 4. 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](https://wpcacheautopilot.com/docs/cache-invalidator/#post-type-archive). #### 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](https://wpcacheautopilot.com/docs/cache-warmup/) · [Pacing](https://wpcacheautopilot.com/docs/cache-warmup/#batch-execution-and-pacing)· [Run history](https://wpcacheautopilot.com/docs/cache-warmup/#logging-and-run-history) #### Cache Autopilot PRO PRO adds deeper awareness for sites where content is reused through builders, relationships or multiple languages: * **[Elementor](https://wpcacheautopilot.com/docs/supported-integrations/#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](https://www.youtube.com/watch?v=VfUHFH6KgyY) * **[ACF relationships](https://wpcacheautopilot.com/docs/supported-integrations/#advanced-custom-fields-acf)**— 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](https://wpcacheautopilot.com/docs/supported-integrations/#multilingual-compatibility)**— WPML, Polylang and TranslatePress support, including translated target URLs and localized post type, taxonomy, date and paginated archives. * **[Timed cache refresh](https://wpcacheautopilot.com/docs/cache-invalidator/#timed-invalidation)**— refresh selected content on a schedule. * **[Access control](https://wpcacheautopilot.com/docs/cache-invalidator/#access-control)**— grant Cache Autopilot access by role or individual user. * **PRO developer extensions** — additional relationship, multilingual and resolver filters. [Compare Free and PRO](https://wpcacheautopilot.com/free-vs-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](https://wpcacheautopilot.com/docs/cache-invalidator/)· [Warmup diagnostics and operation](https://wpcacheautopilot.com/docs/cache-warmup/) ### Documentation * [Supported integrations](https://wpcacheautopilot.com/docs/supported-integrations/) * [Cache targeting and refresh settings](https://wpcacheautopilot.com/docs/cache-invalidator/) * [Cache Warmup and preload](https://wpcacheautopilot.com/docs/cache-warmup/) * [Developer hooks and filters](https://wpcacheautopilot.com/docs/developer-reference/) * [Troubleshooting](https://wpcacheautopilot.com/docs/troubleshooting/) ## Imagens de tela [⌊Configure Post Types and refresh targets⌉⌊Configure Post Types and refresh targets⌉[ Configure Post Types and refresh targets [⌊Define target pages and archive behavior⌉⌊Define target pages and archive behavior⌉[ Define target pages and archive behavior [⌊Configure sitemap sources for Cache Warmup⌉⌊Configure sitemap sources for Cache Warmup⌉[ Configure sitemap sources for Cache Warmup [⌊Prioritize important pages⌉⌊Prioritize important pages⌉[ Prioritize important pages [⌊Inspect targeted and full warmup runs⌉⌊Inspect targeted and full warmup runs⌉[ Inspect targeted and full warmup runs [⌊Automatic preload pacing based on server performance⌉⌊Automatic preload pacing based on server performance⌉[ Automatic preload pacing based on server performance ## Instalação 1. Install and activate a supported cache plugin. 2. Install and activate Cache Autopilot. 3. Open Cache Warmup and add your sitemap XML. 4. Configure the post types and targets relevant to your site. 5. Make a test edit and check the Cache Warmup log. [Getting started](https://wpcacheautopilot.com/docs/getting-started/) ## FAQ ### Is Cache Autopilot a WordPress caching plugin? No. You still need a supported cache plugin. Cache Autopilot determines which cached URLs need to refresh, asks the cache plugin to purge them, and preloads those pages again. ### Why does my WordPress cache still show old content after an update? The changed URL may not be the only cached page displaying that content. Query Loops, archives, shared blocks, templates, forms, widgets, WooCommerce data and builder components can all make one change visible on multiple URLs. Cache Autopilot resolves those affected pages and refreshes them through your existing cache plugin. ### Does Cache Autopilot clear the entire WordPress cache after every update? Usually not. It targets affected URLs whenever they can be determined safely. A broader purge is used only when configured or when targeted resolution cannot safely cover the change. ### Which WordPress cache plugins are supported? LiteSpeed Cache, WP Rocket, WP Fastest Cache, WP Optimize, Speed Optimizer, FlyingPress, SpeedyCache, Breeze and Cache Enabler. [See cache adapter compatibility](https://wpcacheautopilot.com/docs/supported-integrations/#cache-adapters). ### Does Cache Autopilot work with Gutenberg and block themes? Yes. Cache Autopilot Free understands Site Editor templates, template parts, synced patterns, Navigation, global styles and standard WordPress content. [See Gutenberg and block theme support](https://wpcacheautopilot.com/docs/supported-integrations/#gutenberg). ### Does Cache Autopilot support WooCommerce? Yes. WooCommerce support is included in Cache Autopilot Free. It covers products, variations, the Shop page, product categories and tags, grouped products, upsells and other connected storefront targets. [See WooCommerce support](https://wpcacheautopilot.com/docs/supported-integrations/#woocommerce). ### Does Cache Autopilot support Elementor? Yes, in Cache Autopilot PRO. The Elementor integration understands reusable content, templates, nested references and Display Conditions so affected frontend pages can refresh when shared Elementor content changes. [See Elementor support](https://wpcacheautopilot.com/docs/supported-integrations/#elementor). ### Does Cache Autopilot support multilingual WordPress sites? Yes, in Cache Autopilot PRO. WPML, Polylang and TranslatePress are supported, including translated target URLs and localized archive pagination. [See multilingual compatibility](https://wpcacheautopilot.com/docs/supported-integrations/#multilingual-compatibility). ### Does Cache Autopilot preload pages after purging them? Yes. Purged pages are queued for paced background preload so visitors are less likely to encounter a cold cache. [See Cache Warmup](https://wpcacheautopilot.com/docs/cache-warmup/). ### What happens if Cache Autopilot cannot determine every affected page? Where precise targeting cannot be resolved safely, Cache Autopilot can fall back to a broader refresh rather than risk leaving affected pages stale. ### Can developers extend Cache Autopilot for custom WordPress setups? Yes. Free includes filters for post changes, options, widgets/sidebars, metadata, archives and custom workflows. PRO adds relationship and multilingual extension points. [See the Developer Reference](https://wpcacheautopilot.com/docs/developer-reference/#filters). ## Avaliações There are no reviews for this plugin. ## Contribuidores e desenvolvedores “Cache Autopilot” é um software com código aberto. As seguintes pessoas contribuíram para este plugin. Contribuidores * [ ekesto ](https://profiles.wordpress.org/ekesto/) [Traduzir “Cache Autopilot” para o seu idioma.](https://translate.wordpress.org/projects/wp-plugins/cache-autopilot) ### Interessado no desenvolvimento? [Navegue pelo código](https://plugins.trac.wordpress.org/browser/cache-autopilot/), dê uma olhada no [repositório SVN](https://plugins.svn.wordpress.org/cache-autopilot/) ou assine o [registro de desenvolvimento](https://plugins.trac.wordpress.org/log/cache-autopilot/) via [RSS](https://plugins.trac.wordpress.org/log/cache-autopilot/?limit=100&mode=stop_on_copy&format=rss). ## Registro de alterações 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. #### 1.5.1 _Release Date: 14th September 2026_ * [PRO] Fix: Corrected changelog and banner presentation in native “View details” for Freemius and Git Updater distributions. #### 1.5.0 _Release Date: 14th September 2026_ * New: Added targeted refresh and full warmup support for native Post date archives. * New: Added configurable pagination support for post type, taxonomy, and date archives, including multilingual archive URLs in PRO. * [PRO] Enhancement: Improved the native “View details” information for Freemius and Git Updater, including descriptions, changelogs, and banners. * [PRO] Maintenance: Updated the Freemius SDK to 2.13.4. #### 1.4.0 _Release Date 10th September 2026_ * New: Added cache adapters for SpeedyCache, WP Optimize, and SiteGround Speed Optimizer. * New: Added WP Fastest Cache adapter support, ready to activate with their upcoming URL-purge release. * [PRO] Fix: Ensured pages refresh when an assigned Elementor Theme Builder template is moved to Trash or permanently deleted. #### 1.3.0 _Release Date 8th September 2026_ * Enhancement: Admin notices optimized. * [PRO] Enhancement: Non-Administrator users with plugin access now see the _Cache Invalidator_ and _Cache Warmup_ menu items under `Settings` instead of as top- level admin menu items. * [PRO] New: Added Elementor 4.3 support for Atomic Default Styles and Global Classes. * [PRO] Enhancement: Added targeted refresh support for alternate Loop Grid templates and improved Theme Builder Display Condition changes. * [PRO] Fix: Prevented first-time Theme Builder assignments and unrelated Elementor saves from triggering unnecessary full-site refreshes. #### 1.2.1 _Release Date 3rd September 2026_ * Enhancement: Settings UI improvements. #### 1.2.0 _Release Date 2nd September 2026_ * **New: WooCommerce support is now included in Free.** Product changes refresh affected product, Shop, category, and tag pages — targeted by default, with optional all-product refresh for dynamic product-page content. [Learn more about WooCommerce support](https://wpcacheautopilot.com/docs/supported-integrations/#woocommerce). * **New: Additional Singular Post Types is now included in Free.** Refresh all singular pages of selected post types when broader coverage is needed. [Learn more](https://wpcacheautopilot.com/docs/cache-invalidator/#additional-singular-post-types). #### 1.1.14 _Release Date 1st September 2026_ * Fix: Parent category pages now refresh after category edits and updates to content in child categories. * Fix: Category and tag pages now warm up after URL changes without waiting for sitemap updates. #### 1.1.13 _Release Date 31st August 2026_ * [PRO] Enhancement: Made warmup logs easier to scan with clear labels for Elementor components, templates, and global widgets. * Enhancement: Optimized sitemap notifications. #### 1.1.12 _Release Date 28th August 2026_ * [PRO] Fix: Prevented unnecessary full cache refreshes when unpublished Elementor pages is published with newly created components. * Fix: Prevented invalid duration values from appearing in warmup run logs. #### 1.1.11 _Release Date 26th August 2026_ * [PRO] Fix: Prevented delegated-access admin menu conflicts and kept both Cache Autopilot menus neatly together. * Enhancement: Improved the plugin readme for clarity and feature discovery. #### 1.1.10 _Release Date 22nd August 2026_ * Enhancement: Polished the settings experience with clearer user search feedback and priority controls that follow the selected WordPress admin color scheme. * Fix: Made warmup transport diagnostics clearer and more accurate about browser- profile requests and standard fallbacks. * [PRO] Fix: Prevented Elementor autosaves from triggering premature cache refreshes. #### 1.1.9 _Release Date 14th August 2026_ * [PRO] Enhancement: Preserved the active WPML language after multilingual form changes. * Enhancement: Updated WordPress compatibility to 7.1. * Fix: Ensured shared block theme changes refresh all affected pages when template usage cannot be resolved completely. #### 1.1.8 _Release Date 13th August 2026_ * Enhancement: Warmup diagnostics are now cleaner, easier to understand, and more precise about browser-profile performance and fallbacks. * [PRO] Enhancement: Priority pages and Home now start multilingual full refreshes in the right order across configured languages. * Enhancement: Improved settings navigation and made priority-page choices easier to refresh reliably. #### 1.1.7 _Release Date 12th August 2026_ * Enhancement: Improved targeted Brotli cache warming compatibility by routing browser-profile requests through the WordPress HTTP API. * Enhancement: Full cache refreshes now begin rebuilding pages promptly after manual actions and automated updates. #### 1.1.6 _Release Date 29th July 2026_ * Improvement: Added a dedicated, lightweight kick for new warmup runs on sites using server cron, without triggering unrelated WordPress cron tasks. #### 1.1.5 _Release Date 28th July 2026_ * Fix: Prevented overlapping warmup runs from becoming stuck while preparing after concurrent plugin or theme updates. #### 1.1.4 _Release Date 27th July 2026_ * Fix: Improved targeted warmup coordination for late-arriving URLs and concurrent multilingual invalidations. * [PRO] Fix: Resolved WPML post type archive URLs in their target-language context. * [PRO] Fix: Made targeted run labels distinguish distinct content changes from related multilingual emissions. * Enhancement: Improved warmup log clarity and status presentation. #### 1.1.3 _Release Date 7th July 2026_ * Enhancement: Release workflow optimizations. #### 1.1.2 _Release Date 6th July 2026_ * Security: Hardened trusted cache-clear handling and plugin access checks. * Fix: Improved support-log protection, cron loopbacks, and internal storage prefixes. * Fix: Resolved remaining Plugin Check naming warnings for legacy plugin constants. #### 1.1.1 _Release Date 25th June 2026_ * Fix: Preserved settings when deleting Free or PRO while the other edition remains installed. #### 1.1.0 _Release Date 23nd June 2026_ * Fix: Improved WordPress.org compatibility for plugin prefixes, admin notices, diagnostics data, and cache purge permissions. #### 1.0.2 _Release Date 19th June 2026_ * [PRO] Fix: Improved Plugin Check compatibility for PRO integrations. #### 1.0.1 _Release Date 19th June 2026_ * Enhancement: Admin notification optimized for first installs. #### 1.0.0 _Release Date 18th June 2026_ * Initial public release of Cache Autopilot after extended production use on real WordPress sites, including large installations with more than 1,200 pages. * Added Free/PRO-ready internal structure while keeping the free plugin fully functional on its own. * Preserved historical changelogs for the former two separate plugins [Cache Invalidator](https://ekesto.github.io/cache-autopilot-site/docs/changelog/cache-invalidator/) and [Cache Warmup](https://ekesto.github.io/cache-autopilot-site/docs/changelog/cache-warmup/). [View the full changelog](https://ekesto.github.io/cache-autopilot-site/docs/changelog/cache-autopilot/) ## Meta * Version **1.5.1** * Last updated **20 horas atrás** * Active installations **10+** * WordPress version ** 6.5 ou maior ** * Tested up to **7.1** * PHP version ** 8.0 ou maior ** * Language * [English (US)](https://wordpress.org/plugins/cache-autopilot/) * Tags * [cache](https://pt-ao.wordpress.org/plugins/tags/cache/)[cache purge](https://pt-ao.wordpress.org/plugins/tags/cache-purge/) [performance](https://pt-ao.wordpress.org/plugins/tags/performance/)[preload](https://pt-ao.wordpress.org/plugins/tags/preload/) * [Panorama avançado](https://pt-ao.wordpress.org/plugins/cache-autopilot/advanced/) ## Classificações No reviews have been submitted yet. [Your review](https://wordpress.org/support/plugin/cache-autopilot/reviews/#new-post) [See all reviews](https://wordpress.org/support/plugin/cache-autopilot/reviews/) ## Contribuidores * [ ekesto ](https://profiles.wordpress.org/ekesto/) ## Suporte Tem algo a dizer? Precisa de ajuda? [Ver fórum de suporte](https://wordpress.org/support/plugin/cache-autopilot/)