Skip to content
  • There are no suggestions because the search field is empty.

Why are some of my pages not getting cached?

Three checks to find the cause: cache manager, HTTP status code, and the Ignored URLs list.

TL;DR

If pages on your site are not appearing in your Prerender.io cache, the cause is almost always one of three things: the page has not been cached yet (or has been evicted), the page returns a status code other than 200, 404, or 410, or the URL matches an entry in your Ignored URLs list. Work through the three checks below in order, fix whichever cause applies, and re-test.

Why caching matters

Prerender.io renders your JavaScript pages and caches the HTML so AI crawlers and search engines receive an instant response on subsequent visits. If a page is not being cached, Prerender.io still renders it on each crawler request, which increases your render usage and slows down what crawlers receive.

Pages that are rendered but not cached can also cause inconsistencies between what AI crawlers see and what your website visitors see, which may affect citations and search rankings.

ℹ️ If you would rather have an interactive walk-through, ask Nexus, your AI integration assistant, inside your Prerender.io dashboard. Paste the affected URL and Nexus will help you narrow down the cause. Nexus only available during Onboarding.

Step 1: check whether the URL is in your cache manager.

Start here. If the URL is in the cache manager, the issue is not caching itself but something else, for example a stale cached version. If it is not in the cache manager, continue to Step 2.

  1. Open your Prerender.io dashboard and go to Cache Manager.
  2. Paste the affected URL into the search bar above the table.
  3. Look for the URL in the results:
    • If the URL appears, it is cached. The issue may be elsewhere (cache freshness, headers, or rendering).
    • If the URL does not appear, it has not been cached. Continue to Step 2. A 404 or 410 URL that does not appear may also be listed differently from 200 pages, so continue to Step 2 to check its status code.

A URL that previously appeared in the cache but no longer does has either been evicted because of plan limits, expired due to your cache expiration settings, or been intentionally excluded. A URL that returned 404 or 410 is also removed from the cache at the next scheduled recache if it still returns 404 or 410. Step 3 covers the exclusion case.

Step 2: verify the page returns a cacheable status code.

Prerender.io caches pages with a 200 HTTP status code. Since 2026-10-20, it also caches 404 and 410 responses. Pages returning 301, 302, 5xx, or other codes are rendered and served to crawlers, but they are not cached by default.

  1. Open the affected URL in your browser.
  2. Press F12, or right-click the page and select Inspect, to open Developer Tools.
  3. Click the Network tab.
  4. Press Enter to reload the page.
  5. Click the first item in the Network tab list (the document request). The status code appears at the top of the response details.

If the status code is anything other than 200, 404, or 410, Prerender.io will render the page but, by default, will not cache it. Fix the underlying status code at your application or server level, then re-trigger a render to populate the cache.

⚠️ A <meta name="prerender-status-code" content="..."> tag in the page <head> overrides the HTTP status code for Prerender.io. Check the head of the page for this tag. If it is set to 404, Prerender.io caches the page as a 404, even if the HTTP response itself is 200 OK. Other non-200 values are not cached by default.

How Prerender.io handles 404 and 410 pages

Prerender.io caches 404 and 410 responses from on-demand crawler renders on every account, regardless of your status code caching setting. Here is how it works:

  • Prerender.io serves a cached 404 or 410 page back to crawlers with its original status code.
  • Prerender.io keeps the cached page for the URL's normal cache expiration.
  • Prerender.io does not cache the page 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 cached 404 or 410 entry is removed when a scheduled recache finds the URL still returns 404 or 410.
  • Serving a cached 404 or 410 does not count as a render. Only the first (uncached) render counts, the same as for 200 pages.

ℹ️ A soft 404 is a page that returns 200 but shows an error page. Prerender.io caches it as a 200 unless your site returns a real 404 or the page uses the <meta name="prerender-status-code" content="404"> tag. In that case, Prerender.io caches it as a 404.

Step 3: check whether the URL is in your Ignored URLs list.

If the URL returns 200 OK, 404, or 410 and is not cached, it may be matching an entry in your Ignored URLs list. The list supports regular expressions, so a URL can be excluded by a pattern match, not just by exact match.

  1. Open your Prerender.io dashboard and go to Cache Manager.
  2. Click the Ignored URLs tab at the top of the page.
  3. Look through the list for either the exact URL or a pattern that could match it.

If the URL, or a pattern that matches it, appears in the list, Prerender.io is intentionally skipping cache for that page. Remove or refine the rule if you want the page cached, then trigger a fresh render.

⚠️ Broad regular expressions can match more URLs than you intend. If you are not sure whether a pattern is matching your URL, test it against your URL using a regex tester before changing it.

Still not cached?

If the URL returns 200, 404, or 410, is not in the Ignored URLs list, and is still not appearing in the cache, the next thing to check is whether your Prerender.io integration is working at all on other pages.

→ Run through Verify your Prerender.io integration. If you do not see the Prerender.io headers or IDs on other pages, the integration itself may be the cause, and no pages will cache until it is fixed.

✅ The integration is working when cached pages appear in your Prerender.io dashboard within 2 to 5 minutes of a crawler request.

Best practices to avoid future cache misses

A few habits keep more of your pages in cache and out of trouble.

  • Prerender.io caches 200 OK, 404, and 410 pages. Redirects and server errors are not cached by default.
  • Keep Ignored URLs patterns as narrow as possible. Broad regex patterns often match more URLs than intended.
  • Use the /recache endpoint to force a fresh render for new or recently updated pages.
  • Tune your cache expiration to match how often your content changes. Aggressive expiration causes more renders; long expiration risks stale content.

Related articles

💬 Still need help? If a page is still not cached after working through the three checks above, our support team can help diagnose your specific case.

When you contact us, please include:

  • The full URL or URLs affected.
  • The HTTP status code observed in your browser DevTools.
  • Any relevant integration or middleware configuration.
  • Screenshots of the cache manager and Ignored URLs tab.

→ Contact us at support@prerender.io

 

Was this article helpful?