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

How do I find URLs that failed to cache?

Filter Render History by HTTP status code to identify pages that returned errors during the pre-rendering process.

TL;DR

To find URLs that failed to cache, open Render History in your Prerender.io dashboard and filter the HTTP Status column for codes between 300 and 599. The filter takes under a minute to apply. From there you can sort the results, identify the failure type, and recache affected pages using Cache Manager. A 404 or 410 in the results usually means the URL is dead rather than that caching failed, because Prerender.io now caches those responses from on-demand crawler renders.

Pages that fail to cache typically return HTTP status codes like 503 (service unavailable) or 504 (gateway timeout). These failures mean the page wasn't cached, so when AI crawlers and search engines visit those URLs, they may receive an incomplete or missing page instead of clean, rendered HTML.

Render History in your Prerender.io dashboard gives you a filterable log of every render attempt, including its HTTP status code, so you can pinpoint exactly which pages failed and why.

Prerender.io caches 404 (not found) and 410 (gone) responses from on-demand crawler renders for every account, regardless of your status code caching setting. It serves them back from cache with their original status code and keeps them for the URL's normal cache expiration. 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. Other non-200 codes, such as 301, 302, and 5xx, are still not cached by default.

 ℹ️ Since 20 October 2026, a 404 or 410 from an on-demand crawler render is normally cached, so it usually means the URL is dead rather than that caching failed. It is still worth fixing or redirecting. When a scheduled recache runs and the URL still returns 404 or 410, Prerender.io removes the entry from the cache. Serving a cached 404 or 410 does not count as a render. Only the first, uncached render counts, the same as for 200 pages.

 ℹ️ Common reasons pages fail to cache: timeout errors on slow-loading pages (504), redirect loops or incorrect integrations causing 403 errors, and changes to your site architecture or Prerender.io token that cut off access to certain URLs.

Step 1: Log into your Prerender.io dashboard

Go to dashboard.prerender.io and log in to your account.

Step 2: Open Render History

In the left-hand navigation, click Render History.

Step 3: Set the HTTP status filter

Click the filter icon next to the HTTP Status column header. In the filter modal, set the range to 300–599 to capture all redirect and error codes, then click OK to apply.

ℹ️ A range of 300–599 covers redirects (3xx), client errors (4xx), and server errors (5xx). To focus on server-side failures only, narrow the range to 500–599. This also leaves out 3xx redirects and 404 or 410 pages, which Prerender.io normally caches.

 

Step 4: Review the failed URLs

The filtered view shows every URL that returned an error response in recent render attempts. Check the status codes to understand the failure type. A 504 typically means a timeout, while a 404 or 410 points to a missing or removed page, which Prerender.io normally caches for on-demand crawler renders.

ℹ️ Sort the list by Render Time to surface pages that took longest to load. These are the most likely source of 504 timeout failures. See Understanding status codes for a full breakdown of what each code means.

Step 5: Fix the underlying issue and verify

Once you've identified the failing URLs, resolve the issue on your site. Then use Cache Manager to recache the affected pages.

To confirm the fix worked, return to Render History and re-apply the same 300–599 filter. Pages that failed because of timeouts or server errors and now cache successfully will no longer appear in the results. A page that still returns 404 or 410 keeps showing that status on new renders until you restore or redirect the URL. At the next scheduled recache, Prerender.io removes a still-404 or still-410 entry from the cache.

✅ Your pages are caching correctly when they no longer appear under the 300–599 filter and show a 200 status code in Render History. Pages that still return 404 or 410 are dead URLs, which Prerender.io usually caches until the next scheduled recache. Restore or redirect them if they should exist.

ℹ️ If you're seeing widespread failures across many URLs, export the filtered list from Render History before contacting support. Include the failed URLs, their status codes, and screenshots — this helps our team investigate faster.