> ## Documentation Index
> Fetch the complete documentation index at: https://docs.wpstratos.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Configure Page Caching in Aero for Faster WordPress Load Times

> Learn how Aero's page cache and browser cache work on WP Stratos sites, and how to configure cache settings, set exclusion rules, and purge cached pages.

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.

| Action | What it clears | When to use it |
| - | - | - |
| **Flush All Caches: Sequential** | Aero's minified files, then Batcache, then Edge Cache, in the order set on [Purge & Schedule](https://docs.wpstratos.com/plugins/aero/purge-schedule.md) | After a theme/plugin update, a design change, or anything that could be stale anywhere |
| **Flush Object Cache & Batcache** | Object cache and Batcache only. Minified assets and Edge Cache are untouched | When you just need Batcache cleared fast and don't want to wait on a full Edge purge |

> [!TIP]
>
> 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](https://docs.wpstratos.com/plugins/aero/debug.md) report lists all of them together if you ever need to confirm one actually fired.

> [accordion] Flush cache on plugin & theme updates: Safe, recommended
>
> Runs the **full sequential flush**, deliberately. An update can change CSS, JS, or markup sitewide, so every layer purges in order and the Cache Warmer rebuilds immediately after. Leave this on unless you have a specific reason to manage flushes manually after deployments.

> [accordion] Targeted flush on page/post edit: Safe, recommended
>
> 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](https://docs.wpstratos.com/plugins/aero/cache-warmer.md) is on.

> [accordion] Flush cache on page/post delete: Safe, recommended
>
> Same surgical approach, plus the homepage, since a deletion changes list membership (what shows up in "recent posts," archives, and so on).

> [accordion] Flush cache on comment delete: Safe
>
> Purges only the commented post. The rest of the site stays warm.

## Per-page flushing

> [accordion] Flush Batcache for individual pages: Situational
>
> 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.

> [accordion] Flush Batcache for WooCommerce product pages: Safe if you run WooCommerce
>
> 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.

> [accordion] Extend Batcache storage to 24 hours: Safe, recommended
>
> Raises `max_age` to 86400 seconds so cached pages survive a full day instead of the platform default. Longer cache life means fewer full-render hits on your server, which is almost always a win as long as your automated flush triggers above are on to keep content from actually going stale.

> [accordion] Cache pages that set wpp\_ cookies: Situational
>
> 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.

> [accordion] Ignore gclid query strings: Safe, recommended
>
> Google Ads click IDs (`?gclid=...`) are unique per click, and without this setting each one fragments your cache into a separate, useless entry. Ignoring them for cache-key purposes means ad traffic actually benefits from caching instead of missing it every single time. This has no effect on your analytics, it only affects what Batcache treats as "the same page."

### 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.

> [!WARNING]
>
> 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](https://docs.wpstratos.com/troubleshooting/cache-issues.md) 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.

| Field | Default | What it controls | Guidance |
| - | - | - | - |
| **Cache Duration (max\_age)** | 86400s | How long a cached page is stored before Batcache re-renders it | 86400 to 604800 (1 to 7 days) covers nearly every site. Push it higher only on sites that update rarely and purge reliably on every change. |
| **Wait Time (seconds)** | 0 | Delay before Batcache starts caching a URL after its first request | Recommended: 0. There's rarely a reason to delay caching. |
| **Visitor Threshold (times)** | 1 | Number of visits required before a page gets cached | Recommended: 1. Waiting for multiple visits mostly just means more uncached, slower first loads for no real benefit on typical traffic patterns. Also, the [Cache Warmer](https://docs.wpstratos.com/plugins/aero/cache-warmer.md) is already setup with this in mind. |
| **No-Skip Cookies** | wordpress\_test\_cookie, wp-wpml\_current\_language, wpml\_browser\_redirect\_test | Cookies that should *not* cause Batcache to bypass caching | Add cookies here only after confirming they don't carry per-visitor personalization. Wrong cookies might leak one visitor's state to another so be careful. |

> [!NOTE]
>
> 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](https://docs.wpstratos.com/plugins/aero/optimization.md) 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.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.