Before Tiered Caching was implemented, priming the cache on CloudFlare with APO was pretty useless since you would’ve needed to prime every single CloudFlare server in every country in the world. So I’ve always primed my web server’s cache, but never the CloudFlare cache.
But now that Tiered Caching has been implemented, my understanding is that cached data can be passed along inside the CloudFlare network without having to ever reach the origin, except on the first Pageview. So if that is true, it means that we could now prime the cache on a single CloudFlare server (let’s say the closest one to my web server), and whenever a user in another location would access a page on my website, the first CloudFlare server would look to see if there is already a cached version of the page somewhere in its network (in this case, it would be true), and it would then populate the cache of the server in the new location, which would prevent a round trip to my own web server.
I hope my question is clear @yevgen.
If this works like I think it is, this is pretty awesome since bots (particularly Googlebot) will get even quicker responses than before when a page is not primed on CloudFlare. This might in turn be good for SEO.