Operations
Page Cache
Clear page cache, object cache, and PHP OPcache on your WordPress sites from the MegaManager dashboard or the WordPress admin bar. Works alongside WP Super Cache, W3 Total Cache, LiteSpeed, and other popular caching layers.
Key Highlights
Clear page cache (HTML output from full-page caching plugins)
Clear object cache — Redis, Memcached, and WordPress transients
Reset PHP OPcache for bytecode freshness
One-click full clear for all supported cache layers
Remote actions from the site Cache tab after the site is connected
MegaManager Connector admin bar menu for on-site quick clears
Per-layer clear so you can target only what you need
Success feedback after each clear operation
How It Works
When your site is connected via the MegaManager Connector plugin, MegaManager can send authenticated commands to clear caches through the same secure channel used for metrics and updates. From the site's Cache tab you trigger clears by layer: page cache first for static HTML, object cache for database-backed objects, or OPcache when PHP bytecode should be rebuilt. A full clear runs all supported layers in sequence.
Page Cache Layer
Page cache stores generated HTML so repeat visitors get fast responses without re-running WordPress. Clearing this layer forces fresh HTML on the next request — ideal after publishing changes, theme updates, or when a full-page cache plugin still serves old content. The plugin integrates with common caching stacks so clears reach the right hooks.
Object Cache & OPcache
Object cache speeds up repeated database queries by storing objects in Redis, Memcached, or similar. Clearing it helps when options, transients, or custom object cache entries are stale. OPcache resets PHP's compiled bytecode cache — useful after deploying new PHP files or when opcode behavior seems inconsistent.
WordPress Admin Bar
The connector can add a Clear Cache control to the WordPress admin bar, with sub-actions for page, object, OPcache, or all layers. That lets site admins flush cache without leaving WordPress, while MegaManager keeps the same capabilities in the cloud dashboard for teams managing many sites.
Who it's for
Agencies speeding up client sites: clear stale page cache across an entire client roster so visitors always see the latest published content without logging into each WordPress admin.
Freelancers who manage a handful of sites can flush page, object, and OPcache layers from one dashboard instead of juggling separate caching plugin screens.
High-traffic sites benefit from full-page caching that serves cached HTML to repeat visitors, with targeted clears so a single stale page does not force a full cache rebuild.
WooCommerce stores can clear cache after price changes, stock updates, or theme tweaks so product and checkout pages reflect current data right away.
Frequently asked questions
What types of cache can I manage?
You can manage page cache (the HTML output from full-page caching plugins), object cache (Redis, Memcached, and WordPress transients), and PHP OPcache from one place. Each layer can be cleared individually, or you can run a full clear that flushes all supported layers in sequence.
Can I clear cache across all sites?
You clear cache per-site from each connected site's Cache tab, and you can move through your connected sites to clear them in turn. Cache actions are sent over the same secure MegaManager Connector channel used for metrics and updates.
Does it support object cache / OPcache?
Yes. Object cache clears cover Redis, Memcached, and WordPress transients, while the OPcache reset rebuilds PHP's compiled bytecode cache. These are useful after deploying new PHP files or when stale options, transients, or opcode behavior cause inconsistent results.
Does caching auto-clear after updates?
Many caching plugins clear their own page cache when you publish or update content, and MegaManager works alongside stacks like WP Super Cache, W3 Total Cache, and LiteSpeed. For cases where old content is still served, you can trigger a manual clear by layer from the dashboard or the WordPress admin bar.
Will it improve Core Web Vitals?
Serving cached HTML reduces server response time, which can help metrics tied to load speed such as Largest Contentful Paint. Cache clearing alone will not fix layout shift or script-heavy pages, so it pairs best with the performance analysis feature to find and address other bottlenecks.
Related features
Ready to try Page Cache?
Start with a 14-day trial and manage your WordPress sites smarter from day one.
Start 14-day trial