Themeisle Docs

Appearance

Super Page Cache for Cloudflare - Settings Reference ​

This document lists all available settings in the Super Page Cache for Cloudflare plugin, organized by the tab where you'll find them in the plugin's dashboard.

To access the plugin settings, go to Settings > Super Page Cache in your WordPress admin panel.

General ​

These are the main settings you'll see when you first open the plugin.

Enable Disk Page Cache ​

Stores cached copies of your pages directly on your web server. When a visitor requests a page, it can be served instantly from the saved file instead of being generated fresh by WordPress each time. This is also useful as a backup when a page hasn't been cached on Cloudflare yet. If you use another caching plugin (such as WP Rocket or LiteSpeed Cache), make sure to disable its page caching feature to avoid conflicts.

Skip Caching for These Cookies ​

A list of cookie name patterns (one per line) that will prevent a page from being cached. If a visitor's browser sends a request that contains any of these cookies, the page will always be generated fresh. This is important for pages that display personalized content, such as shopping carts or logged-in dashboards. The plugin comes with sensible defaults for popular plugins like WooCommerce, Jetpack, and Easy Digital Downloads.

Prevent the Following URIs to Be Cached ​

A list of page addresses (one per line) that should never be cached. You can use a wildcard (*) to match multiple pages. For example, /my-account* will exclude your account page and all its sub-pages from caching.

Ignore Marketing Parameters (Pro) ​

Increases your cache hit rate by ensuring that common tracking and marketing parameters do not create duplicate cache entries. When enabled, the plugin ignores the listed query parameter keys when building the cache key, so URLs like https://example.com/?utm_source=google and https://example.com/ are treated as the same page. The text area comes pre-filled with common parameters (utm_source, utm_medium, fbclid, etc.) and you can add custom keys — one per line — for any other parameters that do not affect page content. This feature requires the Pro version.

For step-by-step instructions on adding custom parameters, see Bypass Cache for Specific Query Parameters.

Show Advanced Settings ​

Reveals the Advanced tab in the sidebar navigation. The Advanced tab contains detailed options for fine-tuning cache behavior, setting up a preloader, configuring Varnish, and managing logs. Recommended only if you need more granular control.

Cloudflare ​

This tab handles the connection between your WordPress site and your Cloudflare account.

Authentication Mode ​

Choose how the plugin connects to Cloudflare. You can use either an API Key (your global key plus your Cloudflare email) or an API Token (recommended, as it allows you to limit permissions to only what the plugin needs).

Cloudflare Email ​

Your Cloudflare account email address. Required only when using the API Key authentication mode.

Cloudflare API Key ​

Your Cloudflare Global API Key, found in your Cloudflare dashboard under My Profile > API Tokens. Required only when using the API Key authentication mode.

Cloudflare API Token ​

A scoped API Token created in your Cloudflare dashboard. This is the recommended authentication method because you can restrict the token's permissions to only what the plugin needs.

Zone Selection ​

After connecting your Cloudflare account, you'll be prompted to select which domain (zone) the plugin should manage. If your Cloudflare account has multiple domains, pick the one that matches this WordPress site.

Enable Cloudflare CDN & Caching ​

The core toggle that activates edge caching on Cloudflare. When enabled, the plugin creates a Cache Rule on Cloudflare so that your pages are served from the nearest Cloudflare data center to your visitors, instead of from your web server. You must connect your Cloudflare account and select a zone before this option appears.

Advanced ​

This tab only appears when you enable Show advanced settings on the General tab. It is divided into several sections.

Cache ​

Use cURL ​

Changes how the plugin generates cached pages. By default, it uses WordPress's built-in advanced-cache.php drop-in. Enabling cURL may take slightly longer to generate the cache but improves compatibility with other performance plugins.

Cache Lifespan (seconds) ​

How long cached pages are stored on your server's disk before they expire. Set to 0 for no expiration (pages stay cached until they are explicitly purged).

Save Response Headers ​

Saves the HTTP response headers alongside the cached HTML. This can be useful if your site relies on custom headers. Note that cache-control, set-cookie, and X-WP-CF-Super-Cache headers are never saved.

Don't Cache 4xx / 5xx Responses ​

Prevents error pages (like "404 Not Found" or "500 Server Error") from being cached. This is enabled by default so that temporary errors don't get served to visitors from the cache.

