WordPress plugin

Install the official plugin, connect it to your account, and manage warmers from wp-admin.

8 മിനിറ്റ് വായന

Cache Rocket works on any WordPress site without a plugin — website warmers only need public URLs. The plugin is optional, and it adds two things: managing your warmers from inside wp-admin, and an optional local performance suite.

Do you need it?

SituationRecommendation
You just want your pages warmedSkip the plugin. Create a website warmer with your homepage as the entry URL and enable sitemaps.
You want to manage warmers without leaving WordPressInstall the plugin.
You want warming to happen automatically when you publishInstall the plugin.
You have no caching plugin at all yetInstall it and consider the local page cache — warming is far more effective with a cache to fill.
You already run WP Rocket, W3 Total Cache, or similarInstall the plugin but leave its local caching features off, to avoid two page caches fighting.

Never run two page caches at once

Two plugins both writing an advanced-cache drop-in cause stale pages, broken logins, and puzzling intermittent bugs. Pick one and disable the caching features of the other.

What the plugin adds

  • Remote cache warmers managed from wp-admin — create, edit, start, and stop warmers without opening the Cache Rocket dashboard.
  • Optional local page cache, including early delivery via an advanced-cache drop-in.
  • File optimization — minification and combination of CSS and JavaScript.
  • LazyLoad for images, so they load as they scroll into view.
  • Custom CDN rewriting for your own asset hostnames (Advanced).
  • Managed CDN + cloud Media on paid plans — image optimization, LQIP, Critical CSS, PageSpeed. See Managed CDN.
  • Database cleanup for revisions, transients, and other accumulated cruft.
  • API-key authentication against your Cache Rocket account.

Local performance features work without a paid plan. Remote warmers follow your Cache Rocket warmer limits. Managed CDN and cloud Media jobs require the matching paid entitlements.

Cloud optimization (paid plans)

With API keys connected and a paid plan, the Media and Advanced screens unlock cloud jobs that publish to Managed CDN:

Tip

Quotas for image opts, Critical CSS pages, LQIP, PageSpeed audits, CDN bandwidth, and CDN purges sync from your plan and hard-stop when exhausted.

Where to download it

There are exactly two legitimate sources:

Never install a nulled or cracked copy

Redistributed “free premium” WordPress plugins are routinely modified to include malware, backdoors, and credential stealers. A compromised plugin runs with full access to your site and its database. Download only from the two sources above.

Installing

  1. 1

    Download the plugin

    Get the latest cacherocket.zip from the WordPress page.

  2. 2

    Upload it

    In wp-admin go to Plugins → Add New → Upload Plugin, choose the zip, and install.

  3. 3

    Activate

    Click Activate once the upload finishes.

  4. 4

    Generate API keys

    In Cache Rocket, open Account → Account, click Generate new api keys, and reveal the secret immediately — it is shown only once. See API keys.

  5. 5

    Paste both keys into the plugin

    Open the Cache Rocket settings screen in wp-admin, enter the public and secret keys, and save.

  6. 6

    Verify your hostname

    If you have not already, verify the site's domain under Account → Hostnames. Warmers will not run without it. See Hostname verification.

  7. 7

    Create or sync a warmer

    Use the plugin's warmer screen to create one, or sync warmers you already built in the dashboard.

Warming a WooCommerce store

Stores are where warming pays off most, because product and category pages are expensive to build and there are a lot of them. A few store-specific pointers:

  • Turn on sitemaps. WooCommerce sites have far too many product URLs to list by hand, and your SEO plugin already maintains a sitemap of them.
  • Exclude the parts that must never be cached. Add /cart, /checkout, and /my-account to excluded URLs. These are per-visitor pages; warming them is pointless and can be actively confusing.
  • Exclude faceted filter URLs. Links with query strings like ?filter_color=red&orderby=price multiply endlessly and will flood your queue.
  • Keep the rate limit modest. Store pages are heavy. Start around 10–20 URLs per minute and raise it only while watching your server.
  • Warm mobile too. Most shopping traffic is on phones, and some setups cache mobile separately. See Advanced warming.

Do not warm pages that carry a session

Cart, checkout, and account pages are personalised. Some caching setups will happily store whatever the warmer received, which risks serving one visitor's page to another. Always exclude them.

Warming after you publish

Publishing a post usually purges caches, which leaves the new page — the one about to get the most traffic — cold. Two ways to handle it:

  • Let the schedule catch it. If your warmer runs hourly with sitemaps on, the new URL is picked up on the next pass.
  • Trigger it immediately with a webhook call, which is instant rather than up to an interval later.
Warm right after publishing
bash
curl -X POST https://cacherocket.com/api/wordpress/triggerWarm \
  -H 'Content-Type: application/json' \
  -d '{"publicKey":"YOUR_KEY","secretKey":"YOUR_SECRET","hostname":"example.com"}'

More patterns, including warming an explicit list of URLs, are in Deploy triggers.

Staying up to date

The download link always serves the newest GitHub release, and all releases are listed publicly. Update as you would any WordPress plugin, and — as with every plugin update — take a backup first if the site is business-critical.

Common problems

The plugin says my API keys are invalid.
Re-copy both keys from Account → Account, watching for leading or trailing spaces. If the secret was never revealed, or a newer pair has since been generated, the old one no longer works — generate a fresh pair and paste both again.
Warmers show up but never run.
Check that the warmer is Active and that the site's hostname is Verified. An unverified hostname blocks every run, whether started from the plugin or the dashboard.
My site broke after enabling the local page cache.
Almost certainly a conflict with another caching plugin. Disable Cache Rocket's local caching features and keep your existing cache, or disable the other plugin's caching. Remote warming works fine either way.
Logged-in users see the wrong content.
A page cache is serving a cached page to logged-in visitors. Configure your cache to bypass logged-in sessions, and make sure the warmer is not sending session cookies for pages that should be anonymous.
Do I need the plugin for Cache Rocket to work?
No. Website warmers work over plain HTTP against public URLs. The plugin adds wp-admin management and optional local optimisation.