# Features

### Search Query

The `q` parameter is the main search input for Google Places. It accepts any place type, business name, or category keyword. Results returned will be local business listings that match the query within the targeted geographic area.

**Parameter**

`q: string`

**Example**

```http
https://serp-api.netnut.io/search?engine=google_places&q=coffee
```

**Use Cases**

* Local business discovery by category
* Point-of-interest searches
* Competitor location mapping

***

### Language

Defines the language of the Google Places results and search interface.

**Parameter**

`hl: string`

**Example**

```http
https://serp-api.netnut.io/search?engine=google_places&q=coffee&hl=en
```

**Use Cases**

* Retrieve results in a specific language
* Localized business listings
* Multi-language data pipelines

***

### Geographic Location

Defines the country context for the Google Places search. This influences which regional listings are surfaced in the results.

**Parameter**

`gl: string`

**Example**

```http
https://serp-api.netnut.io/search?engine=google_places&q=coffee&gl=us
```

**Use Cases**

* Country-level place discovery
* Regional market research
* Location-based business analysis

***

### UULE Location Targeting

The `uule` parameter is an encoded location string used to set a precise geographic context for the search. It overrides general country-level targeting set by `gl` and allows you to simulate searches from a specific city or area.

UULE values are typically derived from Google's internal location encoding format.

**Parameter**

`uule: string`

**Example**

```
https://serp-api.netnut.io/search?engine=google_places&q=coffee&uule=w+CAIQICINVW5pdGVkIFN0YXRlcw
```

**Use Cases**

* Simulate searches from a specific city
* Reproduce a precise Google Places results page
* Hyperlocal business data collection

***

### Location

The `location` parameter accepts a plain-text city or region string and uses it to target results to that area. This is a simpler alternative to `uule` when you do not have an encoded location value available.

**Parameter**

`location: string`

**Example**

```
https://serp-api.netnut.io/search?engine=google_places&q=coffee&location=New+York,NY
```

**Use Cases**

* City-level place searches without encoding
* Quick geographic targeting for common locations
* Travel and hospitality data workflows

***

### Places Mode (udm)

The `udm` parameter controls the Google search mode. Setting it to `1` activates the Places results mode, ensuring the response returns local business listings rather than standard web results.

**Parameter**

`udm: integer`

**Example**

```
https://serp-api.netnut.io/search?q=coffee&udm=1
```

**Use Cases**

* Ensure place-specific result format
* Activate local listing extraction
* Prevent mixed web and place results

***

### Raw HTML Output

Controls whether raw HTML is returned alongside or instead of the structured JSON response.

Setting `rawHtml=1` appends the full HTML of the Google Places results page under the `html` key in the response. Setting `rawHtml=2` returns only the raw HTML with no structured data.

**Parameter**

`rawHtml: integer`

**Example (structured JSON plus raw HTML)**

```
https://serp-api.netnut.io/search?engine=google_places&q=coffee&rawHtml=1
```

**Example (raw HTML only)**

```
https://serp-api.netnut.io/search?engine=google_places&q=coffee&rawHtml=2
```

**Use Cases**

* Custom extraction logic from raw markup
* Archiving the full rendered results page
* Debugging structured field discrepancies

***

### Combined Example

You can combine multiple parameters to create a more precise Google Places search.

**Example**

```http
https://serp-api.netnut.io/search?engine=google_places&q=coffee&hl=en&gl=us&uule=w+CAIQICINVW5pdGVkIFN0YXRlcw&udm=1
```

This request will:

* Search Google Places for `coffee`
* Use English results for the US market
* Apply precise location targeting via `uule`
* Activate Places results mode


---

# 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://help.netnut.io/netnut-documentation/netnut-scraper-apis/serp-api/google-scraper/google-places/features.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.
