Cache Management

Overview

The cache management page lets you view all cached pages for a domain, purge cached entries when content changes, and warm the cache for important pages. Effective cache management ensures bots always see your latest content while maintaining fast response times.

Viewing Cached Pages

Navigate to a domain's Cache tab to see all currently cached pages. Each entry shows:

  • URL path -- The cached page URL
  • Cached at -- When the page was last rendered and cached
  • Expires at -- When the cache entry will expire (1 hour after caching)
  • Size -- The size of the cached HTML

The cache is stored in Redis with a default TTL of 1 hour. After expiration, the next bot visit to that page triggers a fresh render.

Purging Cache

Purge a Single Page

When you update a specific page and want bots to see the changes immediately:

  1. Go to the domain's Cache tab.
  2. Find the page in the cached pages list.
  3. Click the Purge button next to that page.

The cached entry is removed instantly. The next bot visit will trigger a fresh render with your updated content.

Purge All Cache

After a major site update, you may want to clear all cached pages:

  1. Go to the domain's Cache tab.
  2. Click Purge All Cache.
  3. Confirm the action.

This removes every cached page for the domain. Subsequent bot visits will trigger fresh renders for each page. Be aware that this temporarily increases render times and load until the cache is rebuilt.

Cache Warming

Cache warming lets you proactively render pages before bots visit them. Instead of waiting for the first bot request (which takes 2-5 seconds to render), you can pre-render pages so bots get instant cached responses.

Warming Individual Pages

  1. Go to the domain's Cache tab.
  2. Enter a URL path in the Warm URL field (e.g., /about).
  3. Click Warm.
  4. The page will be rendered and cached.

Warming Multiple Pages

You can warm multiple pages at once by entering URLs one per line or by importing from your sitemap. This is especially useful after:

  • Deploying a new version of your site
  • Purging all cache
  • Adding a new domain to RndrKit

For more details on warming strategies, see Cache Warming.

Emergency Refresh

The domain detail page includes an Emergency Refresh button that re-renders all cached pages for the domain in one action. This is useful after deploying a major site update when you need all content refreshed immediately.

Emergency refreshes are limited per billing period based on your plan:

  • Starter: 2 per period
  • Pro: 5 per period
  • Agency: 25 per period
  • Agency+: 50 per period

The count resets when your billing period renews. See Plans and Pricing for details.

Cache Refresh Frequency

Your plan determines how frequently cached pages are automatically refreshed:

  • Daily (Starter, Pro) -- Cached pages are refreshed once per day.
  • Hourly (Agency) -- Cached pages are refreshed every hour.
  • Real-time (Agency+) -- Cached pages are refreshed as content changes.

This is separate from the 1-hour cache TTL. The refresh frequency controls proactive cache updates, while the TTL controls when stale entries expire on demand.

Cache Statistics

The cache management page also shows performance metrics:

  • Total cached pages -- Number of pages currently in the cache
  • Cache hit rate -- Percentage of bot requests served from cache
  • Average render time -- Mean time for fresh renders (cache misses)
  • Cache size -- Total memory used by cached pages

Best Practices

  • Purge selectively -- Only purge pages that have actually changed. Purging everything unnecessarily increases render load.
  • Warm after purging -- After purging important pages, immediately warm them so the next bot visit gets a cached response.
  • Monitor hit rate -- A hit rate below 50% suggests that your cache is expiring faster than bots revisit. Consider warming your most-crawled pages regularly.
  • Time updates wisely -- If possible, deploy site changes during low-traffic periods and warm the cache before peak bot activity.

Next Steps

Previous

Analytics

Next

Sitemaps