lookitdesign

<p>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.</p>
<h4>What happens when you purge everything</h4>
<p>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 <em>after</em> 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 <em>next</em> visitor to the same page gets the fast, cached copy.</p>
<p>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.</p>
<p><strong>Lookit® Cloudflare Cache Purge gives you granular control.</strong> 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.</p>
<p>From any page in WordPress — whether you are editing a post in wp-admin or viewing the live site while logged in — a lightweight <strong>CF Purge</strong> menu (☁) appears in the admin bar with three options:</p>
<ul>
<li><strong>Purge This URL</strong> — clears only the page you are currently on or editing</li>
<li><strong>Purge Entire Site</strong> — full cache purge when you genuinely need it (with a confirmation dialog so it is never accidental)</li>
<li><strong>Or enter any URL</strong> — type any URL on the site and purge it directly, without navigating to that page first</li>
</ul>
<p>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.</p>
<h4>Why this plugin exists</h4>
<p>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.</p>
<p>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.</p>
<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 <strong>Zone / Cache Purge / Purge</strong> and <strong>Zone / Zone / Read</strong> 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 <strong>Settings <span aria-hidden="true" class="wp-exclude-emoji">→</span> CF Purge Settings</strong></li>
<li>Paste your Cloudflare API Token and Zone ID</li>
<li>Click <strong>Test Cloudflare Connection</strong> to verify</li>
<li>The <strong>☁ CF Purge</strong> menu will now appear in your admin bar</li>
</ol>
<h4>Creating a Scoped API Token</h4>
<p>In your Cloudflare dashboard: <strong>My Profile <span aria-hidden="true" class="wp-exclude-emoji">→</span> API Tokens <span aria-hidden="true" class="wp-exclude-emoji">→</span> Create Token <span aria-hidden="true" class="wp-exclude-emoji">→</span> Create Custom Token</strong></p>
<p>Set these permissions:</p>
<ul>
<li>Zone / Cache Purge / Purge</li>
<li>Zone / Zone / Read</li>
</ul>
<p>Set Zone Resources to the specific zone for this site. This keeps the token scoped and secure.</p>
<p><strong>Do not use your Global API Key.</strong> A scoped token is always the correct approach.</p>
<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>
<p><em>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.</em></p>
<h3>External Services</h3>
<p>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.</p>
<p><strong>What data is sent and when:</strong></p>
<p>When you trigger a cache purge (manually or via the Test Connection button), this plugin sends the following data to Cloudflare’s API:</p>
<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>
<p>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>).</p>
<p>This service is provided by Cloudflare, Inc.:</p>
<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.

webheadcoder

