Skip to main content
The Cache screen (Aero → Cache) controls Batcache, WP Stratos’s server-level full-page cache. This is the layer that skips PHP and your database entirely on a hit, and it’s the single biggest lever you have over Time to First Byte (TTFB), a metric that feeds directly into Core Web Vitals and, through it, page experience signals in Search.

​
Manual purge

Two buttons live at the top of the screen, and they’re not the same action.
If you only ever click one button, make it “Flush All Caches”. The narrower object-cache flush is there for speed when you’re certain nothing else needs clearing, not as your default habit.

​
Automated flush triggers

These decide what makes Aero purge cache without you doing anything. Each one is independently safe to leave on, and each is deliberately scoped to purge only what actually changed, so the rest of your cache stays warm. Each trigger below has its own last-run timestamp, and the Debug report lists all of them together if you ever need to confirm one actually fired.
Surgical, not sitewide. Purges the edited URL, its archive pages, the author page, and the feed. The homepage is only included when the edit could plausibly appear there. Everything purged is re-warmed within seconds if the Cache Warmer is on.
Same surgical approach, plus the homepage, since a deletion changes list membership (what shows up in “recent posts,” archives, and so on).
Purges only the commented post. The rest of the site stays warm.

​
Per-page flushing

Adds a “Flush Cache” row action on the Pages/Posts list and a toolbar button on the frontend. Useful for editors who need to push a single change live without touching the full Aero dashboard. Turn it on if non-admin editors need self-serve cache control; skip it on tightly locked-down sites.
Product pages updated through the WooCommerce REST API (inventory syncs, price updates from a PIM, etc.) get flushed individually, deployed as an mu-plugin so it runs even outside normal WordPress hooks. If you don’t run WooCommerce this setting has nothing to do.

​
Batcache behavior

These change how Batcache itself decides what to store, not what triggers a purge.
Some plugins set wpp_ prefixed cookies for their own tracking, which by default tells Batcache to treat the visitor as unique and skip caching. This setting overrides that and lets those pages cache normally. Turn it on if you’ve confirmed the plugin’s cookie doesn’t carry personalized content; leave it off if you’re not sure what’s setting that cookie.

​
Exclude pages from Batcache & Edge Cache

A comma-separated list of relative paths (/checkout/, /my-account/) that should never be cached, served with no-store via an mu-plugin so the rule holds even if Batcache’s own logic would otherwise cache them.
Cart, checkout, and account pages must never be served from cache. Caching them means one visitor can see another visitor’s cart or session state. Aero auto-excludes standard WooCommerce URLs when WooCommerce is active, but if you’ve customized those URLs or added extensions with their own transactional pages, add them here explicitly. See Cache Issues for the WooCommerce-specific walkthrough.

​
Page cache configuration (WP Stratos hosting)

If your site runs on WP Stratos infrastructure, an additional panel lets you tune Batcache’s own wp-config.php constants directly, with one-click auto-configuration if they’re not set yet.
This panel only appears when Aero detects it’s running on WP Stratos hosting and wp-config.php is writable. If wp-config.php isn’t writable, values are shown read-only, since Aero can’t safely persist a change it can’t verify was written.

​
What this means for load time and rankings

Batcache’s job is TTFB, the time before the browser gets its first byte of HTML. TTFB sits upstream of every other Core Web Vitals metric: a slow TTFB delays LCP, delays INP readiness, and delays the point where any of Aero’s Optimization work even starts mattering. A well-tuned cache layer is the highest-leverage 10 minutes you can spend in this plugin. Get the automated triggers right, extend Batcache to 24 hours, and exclude the handful of pages that genuinely need to stay dynamic. Everything else here is refinement.
Last modified on August 24, 2026