Ezoic's caching is available to publishers on nameserver or Cloudflare integration. It serves your site's static content from a global CDN, reducing load times for visitors around the world. This article covers how to enable and configure caching, clear cached content, create exclusion rules, and verify that caching is active.

Step 1: Enable Caching

1. In your Ezoic dashboard, navigate to Settings > Caching.
2. Click Enable Caching.

Step 2: Set Cache Duration

By default, Ezoic's caching respects the maximum age cache headers set by your origin server. If no maximum age is specified, pages are cached for 30 days.

To set a custom cache duration:

1. Scroll to the Advanced Settings section of the Caching tab.
2. Enter your desired duration in seconds under Default Cache Age. 
3. Click Save.

To override the cache headers set by your origin server entirely, enable Override Cache Control Headers in Advanced Settings.

Note: Enabling Override Cache Control Headers can break site layouts if your site depends on specific cache headers. Test after enabling.

Step 3: Manually Clear the Cache

To clear the entire site:

1. In the Caching section, click Clear All under Clear All Caching.

To clear a single URL:

1. Enter the URL in the Clear cache by URL field and click Clear For URL.

To clear multiple specific URLs:

1. Enter each URL in the Clear cache by multiple URLs field and click Clear for URLs.

Step 4: Create Exclusion Rules

To prevent specific pages, directories, URL parameters, or cookies from being cached:

1. In the Caching section, scroll to Advanced Settings and click the Exclusion Rules tab.
2. Click Create New Rule.
3. Select your Rule Target (page, directory, URL parameter, or cookie).
4. Enter the value to be excluded.
5. Click Save.

Step 5: Verify Caching is Active

To confirm caching is working on your site:

1. Open Chrome and press F12 to open Developer Tools.
2. Click the Network tab.
3. Load or refresh a page on your site.
4. Click your domain name in the list of requests (typically near the top).
5. Select the Headers tab and look for the x-ezoic-cdn response header.

The header value indicates the caching status:

• Hit — the page is being served from Ezoic's cache
• Miss — the page was not served from cache
• Bypass — caching is active but this URL has been excluded

If the x-ezoic-cdn header is absent, caching is likely disabled. Confirm it is enabled at Settings > Caching.

Low or 0% Cache Hit Rate

A low cache hit rate is most commonly caused by other caching plugins or third-party CDNs interfering with Ezoic's caching.

If you are using a third-party CDN (e.g., Cloudflare in front of your own account, WP Rocket, or similar), we recommend switching to JavaScript integration and allowing your third-party CDN to handle caching directly. This is Ezoic's recommended integration method and avoids conflicts between competing caching layers. See the JavaScript integration guide for instructions.

If you are not using a third-party CDN and still seeing a low hit rate, disable any caching plugins on your site (e.g., WP Super Cache, W3 Total Cache), then enable the following in the Caching section under Advanced Settings:

• Force Caching by Device Type — ON
• Override Cache Control Headers — ON
• Ignore Cache-Control: no-cache — ON

Note: Allow time after activating these settings before assessing the cache hit rate. It takes time to build up cached content across Ezoic's CDN.

Consistent Cache Misses

If caching is enabled but you are consistently seeing misses in the x-ezoic-cdn header, check whether any exclusion rules are unintentionally covering the URLs you are testing.

Does Ezoic's caching work with JavaScript integration?

No. Ezoic's caching is only available for sites on nameserver or Cloudflare integration. JS-integrated publishers should use a third-party CDN. See Optimizing Site Speed with Ezoic for guidance.

Will enabling Override Cache Control Headers cause problems?

It can, if your site relies on specific cache headers for certain pages. Enable it, then test your site layout and functionality — particularly on pages with dynamic content or user authentication.

My DNS records appear to have changed since integrating via nameservers — is that normal?

Yes. When integrated via nameservers, Ezoic acts as a proxy between your visitors and your origin server. DNS records will point to Ezoic's servers rather than your host's servers — this is expected behavior and does not affect your hosting setup. See Cloud Integration — DNS Management and Troubleshooting for more detail.

If you need further assistance with caching, please log in via support.ezoic.com to make use of our dedicated resources for support. We're here to help!