About this plugin
A WordPress cache preloader warms your server. rocks warms the CDN edges between your server and visitors around the world.
A visitor in Zurich and a visitor in Singapore do not use the same CDN cache. One location may return a fast cache hit while another still has to contact your origin.
rocks connects WordPress to a managed cache warmer. After you publish or update public content, the plugin asks the service to request your sitemap URLs from distributed locations. The run records which CDN edge answered and whether it returned a HIT, MISS, BYPASS, or another cache status.
net, and CDN77. Detection uses the response headers each CDN already sends. Other CDNs can still be warmed, but their provider and edge location may appear as unknown when they do not expose recognizable headers.
You do not need to install a proxy list, run a crawler inside WordPress, or deploy your own Cloudflare Worker. rocks handles the remote requests. The WordPress plugin stays small and only sends a trigger when the site changes.
Use it after WordPress updates, CDN cache purges, deploys, or TTL expiry. The dashboard shows whether each request produced a HIT, MISS, EXPIRED, BYPASS, or DYNAMIC response, so a completed crawl is not mistaken for a warm edge cache.
The plugin:
- groups quick edits for 90 seconds before requesting a run;
- reacts to published posts, pages, products, taxonomies, themes, and plugins;
- adds a manual Warm now action;
- shows project and latest-run status in WordPress;
- detects and securely syncs same-site WordPress core or Yoast sitemap URLs;
- sends no post content, customer data, WordPress credentials, or visitor cookies;
- includes a complete German translation source for WordPress.org language packs.
rocks account and project are required. The remote service performs the cache-warming requests and may require a paid plan. See how the global cache warmer works, including supported CDNs, edge reporting, and current plans.
The plugin does not make private pages public, change cache headers, or weaken WooCommerce safety rules.
External service
rocks when an administrator checks status, starts a manual run, or when a scheduled automatic warming request is due.
Data sent: plugin version, the public site URL, detected same-site sitemap URLs, a short change reason such as content or site, and the secret Deploy Hook token when a run is triggered. During one-click setup, WordPress sends the HTTPS site URL, its same-origin admin callback URL, a random state value, and a short-lived exchange code. The hook secret never appears in the browser address.
No post content, customer data, WordPress credentials, or visitor cookies are sent.
rocks/terms
rocks/privacy