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.

pageURL

pageShopping Search

pageShopping Product

pageProduct Pricing

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

The geo_location parameter facilitates obtaining localized Google 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 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"

4. 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.