Force Refresh
View on WordPress.orgScores higher than 69% of indexed plugins
About
Force Refresh lets you request page refreshes for visitors viewing your site, whether you want to refresh the whole site or a single page.
What It Does
Force Refresh gives site administrators a manual control to push a full or page-specific refresh request to visitors currently viewing the site. In practice, an editor clicks a button in wp-admin and every browser session loading that URL reloads on demand. It works well as a simple trigger for sites where the underlying content changes faster than a typical cache would serve.
Who It's For
This plugin is built for operators of live or frequently updated sites such as breaking news desks, sports scoreboards, live event coverage, live auctions, and stock or weather tickers where editors need a quick way to force currently watching visitors to see the newest content without waiting for cache TTLs to expire. It suits small teams that do not need a full live-reload framework and just want a button to push a refresh.
Who Should Skip It
If your site is mostly static content, a blog, a portfolio, or any page where visitors do not need second-by-second updates, this plugin adds nothing useful and may cause unnecessary reloads that hurt the experience. Anyone already running a robust frontend live-update system, like a WebSocket-based solution or a headless stack with reactive data, will also not benefit from forcing full page reloads.
The Bottom Line
Force Refresh is a focused, well-maintained utility that does one thing and does it cleanly, which is why it earns an overall Quality Score of 78.63/100 despite a small install base. Its perfect rating from a limited pool of 12 users is encouraging but not yet definitive proof of reliability at scale. For the right use case, it is a lightweight, sensible choice; for static sites, it is unnecessary overhead.
Related Plugins
Pick this if your main refresh need is around new comment submissions rather than page-level content updates.
Pick this when you want cache-busting combined with asset optimization rather than a dedicated visitor-facing refresh trigger.
Pick this if you are debugging scheduled tasks, since it addresses cron health rather than on-demand visitor refreshes.
Pick this when you want automatic time-based reloads on the visitor side instead of an editor-pushed manual refresh.