Cloudflare Cache Setup
Most sites proxy through Cloudflare with nothing cached, so the origin still handles every visit. I configure cache rules, APO, and exclusions for your exact stack, then prove it with before and after numbers.
500M+ lifetime search impressions, served from behind Cloudflare on my own sites
Replies within 24 hours, usually the same day
Work delivered for, or alongside, teams at:
What it costs
The setup is tested on staging before it touches production, because a misconfigured CDN is worse than no CDN. You get the config, the purge automation, and a report you can actually read.
Cloudflare plan fees, if any, are billed by Cloudflare; most sites do fine on the free plan.
All prices include GST.
How this runs
I review your DNS, page rules, cache headers, and current hit ratio. Most problems announce themselves within the first half hour: proxied, but nothing cached.
You leave with: a plain diagnosis of the current setup.
I map which URLs get full-page caching, which need bypass rules, and which cookies must break the cache. This map is the real work; the clicking comes after.
You leave with: a cache map for your exact stack.
Cache rules, APO, exclusions, and purge hooks go in, tested on staging first. Your caching plugin gets aligned so the two layers cooperate instead of fighting.
You leave with: edge caching that’s safe to trust.
I measure TTFB and cache hit ratio from multiple locations, logged in and logged out, and put the numbers side by side with the baseline.
You leave with: proof it worked, not a promise.
The dirty secret of Cloudflare setups is that most of them cache nothing. The orange cloud is on, the marketing feels done, and every single visit still hits the origin.
The real work is the exclusion rules. Getting HTML cached is easy; making sure a logged-in customer never sees someone else’s cart is the part most tutorials skip, and the part I test hardest.
My own sites run behind Cloudflare with APO, so this is the config I live with, not one I read about.
— Gaurav
Before you write in
Not answered here? Ask directly and you will hear back within 24 hours.
₹10,000 fixed for one domain, and the price includes GST. That covers the audit of your current rules, cache and page rule configuration, APO where it fits, cookie exclusions, automated purging, and a before and after report with TTFB and hit-ratio numbers.
Automatic Platform Optimization caches your WordPress HTML at Cloudflare’s edge, so pages load fast for visitors far from your server. For sites with a spread-out audience it’s usually worth its small monthly fee. If your audience sits next to your server, I’ll tell you to skip it.
Not with proper exclusions, and this is exactly where DIY setups go wrong. Carts, checkout, accounts, and admin get bypass rules keyed on cookies, so dynamic pages stay dynamic while everything public serves from the edge. I test both states before calling it done.
For most sites, yes. The free plan plus correct configuration delivers most of the gain, and APO is the one paid add-on that regularly earns its cost for WordPress. I only recommend paid features that will visibly move your numbers.
No, they work as layers: Cloudflare caches at the edge, your plugin handles page generation at the origin. Configured together they compound; configured carelessly they serve stale pages and fight over purging. Aligning the two is part of the setup.
About me
Everything I would put on your site is running on mine first.
Care clients get the same stack I trust with my own traffic: GT Performance, Cloudflare, Redis, Hetzner.
I was a teacher before I was a developer. I taught mathematics to competitive-exam students, which is why I explain hard things plainly instead of hiding behind jargon.
What I am actually good at is the join: technical SEO, fast front-ends, and content treated as one system instead of three vendors blaming each other.
I’ll look at what Cloudflare is actually doing for it right now and reply with what a proper setup would change, plus the start date.
Replies within 24 hours, usually the same day