<p>W3 Total Cache and WP Super Cache are great caching plugins, but they do not know when a widget is updated.  WPEngine is the best place to host your WordPress installation, but their caching system is no smarter when it comes to updating widgets and menus.  I created this plugin because my website did not see any changes when saving widgets or menus using these caching systems.  Clear Cache For Me will purge ALL your cache each time you do a save without having to press an additional button.  It may be overkill, which may be why it’s not built in, but some people need simplicity.</p>
<p>In addition to clearing those pesky caching engines, Clear Cache for Me can force your browser to reload your current theme’s CSS and JS files.  I modify my theme’s CSS and JS files every so often and always have trouble with the browser not getting the latest version.  So now after clicking on the “Clear Cache Now!” button on the dashboard the browser will be forced to reload the current theme’s CSS and JS files.  If you do not click the “Clear Cache Now!” button, the browser will cache the CSS and JS files like it normally does.</p>
<p>The popular Qode themes has a options to set your own custom CSS and JS.  Sometimes you may not see your changes for a long while because your browser is trying to get the cached file.  Whenever you save your Qode’s options, the CSS and JS files will be forced to reload in the browser on the public side.</p>
<p>Works with the following caching plugins:</p>
<ul>
<li>Autoptimize</li>
<li>Breeze Cache</li>
<li>Cache Enabler</li>
<li>Cloudflare</li>
<li>GoDaddy Cache</li>
<li>Kinsta Cache</li>
<li>LiteSpeed Cache</li>
<li>Elementor (CSS cache)</li>
<li>Premium Addons for Elementor</li>
<li>SiteGround SuperCacher</li>
<li>Super Page Cache</li>
<li>WP Fastest Cache</li>
<li>WP Optimize Cache</li>
<li>WP Rocket</li>
<li>WP Super Cache</li>
<li>W3 Total Cache</li>
<li>WPEngine Cache</li>
</ul>
<p>Clears all cache for following actions (requires a caching system above to be active):</p>
<ul>
<li>When Widgets are saved.</li>
<li>When Customizer is saved.</li>
<li>When Menus are saved.</li>
<li>When a fields in Advanced Custom Fields are saved.</li>
<li>When a Contact Form 7 form is saved.</li>
<li>When a Formidable Form form is saved.</li>
<li>When WooThemes settings are saved.</li>
<li>When NextGen Gallery albums and galleries are updated (beta – may not clear cache on all actions).</li>
<li>When Qode options are saved this plugin forces browsers to reload the custom css and custom js.</li>
<li>When a WP Forms forms or settings are saved.</li>
<li>When WooCommerce settings are saved. (Cache should already be clearing when products are saved.)</li>
<li>When settings from the Insert Headers and Footers plugin by WPBeginner are saved.  </li>
<li>When Settings from a settings page is saved.  This includes settings from WordPress core, Yoast SEO, and most other plugins using the Settings API.</li>
<li>When WordPress is updated.</li>
<li>When plugins are updated, activated, and deactivated.</li>
<li>When WordPress, plugins, and themes are automaticallly updated.</li>
</ul>
<p><a href="https://webheadcoder.com/clear-cache-for-me/" rel="nofollow ugc">See the plugin’s homepage for more details</a>.</p>
<p>Note:  Since some caching systems run in the <code>shutdown</code> hook, this plugin also runs in that hook.  This means if PHP does not have enough time, some code including any hooks within the <code>ccfm_clear_cache_for_all()</code> function are not guaranteed to run.  If you need code to run, consider using the <code>ccfm_clear_cache_for_me_setup</code> hook.</p>
<p>Some plugins may have “auto purge” (like Cloudflare), but it doesn’t cover all the items this plugin covers.</p>
<h3>Developer Options</h3>
<h4>ccfm_supported_caching_exists</h4>
<p>Use this filter to determine if this plugin should do anything including showing the button on the dashboard.  Return true if a caching system is supported.<br />
Default: True if any of the supported caching systems is active.<br />
See Example 1 below.</p>
<h4>ccfm_admin_init or ccfm_init_actions</h4>
<p>Use this action to add hooks when cache is to be cleared.  Or do any other setup activity.</p>
<h4>ccfm_clear_cache_for_me_before</h4>
<p>Use this action to clear cache from an unsupported caching system before the default caching systems clear their cache.</p>
<h4>ccfm_clear_cache_for_me</h4>
<p>Use this action to clear cache from an unsupported caching system after the default caching systems clear their cache.</p>
<h4>Example</h4>
<p>If you were using an unsupported caching system you’ll need to identify the caching plugin’s class or function which clears the cache.  As an example, if the unsupported caching system called the <code>MyOtherCache::clear_all()</code> function, you would use the following code to get this plugin to clear the cache.</p>
<pre><code><?php
function my_other_cache_enable( $return = false ) {
    if ( class_exists( 'MyOtherCache' ) )
        return true;
    return $return;
}
add_filter('ccfm_supported_caching_exists', 'my_other_cache_enable');

function my_other_cache_clear() {
    if ( my_other_cache_enable() )
        MyOtherCache::clear_all();
}
add_action('ccfm_clear_cache_for_me', 'my_other_cache_clear');
</code></pre>


Clear Cache for Me

Purges cache on WPEngine, W3TC, WP Super Cache, WP Fastest Cache when widgets, menus, settings update.  Forces browsers to reload CSS and JS files.

Lookit Cloudflare Cache Purge vs Clear Cache for Me