> For the complete documentation index, see [llms.txt](https://developers.oxylabs.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developers.oxylabs.io/products/web-scraper-api/features/localization/serp-localization.md).

# SERP Localization

Learn how to get SERP results from the required geolocation.

Use the `geo_location` parameter to adjust the Search Engine Results Page (SERP) to show results relevant to the specified location, reflecting what users in that area would see.

## Value formats

Use one of the value formats below. The last two columns show whether the format localizes results on each engine.

<table><thead><tr><th width="121.60546875">Format</th><th width="258.8046875">Value pattern</th><th width="204.9140625">Example</th><th width="94.42578125" align="center">Google</th><th width="80.62109375" align="center">Bing</th></tr></thead><tbody><tr><td>City</td><td><code>City,State,Country</code> (Google's canonical location name)</td><td><code>New York,New York,United States</code></td><td align="center">✓</td><td align="center">—</td></tr><tr><td>State</td><td><code>State,Country</code></td><td><code>California,United States</code></td><td align="center">✓</td><td align="center">—</td></tr><tr><td>Country</td><td>official country name</td><td><code>United Kingdom</code></td><td align="center">✓</td><td align="center">✓</td></tr><tr><td>ISO country code</td><td><a href="https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzrXw45naRpCZ0Ku9AjY1%2Fuploads%2FB6LB4bYPdwi7hXuoCJ6Z%2Fcountries.json?alt=media&#x26;token=f5c16d44-6f91-4590-a0f7-cad79bc5dd3a">ISO-3166</a> alpha-2, converted to the country name</td><td><code>GB</code></td><td align="center">✓</td><td align="center">✓</td></tr><tr><td>Coordinates + radius</td><td><code>lat: &#x3C;lat>, lng: &#x3C;lng>, rad: &#x3C;metres></code> — for hyperlocal results such as "restaurants near me"</td><td><code>lat: 47.6205, lng: -122.3493, rad: 25000</code></td><td align="center">✓</td><td align="center">—</td></tr><tr><td>Google Criteria ID</td><td>numeric ID from Google's <a href="https://developers.google.com/google-ads/api/data/geotargets">geotargets list</a></td><td><code>1023191</code></td><td align="center">✓</td><td align="center">—</td></tr></tbody></table>

## Google

A misspelled or unrecognised `geo_location` value is not rejected: the request succeeds with no location applied. Double-check spelling, and use a Criteria ID when precision matters.

Additionally, consider combining the `locale` parameter with the correct `geo_location` structure. This combination enhances precision and ensures that your queries align with your intended localization preferences.

{% hint style="info" %}
You can also use `results_language`, `locale` parameters when scraping Google. Learn more [**here**](/products/web-scraper-api/features/localization/domain-locale.md).
{% endhint %}

### Exceptions

#### Google Travel Hotels

* Use city-level `geo_location` values (e.g., "`Seattle,Washington,United States`") for accurate results.
* Wide-area values (e.g., "`United States`") are accepted but return hotels from across the whole area rather than one city.
* Please refer to the attached file for a list of `geo_location` values that do not yield accurate results.

{% file src="/files/0jdP98jjNOFLgOlJfTP2" %}

## Bing

For Bing, `geo_location` localizes results at **country level**: pass an official country name or an ISO-3166 alpha-2 code (see the table above). City-, state- and coordinate-level values are accepted but only their country is applied.

{% hint style="info" %}
You can also use `locale` parameter when scraping Bing. Learn more [**here**](/products/web-scraper-api/features/localization/domain-locale.md).
{% endhint %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://developers.oxylabs.io/products/web-scraper-api/features/localization/serp-localization.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.