Cito Boost is currently available for WordPress sites only. The ‘Caching’ tab is not shown for other site types.
Enabling & disabling Boost
Use the ‘Enable Cito Boost’ switch at the top of the Caching tab. Changes apply immediately. Pages are cached for 6 hours. Only successful responses and redirects (HTTP 200, 301 and 302) are cached.Checking if a page is cached
Every response from a Boost-enabled site includes anx-prostack-boost header. The main statuses are:
- HIT - the page was served from the cache.
- MISS - the page was not in the cache, so it was generated by WordPress and stored for next time.
- BYPASS - the request skipped the cache because of an automatic exclusion, a cache exclusion or a cookie.
The first request for any page will be a
MISS unless the cache is already populated, so always test twice. Test in a private browser window: if you’re logged in to WordPress, or your browser has any cookie that isn’t on your ignored cookies list, you’ll always see BYPASS.What’s excluded automatically
Boost always bypasses the cache for the following, so you don’t need to add rules for them. Requests- POST requests (e.g. form submissions)
- Any URL with a query string, unless it contains only tracking parameters
- Add-to-cart links (
add-to-cart=) andwp-api=requests
- The WordPress admin area and login page (
/wp-admin/,wp-login.phpand otherwp-*.phpfiles) xmlrpc.phpandindex.php- RSS feeds and XML sitemaps
- Any URL containing
/cart,/basket,/checkout,/check-out,/my-account,/storeor/addons - WooCommerce API endpoints (
/wp-json/wc,/wc-api),/coupon,/products-compareand/my-account/lost-password
- Logged-in WordPress users, visitors who have left a comment, and visitors viewing a password-protected post
- WooCommerce shoppers with items in their basket or an active session
- Any visitor with a cookie that isn’t on your ignored cookies list
URL checks match anywhere in the path, so a blog post at
/blog/cart-buying-guide would also bypass the cache. If this is a problem for your site, contact Support.Cache exclusions
Cache exclusions let you keep specific pages out of the cache, for example a members area or a page that shows live stock levels. You’ll find them in the Caching tab under ‘Cache Exclusions’.Adding an exclusion
Click ‘Add Exclusion’ and enter the path you want to exclude, plus an optional comment to remind you why.- Paths must start with
/. - A rule matches any URL that begins with the path, so
/membersexcludes/members,/members/profileand/membership. Add a trailing slash (/members/) to match only pages inside that section. - Use
*as a wildcard to match anything, e.g./shop/*/reviewsexcludes the reviews page of every product. - Matching is case-insensitive.
Ignored cookies
Boost only serves a cached page when every cookie the visitor’s browser sends is on your site’s ignored cookies list. If a visitor has any other cookie, they get a freshly generated page. This means an unexpected session cookie from a plugin can never cause one visitor’s personalised page to be shown to someone else. Visitors with no cookies at all, such as first-time visitors and search engine crawlers, are always served from the cache.The ignored cookies list starts empty, so any cookie at all will bypass the cache. Most sites use analytics or a cookie consent banner, which set cookies after the first page view. Until you add those cookies here, returning visitors won’t benefit from Boost.
Adding an ignored cookie
Under ‘Ignored cookies’ in the Caching tab, enter the cookie name and click ‘Ignore Cookie’.- Add a trailing
*to match every cookie starting with that name, e.g._ga*matches_gaand_ga_ABC123. - Names can contain letters, numbers, dots, hyphens and underscores, and are matched case-insensitively.
- You can add up to 50 cookies per site.
Which cookies to ignore
Only ignore cookies that never change what a page looks like. Common examples:
Don’t ignore login or session cookies, or cookies that change content, such as currency or language switchers. If you do, visitors could be shown a cached page meant for someone else.
To see which cookies your site sets, open it in a private browser window, accept the cookie banner, browse a few pages, and then check your browser’s developer tools (Application or Storage tab, then Cookies). If a page still shows
BYPASS in the x-prostack-boost header, one of those cookies isn’t on your list yet.
Query strings
A query string is the part of a URL after the?, such as /products?colour=red. Because these often change what a page shows, Boost bypasses the cache for any URL with a query string.
The exception is tracking parameters added by ad platforms and email campaigns, which never change page content. If a URL’s query string contains only tracking parameters, it’s served from the same cache entry as the plain URL. For example, /?utm_source=newsletter and /?gclid=abc123 both get the cached copy of /. The parameters aren’t removed, so analytics tools running in the visitor’s browser still see them.
If the query string contains any other parameter, even alongside tracking parameters (e.g. /?utm_source=newsletter&page=2), the cache is bypassed.
The following are treated as tracking parameters:
utm_*(e.g.utm_source,utm_medium,utm_campaign)- Ad click IDs:
gclid,dclid,fbclid,msclkid,ttclid,twclid,srsltid,ScCid - Others:
_,_ga,__lsa,affiliate,eref,fb_ref,fb_source,fb_xd_bust,fb_xd_fragment,fbid,gref,hootPostID,hpt,ia_share_url,icid,iid,iref,linkId,migAgencyId,migRandom,migSource,migTrackDataExt,migTrackFmtExt,mod,ncid,npt,omcamp,pretty,snapid,wsrlui
Cached pages for tracking URLs are generated without the parameters, so any server-side (PHP) code that reads them won’t run on a cache hit. Client-side analytics such as Google Analytics are unaffected.
