How Prerender Caching Works
- When a bot requests a URL that isn’t cached, Prerender will render the page on the fly and serve it to the bot.
- If the page returns a 200 status code, Prerender will cache the rendered page, ensuring it is readily available for subsequent requests.
- If the page returns a non-200 status code, such as 404, 301, or 302, Prerender will not cache the page after serving it to the bot.
Note: A URL or page cached first time will be a "Cache Miss", but when Prerender receives subsequent requests, it'll be a "Cache Hit." This means the first response takes a bit longer, but after that, pages are served in an instant.
Tips and Solutions for Reducing Cache Misses
If you're experiencing a large number of cache misses, here are two effective solutions to address this:
- Add a Sitemap: Reduce cache misses by adding a sitemap. This method allows ensures pages are prerendered in advance for bots.
- Ensure Your Server Returns a 200 Status Code: For a page to be cached successfully, your server must return a 200 HTTP status code.
- Use the Recache API: Cache URLs proactively by using the Recache API to render and cache pages before they are requested by bots, improving response times when bots request them.
Important:
Please note that API access is a premium feature available exclusively with our Advanced and Custom/Enterprise plans. For more information or to upgrade your plan, please get in touch with us.