The Advanced Options tab in the Breeze plugin gives you more control over caching behavior, especially when handling query strings, custom URLs, or API integration.
These settings are useful for fine-tuning how specific content is cached, whether it’s part of your blog, WooCommerce store, or multilingual site.
This article will guide you through all steps with each advanced option and explain how to use them, even if you’re not a developer.
Table of Contents:
How to Use Breeze Advanced Options for Custom Settings?
The Advanced Options tab in Breeze gives you more control over what gets cached and how. It’s ideal for handling dynamic content, query strings, and API-based cache purging.
How to Use the Advanced Options Tab?
To access the advanced settings:
Go to your WordPress Dashboard.
Navigate to Settings > Breeze.
Click on the Advanced Options tab to get started.
Never Cache These URLs
This setting lets you exclude specific URLs or URL patterns from being cached. It’s useful for excluding dynamic content such as certain blog categories or custom pages.
Note: If you are using WooCommerce, the Cart, Checkout, and My Account pages are automatically excluded from Breeze caching, no manual setup is needed.
WooCommerce Example:
Let’s say you want to prevent a WooCommerce category from being cached.
Create two product categories and add a few products to each.
In the Never Cache These URLs field, enter the category you want to exclude using a wildcard:
http://yourdomain.com/shop/category-1(.*). Example:http://breeze.demo/category/(.*)(this is a sample URL)Make sure your permalink structure includes product category and name.
Visit a product from the excluded category → view page source → there should be no cache tag.
Visit a product from a non-excluded category → it should show cached content.
Blog Example:
Want to exclude a blog category?
Create two blog categories with two posts each.
Enter the URL pattern of one category in the exclusion list:
http://yourdomain.com/category/news(.*)Make sure your permalink settings include categories.
Posts from the excluded category will not be cached. Others will be.
Tip: Use wildcards (.*) to exclude all posts or products under a specific category or URL pattern.
Cache Query Strings
By default, Breeze does not cache URLs with query strings, such as ?ref=newsletter. But you can configure which query strings should or shouldn’t be cached.
Ignored Query Strings (Default):
These are common tracking or marketing parameters like:
utm_source, utm_campaign, fbclid, gclid, _ga, etc.
When these are found in a URL, Breeze ignores them and serves the cached version of the base URL instead.
Example 1:
Added 2 strings to "Cache query strings" in the backend for testing purposes.
Example 2:
*These ignored query strings can be customized using filters if needed.
Always Cached Query Strings
Some query strings are always cached, such as:
?lang=english?lp-variation-id=123
These values create separate cache files for each variation, which is useful for:
Multilingual pages (
?lang)Custom landing pages (
?lp-variation-id)
Breeze also auto-caches special WordPress query variables (e.g., ?page_id, ?author, ?tag, ?category, etc.) — so core WP content is handled efficiently.
User-defined Cached Query Strings
You can add custom query strings directly in the Breeze Advanced Options tab to allow specific parameter-based pages to be cached.
Example Test:
Let’s say you add country and tester to the cached list.
Visit:
https://example.com/?country=RO&tester=Mike
Page is cached.Visit:
https://example.com/?country=RO&tester=Mike_testing
A separate cache file is created for this version.Visit:
https://example.com/?utm_source=google&country=RO
Cache is served by ignoring utm_source but keeping country=RO.
*This lets you cache different versions of the same page based on user-defined parameters.
Breeze API Integration for Cache Purging
If you’re using external tools or automated workflows, Breeze supports REST API integration to clear cache programmatically.
This is useful for:
Automatically clearing cache after publishing or updating content.
Integrating with WooCommerce or custom systems.
Use These API Endpoints
Without Authentication:
With Key Authentication:
For WordPress Multisite:
*You can also trigger cache clearance when adding WooCommerce products via REST API.
That’s it! We hope this article was helpful.
Need Help?
If you need assistance, feel free to:
Visit the Cloudways Support Center
Chat with us: Need a Hand > Send us a Message
Or create a support ticket anytime.
We're here 24/7 to help you!