Lookit Cloudflare Cache Purge for WordPress

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.

What happens when you purge everything 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:

Purge This URL — clears only the page you are currently on or editing

Purge Entire Site — full cache purge when you genuinely need it (with a confirmation dialog so it is never accidental)

Or enter any URL — type any URL on the site and purge it directly, without navigating to that page first

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.