WP Cache Autopilot
Knows what changed. Refreshes what matters.
Change an Elementor or Gutenberg template, pattern, or shared component — every affected page refreshes automatically. Built-in support for WooCommerce, ACF and Form Plugins.
Included plugins:
You build the site.
You configure the plugins.
You hand it over.
Client publishes.
The right pages refresh.
See how it works — 90 seconds.
The Problem
Most cache plugins purge either too little or too much.
You update a venue post type, and the event referencing it stays stale. You edit a synced pattern/global widget, and every page using it stays stale.
The usual fix? Clear everything. But a full cache flush means every page regenerates from scratch — visitors hit cold pages, server load spikes.
These are not edge cases — posts referencing other posts, builders with shared templates/template parts, multilingual variants, WooCommerce products linked through upsells and variations.
Most cache plugins don’t track these relationships. They purge the single changed URL, or they usually purge everything. Neither is correct.
How it works
You change content. The right pages refresh. Warmup rebuilds them. Done.
WP Cache Autopilot manages the full cache lifecycle automatically:
- Detect:
Cache Invalidator finds every page that could show the changed content — dynamic content (components/synced patterns), templates, related posts, and translations. - Purge:
Only those pages refresh. Everything else stays fast. - Warm:
Cache Warmup rebuilds the purged pages in prioritized batches. By the time visitors arrive, the cache most likely is already fresh.
Detection combines automatic relationship resolution with any target pages you’ve defined manually.
Both plugins work independently and don’t interfere with your existing setup.
See: How It Works for the full lifecycle overview.
Safe to test on a real site
Wide Compatibility
- Compatible with your existing cache plugin (requires URL-level purging support)
- Reliable even on shared hosting and complex plugin stacks
Automatic Cache Freshness
- Elementor and Gutenberg dynamic content — zero config
- Optional WooCommerce product relationships (few clicks)
- Optional ACF relationship support (few clicks)
Simple & Safe
- Built-in diagnostics and debug logging
- Safe to deactivate
- 30-day refund policy
Built for precision, not guesswork
- WP Cache Autopilot works with cache plugins that support URL-level purging.
- This allows the system to invalidate exactly the pages that changed — no full flushes, no guesswork.
- Some cache plugins only support broad or indirect clearing methods. In those setups, cache refresh becomes unpredictable.
Created by a Swiss WordPress developer who ran into this problem on his own sites — and decided to solve it properly. Beat Schenkel ∙ ekesto.com
Integrations
Works with how your site is actually built — detected automatically.
Elementor
Deep structural awareness.
Global widgets, reusable components, Templates (like headers, popups, sections, loop items) — change any shared component and every page using it refreshes automatically – even when nested.
Zero configuration.
See: Supported Integrations → Elementor
Gutenberg (Block & Site Editor)
Full nesting chain and template targeting resolved.
Synced patterns, template parts, and templates — including archives, single, and per-post templates — all resolved automatically across the full nesting chain.
Zero configuration.
See: Supported Integrations → Gutenberg
Also supported for content and form resolution: Divi, Beaver Builder, WPBakery.
WooCommerce
Storefront stays accurate.
Product updates, variations, upsells, cross-sells, and archives refresh automatically — shop included.
A few clicks to set up, no coding required.
Advanced Custom Fields (ACF)
Relationships resolved automatically.
When referenced content changes, pages displaying that data refresh automatically — across multi-level chains like Country → Venue → Event.
A few clicks to set up, no coding required.
See: Supported Integrations → ACF
Cache Plugins
Targeted invalidation requires cache plugins that support URL-level purging.
Works with:
Multilingual
Translation variants refresh alongside primary content.
Works with:
Form plugins
Form changes resolve which pages embed the form and purge their cache.
Works with:
Have a question?
Whether it’s about compatibility, a feature you need, or something the product doesn’t cover yet — reach out. Questions are welcome before purchase.
Running in production
Set up by the developer, handed off to the client. Settings haven’t been touched since.
Cache management scales down as well as up.
tierpark-bern.ch
- WPBakery Page Builder
- Classic Theme
- Multilingual
Over 1100 posts from 16 custom post types embedded across multiple pages — each post update traces its references.
15 forms across 150 pages — form changes automatically purge the pages that embed them.
Classic widgets and options are mapped to specific pages — updates purge only those pages.
beatmusic.ch
- Gutenberg – Block Theme
- ACF relationships
17 pages containing synced patterns — pattern changes purge the pages that embed them.
Edit an event — the event page and every event single page showing related events get refreshed.
bernliesteinbuch.ch
- Gutenberg – Block Theme
- Multisite install
Edit a venue — every event referencing it and every page showing related events refreshes automatically.
Form updates purge the pages embedding them — automatically.
Reported side effect: suspiciously fresh and fast pages.
More features
Capabilities that don’t fit neatly in a demo, but make the difference in production.
Scheduled cache refresh
Some content goes stale on a clock, not on a save. Event listings, pricing tables, external feed aggregations — they expire at a known time, not when someone clicks Publish.
Timed invalidation lets you define rules that purge specific pages at a set time each day. Target mode controls the scope: selected pages for surgical freshness, all pages for broader sweeps, or delegate entirely to an existing post type configuration – archives included.
Scheduled posts are covered too — when WordPress publishes a future post, the right pages refresh automatically.
Who can touch the cache
On agency-managed sites, editors sometimes need access to warmup controls — without getting admin rights to the rest of WordPress.
Access control lets you grant plugin access by role or by specific user. Editors you add see Cache Invalidator and Cache Warmup as a top-level menu item, scoped to just those tools. Remove a user and the access is gone.
No role changes elsewhere. No partial-access edge cases. Either someone can manage the plugin, or they can’t.
See: Cache Invalidator → Access Control
Built to be reliable
Warmup auto-paces batch size based on past server response times, prioritizes high-value pages first, and merges new URLs mid-run at the current position. The crawler adapts to your server, not the other way around.
Built-in warmup log shows what triggered each refresh and which pages were updated. And when something unexpected happens, Support Debug Mode writes a shared log across both plugins — downloadable directly from WordPress, no server access needed.
Safe to deactivate: no leftover jobs, no database clutter.
See: Cache Warmup & Cache Warmup
The Bundle
Cache Invalidator
Decides what’s stale.
Cache Warmup
Rebuilds what was purged.
Precision over broad purges.
Full-site flushes are a last resort, not the default.
Honest about limitations.
WP-Cron timing is host-dependent. The system handles uncertainty gracefully rather than making promises it can’t keep.
Extensible without modification.
All major decision points expose WordPress hooks and filters. Customization happens outside plugin code.
Built for developers
Developers can extend behavior through standard WordPress hooks when needed. Most customizations are a short PHP snippet — no plugin code changes needed.
Add custom post relationship definitions, map options, widgets or non-public post types to pages, and more.
Documentation includes a growing number of ready-to-use snippets for common scenarios.
See: Developer Reference → Filters for full hook signatures, examples, and snippet templates.
Pricing
All features included. Tiers differ by site count only.
30-day refund period. Secure checkout. Instant download.
Safe to try. Safe to remove.
Single
$
49
Per year
Use on 1 site
1 year of updates
Email support included
Freelancer
$
179
Per year
Use on 5 sites
1 year of updates
Email support included
Agency
$
299
Per year
Use on unlimited sites
1 year of updates
Email support included
Both plugins, all features, all integrations, all updates. No feature gating between tiers.
Staging and localhost environments don’t count toward your site limit.
- Cache Invalidator + Cache Warmup plugins
- All features, all integrations, all extension points
- All updates for the license period
- Email support for plugin usage and compatibility
- Access to documentation and snippet examples
- Response times are typically within one or two business days.
- Custom theme or third-party plugin debugging is outside normal scope.
- Feature requests and bug reports are tracked and considered for future releases.
If the product doesn’t work for your use case, request a refund within 30 days — no questions asked.
FAQ
Getting started
WordPress 6.0+, PHP 7.4+, and a supported cache plugin.
See Requirements for details.
No. You still need a cache plugin for storage and serving. WP Cache Autopilot adds intelligent invalidation and warmup on top. It doesn’t modify your database, .htaccess, or cache configuration.
Activate the Post Types you want to manage in Cache Invalidator, add your sitemap URL in Cache Warmup, and you’re set. Both plugins ship with sensible defaults — auto-pacing, fallback handling, and archive resolution work out of the box.
See Getting Started for setup steps.
Cache Warmup shows run history and diagnostics for WP-Cron health and loopback connectivity. Enable debug mode to see invalidation decisions logged.
See Verify it’s working for details.
Compatibility
If you use a supported cache plugin, yes — detection is automatic:
New adapters can be added based on demand, if the cache plugin meets the requirements.
Gutenberg and Elementor get deep structural support — templates, synced patterns, reusable components.
See: Supported Integrations → Builders & Content Systems
Divi, Beaver Builder, and WPBakery are also supported for content and form resolution.
Yes. Built-in relationship propagation for variations, upsells, cross-sells, WooCommerce core pages and archives. Set up with a few clicks. Custom relationships can be added or overridden via filter.
Yes. ACF relationship and post object fields are resolved automatically once set up in a few clicks — when referenced content changes, pages displaying that data are invalidated.
See: Supported Integrations → ACF
Yes, where the underlying cache plugin supports multisite-aware operations.
How it runs
Set up a server-side cron job to call wp-cron.php at a regular interval. The diagnostics panel tests WP-Cron status and loopback connectivity so you can verify it’s working.
Auto-pacing adjusts batch size based on server response times. You can also set manual limits on batch size, throttle delay, and duration. Actual impact depends on hosting resources.
No. WP Cache Autopilot focuses on cache freshness and automation — making sure the right pages are cached and up to date. Performance depends on your hosting, cache plugin, and site architecture.
Licensing
No. WP Cache Autopilot is a paid product.
Yes. Standard staging domains (.dev, .local, staging.domain.com, and most major hosting providers) do not count toward your site limit — handled automatically.
For custom staging domains, deactivate the licence on the staging site and reactivate it when needed — no site limit consumed.
Yes. Tiers differ only by number of sites.
Yes. The price difference is prorated.
The plugins continue to work. You just won’t receive updates — including bug fixes, improvements, and compatibility patches.
Roadmap
Development is driven by real-world usage, not feature checklists. Stability comes first. New capabilities ship when they solve a genuine problem.
Updates ship when ready — not on a fixed schedule. Priorities come from production site needs, support interactions, and the evolving WordPress ecosystem.
Feature requests are welcome and tracked.
Full version history for each plugin:
Ready when you are.
Install in minutes. If something doesn’t work for your setup, the 30-day refund policy has you covered.
Common questions about WordPress cache issues
Why is my WordPress cache not updating?
Most cache plugins do not track relationships between content, so only the edited page is refreshed while others stay stale.
Why doesn’t cache preload fix stale pages?
Preload rebuilds cache but does not determine which pages were affected by a change.
Do I need to clear the entire cache?
No. Full cache clearing is a workaround. Proper invalidation targets only affected pages.