Geo Location
Last updated
Last updated
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 results through UULE-based values, compatible with most Google Shopping 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 Shopping. Learn more here.
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.
For all other targets geo_location
parameter picks the location of a proxy we will use for scraping.
Check the complete list of supported geo_location
values here.
Here is an example: