Has your Rendering paused?

Overview

If your website is no longer being rendered or updated in the Prerender.io cache, your content may not be properly served to search engines or social crawlers. This can lead to outdated or missing content in search results, directly impacting your site's SEO performance and user experience.

There are several reasons why rendering or recaching may be paused, especially depending on your plan level or account status. This article helps you identify and resolve those issues.

What Happens When Rendering Is Paused

• Recache paused - cached pages are not refreshed

• New pages cannot be added to the cache.

• Cannot use Dashboard or API endpoint to add new pages

  • If a bot requests a page that is not in the cache, the service.prerender.io endpoint returns 429 and sets the response header X-Prerender-Reject-Reason:free-limit-reached
• Cannot recache

Possible Causes

1. Starter trial plan has ended

If you are on the Starter trial plan and want to continue using the Starter plan, you’ll need to add a payment method before the trial ends. Otherwise, your plan will be automatically canceled.

Solution:

• Add a payment method:

• • Go to your Prerender dashboard
  • Open the Billing menu > Billing Info tab (Payment Method)
  • Add your payment details 
    
    

Paid Plan Overage

• Paid plans allow rendering beyond the included limit, with additional renders charged per 1,000 units.

• Rendering continues even after the included quota is exceeded.

• You will see charges for additional renders on your next invoice.

2. Automatic Recaching is Paused in the Dashboard

You may have paused recaching through your Prerender Dashboard.

Solution:

• Check if recaching is disabled/inactive

• • Go to the Prerender dashboard menu > Advanced Settings

  •  Locate Recaching

  • If inactive, toggle it back on to resume refreshing cached content.

Paused recache symptoms:

• Cached pages are not updated.

• No error response, but bots may see outdated content.

• Page freshness declines over time.

3. Cancelled account

If your account was canceled:

• Rendering and recaching are disabled.

• Requests to service.prerender.io return:

  • HTTP 503 Service Unavailable

  • Header: X-Prerender-Reject-Reason: invalid-x-prerender-token-provided

Solution:

• Contact Prerender Support to check reactivation eligibility.

• If you do not plan to continue service:

  • Remove the Prerender integration within 30 days.

  • Failure to do so could result in search engines dropping your pages from the index.

Related Articles / FAQs

• What to do if some pages are not getting cached?
• How to Avoid 429 Error Codes with Prerender
• What Should I Do If I Reach My Render Limit?
• Plan Options and How to Find the Best Plan
• Canceled or suspended account
• Changing Your Prerender Pl