Prevent Caching URLs Without Trailing Slash ​

Skips caching for URLs that don't end with a /. This helps avoid serving duplicate cached versions of the same page (e.g., /about vs /about/).

Auto-Purge Cache on Comment Activity ​

Automatically clears the cache for a post when someone leaves a new comment, or when a comment is approved or deleted. This ensures visitors always see the latest comment count and content.

Auto-Purge on Updates ​

Automatically clears the entire cache whenever a plugin, theme, or WordPress core update completes.

Strip Response Cookies ​

Removes cookies from server responses on pages that should be cached. Cloudflare won't cache a response that contains cookies unless they are stripped out. Only enable this if you're sure the cookies aren't essential for your site to function properly.

Overwrite the Cache-Control Header Using Web Server Rules ​

Writes rules into your .htaccess file to override cache-control headers set by other plugins. This is useful if another performance plugin is sending headers that conflict with Cloudflare caching. Works automatically on Apache; for Nginx, you'll need to manually add the rules (instructions are provided in the plugin).

Purge HTML Pages Only ​

When purging the cache, only clears cached HTML pages instead of the entire cache (which includes static assets like images, CSS, and JavaScript). This is faster and avoids unnecessarily clearing assets that rarely change.

Disable Cache Purging Using Queue ​

By default, the plugin waits 10 seconds before executing a cache purge to batch multiple rapid events into a single request. Enable this to purge immediately instead. This can be useful if you notice issues with WordPress scheduled events.

Don't Cache the Following Dynamic Contents ​

A set of checkboxes that let you exclude specific types of WordPress pages from being cached:

  • 404 Page - Error pages (enabled by default)
  • Single Posts - Individual blog posts
  • Pages - Static pages
  • Front Page - Your site's designated front page
  • Home - Your blog posts index page
  • Archives - Date-based and other archive pages
  • Tags - Tag archive pages
  • Categories - Category archive pages
  • Feeds - RSS/Atom feeds (enabled by default)
  • Search Pages - Search results (enabled by default)
  • Author Pages - Author archive pages
  • AMP Pages - Accelerated Mobile Pages
  • Ajax Requests - Background requests made by JavaScript (enabled by default)
  • Pages with Query Args - URLs with query strings (e.g., ?page=2)
  • WP JSON Endpoints - WordPress REST API requests

Don't Cache the Following Static Contents ​

  • XML Sitemaps - Your site's XML sitemap files (enabled by default)
  • Robots.txt - Your site's robots.txt file (enabled by default)

Note: these options write rules into your .htaccess file. If you use Nginx, you will need to add the rules manually.

Posts Per Page ​

Tells the plugin how many posts your theme displays per page. This is used to correctly purge paginated archive pages (e.g., /blog/page/2/) when content changes.

Browser Caching ​

Add Browser Caching Rules for Static Assets ​

Writes rules into your .htaccess file to enable browser caching for images, CSS, JavaScript, and other static files. This tells visitors' browsers to store these files locally so they don't need to be downloaded again on repeat visits. Works automatically on Apache. If you use Nginx, you'll need to add the rules manually. If you use Plesk, make sure to disable "Smart static files processing" and "Serve static files directly by Nginx" in your Plesk panel.

Cache Lifetime Settings ​

Cache-Control max-age ​

Controls how long Cloudflare keeps your pages in its cache (in seconds). The default is 31,536,000 seconds (1 year). Don't change this unless you have a specific reason to.

Browser Cache-Control max-age ​

Controls how long a visitor's browser keeps a cached copy of your pages (in seconds). The default is 60 seconds. A value between 60 and 600 is recommended.

Cloudflare Cache Behavior ​

Automatically Purge Cloudflare's Cache When Something Changes ​

Controls what happens when you update or publish content:

  • Purge cache for related pages only (recommended) - Only clears the cache for the updated page and its related pages (like the homepage and category pages).
  • Purge whole cache - Clears the entire Cloudflare cache. Use this only if you experience stale content issues with the recommended option.

Automatically Purge the Page Cache When Cloudflare Cache Is Purged ​

When enabled, your server's disk cache is also cleared whenever the Cloudflare cache is purged, keeping both caches in sync. Only visible when Disk Page Cache is enabled.

Force Cache Bypassing for Backend with an Additional Cloudflare Page Rule ​

