A unique id created for this SERP object. This id can be used to read or update this object.
The keyword to be used when doing the search. We will not automatically append any city name to the keyword. The search will be done using the exact same keyword sent. Example: pizza delivery
Unique and persistent assigned ID for the region. Example: 167
Best available English name of the geo region. Example: New York
The name of the region in the local language. Example: New York City
Fully qualified region name in a human readable format. Example: New York, NY, USA
The constructed fully qualified English name consisting of the region's own name, and that of its parent and country. This is unique and should be used when sending Regions names via our API. Example: New York,United States
ID code of the region in google maps API.
If the region is inside another region, this field contains the parent's region ID. Example: 2840
The ISO-3166-1 alpha-2 country code that is associated with the region. Example: US
The type of the region. Example: State
The approximate total population of the region. Example: 8173
The latitude of the center of the region. Example: 40.837
The longitude of the center of the region. Example: -74.413
The type of mark on map
The longitude and latitude coordinate values
Search for the nearest Region provided by its longitude, latitude, maximum distance in meters (optional) and a list containing the allowed target types, which are: autonomous community, canton, city, congressional district, country, county, department, governorate, municipality, prefecture, province, region, state, territory, tv region and union territory.
The latitude coordinate value
The longitude coordinate value
Constrain the search results to a maximum distance in meters
The list of allowed GeoTarget Location types
The search engine used to search the content. Complete list of available Search Engines: google, googlelocal, yahoo, bing, yandex, youtube, naverwebdocs, naverlocal, baidu, googlenews, googleimages, googleadvertiser, daumsite, daumweb, seznam, sogou. Examples: google, googlelocal, yahoo, bing, yandex, youtube, naverwebdocs, naverlocal, baidu, googlenews, googleimages, googleadvertiser, daumsite, daumweb, seznam, sogou
A URL that will be called when this SERP Request is ready to be downloaded. We will do a POST HTTP request sending the id from the request in a key called 'id' and telling its type which is 'serp' to the callback URL as soon the data is ready on our database. Example: mysite.com/process.php
The maximum amount of organic results we will collect from the search engine. The maximum value of this variable is determined by the user plan. This parameter counts only organic results. Default: Value defined by the search engine
If True, we will do the search using a mobile browser. By default, this variable is False. Note that, if a customUserAgent is set, this flag is ignored
If True, the system will try to prioritize this job to solve in the same request. IsRealTime flag and isLowPriority can not be used together, choose only one of them. Additional costs will apply. Default: FALSE
If True, the system will set low priority on the job to solve in the same request. IsRealTime flag and isLowPriority can not be used together, choose only one of them. Default: FALSE
True if the client created the request passing his account's credit limits
Two letters ISO 639-1 language code. If this field is not provided, we will use the default language for the country. Default: en
If this object is false, means that the SERP data is not ready yet and we are still processing it. If true, the data can be consumed.
If true, this SERP was created by our API
True if the SERP request was already sent to one of our crawlers.
Indicates if the callback URL was notified when the SERP was solved. Example: true
Indicates a failure on the callback URL notification. Example: false
When this search was requested to be processed.
When this Search was performed at the search engine.
True if you want the raw data to be saved. If you use a custom user-agent, we recommend turning this flag on.
Force our crawlers to use a specific User-Agent header for this SERP. By default, and in most situations, this field should be NULL. If you use a custom user-agent, our parsers may not be able to parse the results automatically. You should implement your own parser using the raw data provided, thus, please make sure the saveRawData field is true when using a custom user-agent. This field cannot have more than 250 characters.
True if the serp could not be solved. The spent credits will be reversed.
The amount of results the search engine has indexed to that keyword. Example: 2005
The RAW data used to parse the results.
The organic list of results for this search. This can include some special data like, for example, Google Maps Pack.
The list of advertisers that was displayed when doing this search.
The list of answers that was displayed when doing this search.
The list of videos that was displayed when doing this search.
The list of images that was displayed when doing this search.
The list of maps that was displayed when doing this search.
The list of news that was displayed when doing this search.
The list of people also ask that was displayed when doing this search.
The list of twitter that was displayed when doing this search.
The list of knowledge graph that was displayed when doing this search.
The list of playlists that was displayed when doing this search.
The list of channels that was displayed when doing this search.