How Prerender.io caching works
From the first uncached request to instant subsequent responses — how Prerender.io stores and serves rendered pages to AI crawlers and search engines.
TL;DR
Prerender.io renders and caches a page the first time an AI crawler or search engine requests it — this first request is called a cache miss and takes a moment longer to serve. Every subsequent request for the same URL is served instantly from the cache — this is a cache hit. Prerender.io caches pages when your server returns a 200 status code, and it also caches 404 and 410 responses from on-demand crawler renders, so a dead URL is not rendered again on every request until it is dropped at the next recache. Other non-200 responses (301, 302, 5xx) are served to the crawler but not stored by default.
What gets cached — and what doesn't
When an AI crawler or search engine requests a URL that isn't yet in the cache, Prerender.io renders the page on the fly and serves it immediately.
Whether Prerender.io then stores that rendered page depends on the HTTP status code your server returns:
- 200 status code — Prerender.io caches the rendered page. Future requests for that URL are served instantly.
- 404 and 410 status codes — For on-demand crawler renders, Prerender.io caches the rendered page and serves it back from the cache with its original 404 or 410 status code. It keeps the entry for the URL's normal cache expiration (see the exceptions below). This applies to every account, regardless of your status-code caching setting.
- Other non-200 status codes (301, 302, 5xx, and others) — Prerender.io serves the response to the crawler but does not cache it by default. The next request will trigger a fresh render.

ℹ️ Prerender.io does not cache a 404 or 410 if the render produced no page content, or if the URL's cache is set to never expire. When a scheduled recache runs and the URL still returns 404 or 410, Prerender.io removes the entry from the cache. A dead URL is cached once, then dropped at the next recache. Serving a cached 404 or 410 does not count as a render. Only the first, uncached render counts, the same as for 200 pages.
ℹ️ Soft 404s (pages that return a 200 status code but show an error page) are still cached as 200. If your site returns a real 404, or you add <meta name="prerender-status-code" content="404"> to the page, Prerender.io caches it as a 404.
Cache hits and cache misses
The first time Prerender.io renders and stores a page, that request is a cache miss — the page wasn't in the cache yet, so Prerender.io had to render it. This takes a moment longer than a cached response.
Every request after that is a cache hit — Prerender.io serves the stored HTML instantly, with no rendering delay.
The goal is to have as many cache hits as possible. A high cache miss rate means AI crawlers and search engines are frequently waiting for pages to render on the fly.
How to reduce cache misses
If you're seeing a high volume of cache misses, there are three approaches to address it.
Add a sitemap
A sitemap tells Prerender.io which URLs exist on your site, allowing it to pre-render pages before AI crawlers request them. This converts what would have been cache misses into cache hits. See How to use Prerender.io's sitemap for setup instructions.
Ensure your server returns 200 for pages you want cached
Pages you want live must return a 200 response. If your server is returning non-200 codes for pages you expect to be cached, investigate your server configuration — a redirect or server error on a page that should be live will never accumulate cache hits. A 404 or 410 is cached and served from the cache with its original status code until the next scheduled recache. If the URL still returns 404 or 410 at that point, Prerender.io removes it, so a page that should be live is never cached as a working page.
Use the Recache API to cache pages proactively
The Recache API lets you trigger renders and cache pages before AI crawlers request them. This is useful for high-priority pages or after publishing new content. See What can I do with the Prerender.io REST API? for details.
💬 Still need help?
If you have questions about caching behaviour or cache miss rates in your account, our support team can help.
→ Contact us at support@prerender.io