Caching and Speed - BizzCMS/bizzcms GitHub Wiki

Caching and Speed

BizzCMS keeps your public pages on Cloudflare's servers for a few minutes. Visitors and search engines get them straight from there, close to where they are, and your database is not asked to rebuild the same page again and again.

Your changes show right away

Every time you save something in the admin (a page, a post, an image, a setting, SEO, a redirect), all cached pages are replaced at once, everywhere. You never have to wait for the cache to run out.

Settings › Cache

Setting Default What it does
Cache public pages on Switch caching on or off for the whole site.
Keep pages for (minutes) 5 How long a page is kept when nothing is saved. 0 = no caching for pages.
Keep sitemaps and feeds until content changes on Sitemaps, feeds, robots.txt and llms.txt are built once and kept until you save something. Search engines still always get the current version.
Keep sitemaps, feeds, robots.txt and llms.txt for (minutes) 60 Used when the box above is off.
Clear the cache now Replaces every cached page straight away.

Saving these settings also clears the cache.

What is never cached

  • The admin, sign-in pages, the API, files and the MCP server.
  • Anything you see while signed in: editors always see fresh pages.
  • Errors, redirects and "page not found".

Search engines

Google and other crawlers fetch your pages gradually. Every page tells them when it last changed, and a crawler that already has a page gets a tiny "not modified" answer instead of the whole page. Together with the sitemap's dates (SEO), this keeps crawling light even for sites with thousands of posts.

Check it

Every public page carries a header x-bizz-cache: HIT (from the cache) or MISS (freshly built). Add ?nocache to an address to skip the cache once.