Skip to content
IP Location Block
Home Pricing Articles Docs Changelog Contact My Account Get Started

Use location blocking with page cache

Prevent one cached response from being reused for visitors in different locations.

Updated Aug 23, 2026

Simple mode Explore Advanced mode

Full-page caches can serve a saved response before WordPress and IP Location Block run. That can make blocking appear inconsistent.

When to enable bypass

The Bypass full-page cache toggle
Enable the bypass when a page-caching layer handles public requests.

Turn on Bypass full-page cache if you use a WordPress page-cache plugin or another cache that honors the plugin bypass. Leave it off when there is no public page cache.

Clear existing cache

After changing the setting or the location rule, purge the WordPress cache and any host or CDN cache. Old cached pages can remain visible until they expire.

Test the result

  • Use a private browser window.
  • Test both an allowed and blocked location.
  • Confirm a blocked request appears in Logs.
  • If a CDN still serves the page first, configure its own cache or edge rules.

The plugin cannot run after a proxy or edge cache has already returned a response. CDN behavior must be configured at that layer.