# Google Product

#### SERP API Google Query Parameters

Configure Google product queries using Thordata’s SERP API, including localization parameters, geotargeting, search type,pagination, and "advanced filters" output options.

<details>

<summary><code>product_id</code>,Product ID<strong>(Required)</strong></summary>

The parameter defines the product for which to retrieve results. Typically found in shopping results that support products (e.g., <mark style="color:$primary;"><https://www.google.com/shopping/product></mark>/{product\_id}).

**Example Request:**\
Example using the parameter `product_id`: 4887235756540435899

```sh
curl -X POST https://scraperapi.thordata.com/request \
 -H "Content-Type: application/x-www-form-urlencoded" \
 -H "Authorization: Bearer token" \
 -d "engine=google_product" \
 -d "product_id=4887235756540435899" \
 -d "json=1"
```

</details>

## Localization

<details>

<summary><strong><code>google_domain</code>,</strong>Domain<strong>(Optional)</strong></summary>

Define the search engine domain name for data crawling (default value: `google.com`).

You can modify this parameter in the system or refer to the [Google domain page](https://domains.squarespace.com/) to obtain the complete list of supported domain names.

**Example Request:**

Example results for `product_id`: 4887235756540435899 ,`google_domain`: <mark style="color:blue;">google.co.ao</mark>

```sh
curl -X POST https://scraperapi.thordata.com/request \
 -H "Content-Type: application/x-www-form-urlencoded" \
 -H "Authorization: Bearer token" \
 -d "engine=google_product" \
 -d "product_id=4887235756540435899" \
 -d "google_domain=google.co.ao" \
 -d "json=1"
```

</details>

<details>

<summary><strong><code>gl</code> ,</strong>Country<strong>(Optional)</strong></summary>

Specify the target country/region for search results (default value: `us`). Use two-letter country codes(e.g., `us`, `ru`, `uk`).

For the complete list of supported country codes, please refer to: [Google’s Country List](https://developers.google.com/adwords/api/docs/appendix/geotargeting).

**Example Request:**

Example results for`product_id`: 4887235756540435899,`gl`: <mark style="color:blue;">ru</mark>

```sh
curl -X POST https://scraperapi.thordata.com/request \
 -H "Content-Type: application/x-www-form-urlencoded" \
 -H "Authorization: Bearer token" \
 -d "engine=google_product" \
 -d "product_id=4887235756540435899" \
 -d "gl=ru" \
 -d "json=1"
```

</details>

<details>

<summary><strong><code>hl</code> ,</strong>Language<strong>(Optional)</strong></summary>

Set the interface language for search results (default value: `en`). Adopt standard language code formats (e.g., `en`, `es`, `zh-CN`).

For the complete list of supported language codes, please refer to: [Google Language Codes](https://developers.google.com/google-ads/api/docs/start).

**Example Request:**

Example results for`product_id`: 4887235756540435899,`hl`: <mark style="color:blue;">es</mark>

```sh
curl -X POST https://scraperapi.thordata.com/request \
 -H "Content-Type: application/x-www-form-urlencoded" \
 -H "Authorization: Bearer token" \
 -d "engine=google_product" \
 -d "product_id=4887235756540435899" \
 -d "json=1" \
 -d "hl=es"
```

</details>

## Geographical Location

<details>

<summary><strong><code>location</code> ,</strong>Location<strong>(Optional)</strong></summary>

Simulate initiating a search from an exact location, which must be used in conjunction with the `uule` parameter. If not specified, the geographical location of the proxy server may be adopted.

**Example Request:**

Example results for `product_id`:4887235756540435899,`location`:<mark style="color:blue;">India</mark>,`uule`:<mark style="color:blue;">w+CAIQICIFSW5kaWE</mark>

```
curl -X POST https://scraperapi.thordata.com/request \
 -H "Content-Type: application/x-www-form-urlencoded" \
 -H "Authorization: Bearer token" \
 -d "engine=google_product" \
 -d "product_id=4887235756540435899" \
 -d "json=1" \
 -d "location=India" \
 -d "uule=w+CAIQICIFSW5kaWE"
```

</details>

<details>

<summary><strong><code>uule</code> ,</strong>Encoded Location<strong>(Optional)</strong></summary>

Encode the target geographical `location` using Base64, which must be used in conjunction with the location parameter.

**Example Request:**

Example results for`product_id`: 4887235756540435899,`location`:<mark style="color:blue;">India</mark>,`uule`:<mark style="color:blue;">w+CAIQICIFSW5kaWE</mark>

```sh
curl -X POST https://scraperapi.thordata.com/request \
 -H "Content-Type: application/x-www-form-urlencoded" \
 -H "Authorization: Bearer token" \
 -d "engine=google_product" \
 -d "product_id=4887235756540435899" \
 -d "json=1" \
 -d "location=India" \
 -d "uule=w+CAIQICIFSW5kaWE"
```

</details>

## Search Types

<details>

<summary><code>offers</code> <strong>,</strong>Offers Results<strong>(Optional)</strong></summary>

Get parameter for offer results. Replaces previous seller=online results. It can be set to `1` or `true`.

The `offers` parameter cannot be used with the `offer_id` parameter.

**Example Request:**

Example results for `product_id`: 4887235756540435899<mark style="color:blue;">,</mark>`offers` :<mark style="color:blue;">1</mark>

```sh
curl -X POST https://scraperapi.thordata.com/request \
 -H "Content-Type: application/x-www-form-urlencoded" \
 -H "Authorization: Bearer token" \
 -d "engine=google_product" \
 -d "product_id=4887235756540435899" \
 -d "json=1" \
 -d "offers=1"
```

</details>

<details>

<summary><code>specs</code> <strong>,</strong>Fetch Specs Results<strong>(Optional)</strong></summary>

Parameter for getting spec results. It can be set to `1` or `true`.

The specs parameter cannot be used with the `offer_id` parameter.

**Example Request:**

Example results for `product_id`: 4887235756540435899,`specs`:<mark style="color:blue;">1</mark>

```sh
curl -X POST https://scraperapi.thordata.com/request \
 -H "Content-Type: application/x-www-form-urlencoded" \
 -H "Authorization: Bearer token" \
 -d "engine=google_product" \
 -d "product_id=4887235756540435899" \
 -d "json=1" \
 -d "specs=1"
```

</details>

<details>

<summary><code>reviews</code> <strong>,</strong>Fetch Reviews Results<strong>(Optional)</strong></summary>

Parameter for getting review results. It can be set to `1` or `true`.

The reviews parameter cannot be used with the `offer_id` parameter.

**Example Request:**

Example results for `product_id`: 4887235756540435899,`reviews`:<mark style="color:blue;">1</mark>

```sh
curl -X POST https://scraperapi.thordata.com/request \
 -H "Content-Type: application/x-www-form-urlencoded" \
 -H "Authorization: Bearer token" \
 -d "engine=google_product" \
 -d "product_id=4887235756540435899" \
 -d "json=1" \
 -d "reviews=1"
```

</details>

## Pagination

<details>

<summary><strong><code>start</code> ,</strong>Result offset<strong>(Optional)</strong></summary>

Set the starting point for search result pagination (e.g., "`start=30`" means skipping the first 30 results and starting to display from the 31st result).

**Example Request:**

Example results for `product_id`: 4887235756540435899,`start`:<mark style="color:blue;">30</mark>

```sh
curl -X POST https://scraperapi.thordata.com/request \
 -H "Content-Type: application/x-www-form-urlencoded" \
 -H "Authorization: Bearer token" \
 -d "engine=google_product" \
 -d "product_id=4887235756540435899" \
 -d "json=1" \
 -d "start=30"
```

</details>

<details>

<summary><code>page</code> <strong>,</strong>Start From Page<strong>(Optional)</strong></summary>

The parameter defines the page number of Google online sellers. There are 10 results per page. This parameter is equivalent to `start (offset)` = page \* 10.
\
This parameter is only available when offers are enabled.

**Example Request:**

Example results for `product_id`: 4887235756540435899,`page`:<mark style="color:blue;">20</mark>

```sh
curl -X POST https://scraperapi.thordata.com/request \
 -H "Content-Type: application/x-www-form-urlencoded" \
 -H "Authorization: Bearer token" \
 -d "engine=google_product" \
 -d "product_id=4887235756540435899" \
 -d "json=1" \
 -d "page=20"
```

</details>

## Advanced Filters

<details>

<summary><strong><code>filter</code> ,</strong>Results Filtering<strong>(Optional)</strong></summary>

Parameter defines filters, sorting, and pagination for reviews and offers results.

Offers filters:

fr`eeship:1` Show only products with free shipping

`ucond:1` Show only used products

`scoring:p` Sort by base price

`scoring:tp` Sort by total price

`scoring:cpd` Sort by current promotion deals (special offers)

`scoring:mrd` Sort by sellers rating

**Code Example:**

Example results for `product_id`: 4887235756540435899,`filter`:ucond:1

```sh
curl -X POST https://scraperapi.thordata.com/request \
 -H "Content-Type: application/x-www-form-urlencoded" \
 -H "Authorization: Bearer token" \
 -d "engine=google_product" \
 -d "product_id=4887235756540435899" \
 -d "filter=ucond:1" \
 -d "json=1"
```

</details>

<details>

<summary><strong><code>offer_id</code>,</strong>Offer ID<strong>(Optional)</strong></summary>

The parameter defines the ID used to get multiple offers from online sellers, which can be found in sellers\_results.online\_sellers.

The `offer_id` parameter cannot be used with the `offers`, `specifications`, and `reviews` parameters.

**Code Example:**

Example results for `product_id`: 4887235756540435899,`offer_id`:detali

```sh
curl -X POST https://scraperapi.thordata.com/request \
 -H "Content-Type: application/x-www-form-urlencoded" \
 -H "Authorization: Bearer token" \
 -d "engine=google_product" \
 -d "product_id=4887235756540435899" \
 -d "json=1" \
 -d "offer_id=detali"
```

</details>

For further assistance, contact us at **<support@thordata.com>**.


---

# Agent Instructions: 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:

```
GET https://doc.thordata.com/doc/scraping/serp-api/query-parameters/google/google-product.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.