Oxylabs Documentation
English
Search
K

Google Shopping

There are various page types we can scrape and parse on Google Shopping. You can either provide us with a full URL or a few input parameters via specifically built data sources (e.g. Shopping Search, Shopping Product, Product Pricing) so we can form the URL on our end.

Overview

Below is a quick overview of all the available data source values we support with Google Shopping.
Source
Description
Structured data
google_shopping
Submit any Google Shopping URL you like.
Depends on the URL.
google_shopping_search
Search results for a search term of your choice.
Yes.
google_shopping_product
Product page of a product ID of your choice.
Yes.
google_shopping_pricing
List of offers available for a product ID of your choice.
Yes.
You can always write your own parsing instructions with Custom Parser feature and get structured data.
You can jump to your preferred Google Shopping page type by selecting the page link below. Each page contains the parameter table as well as code examples to help you get started with your query.

Parameter values

Locale

Using thelocale parameter will allow you to change the interface language (not results) of the Google Shopping web page.
For example, if you use domain com and locale parameter de-DE, the results will still be American, but the Accept-Language header value will be set to de-DE,de;q=0.8. This would imitate a person from US searching in com domain, who has the UI of his browser set to German language.
If you don't use this parameter, we will set the 'Accept-Language' parameter to match the domain (i.e. en-US for com).
Download the full list of locale values in JSON here.
[
{
"locale":{
"en-ai":{
"description":"Anguilla - English",
"domain":"com.ai"
},
"es-pr":{
"description":"Puerto Rico - Spanish",
"domain":"com.pr"
},
...
"en-by":{
"description":"Belarus - English",
"domain":"by"
},
"en-in":{
"description":"India - English",
"domain":"co.in"
}
}
}
]

Results Language

Download the full list of results_language values in JSON here.
[
{
"results_language": "af",
"language": "Afrikaans"
},
{
"results_language": "ar",
"language": "Arabic"
},
...
{
"results_language": "vi",
"language": "Vietnamese"
}
]

Geo_location

There are a few ways you can use the geo_location parameter to get correctly-localized Google results.
  • Using a city name. It is very straightforward. Just pass us one of the values found on the CSV download here, in "City,State,Country" format. Example: "geo_location": "New York,New York,United States".
  • Using a state name. Strip the first part of a Google's Canonical Location Name and pass a geo_location value in a "State,Country" format. Works with United States, Australia, India and other countries with federated states. Example: "geo_location": "California,United States".
  • Using a country name. To get results localized for the geographical center point of a country, pass a country name. Example: "geo_location": "United Kingdom".
  • Using coordinates and radius. To get hyperlocal search results (especially useful 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".
If you pass a misspelled geo_location parameter, chances are, either we or Google will interpret and correct it for you. Nonetheless, we recommend using the parameter structures outlined above, combined with the locale and domain parameters, to get the most accurate results.
Last modified 1mo ago