By default, all WordPress admin pages are excluded from caching through response headers. If your admin area is still being cached for some reason, enabling this creates an additional rule on Cloudflare to force-bypass caching for the entire WordPress backend.

Preloader ​

Enable Preloader ​

Turns on the cache preloader. The preloader visits your pages in the background to ensure they are cached before a real visitor arrives. This means the first visitor to any page will get a fast, cached version instead of waiting for it to be generated.

Automatically Preload Pages You Have Purged From Cache ​

When the cache is purged, the preloader automatically re-visits those pages to rebuild the cache right away.

Preloader Operation ​

Choose which URLs the preloader should visit:

  • Preload all internal links in [Menu Name] WP Menu - Select one or more of your WordPress navigation menus. The preloader will visit every link in the selected menus.
  • Preload last 20 published/updated posts, pages & CPTs combined - Preloads your most recently changed content.

If no option is selected, the preloader will visit the homepage and the most recently published URLs.

Preload All URLs Into the Following Sitemaps ​

Enter the paths to your XML sitemaps (one per line), and the preloader will visit every URL listed in them. For example: /post-sitemap.xml.

Start the Preloader via Cronjob ​

Provides a URL that you can use in an external cron job to trigger the preloader on a custom schedule.

Cronjob Secret Key ​

A secret key included in the preloader cron URL to prevent unauthorized access. Don't change this unless you know what you're doing.

Varnish Settings ​

These settings are for sites that use Varnish (a server-side caching layer) in addition to Cloudflare.

Varnish Support ​

Enable this if your server uses Varnish caching and you want the plugin to purge Varnish when it purges the Cloudflare cache.

Hostname ​

The hostname of your Varnish server. Defaults to localhost.

Port ​

The port number your Varnish server listens on. Defaults to 6081.

HTTP Method for Single Page Cache Purge ​

The HTTP method used to purge a single page from Varnish. Defaults to PURGE.

HTTP Method for Whole Page Cache Purge ​

The HTTP method used to purge the entire Varnish cache. Defaults to PURGE.

Cloudways Varnish ​

Enable this if you're using Varnish on Cloudways hosting, which requires a slightly different purge configuration.

Automatically Purge Varnish Cache When the Cache Is Purged ​

When enabled, the plugin also purges Varnish every time it purges the Cloudflare or disk cache.

Logs Settings ​

Log Mode ​

Enables activity logging for the plugin. Useful for debugging issues. When enabled, you can download, view, or clear the log file directly from this section.

Max Log File Size in MB ​

Sets the maximum size of the log file. When the file exceeds this size, it is automatically reset. Set to 0 to never automatically reset.

Log Verbosity ​

Controls how much detail is recorded in the log:

  • Standard - Logs basic activity like cache purges and preloader events.
  • High - Also logs Cloudflare HTTP request and response details. Useful for troubleshooting API issues.

Other Settings ​

Automatically Purge the OPcache When Cache Is Purged ​

Clears PHP's OPcache whenever the plugin purges the cache. This can help if you see stale content after code changes.

Automatically Purge the Object Cache When Cache Is Purged ​

Clears your site's object cache (e.g., Redis, Memcached) whenever the plugin purges the cache.

Purge the Whole Cache via Cronjob ​

Provides a URL that you can use in an external cron job to periodically purge the entire cache on a schedule you choose.

Purge Cache URL Secret Key ​

A secret key included in the cache purge cron URL to prevent unauthorized access. Don't change this unless you know how to use it.

Remove Purge Option from Toolbar ​

Hides the "Purge CF Cache" button from the WordPress admin toolbar.

Hide Metaboxes ​

Removes the Super Page Cache metabox from the post and page editing screens. The metabox normally lets you exclude individual pages from caching.

SEO Redirect ​

Enables a 301 redirect for URLs that have been indexed by search engines with the cache buster query parameter. This helps clean up your SEO if those URLs were accidentally indexed.

Select User Roles Allowed to Purge the Cache ​

Choose which WordPress user roles (beyond Administrators, who always have access) are allowed to purge the cache from the admin toolbar.

Auto Prefetch URLs in Viewport ​

When a visitor loads a page, the browser silently prefetches all internal links visible on screen. This makes the next page the visitor clicks load almost instantly.

Auto Prefetch URLs on Mouse Hover ​

When a visitor hovers their mouse over a link, the browser begins prefetching that page in the background. By the time they click, the page is already partially or fully loaded.

Keep Settings on Deactivation ​

When enabled, your plugin settings are preserved if you deactivate the plugin. Without this, all settings are reset when the plugin is deactivated.

Files ​

Settings for optimizing JavaScript, CSS, and font loading.

Assets Manager ​

Enable Assets Manager ​

Lets you control which CSS and JavaScript files load on specific pages. Once enabled, a "Manage assets" button appears that opens a frontend interface where you can disable unnecessary scripts and styles on a per-page basis.

Fonts Optimizations ​

Optimize Google Fonts ​

Combines multiple Google Fonts requests into a single request or CSS file, reducing the number of network calls your pages make.

Local Google Fonts ​

Downloads Google Fonts and serves them from your own server instead of loading them from Google's servers. This can improve privacy compliance and loading speed.

Javascript Optimizations ​

Defer Javascript (Pro) ​

Moves JavaScript loading to after the page's HTML has been parsed, eliminating render-blocking scripts. This can significantly improve how fast your page appears to load.

Delay Javascript (Pro) ​

Delays loading JavaScript entirely until the visitor interacts with the page (by scrolling, clicking, or tapping). This makes the initial page load much faster since JavaScript isn't executed until it's actually needed.

Exclude JS (Pro) ​

Enter keywords (one per line) to prevent specific JavaScript files or inline scripts from being delayed. Use this if delaying a particular script breaks functionality on your site.

Exclude Pages (Pro) ​

Enter page paths (one per line) where JavaScript delay should not be applied. Useful if certain pages require JavaScript to load immediately.

CSS Optimizations ​

Remove Unused CSS (Pro) ​

Analyzes each page and strips out CSS rules that aren't used on that page. This can dramatically reduce page size. The plugin automatically rebuilds the optimized CSS cache.

Exclude Pages (Pro) ​

Enter page paths (one per line) where unused CSS removal should not be applied.

Exclude CSS (Pro) ​

Enter keywords (one per line) to prevent specific CSS files or inline styles from being removed. Any file or content matching your keywords will be kept intact.

Media ​

Settings for controlling how images, videos, and other media load on your pages.

Native Lazy Load ​

Uses the browser's built-in lazy loading feature to defer loading images until they are about to scroll into view. This is the simplest option and works in all modern browsers. This is automatically disabled if you enable the custom Lazy Load option below.

Lazy Load ​

Replaces native lazy loading with a custom solution that gives you more control over how images load. When enabled, additional options appear below.

Lazy Load Behavior for Images ​

Choose how lazy loading decides which images to defer:

  • Lazy load all images - Every image on the page is lazy loaded.
  • Skip Lazy Loading for First Images - A specified number of images at the top of the page load immediately (to avoid visible delays for above-the-fold content), and the rest are lazy loaded.
  • Skip Lazy Loading for Initial Viewport (Pro) - Automatically detects which images are visible when the page first loads and loads those immediately. All other images are lazy loaded.

Skip Lazy Loading for First Images ​

When using the "Skip Lazy Loading for First Images" behavior, this sets how many images at the top of each page should load normally without lazy loading.

Lazy Load Videos and Iframes ​

Extends lazy loading to embedded videos and iframes (like YouTube embeds). By default, lazy loading only applies to images.

Media Lazy Load Exclusions ​

Enter keywords (one per line) to exclude specific items from lazy loading. The plugin checks image URLs, class names, and data attributes for matches. For example, entering logo would prevent your site logo from being lazy loaded.

Background Images Lazy Load ​

Extends lazy loading to CSS background images. These are normally invisible to standard lazy loading since they're set in CSS rather than in <img> tags.

Background Images Lazy Load Selectors ​

Enter CSS selectors (one per line) for additional background images that should be lazy loaded. The plugin already handles common patterns from Elementor and WordPress blocks by default.

Compatibilities ​

This tab appears only when the plugin detects a supported third-party plugin on your site. It shows relevant integration options for each detected plugin.

WooCommerce ​

Don't Cache the Following WooCommerce Page Types ​

