by
Per Søderlind
1 (0 reviews)
Cache Tags for Cloudflare
Precise Cloudflare cache purging for WordPress: adds Cache-Tag headers and purges only affected posts, pages, and terms.
Cache Tags for Cloudflare ranks #57,797 among WordPress.org plugins with 1+ active installations, is #890 of 1,528 in the Performance category, a 1/5 rating from 0 reviews, and was last updated Jul 21, 2026. Data from WordPress.org, refreshed twice daily — see methodology.
Tested up to WP 7 (Current: 7.1.1)
v1.3.1
Current Version v1.3.1
Updated 1 month ago
Last Update on 21 Jul, 2026
Refreshed 8 hours ago
Last Refreshed on
#890 of 1,528 in Performance
Rank
#57,797
+7211 this week
Active Installs
1+
-75%
KW Avg Position
139
—
No change
Downloads
330
+3 today
Support Resolved
0%
—
No change
Rating
20%
Review 1 out of 5
1
(0 reviews)
Next Milestone 10
0+
10+
57,090
Ranks to Climb
-
Growth Needed
8,000,000
Active Installs
Pro
Unlock Exact Install Count
See the precise estimated active installs for this plugin, calculated from real-time ranking data.
- Exact install estimates within tiers
- Track install growth over time
- Milestone progress predictions
Need 8 more installs to reach 10+
Rank Changes
Current
#57,797
Change
Best
#
Downloads Growth
Downloads
Growth
Peak
Upgrade to Pro
Unlock 30-day, 90-day, and yearly download history charts with a Pro subscription.
Upgrade NowReviews & Ratings
1.0
0 reviews
Overall
20%
5
0
(0%)
4
0
(0%)
3
0
(0%)
2
0
(0%)
1
0
(0%)
Track This Plugin
Get detailed analytics, keyword tracking, and position alerts delivered to your inbox.
Start Tracking FreePlugin Details
- Version
- 1.3.1
- Last Updated
- Jul 21, 2026
- Requires WP
- 6.8+
- Tested Up To
- 7
- PHP Version
- 8.3 or higher
- Author
- Per Søderlind
Support & Rating
- Rating
- ★ ☆ ☆ ☆ ☆ 1
- Reviews
- 0
- Support Threads
- 0
- Resolved
- 0%
Keywords
Upgrade to Pro
Unlock keyword rankings, search positions, and detailed analytics with a Pro subscription.
Upgrade NowSimilar Plugins
Adminify – White Label, Admin Menu Editor, Login Customizer
6K+ installs
#2,754
Master Addons for Elementor – Elementor Addons, Widgets, Mega Menu Builder, Popup Builder, Widget Builder & Template Kits
30K+ installs
#1,007
LiteSpeed Cache
7M+ installs
#5
Wordfence Security – Firewall, Malware Scan, and Login Security
5M+ installs
#11
Hostinger Tools
3M+ installs
#20
WP Super Cache
1M+ installs
#38
Speed Optimizer – The All-In-One Performance-Boosting Plugin
1M+ installs
#43
WP Fastest Cache – WordPress Cache Plugin
1M+ installs
#47
WP-Optimize – Cache, Compress images, Minify & Clean database to boost page speed & performance
1M+ installs
#52
Maintenance
1M+ installs
#57
Frequently Asked Questions
Common questions about Cache Tags for Cloudflare
In the Cloudflare dashboard, create a scoped API token (My Profile → API Tokens → Create Token) with the Zone → Cache Purge permission, limited to the zone you want to purge. Your Zone ID is on that zone's Overview page. Add both under Settings → Cache Tags, or define CACHE_TAGS_CF_API_TOKEN and CACHE_TAGS_CF_ZONE_ID in wp-config.php.
No extra setup is required. Cloudflare reads the Cache-Tag header the plugin adds automatically, and the plugin purges by tag through the API. Just make sure your site is proxied through Cloudflare (orange-clouded) so responses are cached.
When traffic is proxied through Cloudflare, Cloudflare consumes the Cache-Tag header and strips it before the response reaches visitors. Check it at the origin instead: curl -I https://example.com/sample-post/.
Auto-purge only runs when Auto-purge on changes is enabled and valid credentials are saved and verified. It also only fires for public post types/taxonomies on real content changes — draft-only edits, comments, menu/widget/theme changes, and plugin/core updates are ignored. For those, use the Purge tab, WP-CLI, or a purge hook. Enable debug logging on the Settings tab to see what was purged.
Yes. Use the Purge tab (by post type, taxonomy term, everything, or raw tags), the wp cache-tags purge WP-CLI command, or the programmatic purge hooks (cache_tags_for_cloudflare/purge_post, /purge_terms, /purge_all, and more). See the Developer guide.
Yes. Every tag is scoped to the current blog (b{blog_id}), so purges on one subsite never affect another. Each subsite uses its own Cloudflare credentials. "Purge everything" (the Purge tab, --all, or purge_all) is also scoped to the current subsite; to purge every site sharing the same Cloudflare zone at once, purge the global content tag with wp cache-tags purge --tags=content.
No. Requests to Cloudflare contain only your API token, Zone ID, and the list of cache tags to purge — never post content, personal data, or visitor information. See the External services section above for the exact endpoints.
