Know which layer owns the response
Browser cache, CDN edge cache, reverse proxy, page cache and object cache are separate layers with different purge behavior.
← All tools
Free WordPress Tool
WordPress Cache & CDN Cutover Checker
Plan cache, CDN and reverse-proxy changes when moving a WordPress origin server or changing DNS.
Free to useNo account requiredRuns in your browser
Planning result
Ready
Adjust the inputs to generate a planning recommendation.
Technical explanation
How to interpret this tool before a WordPress migration
Caching can make a migration look successful or broken for the wrong reason. A CDN may continue serving old content after the origin changes, while a stale object cache can preserve data assumptions from the previous server. Treat cache invalidation as part of cutover rather than an afterthought.
Update the origin deliberately
When Cloudflare or another proxy sits in front, confirm whether you are changing public DNS, the proxied origin, a load balancer or only server-side routing.
Purge after the right event
Purging too early can simply refill caches from the old origin. Align cache invalidation with the actual production switch.
Practical questions
Should I disable CDN during migration?
Not always. Sometimes keeping the proxy active reduces visible DNS change, but the origin configuration must be understood.
Can stale cache hide errors?
Yes. Cached HTML can look healthy even if dynamic requests or the new origin are failing.
What should I test after purge?
Anonymous pages, logged-in behavior, cart/checkout where relevant, assets, redirects, headers and origin/server logs.