> For the complete documentation index, see [llms.txt](https://help.netnut.io/netnut-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.netnut.io/netnut-documentation/netnut-scraper-apis/serp-api/google-scraper/google-search/js-rendering.md).

# JS Rendering

#### JavaScript Rendering for Google SERPs

{% hint style="info" %}
If you only need AI Overview, please make sure to use our Enhanced AI Overview feature
{% endhint %}

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 **8-12 seconds**, though in many cases it may complete faster.

***

#### Example API Request with Rendering Enabled

```bash
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** with a different price tag than regular SERP requests.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.netnut.io/netnut-documentation/netnut-scraper-apis/serp-api/google-scraper/google-search/js-rendering.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.