Ezoic
How often does the Ezoic cache refresh?
How can I make content update faster?
Caching essentially means content is stored on a CDN, meaning the Ezoic system does not need to make an external call back to the origin to retrieve content for returning visitors.
The Ezoic system caches a site's static content to improve user experience for web visitors. Caching will typically boost Time to Interactive on a website, which Ezoic has found from testing with thousands of sites has a positive effect upon metrics like Bounce Rate, Engaged Page Views, and Time on Site, and as a result - session revenue for digital publishers.
The cache expiry is configured in seconds with 2592000 (30 days) being the default. The default setting is suitable for most sites and typically need not be changed, however we recommend that you install Ezoic's WordPress plugin to automate clearing your site's cache whenever you make changes: https://support.ezoic.com/kb/article/how-can-i-set-up-the-ezoic-wordpress-plugin-for-cdn-management. This often provides the best balance between cache refresh and site speed for web users.
You may have pages or directories that are updated very frequently - such as a news feed or posts page. In these circumstances you would want this page to update more quickly than 24 hours.
There are a few things you can do:
1. A cache update function is built into the UI to allow you to to force an update if significant changes to content have been made and to see changes reflect in the site variants quickly. You can clear the cache by URL within the Ezoic caching app to force the content to update:
2. You could set a page level rule which tells the Ezoic system to cache this page or directory for a shorter amount of time. Please note if this URL is the homepage this is represented by a forward slash like this:
3. You could exclude the URL from Ezoic caching so that the caching for this URL should always default to that specified on the origin server:
We would not recommend adjusting the max cache time for the entire site in most cases as this would impact upon the Time to Interactive and user experience site wide: