Cookie consent for WP Super Cache

What WP Super Cache adds to your visitors’ browser

What matters for consent with WP Super Cache

Cookie Rocks with WP Super Cache

What our tests found on WP Super Cache

• Good to know · Cookie RocksCookie Rocks works with four page caches on a real site

  With WP Super Cache, W3 Total Cache, WP Fastest Cache or Breeze serving cached pages, each visitor still gets their own banner and choice.

  Seen in our tests, 23 October 2026, Cookie Rocks 3.1.4 / 2.11.0 / 1.5.3 / 2.6.3.

  Full detail

  On a real site with the page cache of each plugin on and serving (cache marker in the page), the cached page keeps the Cookie Rocks head script and a single Google consent default, each visitor gets their own banner, one visitor's choice is never served to another, and the country rules endpoints answer 404 while the rules are off: WP Super Cache 3.1.4 (PHP mode, preload), W3 Total Cache 2.11.0 (Disk: Enhanced), WP Fastest Cache 1.5.3, Breeze 2.6.3. Three checks of three for each.

• Depends on a setting · W3 Total Cache, BreezeW3 Total Cache and Breeze can remove WP Super Cache's .htaccess block

  Trying W3 Total Cache or Breeze can remove WP Super Cache's block from .htaccess. Keep a copy of .htaccess before testing page caches.

  What to do: Keep a copy of .htaccess before testing page caches and compare it afterwards.

  Seen in our tests, 23 October 2026, W3 Total Cache, Breeze 2.11.0 / 2.6.3.

  Full detail

  On a real site, after W3 Total Cache 2.11.0 then Breeze 2.6.3 were each installed, enabled and removed, the '# BEGIN WPSuperCache ... # END WPSuperCache' block of an inactive WP Super Cache was gone from .htaccess: both plugins rewrite .htaccess. WP Super Cache in simple (PHP) mode keeps working without the block.

• Good to know · W3 Total Cache, WP Super Cache, WP Fastest Cache, BreezeFour cache plugins keep the banner, and each visitor gets their own

  setting “Page cache”

  With W3 Total Cache, WP Super Cache, WP Fastest Cache or Breeze, the cached page keeps the Cookie Rocks banner. One visitor's choice is never served to another from the cache.

  Seen in our tests, 17 October 2026, W3 Total Cache, WP Super Cache, WP Fastest Cache, Breeze 2.10.7, 3.1.4, 1.5.3, 2.6.2. Source

  Full detail

  With the page cache of W3 Total Cache (Disk: Enhanced), WP Super Cache (Simple mode), WP Fastest Cache or Breeze turned on, the page served from the cache keeps the Cookie Rocks banner, and each visitor gets their own banner: a choice made by one visitor is never served to another from the cache.

• Good to know · WP Super CacheWP Super Cache sets no cookie and adds no script for visitors

  Visitors with a login, comment or registered cookie get a separate copy. Registering a consent cookie that way would split the cache for everyone who has chosen.

  Read in its code, 16 October 2026, WP Super Cache 3.1.4.

  Full detail

  WP Super Cache's code contains no setcookie, document.cookie, localStorage or sessionStorage, adds no script to visitor pages (its delete-cache button loads only for logged-in users) and does not minify, combine or delay scripts. A visitor with a login, post password or comment cookie, or a cookie registered with wpsc_add_cookie, is a known visitor and gets a PHP-served copy keyed to their cookies instead of the static file; registering a consent cookie that way would split the cache for everyone who has chosen.

• Good to know · Cookie Rocks ProCookie Rocks Pro clears page caches when an update changes banner values

  It clears the caches of seven known plugins, such as WP Rocket and LiteSpeed Cache, at the first request after the update. Host and CDN caches keep the old pages until they expire.

  What to do: After an update that changes banner defaults, clear the host or CDN cache by hand.

  Read in its code, 15 October 2026, Cookie Rocks Pro.

  Full detail

  When an update of Cookie Rocks Pro changes or removes a value it sends to visitors (for example the default accent colour), Pro clears the known page caches (WP Rocket, LiteSpeed Cache, W3 Total Cache, WP Super Cache, SiteGround Optimizer, WP Fastest Cache, Breeze) at the first request after the update, with no extra database query and nothing more for visitors. An added value clears nothing. Host and CDN caches are not cleared and keep the old pages until they expire.

• Good to know · WP Super CacheWP Super Cache can serve an old home page without the cookie banner

  WP Super Cache can keep serving a copy of the home page cached before a cookie banner was turned on: on a real site, visitors arriving on the home page saw no banner although it was enabled, until the page cache was cleared.

  Seen in our tests, 14 October 2026, WP Super Cache.

• Depends on a setting · WP Super CacheWP Super Cache skips its cache for visits with ad and campaign parameters

  setting “Ignore tracking parameters” · by default: off

  By default, pages with gclid, fbclid or utm_ parameters are built again on every visit. Its option to ignore them serves the cached page, but server-filled form fields lose them.

  Seen in our tests, 9 October 2026, WP Super Cache.

  Full detail

  By default, WP Super Cache does not serve a cached page when the address carries ad or campaign parameters (gclid, fbclid, utm_...): WordPress builds the page again on every such visit (its rewrite rules require an empty query string). Its option to ignore tracking parameters makes these visits get the cached page; its list can be extended with gad_source, gbraid, wbraid, msclkid and srsltid. A form field filled on the server with the page address then loses these parameters, while values read in the browser (a cookie set by a tag, a field filled by script) keep them.

Page cache

Other plugins of the same kind.

Every plugin and theme we test →