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. A 200 OK, a 404 or a 410 normally counts once, when Prerender.io first renders and caches it, and cache hits afterwards are free. Prerender.io drops a cached 404 or 410 at the next recache if the URL still returns it. A 301, 302 or 500 server error is not cached by default, so each request is rendered and counted. The most common causes of inflated render counts are large numbers of redirects, many different invalid URLs, 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. A 200 OK, 404 or 410 response normally counts once, on the first (uncached) render. Serving a cached copy does not count as a render. Other status codes, such as 301 and 302 redirects and 500 server errors, are not cached by default, so each request for them is rendered and counted. 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.
If you notice a difference between the render counter and dashboard values, this is most likely due to a timezone mismatch rather than an error in the actual render count.
How Prerender.io handles 404 and 410 pagesSince 20 October 2026, Prerender.io caches 404 and 410 responses from on-demand crawler renders for every account, whatever your status code caching setting is. Prerender.io serves the cached page back with its original 404 or 410 status code and keeps it for the URL's normal cache expiration.
Since 26 October 2026, serving a cached 404 or 410 does not count as a render. Only the first, uncached render counts, the same as for 200 pages.
When a scheduled recache runs and the URL still returns a 404 or 410, Prerender.io removes the entry from the cache. A dead URL is therefore cached once, then dropped at the recache. If a crawler requests it again after that, Prerender.io renders and counts it again.
ℹ️ Prerender.io does not cache a 404 or 410 when the render produced no page content, or when the URL's cache is set to never expire. Those requests are rendered and counted each time.
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. Prerender.io renders and counts the first request for each dead URL, then serves the cached 404 or 410 without counting it again until it drops the entry at the next recache. Repeat visits to the same dead URL are therefore cheap, but a large number of different dead URLs still adds up, because each one counts once.
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 yourrobots.txtfile. - 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 caches the response as a 404. - 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-codemeta 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
- How to reduce the number of pages
- How to export a report of all 404s in the past XX days
- What you pay for, and what you don't
- Status codes
- Ignore URLs and query parameters
- Best practices
💬 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