Proxy Cache Purge

How well this listing is tuned to rank in WordPress.org search, on the factors an owner controls. Not popularity, optimization.

Directory rank vs rivals

wp.org popularity rank over time · higher is better · when a rival's line climbs above yours, they've overtaken you

How often this plugin actually ships. A steady rhythm is the maintenance signal a single "last updated" date can't show.

Share of active installs on each version of this plugin · 37% run the current release. Green is the current release; a big slice on older versions is a user base that has stopped updating.

Modeled within the band wp.org reports; tightens as we track daily.

At the current install trend, crossing 50K+ in roughly 422 days.

No paid tier is visible, so we don't put a figure on revenue or sale value: that would be guessing. The install base is a real asset to an acquirer, just not one public data lets us price. The recent download trend is too spiky to read.

1. ★★★★★ manuamaro

   7mo ago

   I had lot of problems with cache but this solved them! Thank you.

   Read on wp.org ↗
2. ★★★★★ Skrlance

   1.3y ago

   The plugin simply works even for all types of cache servers. Only one things bothers me about this plugin is its support for PHP 5.6+ where core itself doesn’t support upto php 7.1 while WordPress recommends using PHP 7.4+. So, this plugin should be compatible with PHP 7.4+. Using newer php code is good for security and performance while deprecated codes might produce venerability!

   Read on wp.org ↗
3. ★★★★★ bandsaw12

   3.0y ago

   Spent most of the day working on getting this working with a remote NGINX reverse proxy. The plug-in keeps complaining about no age header in the response. Google seems to suggest that etags and age headers no longer supported in dynamic content with NGINX. Plug-in help is of no help on what header the plug in is expecting to see in order to work. removed. Will have to keep deleting the cache the old manual way. This topic was modified 2 years, 10 months ago by bandsaw12.

   Read on wp.org ↗
4. ★★★★★ random9q

   3.4y ago

   No complaints, it’s been working perfectly for years. Need it very, very seldom — but when I do need it it works. When I don’t need it? It’s out of the way and doesn’t advertise itself overmuch, like some of the other plugins I’ve used over time.

   Read on wp.org ↗
5. ★★★★★ senatmedia

   3.6y ago

   ОТЛИЧНО, СПАСИБО ВАМ!

   Read on wp.org ↗
6. ★★★★★ Dave Loodts

   4.0y ago

   Thanks for bringing out this plugin! Varnish can be quit “dogged” in it’s caching, this plugin solves it very nicely. 1000% thanks!

   Read on wp.org ↗
7. ★★★★★ rvry

   6.4y ago

   I host my site on a Dreampress host and I’ve been using this plugin for years with success and I was super comfy given the plugin is “Brought to you DreamHost.” However a couple of weeks ago Dreamhost initiated a migration of my site to another server. Ever since then my site has been really slow when post updates have been performed (ie whenever wp_insert_post() is called). AJAX calls and routines would stall for ~30 seconds. After hours and hours debugging my code (custom plugin) it turns out this plugin caused the problem! When you specify a custom IP, and that IP no longer exists, the plugin stalls presumably because it’s trying to connect to the old specified IP. Suggested improvements: 1) The plugin should detect this and spit out an error (to errors.log or ideally to admin console) if proxy connections are taking too long. I’m guessing it does a check when you first set an IP but perhaps it should do a more regular check. 2) Dreamhost operational processes should be modified given the plugin comes from Dreamhost! If Dreamhost choose to migrate someones site, they should check for the existence of this plugin, and either update the custom ip to suit the new host or perform some alternate remediation before migrating and breaking the site. I trust implementing both of these will go a long way to keeping a site operational and be well received by Dreamhost customers.

   Read on wp.org ↗
8. ★★★★★ lars Portman

   7.1y ago

   Don’tneed anyother catching plugin if it’s setup right! This topic was modified 6 years ago by lars Portman.

   Read on wp.org ↗

Recent releases and news for this plugin

1. — Version 5.12.0 Change: The GetPageSpeed Amplify recommendation links (readme + Check Caching results) now point to the dedicated Varnish monitoring landing page for a more relevant first impression. 5.12.0
2. — Version 5.11.1 Security: The manual “Purge Cache (This Page)” action ( vhp_flush_do ) now only purges URLs on this site’s own host, and requires a capability (filter: vhp_manual_purge_capability , default edit_published_posts ) in addi 5.11.1
3. — Version 5.11.0 Fix: Async purge queue self-heals from the stuck full-queue state where vhp_process_purge_queue was silently never re-scheduled. Watchdog re-arms a ghost event when the queue is non-empty and vhp_varnish_last_queue_run i 5.11.0
4. — Version 5.10.0 New: Recommendation for GetPageSpeed Amplify cache monitoring (readme + Check Caching results). 5.10.0
5. — Version 5.9.2 Fix: Corrected @param/@return docblock types on purge_post(), purge_url(), and related methods so they match the values actually passed and returned, removing false IDE and static-analysis warnings (reported by Sjoerd Bo 5.9.2
6. — Version 5.9.1 Update: Tested up to WordPress 7.0 Update: Requires PHP bumped from 5.6 to 7.4 to match WordPress 7.0’s PHP floor. Sites on PHP 5.9.1

Automated install-time checks, tested on PHP 8.1.12 · WP 7.0

Translated into 10 languages, 0 at 90% or more

Growth timeline

Install-tier crossings we have observed, and how long each tier took to outgrow

1. 2026-08-24 50K+ → 40K+ down after 4 days in tier
2. 2026-08-20 40K+ → 50K+ up after 52 days in tier
3. 2026-06-29 40K+ → 50K+ up after 3 days in tier
4. 2026-06-26 50K+ → 40K+ down after 17 days in tier
5. 2026-06-09 40K+ → 50K+ up after 1 days in tier
6. 2026-06-08 50K+ → 40K+ down after 2 days in tier
7. 2026-06-06 40K+ → 50K+ up after 947 days in tier
8. 2023-11-02 50K+ → 40K+ down after 21 days in tier

Competes with

The plugins that solve the same job, ranked by shared tags then reach, closest match first. The letter on the right is each plugin's health grade (A best, F worst).

• Varnish/Nginx Proxy Caching 600+ installs · 4.4★ · 4 shared tags D
• Webglobe Purge Cache 90+ installs · 3.6★ · 4 shared tags D
• Nginx Cache 10K+ installs · 4.3★ · 3 shared tags A
• Purge Varnish Cache 1K+ installs · 4.4★ · 3 shared tags A
• Hestia Nginx Cache 1K+ installs · 4.4★ · 3 shared tags A
• Cache Purge Helper 300+ installs · 4.1★ · 3 shared tags D

Embed this report card

Drop a live Pulse card for Proxy Cache Purge into a readme, a review or a deck. It updates itself.

Proxy Cache Purge: 40K+ active installs, 4.4★ (26 reviews). Plugin Pulse (WP Mayor), as of 2026-08-25. https://plugins.wpmayor.com/plugin/varnish-http-purge