GoBuildWP CloudConnect your sites through one workspace.Explore Cloud →
GoBuildWP
Download freeDownload

Caching and page speedPro

Powered Cache MCP: purge, preload and native options from an agent

Powered Cache is the only unmapped plugin where GoBuildWP exposes an action as well as a purge. A Powered Cache MCP session can flush the cache through the plugin's namespaced powered_cache_flush() function and then start Powered Cache's own preloader, which queues the site's URLs within its batching and server-load limits. Settings stay reachable by option name only, and presets do not apply.

By GoBuildWPContent updated How we check claims

Get GoBuildWP free See Pro pricing
Powered Cache driverpowered_cache
Layer
page
Declared purge scopes
all
Shared keys
None
Detected by
plugin folder powered-cache

Installed class, method or listener checks and per-layer results determine whether a purge ran. Neither a declaration nor a returned ran flag proves public freshness.

Edition
Pro
Abilities
16
Requires
WordPress 6.9+, PHP 8.0+

Before changing cache settings, inspect captured drivers and not_captured. After reverting, inspect restored, deleted, not_restored, verified and purged_layers. Use a separate cache-purge result when you need details for each layer. Storage verification checks captured values; it does not establish functional recovery or public freshness. Revert may overwrite later settings, and vendor configuration regeneration or a re-save can still be required.

Check each measurement run’s fetched_via before treating it as public-path evidence. cache-verify-in-browser supplies checks and does not operate a browser. Automatic purge coalesces targets within the request and runs on shutdown; it is not necessarily one immediate flush per call. Verify generated files, object/page/edge caches and actual visitor behavior separately.

Worked example

Flush after a theme update and preload the whole site

Expected outcome to verify on the installed stack; this sequence has not been recorded as a runtime test.

Inspect the purge result and Powered Cache's background preload status, then test the important URLs. An unavailable preload means its declared entry point did not resolve; check the installed version and configuration, or warm selected URLs while reporting the gap.

GoBuildWP has no direct Cloudflare call in this driver; inspect any configured extension cascade. Check the PoweredCache HTML comment and expected theme content. Report preload queue start separately from completion, and re-save or inspect generated rules after native writes and reverts.

AI clientyour-site.comVerify site policy

I updated the theme. Clear Powered Cache and get the site preloaded again.

  1. wppilot/cache-check-setupRead

    Shows powered_cache with purge_scopes.all true, plus any other layer.

  2. wppilot/cache-purgeWrite

    Scope all; the layer result names PoweredCache\Utils\powered_cache_flush() as the entry point.

  3. wppilot/cache-list-actionsRead

    Returns preload with available true, blocking false and destructive false.

  4. wppilot/cache-run-actionConfirm first

    Runs preload; returns ran true as soon as the preloader has been started.

  5. wppilot/cache-measure-pageRead

    Taken some minutes later, shows whether key pages are being served quickly again.

Proposed sequence from source declarations; not a recorded task or proof of client compatibility. Inspect saved state and browser or provider results separately.

A suggested sequence from the ability reference, not a recorded run.

Abilities

Powered Cache through each cache ability

AbilityWhat it does hereUndo and limits
cache-list-actionscache-run-actionList preload, non-blocking and non-destructive, resolved to PoweredCache\Preloader::factory()->start_preload(), and report whether it resolves on this install. Running it queues URLs and returns straight away.ran means the entry point was called without throwing; whether pages were preloaded is Powered Cache's decision. Re-measure later rather than immediately.
cache-purgeCalls PoweredCache\Utils\powered_cache_flush(); url and post requests widen to that flush and the result says so.An earlier mapping as a hook, then by bare name, found nothing; installing the plugin showed the namespaced function. If it ever goes missing, purge_scopes.all reads false.
cache-warmFetches up to ten URLs synchronously and reports for each whether a cache hit came back, which suits the handful of pages you just changed.The preloader, not warm, is the tool for the whole site.
cache-check-setupcache-measure-pagecache-verify-in-browserDetect the powered-cache folder, measure delivery from the server, and list the checks a person should run in a browser for optimisation damage.Powered Cache's own proof of a cached page is the HTML comment Cache served by PoweredCache in the source; measure-page reads response headers, so view source for that comment.
cache-get-settingscache-set-nativeList the powered_cache rows and write one by exact name, confirm=true, after reading it back.A direct row write is not a settings-screen save.
cache-set-settingscache-apply-presetcache-list-presetsReport all keys unsupported; GoBuildWP has not mapped Powered Cache onto its shared vocabulary.No risk tiering: a native change to minify or combine gets no extra gate.
cache-begin-experimentcache-revert-experimentrollback-changeSnapshot and restore powered_cache rows and purge.Queued preloading and flushes are not undoable; the ledger records that a cache action changes no restorable setting.

