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

How to Avoid 429 Error Codes with Prerender

Prerender will return a 429 error code to the bots if the Prerender crawlers get a 429 error or if the Free Prerender plan's rendering limit is reached.

 

Overview

If you're on the Free plan and see 429 status codes in your Google Search Console or logs, it likely means you've reached your monthly usage limit on Prerender. When that happens, any uncached pages requested by bots won’t be rendered — instead, they receive a 429 "Too Many Requests" response. This can negatively affect your SEO if search engines can't access your fully rendered pages.

Basic_Plan_Render_Counter

 

Why It Matters

Search engine bots rely on receiving complete HTML content, especially for JavaScript-heavy sites. A 429 error prevents proper indexing and ranking. Paid plans allow continuous rendering even when limits are reached, preserving both user experience and SEO visibility.

 

How to Check

Go to the Billing section in your Prerender dashboard to view your current usage and plan limits.

 

Solutions

Upgrade Your Plan

Switch to a paid plan (Essential, Advanced, Enterprise) to avoid 429 errors. These plans continue to render uncached pages and charge overage fees without interrupting bot access.

Avoid Internal Rate Limits

If you're on a paid plan and still seeing 429s, the issue may come from your own infrastructure:

 

Recaching Strategy

Excessive recaching can also overload your server. If your cache expiration time is too low, Prerender may flood your origin with requests, triggering rate limits.

Tip: Increase your cache duration in the dashboard or selectively refresh only updated pages using the /recache API.

Additional Tips / Best Practices

  • 429s are SEO-critical: If bots receive them frequently, they may slow down or halt crawling.

  • Paid Prerender plans do not send 429s—they only occur if your server does.

  • Set cache durations based on how often your pages actually change.

  • Use regex filters or ignored URL lists to reduce unnecessary rendering of low-priority pages.

  • Ensure your integration only sends bot traffic to Prerender—filter out human traffic in middleware.

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:

  • Affected URLs

  • Your current Prerender plan

  • Screenshots of 429 errors

  • Details on any recaching or firewall settings

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

 

Related Articles / FAQs