lookitdesign

Most Cloudflare integrations for WordPress give you only one option: purge everything. That is the nuclear option, and it is more expensive than it looks.
<h4>What happens when you purge everything</h4>
When you purge the entire cache in Cloudflare, every cached page is cleared at once — but Cloudflare does not rebuild those caches for you. A page is only re-cached after the next time someone requests it. That first request following a purge is a cache miss: it travels all the way back to your origin server, which is slow to render, and that visitor waits for the full render. Only the next visitor to the same page gets the fast, cached copy.
The catch is traffic. Busy pages re-cache almost immediately. But pages that are visited infrequently can sit uncached for hours or even days, and the first person to land on each one pays the slow-render penalty. There is no way inside Cloudflare to warm the cache ahead of time or speed this up — re-caching happens only on demand, page by page, as real traffic trickles in.
Lookit® Cloudflare Cache Purge gives you granular control. Instead of wiping everything and forcing your whole site back to origin speed, you clear only the page you actually changed — and every other page keeps its cache intact.
From any page in WordPress — whether you are editing a post in wp-admin or viewing the live site while logged in — a lightweight CF Purge menu (☁) appears in the admin bar with three options:
<ul>
<li>Purge This URL — clears only the page you are currently on or editing</li>
<li>Purge Entire Site — full cache purge when you genuinely need it (with a confirmation dialog so it is never accidental)</li>
<li>Or enter any URL — type any URL on the site and purge it directly, without navigating to that page first</li>
</ul>
The manual URL field is especially useful for URLs that do not correspond to a standard WordPress post or page — such as custom archive paths, Events Calendar URLs, or other custom post type archives.
<h4>Why this plugin exists</h4>
If you manage WordPress sites on Cloudflare with a caching plugin like WP Rocket, you have likely run into this problem: WP Rocket’s Cloudflare integration only supports full-site purge. The official Cloudflare WordPress plugin is heavyweight and touches your zone settings. Neither gives you a simple, context-aware button to clear just one URL.
This plugin does exactly that — nothing more, nothing less. It connects to Cloudflare via a scoped API token, adds a clean menu to the admin bar, and stays completely out of your Cloudflare zone configuration.
<h4>Features</h4>
<ul>
<li>Context-aware: automatically detects the URL of the post or page you are editing or viewing</li>
<li>Works in both the wp-admin editor and the frontend (when logged in)</li>
<li>Manual URL field for purging arbitrary URLs without navigating to them</li>
<li>Full-site purge option with confirmation dialog</li>
<li>Lightweight — no zone settings, no DNS, no SSL toggles, no bloat</li>
<li>Secure — uses a scoped API token with minimum required permissions</li>
<li>Compatible with WP Rocket, the official Cloudflare plugin, and any other caching setup</li>
</ul>
<h4>Requirements</h4>
<ul>
<li>A Cloudflare account with your site’s domain active</li>
<li>A Cloudflare API Token with Zone / Cache Purge / Purge and Zone / Zone / Read permissions</li>
<li>Your Cloudflare Zone ID (found on the domain’s Overview page in the Cloudflare dashboard)</li>
</ul>
<h4>Setup</h4>
<ol>
<li>Install and activate the plugin</li>
<li>Go to Settings → CF Purge Settings</li>
<li>Paste your Cloudflare API Token and Zone ID</li>
<li>Click Test Cloudflare Connection to verify</li>
<li>The ☁ CF Purge menu will now appear in your admin bar</li>
</ol>
<h4>Creating a Scoped API Token</h4>
In your Cloudflare dashboard: My Profile → API Tokens → Create Token → Create Custom Token
Set these permissions:
<ul>
<li>Zone / Cache Purge / Purge</li>
<li>Zone / Zone / Read</li>
</ul>
Set Zone Resources to the specific zone for this site. This keeps the token scoped and secure.
Do not use your Global API Key. A scoped token is always the correct approach.
<h4>Documentation and support</h4>
<ul>
<li>Full documentation: https://lookitdesign.com/software/cloudflare-cache-purge/</li>
<li>Support: https://lookitdesign.com/cloudflare-purge-support-form/</li>
</ul>
Lookit® is a registered trademark of ZENOVA CORP. Cloudflare is a registered trademark of Cloudflare, Inc.; this plugin is an independent integration and is not affiliated with, sponsored by, or endorsed by Cloudflare.
<h3>External Services</h3>
This plugin connects to the Cloudflare API to purge cached files from the Cloudflare CDN. This is required for the core functionality of the plugin — without it, no cache purging can occur.
What data is sent and when:
When you trigger a cache purge (manually or via the Test Connection button), this plugin sends the following data to Cloudflare’s API:
<ul>
<li>Your Cloudflare Zone ID (to identify which zone to purge)</li>
<li>Your Cloudflare API Token (for authentication)</li>
<li>The specific URL(s) to purge, or a full-site purge flag</li>
</ul>
No visitor data, personal information, or site content is ever transmitted. API credentials are stored in your WordPress database and are only sent directly to Cloudflare’s API endpoint (<code>https://api.cloudflare.com/client/v4</code>).
This service is provided by Cloudflare, Inc.:
<ul>
<li>Terms of Service: https://www.cloudflare.com/terms/</li>
<li>Privacy Policy: https://www.cloudflare.com/privacypolicy/</li>
</ul>

Lookit Cloudflare Cache Purge

Granular Cloudflare cache control from the admin bar — purge a single page, any URL, or the entire site, right from wp-admin.

webreact

This plugin connects your SpinupWP-managed sites to Cloudflare, automatically purging cache when you purge sites, posts, or URLs in SpinupWP. It supports both modern API tokens and legacy API keys for flexible authentication.
Features:
<ul>
<li>Automatic cache purging on SpinupWP site purges</li>
<li>Purge specific URLs from Cloudflare cache</li>
<li>Manual purge button in WordPress admin bar</li>
<li>Support for Cloudflare API tokens (recommended) and legacy API keys</li>
<li>Clean, intuitive settings interface</li>
<li>Full nonce verification for security</li>
<li>PSR-12 compliant code with strict typing</li>
</ul>
<h3>Configuration</h3>
Authentication Type: 
– API Token (Recommended): Modern, scoped authentication method. More secure with granular permissions. 
 – Only requires your API token and Zone ID 
– API Key (Legacy): Original authentication method 
 – Requires email, Zone ID, and global API key
Finding Your Cloudflare Zone ID: 
1. Log in to Cloudflare 
2. Select your domain 
3. In the right sidebar, copy the Zone ID
Creating an API Token: 
1. Go to Cloudflare Profile > API Tokens 
2. Create Token with “Cache Purge” permissions 
3. Copy the token and paste into plugin settings
Using API Key (Legacy): 
1. Go to Cloudflare Profile > API Tokens 
2. Find Global API Key (or create one) 
3. Copy your email and API key to plugin settings
<h3>Security</h3>
This plugin stores Cloudflare credentials in the WordPress options table. Ensure your WordPress installation is properly secured: 
– Use strong admin passwords 
– Keep WordPress and plugins updated 
– Consider using a Web Application Firewall
All API requests use HTTPS and verify SSL certificates. All output is properly escaped and all nonces are verified.
<h3>Support</h3>
For issues or feature requests, please visit the plugin repository or contact Webreact.
<h3>License</h3>
GPLv2 or later

Webreact integration for SpinupWP and Cloudflare

Integrates SpinupWP with Cloudflare for automatic cache purging using API tokens or API keys.

Lookit Cloudflare Cache Purge vs Webreact integration for SpinupWP and Cloudflare