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

What to do if some pages are not getting cached?

Make sure the page returns a 200 status, isn’t ignored by URL filters, and appears in the Cache Manager to confirm it's being cached.

Overview

If you notice that certain pages on your site aren’t appearing in the Prerender cache or aren’t being served as expected, it’s important to identify whether these pages are being cached at all. When a page isn’t cached, it may still be rendered and served to bots, but without caching, this can increase render usage and reduce performance benefits.

Uncached pages may affect SEO, increase bot load times, and lead to inconsistencies in what bots see vs. what users experience. This article outlines the most common reasons pages don’t get cached—and how to resolve them.

 

Possible Causes / Scenarios

1. Page Does Not Return a 200 OK Status

  • Prerender only caches pages with a 200 HTTP status. Pages returning 301, 404, 500, or other non-200 codes will not be cached, even if they’re rendered.

2. Page Is Excluded by the Ignored URL List

  • Prerender can be configured to ignore specific URLs or URL patterns using filters or regular expressions. If a page matches one of these patterns, it will be skipped.

3. Page Does Not Appear in the Cache Manager

  • If a page is not found in the Cache Manager, it likely hasn’t been cached yet or was evicted due to cache expiration, plan limits, or intentional exclusion.

 

Solution Steps / Troubleshooting Guide

1. Check if the URL is included in the cache manager table

  1. Go to the Cache Manager menu in your Prerender dashboard.

  2. In the search bar above the Cache Manager table, paste the URL you suspect is missing from the cache.

  3. Check the table for the URL:

    • If the URL appears in the list, it is cached.

    • If it doesn’t show up, the URL is not cached.

image-1702558626463

 

2. Verify the Page's HTTP Status Code

Prerender will only cache pages with 200 OK status, so checking what HTTP status code is returned by the page should be the first step while troubleshooting this issue. 

  1. Copy and paste the URL into your browser’s address bar (use the one that’s not being cached).

  2. Press F12 on your keyboard or right-click on the page and select “Inspect” to open Developer Tools.

  3. Click the Network tab at the top of the Developer Tools panel.

  4. Press Enter to reload the page while Developer Tools is open.

  5. Look at the first item that loads in the Network tab—this will show the HTTP status code (e.g., 200, 404, 301).

If the status code is not 200 OK, Prerender will not cache the page.

image-1702558747107

Prerender will only cache the page if it has a 200 response. Other non-200 pages will be rendered and served to bots but not cached.

It is also recommended to check the <head> part of the page if there is a <meta name="prerender-status-code" content="xxx"> tag added to the page.
This meta tag overwrites the original HTTP status of the page for Prerender so Prerender will handle the page according to the status code added in the tag. 

 

3. Is the URL included in the Ignored URL list? 

  1. Go to the Cache Manager menu in your Prerender dashboard.

  2. Click on the "Ignored URLs" tab at the top left.

  3. Check the list for the URL you’re troubleshooting.

Note: The Ignored URLs list supports regular expressions, so partial or pattern-based matches may also exclude a URL from being cached. Be sure to look beyond exact matches.

If the URL—or a matching pattern—is present in the list, Prerender will skip caching that page.

image-1702558777198

 

Additional Tips / Best Practices

  • Only 200 OK pages get cached. Redirects, errors, and meta-tag-overridden pages do not.

  • Avoid broad regex patterns in the Ignored URLs list unless needed.

  • Use the /recache endpoint to force caching of specific URLs—especially useful for new or recently updated pages.

  • Enable cache expiration wisely depending on how often your content changes (this can impact whether a page remains in cache).

 

 

Is the Prerender integration working on other pages?

Test if the Prerender integration works on the other pages based on this guide: Verify the integration

If you don't see the Prerender headers / IDs, then the Integration is not working, which might be why the other URL is not cached. 

 

Get Support

Still have questions or need help? We’re here for you!

If you’ve followed the troubleshooting steps and still can’t resolve the issue, feel free to reach out to our support team. You can contact us via:

To help us resolve your issue as quickly as possible, please gather and include any relevant information, such as:

  • The full URL(s) affected

  • HTTP status codes observed

  • Any relevant middleware configuration

  • Screenshots or screen recordings of your troubleshooting steps

Providing these details up front will help our team diagnose the problem more efficiently and get you back on track faster.

 

Related Articles / FAQs