JS Rendering

JavaScript Rendering for Google SERPs

Some features load content dynamically through JavaScript, meaning the initial HTML source does not contain all the visible content rendered in the browser. To accurately capture such dynamic content, NetNut's SERP API offers JavaScript Rendering for Google searches via the render parameter.

This feature is specifically designed and optimized to handle complex Google SERP elements, including AI Overviews, dynamic widgets, and JavaScript-driven search result blocks, ensuring you retrieve fully rendered, complete SERP data.

Parameter: render

Field	Description
Type	Boolean (true / false)
Default	false
Description	When set to true, the API will fully render the search result page, executing JavaScript before scraping. This is essential for pages where content loads asynchronously via client-side scripts.

Time & Performance

The average processing time for rendered request is approximately 12 seconds, though in many cases it may complete faster.

---

Example API Request with Rendering Enabled

curl --location 'https://serp-api.netnut.io/search?hl=en&rawHtml=1&googleDomain=www.google.com&q=Explain%20how%20photosynthesis%20converts%20light%20energy%20into%20chemical%20energy%20in%20plants&render=true' \
--header 'Authorization: Basic base64(username:password)'

---

Things to Consider

• Rendering increases response time, as it requires full page load and script execution.

• It is recommended to only use render=true when necessary (e.g., sites that heavily rely on JS).

• This feature currently supports Google SERPs only.

• Rendering is a premium feature and each rendered request will be billed as 3 standard API requests due to the additional processing resources required.