Geo Location
Last updated
Last updated
The geo_location parameter customizes our service based on geographic locations and works differently depending on the website you're scraping:
General: It selects the proxy server location, allowing you to scrape data as if you're in a different country. For a complete list, click here.
Amazon: It sets the "deliver to" location, affecting product availability, prices, and how products are displayed based on the chosen delivery destination.
Google: It adjusts the Search Engine Results Page (SERP) to show results relevant to the specified location, reflecting what users in that area would see.
Continue reading below for more detailed examples for each website.
The geo_location parameter value you pass to us will yield a result with a corresponding delivery preference setting, as seen in the screenshots below:
There are a few ways you can use the geo_location parameter to get correctly-localized Amazon results.
For most Amazon domains, you can either send a zip/postcode, or a 2-letter ISO 3166-1 alpha-2 country code. Apart from a few exceptions, it sums up to two cases:
To localize the result to a place within the native country of the target marketplace, please use a zip/post code as geo_location parameter value. Examples of accepted domain & geo_location value pairs: {"domain": "com", "geo_location": "90210"}, {"domain": "co.uk", "geo_location": "W105LT"};
To localize the result to a place outside the native country of the target marketplace, please use a 2-letter country code. Examples of accepted domain & geo_location value pairs: {"domain":"com", "geo_location": "LT"}, {"domain":"de", "geo_location": "US"}.
Not all Amazon marketplaces are created equal - there are a couple of exceptions to the rules mentioned above:
cn, com.tr, com.be and nl domains don't support setting a custom delivery location - please don't send the geo_location parameter with requests to these domains;
com.au domain doesn't support setting a delivery location outside Australia - please send an Australian postcode with requests to this domain;
Instead of postcodes, .ae domain supports UAE city names as geo_location parameter values, e.g. "geo_location":"Abu Dhabi". Of course, you can use 2-letter country codes with this domain, too.
You can also use domain and locale parameters when scraping Amazon. Learn more here.
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:
Using a State Name:
Format: "State,Country"
Example: "geo_location": "California,United States"
Using a Country Name:
Pass the official country name.
Example: "geo_location": "United Kingdom"
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"
Using Google's Canonical Location Name or Criteria ID:
Find values here 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 and domain parameters along with the correct geo_location structure. This combination enhances precision and ensures that your queries align with your intended localization preferences.
You can also use domain , results_language, locale parameters when scraping Google. Learn more here.
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.
The google_suggest source accepts only two-letter ISO-3166 country codes, e.g. US, DE, LT, etc. Don't use any other input format with this source.
You can specify the delivery location at the zip code level by providing a zip code as the value for the geo_location parameter, for example, "geo_location": "60607".
Additionally, you can specify the Store ID using the context parameter.
Find the list of Walmart Store IDs here.
The geo_location parameter can be used to specify the delivery location either by zip code or by country.
Additionally, you can specify the Store ID using the context parameter. The Store ID must be a 4-digit number. For example, if the Store ID is a 3-digit number, prefix it with one zero (e.g., 618 -> 0618).
Find the list of Home Depot Store IDs here.
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".
You can also use locale parameter when scraping Bing. Learn more here.
