# SERP Localization

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.

## Google

The `geo_location` parameter facilitates obtaining localized Google (incl. Google Shopping) results through **UULE-based** values, compatible with most Google sources. There are multiple methods to choose from:

1. **Using a State Name**:
   * Format: `"State,Country"`
   * Example: `"geo_location": "California,United States"`
2. **Using a Country Name**:
   * Pass the official country name.
   * Example: `"geo_location": "United Kingdom"`
3. **Using ISO-3166** **Country Codes:**
   * When an ISO code is provided, our system automatically converts it to the corresponding country name. Find  ISO country codes [**here**](https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzrXw45naRpCZ0Ku9AjY1%2Fuploads%2FB6LB4bYPdwi7hXuoCJ6Z%2Fcountries.json?alt=media\&token=f5c16d44-6f91-4590-a0f7-cad79bc5dd3a). 
   * Example:  `"geo_location": "GB"` for United Kingdom. 
4. **Using Coordinates and Radius**:
   * For hyperlocal results (e.g., "restaurants near me"), provide latitude, longitude, and radius values.
   * Example: `"geo_location": "lat: 47.6205, lng: -122.3493, rad: 25000"`
5. **Using Google's Canonical Location Name** or **Criteria ID**:
   * Find values [**here**](https://developers.google.com/adwords/api/docs/appendix/geotargeting) in the latest zipped CSV file.
   * Example: `"geo_location": "New York,New York,United States"` or `"geo_location": "1023191"`

If you mistakenly enter a misspelled `geo_location` parameter, our system or Google may attempt to correct it for you. However, note that specifying an existing Criteria ID is crucial for successful requests.

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**](https://developers.oxylabs.io/scraping-solutions/web-scraper-api/features/localization/domain-locale-results-language).
{% endhint %}

### Exceptions

#### Google Travel Hotels

* Only city-level `geo_location` values are supported (e.g., "`Seattle,Washington,United States`").
* Wide-area locations (e.g., "`United States`") are not supported.
* Please refer to the attached file for a list of `geo_location` values that do not yield accurate results.

{% file src="<https://63892162-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzrXw45naRpCZ0Ku9AjY1%2Fuploads%2FBMHPgPWsBEhjJRVujAa8%2Fgoogle_travel_hotels-bad_geo_locations.csv?alt=media&token=a393943d-9867-435d-a3fd-48f7a2ccc17b>" %}

## Bing

Bing supports a few `geo_location` parameter value formats.

* **City-level location**. It is very straightforward. Just pass a city-level location in the `City,State,Country` format. \
  Example: `"geo_location": "New York,New York,United States".`
* **State-level location**. Strip the first part of a city-level location and pass a `geo_location` value in the `"State,Country"` format. \
  Example: `"geo_location": "California,United States"`.
* **Country-level location**. To get results localized for the geographical center point of a country, pass an official country name. \
  Example: `"geo_location": "United Kingdom"`.
* **Coordinate-level location**. To get hyperlocal search results (beneficial for searches such as "restaurants near me"), you can pass latitude, longitude, and radius values. \
  The following example passes the coordinates of Space Needle in Seattle, WA: `"geo_location": "lat: 47.6205, lng: -122.3493, rad: 25000"`.

{% hint style="info" %}
You can also use `locale` parameter when scraping Bing. Learn more [**here**](https://developers.oxylabs.io/scraping-solutions/web-scraper-api/features/localization/domain-locale-results-language).
{% endhint %}