Troubleshooting

Default Behavior By default, our service is configured to render and cache every request forwarded to it, consistent with our dedication to efficiency and high service standards. To tailor this behavior and exclude specific segments of your websit...

All Prerender.io plans have a specific number of renders included. What happens once you reach this limit varies according to your plan. If you are in a paid plan, you will be charged according to the specifications of that plan for every 1000 extra...

How we respond to bots We return the same status code that you return to us by default. There are some exceptions when we change your status code. You can read about them in the Status Code Mapping section. These are the status codes that you ca...

CDNs (e.g., Cloudflare, Cloudfront, etc) caching your site content can cause hard to identify issues. We've seen cases when the customer had a CDN hosted in front of their website, and it intercepted the request before it could even make its way to ...

If you find that Prerender.io returns empty or partially rendered pages, here are a few things to check first. Prerender.io fails to detect the ready-ness of the page. Prerender.io contains advanced logic to detect if the page has finished rende...

What can go wrong? Let's first understand how Prerender.io works to pinpoint issues in our setup. A bot tries to fetch your site (e.g., Googlebot). The Prerender.io middleware intercepts the request (based on the user agent) and invokes the ...