Reference: /docs/reference/cache

Shared cache module; do not add this count across drivers. Edition and effect labels describe the source catalogue. The installed schema, dependency versions, licence, WordPress capability, safety profile and per-ability policy determine availability; labels alone do not prove confirmation or recovery.

Data model

Static files, .htaccess rules and powered_cache rows

Powered Cache writes cached pages as static files (index.html, index-https.html, gzipped copies and a meta.php) and, on Apache, serves them through .htaccess rules it manages itself; Nginx needs the sample configuration from its documentation. It can also be the object cache, over Memcache, Memcached, Redis or APCu, with server details given in wp-config.php through $memcached_servers or $redis_server.

Its options start with powered_cache, and that prefix is the boundary GoBuildWP enforces. A cache-set-native write updates the named row directly rather than passing through Powered Cache's settings screen, so .htaccess rules the plugin would regenerate on save stay as they were unless the plugin reacts to the option change itself. Save once in its screen after a delivery-related change.

The premium edition adds critical CSS, unused CSS removal, an image optimiser and Varnish support, and a built-in Cloudflare extension that purges Cloudflare's cache. GoBuildWP calls none of those directly.

Option name prefixes

  • powered_cache

Not mapped onto the shared vocabulary at its current reach. Its options are readable and writable by name, and purge is supported.

Other plugins

Powered Cache with Cloudflare and object caches

  • When Cloudflare fronts the site, inspect edge_layers. GoBuildWP makes no direct Cloudflare call; a configured Powered Cache extension may cascade a purge, so verify the actual edge response.
  • If Powered Cache provides the object cache, check-setup's backend field recognises only Redis Object Cache, Docket and SQLite by name, so expect a less specific answer for Powered Cache's drop-in.

Limits

Powered Cache limits

  • Unmapped: no canonical keys, no presets, and every native write needs confirm=true.
  • Preload is queued, not finished, when cache-run-action returns, and neither it nor a flush can be rolled back.
  • The vendor's WP-CLI commands for purge and preload are Premium-only, so on the free edition these abilities are the scripted route.
  • GoBuildWP does not call the Cloudflare extension; whether a flush also reaches Cloudflare depends on that extension's own settings.

Questions

Powered Cache questions

Can an AI agent preload Powered Cache without WP-CLI?

Yes, where cache-list-actions reports the preload action as available: it calls the plugin's preloader directly and returns while the queue runs.

How do I know a page came from Powered Cache?

View the page source and look for the comment Cache served by PoweredCache, which the vendor documents as the check.

Does the agent's purge clear Cloudflare too?

Not directly. GoBuildWP flushes Powered Cache. If Powered Cache's Cloudflare extension is configured it may pass the purge on; otherwise purge from Cloudflare. Either way, check the edge response afterwards rather than assuming it was cleared.

Where these facts come from

GoBuildWP behaviour is taken from the plugin source and the ability reference; third-party details from the vendor documentation below, checked by the GoBuildWP team.

Powered Cache is a separate product; no partnership or endorsement is implied.

Try it on Powered Cache in Read Only first

Get GoBuildWP free See Pro pricing