[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fkL2j3yc1UdspJnLwho8KfaLJZrVuwFIViTIXbATwz0c":3},{"slug":4,"display_name":4,"profile_url":5,"plugin_count":6,"total_installs":7,"avg_security_score":8,"avg_patch_time_days":9,"trust_score":10,"computed_at":11,"plugins":12},"lookitdesign","https:\u002F\u002Fprofiles.wordpress.org\u002Flookitdesign\u002F",2,40,100,30,94,"2026-08-29T05:16:36.436Z",[13,35],{"slug":14,"name":15,"version":16,"author":4,"author_profile":5,"description":17,"short_description":18,"active_installs":9,"downloaded":19,"rating":20,"num_ratings":20,"last_updated":21,"tested_up_to":22,"requires_at_least":23,"requires_php":24,"tags":25,"homepage":31,"download_link":32,"security_score":8,"vuln_count":20,"unpatched_count":20,"last_vuln_date":33,"fetched_at":34},"lookit-cf-purge","Lookit Cloudflare Cache Purge","1.0.0","\u003Cp>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.\u003C\u002Fp>\n\u003Ch4>What happens when you purge everything\u003C\u002Fh4>\n\u003Cp>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 \u003Cem>after\u003C\u002Fem> 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 \u003Cem>next\u003C\u002Fem> visitor to the same page gets the fast, cached copy.\u003C\u002Fp>\n\u003Cp>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.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Lookit® Cloudflare Cache Purge gives you granular control.\u003C\u002Fstrong> 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.\u003C\u002Fp>\n\u003Cp>From any page in WordPress — whether you are editing a post in wp-admin or viewing the live site while logged in — a lightweight \u003Cstrong>CF Purge\u003C\u002Fstrong> menu (☁) appears in the admin bar with three options:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>Purge This URL\u003C\u002Fstrong> — clears only the page you are currently on or editing\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Purge Entire Site\u003C\u002Fstrong> — full cache purge when you genuinely need it (with a confirmation dialog so it is never accidental)\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Or enter any URL\u003C\u002Fstrong> — type any URL on the site and purge it directly, without navigating to that page first\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>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.\u003C\u002Fp>\n\u003Ch4>Why this plugin exists\u003C\u002Fh4>\n\u003Cp>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.\u003C\u002Fp>\n\u003Cp>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.\u003C\u002Fp>\n\u003Ch4>Features\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Context-aware: automatically detects the URL of the post or page you are editing or viewing\u003C\u002Fli>\n\u003Cli>Works in both the wp-admin editor and the frontend (when logged in)\u003C\u002Fli>\n\u003Cli>Manual URL field for purging arbitrary URLs without navigating to them\u003C\u002Fli>\n\u003Cli>Full-site purge option with confirmation dialog\u003C\u002Fli>\n\u003Cli>Lightweight — no zone settings, no DNS, no SSL toggles, no bloat\u003C\u002Fli>\n\u003Cli>Secure — uses a scoped API token with minimum required permissions\u003C\u002Fli>\n\u003Cli>Compatible with WP Rocket, the official Cloudflare plugin, and any other caching setup\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Requirements\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>A Cloudflare account with your site’s domain active\u003C\u002Fli>\n\u003Cli>A Cloudflare API Token with \u003Cstrong>Zone \u002F Cache Purge \u002F Purge\u003C\u002Fstrong> and \u003Cstrong>Zone \u002F Zone \u002F Read\u003C\u002Fstrong> permissions\u003C\u002Fli>\n\u003Cli>Your Cloudflare Zone ID (found on the domain’s Overview page in the Cloudflare dashboard)\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Setup\u003C\u002Fh4>\n\u003Col>\n\u003Cli>Install and activate the plugin\u003C\u002Fli>\n\u003Cli>Go to \u003Cstrong>Settings \u003Cspan aria-hidden=\"true\" class=\"wp-exclude-emoji\">→\u003C\u002Fspan> CF Purge Settings\u003C\u002Fstrong>\u003C\u002Fli>\n\u003Cli>Paste your Cloudflare API Token and Zone ID\u003C\u002Fli>\n\u003Cli>Click \u003Cstrong>Test Cloudflare Connection\u003C\u002Fstrong> to verify\u003C\u002Fli>\n\u003Cli>The \u003Cstrong>☁ CF Purge\u003C\u002Fstrong> menu will now appear in your admin bar\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Ch4>Creating a Scoped API Token\u003C\u002Fh4>\n\u003Cp>In your Cloudflare dashboard: \u003Cstrong>My Profile \u003Cspan aria-hidden=\"true\" class=\"wp-exclude-emoji\">→\u003C\u002Fspan> API Tokens \u003Cspan aria-hidden=\"true\" class=\"wp-exclude-emoji\">→\u003C\u002Fspan> Create Token \u003Cspan aria-hidden=\"true\" class=\"wp-exclude-emoji\">→\u003C\u002Fspan> Create Custom Token\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>Set these permissions:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Zone \u002F Cache Purge \u002F Purge\u003C\u002Fli>\n\u003Cli>Zone \u002F Zone \u002F Read\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Set Zone Resources to the specific zone for this site. This keeps the token scoped and secure.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Do not use your Global API Key.\u003C\u002Fstrong> A scoped token is always the correct approach.\u003C\u002Fp>\n\u003Ch4>Documentation and support\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Full documentation: https:\u002F\u002Flookitdesign.com\u002Fsoftware\u002Fcloudflare-cache-purge\u002F\u003C\u002Fli>\n\u003Cli>Support: https:\u002F\u002Flookitdesign.com\u002Fcloudflare-purge-support-form\u002F\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cem>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.\u003C\u002Fem>\u003C\u002Fp>\n\u003Ch3>External Services\u003C\u002Fh3>\n\u003Cp>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.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>What data is sent and when:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>When you trigger a cache purge (manually or via the Test Connection button), this plugin sends the following data to Cloudflare’s API:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Your Cloudflare Zone ID (to identify which zone to purge)\u003C\u002Fli>\n\u003Cli>Your Cloudflare API Token (for authentication)\u003C\u002Fli>\n\u003Cli>The specific URL(s) to purge, or a full-site purge flag\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>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 (\u003Ccode>https:\u002F\u002Fapi.cloudflare.com\u002Fclient\u002Fv4\u003C\u002Fcode>).\u003C\u002Fp>\n\u003Cp>This service is provided by Cloudflare, Inc.:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Terms of Service: https:\u002F\u002Fwww.cloudflare.com\u002Fterms\u002F\u003C\u002Fli>\n\u003Cli>Privacy Policy: https:\u002F\u002Fwww.cloudflare.com\u002Fprivacypolicy\u002F\u003C\u002Fli>\n\u003C\u002Ful>\n","Granular Cloudflare cache control from the admin bar — purge a single page, any URL, or the entire site, right from wp-admin.",147,0,"2026-06-12T04:58:00.000Z","7.0.2","5.9","7.4",[26,27,28,29,30],"admin-bar","cache","cdn","cloudflare","purge","","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Flookit-cf-purge.1.0.0.zip",null,"2026-07-22T17:31:50.256Z",{"slug":36,"name":37,"version":16,"author":4,"author_profile":5,"description":38,"short_description":39,"active_installs":40,"downloaded":41,"rating":20,"num_ratings":20,"last_updated":42,"tested_up_to":22,"requires_at_least":23,"requires_php":24,"tags":43,"homepage":46,"download_link":47,"security_score":8,"vuln_count":20,"unpatched_count":20,"last_vuln_date":33,"fetched_at":34},"lookit-cache-purge-for-sucuri","Lookit Cache Purge for Sucuri","\u003Cp>Sucuri’s Website Firewall caches your pages on its global edge network. That caching makes your site fast, but it also means that when you update a page, visitors may continue to see the old version for up to 2 minutes — or longer.\u003C\u002Fp>\n\u003Cp>Sucuri’s dashboard has a “Clear Cache – Per File” feature that lets you purge a single URL from the edge cache. But to use it, you have to leave WordPress, log into the Sucuri WAF dashboard, navigate to Performance, and paste the path manually. Meanwhile, tools like WP Rocket’s Sucuri add-on only support full-site cache clearing — the nuclear option.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Lookit® Cache Purge for Sucuri fills this gap.\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>A clean “🛡 Sucuri Cache Purge” menu appears in your WordPress admin bar with two options:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>Purge This URL\u003C\u002Fstrong> — clears only the page you are currently editing or viewing\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Purge Entire Site\u003C\u002Fstrong> — full cache purge when you need it (with a confirmation dialog)\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>The plugin uses Sucuri’s documented Website Firewall API. It does not touch any other Sucuri settings — no WAF rules, no SSL, no security options. Cache purge only.\u003C\u002Fp>\n\u003Ch4>Why This Plugin Exists\u003C\u002Fh4>\n\u003Cp>Sucuri’s own dashboard can clear a single URL, but there’s no easy way to do it from inside WordPress while you’re editing content. WP Rocket’s Sucuri add-on only offers full-site purging. The official Sucuri WordPress plugin is a security tool, not a cache-clearing tool. This plugin does exactly one thing: give you a button in the WordPress admin bar to purge a URL from Sucuri’s edge cache — without leaving the editor.\u003C\u002Fp>\n\u003Ch4>Features\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Context-aware: automatically detects the URL of the post or page you are editing or viewing\u003C\u002Fli>\n\u003Cli>Works in both wp-admin (post editor) and on the frontend (when logged in as an administrator)\u003C\u002Fli>\n\u003Cli>Full-site purge option with confirmation dialog\u003C\u002Fli>\n\u003Cli>Built-in rate limiting: 6 purges per minute per user, to prevent accidental hammering\u003C\u002Fli>\n\u003Cli>Handles Sucuri’s API rate limit (HTTP 429) gracefully, with clear retry-wait messages\u003C\u002Fli>\n\u003Cli>Lightweight — no zone settings, no DNS, no security toggles, no bloat\u003C\u002Fli>\n\u003Cli>Secure — uses Sucuri’s documented API with a scoped API Key\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Requirements\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>A Sucuri Website Firewall (WAF) account with your site connected\u003C\u002Fli>\n\u003Cli>The “API Key (for plugin)” value from your Sucuri dashboard \u003Cspan aria-hidden=\"true\" class=\"wp-exclude-emoji\">→\u003C\u002Fspan> API \u003Cspan aria-hidden=\"true\" class=\"wp-exclude-emoji\">→\u003C\u002Fspan> API Details\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Setup\u003C\u002Fh4>\n\u003Col>\n\u003Cli>Install and activate the plugin\u003C\u002Fli>\n\u003Cli>Go to \u003Cstrong>Settings \u003Cspan aria-hidden=\"true\" class=\"wp-exclude-emoji\">→\u003C\u002Fspan> Sucuri Cache Purge\u003C\u002Fstrong>\u003C\u002Fli>\n\u003Cli>Paste your Sucuri “API Key (for plugin)” — it looks like \u003Ccode>32characters\u002F32characters\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>Save. The \u003Cstrong>🛡 Sucuri Cache Purge\u003C\u002Fstrong> menu will now appear in your admin bar\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Ch4>Important: Static Files Cache Differently\u003C\u002Fh4>\n\u003Cp>Sucuri caches static files — images, CSS, JS, PDFs, fonts — on its edge network for up to 72 hours, regardless of per-URL purging. If you update a stylesheet or an image, a per-URL purge will not be enough. Use “Purge Entire Site” instead, or use versioning (\u003Ccode>?ver=1.2.3\u003C\u002Fcode>) to force browsers to fetch the new version.\u003C\u002Fp>\n\u003Ch4>Important: 2-Minute Propagation\u003C\u002Fh4>\n\u003Cp>After a successful purge, Sucuri takes up to 2 minutes to fully flush the cache across its global edge network. If you do not see your change immediately, wait two minutes and reload. This is normal Sucuri behavior, not a plugin issue.\u003C\u002Fp>\n\u003Ch4>Documentation and Support\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Full documentation: https:\u002F\u002Flookitdesign.com\u002Fsoftware\u002Fsucuri-cache-purge\u002F\u003C\u002Fli>\n\u003Cli>Support: https:\u002F\u002Flookitdesign.com\u002Fsucuri-purge-support-form\u002F\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cem>Lookit® is a registered trademark of ZENOVA CORP. Sucuri is a trademark of its respective owner (a GoDaddy brand); this plugin is an independent integration and is not affiliated with, sponsored by, or endorsed by Sucuri.\u003C\u002Fem>\u003C\u002Fp>\n\u003Ch3>External Services\u003C\u002Fh3>\n\u003Cp>This plugin connects to the Sucuri Website Firewall (WAF) API to purge cached pages from Sucuri’s global edge network. This connection is required for the plugin’s core function — without it, no cache purging can occur.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>What the service is used for:\u003C\u002Fstrong>\u003Cbr \u002F>\nWhen you trigger a purge (a single URL or the entire site), the plugin sends a request to Sucuri’s WAF API asking it to clear the relevant cache.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>What data is sent, and when:\u003C\u002Fstrong>\u003Cbr \u002F>\nA request is sent to Sucuri only when you click “Purge This URL” or “Purge Entire Site” in the admin bar. Each request includes:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Your Sucuri API Key and API Secret (the combined “API Key (for plugin)” value you enter in the plugin settings), used to authenticate the request\u003C\u002Fli>\n\u003Cli>For a single-URL purge: the path of the page being purged (for example, \u003Ccode>\u002Fabout\u002F\u003C\u002Fcode>)\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>No data about your site’s visitors is collected or transmitted. The plugin does not send any personally identifiable information (PII).\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Service endpoint:\u003C\u002Fstrong> https:\u002F\u002Fwaf.sucuri.net\u002Fapi?v2\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Service provider:\u003C\u002Fstrong> Sucuri (GoDaddy Media Temple, Inc. d\u002Fb\u002Fa Sucuri)\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Terms of Service: https:\u002F\u002Fsucuri.net\u002Fterms\u002F\u003C\u002Fli>\n\u003Cli>Privacy Policy: https:\u002F\u002Fsucuri.net\u002Fprivacy\u002F\u003C\u002Fli>\n\u003C\u002Ful>\n","Granular Sucuri cache purge from the WordPress admin bar. Purge a single URL, or the entire site, without leaving wp-admin.",10,91,"2026-07-14T03:32:00.000Z",[26,27,30,44,45],"sucuri","waf","https:\u002F\u002Flookitdesign.com\u002Fsoftware\u002Fsucuri-cache-purge\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Flookit-cache-purge-for-sucuri.1.0.0.zip"]