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

Do 404 or 301 pages count toward my render counter?

Yes, every page Prerender.io renders counts, regardless of the status code. Here is what causes them and how to keep the count down.

TL;DR

Every page Prerender.io renders counts against your monthly usage, whether the response is a 200 OK, a 301 redirect, a 404, or even a 500 server error. The most common causes of inflated render counts are AI and search crawlers hitting outdated or invalid URLs, large numbers of redirects, soft 404 pages that return 200, and URLs with query parameters being cached as separate entries. Audit your site's link structure and use Prerender.io's Ignore URLs filter to keep the renders focused on pages that matter.

 

Overview

Every page Prerender.io renders is counted against your monthly render quota, regardless of the HTTP status code. That includes 200 OK responses, 301 redirects, 404 errors, and 500 server errors. Keeping your URL inventory clean is what stops broken links, unnecessary redirects, and error-prone pages from quietly draining your renders.

By auditing your site's link structure and using Prerender.io's filtering tools (in particular, the Ignore URLs feature), you can reduce render usage, stay within your plan limits, and make sure only valuable content is being cached for AI crawlers and search engines.

 

Common causes of a high render counter

1. AI and search crawlers requesting invalid or obsolete URLs

AI and search crawlers (Googlebot, Bingbot, GPTBot, ClaudeBot, Perplexity, and others) regularly crawl outdated links or paths that no longer exist. Each request triggers a 404 page, and Prerender.io still renders and counts that response. The service renders every URL requested through it, regardless of the status code that comes back.

How to reduce this:

  • Use tools like Screaming Frog or Google Search Console to identify broken or outdated links still in circulation.
  • If the invalid URLs are within your control (your own site, your sitemap, internal links), correct or remove them.
  • Block crawlers from reaching outdated or irrelevant paths (for example /old-products, /temp, /dev) using your robots.txt file.
  • Exclude specific URL patterns (such as /404, /invalid/*) from rendering by adding them to your Ignore URLs and query parameters list.

2. Large number of redirects

Prerender.io does not follow redirects by default. If a page returns a 301 or 302, Prerender.io renders and counts that redirect response as-is, without automatically fetching the destination page. If that destination is also requested later (by you or by another crawler), it counts as a separate render.

How to reduce this: if your REST endpoint returns a 301 (permanent redirect) and you want crawlers to follow the redirect, add the following two meta tags in the <head> of the source page:

<meta name="prerender-status-code" content="301">
<meta name="prerender-header" content="Location: http://www.example.com">

With these tags in place, Prerender.io returns a 301 with the correct Location header so crawlers follow the redirect to the destination URL. The same pattern works for 302 by changing the status code value.

3. Soft 404 pages and URL parameters get cached

Soft 404 pages are non-existent pages that still return a 200 OK status, so Prerender.io treats them as valid and caches them. Prerender.io also treats every unique URL as a separate render, including URLs that differ only by query parameter. For example:

  • /blog
  • /blog?utm_source=newsletter
  • /blog?page=2

Even when the underlying content is identical, each of these is rendered and cached as a separate entry unless you filter them.

How to reduce this:

  • For real soft 404s on your site, add <meta name="prerender-status-code" content="404"> in the page's <head> so Prerender.io marks the response as a 404 and stops caching it as a regular page.
  • For tracking and pagination query parameters, configure them in your Ignore URLs and query parameters settings so Prerender.io collapses them to the canonical URL instead of caching each variant.

 

Audit and prevention checklist

A short routine that catches most of the cases above:

  • Crawl your site quarterly with Screaming Frog or Google Search Console and fix or remove broken internal links.
  • Keep your sitemap free of redirected or 404 URLs.
  • Disallow non-public paths in robots.txt.
  • Add prerender-status-code meta tags for soft 404s and any source pages that should signal a redirect.
  • Review the Ignore URLs and query parameters list to fold tracking and pagination variants into their canonical URL.

 

Related articles

 

💬 Still need help?
If your render counter keeps climbing despite cleanup, or you are unsure whether a specific URL pattern should be ignored, our support team can help.
→ Contact us at support@prerender.io

Was this article helpful?