WP-CLI Commands
Manage BoostPro from the command line. Purge caches and check status via WP-CLI.
Last updated Feb 10, 2026
Overview
BoostPro includes WP-CLI commands for managing caches from the command line. This is useful for deployment scripts, staging workflows, cron jobs, or managing WordPress sites over SSH.
All commands are registered under the boostpro namespace.
Available Commands
Purge All Caches
wp boostpro purgeClears all BoostPro caches and any detected third-party caches in one command. This is the same action as clicking "Purge All Caches" in the admin bar or dashboard.
What gets purged:
- BoostPro minified CSS cache
- BoostPro page cache (if enabled)
- All detected third-party caches, including WP Rocket, LiteSpeed Cache, W3 Total Cache, WP Super Cache, SG Optimizer, Kinsta, WP Engine, Breeze/Cloudways, Varnish, Pantheon, SpinupWP, Cloudflare, RunCloud Hub, and Batcache
Cache Status
wp boostpro statusDisplays current cache statistics at a glance:
- Cache enabled: Whether page caching is active
- Cached pages: Number of HTML files currently in the cache
- Cache size: Total disk space used by cached files
- Last cleared: When the cache was last purged
Usage Examples
Post-Deployment Script
Add a cache purge to your deployment workflow so visitors always see the latest content:
#!/bin/bash
# deploy.sh
git pull origin main
wp boostpro purge
echo "Deployed and caches cleared."Scheduled Cache Reset
Set up a system cron to purge caches on a schedule:
# Purge BoostPro caches every night at 3am
0 3 * * * cd /var/www/html && wp boostpro purge --quietQuick Health Check
Check cache status across multiple sites:
wp boostpro status
# Page cache: Enabled
# Cached pages: 47
# Cache size: 2.3 MB
# Last cleared: 2 hours agoRequirements
- WP-CLI must be installed on the server
- BoostPro must be activated on the site
- Commands must be run from the WordPress root directory (or use
--path=/var/www/html)