Checkboxes to exclude specific WooCommerce pages from caching: Cart, Checkout, Checkout's Pay Page, Product, Shop, Product Taxonomy, Product Tag, Product Category, WooCommerce Page, and My Account. Cart, Checkout, Checkout's Pay Page, and My Account are recommended to be excluded.

Automatically Purge Cache for Product Page and Related Categories When Stock Quantity Changes ​

Clears the cache for a product and its category pages when inventory levels change, so customers always see up-to-date stock information.

Automatically Purge Cache for Scheduled Sales ​

Clears the cache when WooCommerce scheduled sale prices start or end, so visitors see the correct pricing.

Easy Digital Downloads (EDD) ​

Don't Cache the Following EDD Page Types ​

Checkboxes to exclude specific EDD pages from caching: Primary Checkout Page, Purchase History Page, Login Redirect Page, Success Page, and Failure Page.

Automatically Purge Cache When a Payment Is Inserted into the Database ​

Clears the cache when a new purchase is made.

WP Rocket ​

Automatically Purge the Cache When... ​

Checkboxes for various WP Rocket events that should trigger a Super Page Cache purge: flushing all caches, single post cache, cache directories, files, cache busting, minified files, Critical CSS generation, and Remove Unused CSS generation.

Disable WP Rocket Page Cache ​

Turns off WP Rocket's own page caching so it doesn't conflict with Super Page Cache's caching. You can still use WP Rocket for its other optimization features.

W3 Total Cache ​

Automatically Purge the Cache When... ​

Checkboxes for W3TC events that should trigger a purge: flushing all caches, database cache, fragment cache, object cache, posts cache, and minify cache.

LiteSpeed Cache ​

Automatically Purge the Cache When... ​

Checkboxes for LiteSpeed Cache events: flushing all caches, Critical CSS, CSS and JS cache, object cache, and single post cache via API.

Swift Performance ​

Automatically Purge the Cache When... ​

Checkboxes for Swift Performance events: flushing all caches and flushing single post cache.

Autoptimize ​

Automatically purge the cache when Autoptimize flushes its cache.

Hummingbird ​

Automatically purge the cache when Hummingbird flushes its page cache.

WP-Optimize ​

Automatically purge the cache when WP-Optimize flushes its page cache.

Flying Press ​

Automatically purge the cache when Flying Press flushes its cache.

WP Performance ​

Automatically purge the cache when WP Performance flushes its cache.

WP Asset Clean Up ​

Automatically purge the cache when WP Asset Clean Up flushes its cache.

Nginx Helper ​

Automatically purge the cache when Nginx Helper flushes the cache.

Yet Another Stars Rating (YASR) ​

Automatically purge the page cache when a visitor votes on a star rating.

Kinsta ​

Automatically purge the Kinsta server cache when the Cloudflare cache is purged.

WP Engine ​

Automatically purge the WP Engine server cache when the Cloudflare cache is purged.

Siteground SuperCacher ​

Automatically purge the Siteground server cache when the Cloudflare cache is purged.

SpinupWP ​

Automatically purge the SpinupWP server cache when the Cloudflare cache is purged.

Database ​

Settings for cleaning up and optimizing your WordPress database.

Enable Database Optimization ​

Turns on the database cleanup feature. When enabled, you'll see individual cleanup tasks below, each with a "Clean Now" button for immediate action and a schedule dropdown to automate the cleanup.

Post Revisions Cleanup ​

Deletes old revisions across all post types (posts, pages, and custom post types). WordPress saves a copy every time you edit content, and these can accumulate over time. You can run this once manually or set a recurring schedule.

Auto-Draft Cleanup ​

Deletes auto-draft entries that WordPress creates automatically when you start writing a new post. These leftover drafts can pile up in your database.

Trashed Posts Cleanup ​

Permanently deletes all items currently in the trash across all post types. By default, WordPress only empties the trash after 30 days.

Spam Comments Cleanup ​

Removes comments that have been marked as spam, either automatically by a spam filter or manually by you.

Trashed Comments Cleanup ​

Permanently deletes all comments that are currently in the trash.

Transients Data Cleanup ​

Deletes all transients (temporary cached data) stored in your database. Transients are used by WordPress and plugins to store short-lived data, but expired ones can accumulate.

Database Tables Optimization ​

Runs the database OPTIMIZE TABLE command to defragment tables and reclaim unused space. This is similar to defragmenting a hard drive and helps keep your database running efficiently.