Learn how you can use this source for maximum paid ad visibility.
The google_ads source is optimized to retrieve Google Search (SERPs) and Google AI Overviews results with paid ads at a maximum ad rate. The source will return only ten results per page, ensuring the highest chances of paid results showing up. Other than that, it supports the same parameters as regular WebSearch.
Request samples
In this example, we make a request to google.nl to retrieve search results for the keyword adidas.
Device type and browser. The full list can be found here.
desktop
- mandatory parameter
Localization
Adapt search results to specific geographical locations, domains, and languages.
Parameter
Description
Default Value
geo_location
The geographical location that the result should be adapted for. Using this parameter correctly is extremely important to get the right data. For more information, read about our suggested geo_location parameter structures here.
-
domain
Domain localization for Google. The full list of available domains can be found here.
com
locale
Accept-Language header value which changes your Google search page web interface language. More info.
-
context:
results_language
Results language. List of supported Google languages can be found here.
-
Pagination
Controls for managing the pagination and retrieval of search results.
Parameter
Description
Default Value
start_page
Starting page number.
1
pages
Number of pages to retrieve.
1
Filtering
Options to filter and refine search results based on various criteria.
Parameter
Description
Default Value
context:
udm
udm parameter allows switching between different search tabs, such as images, places, or videos, to customize the type of results displayed. Find the accepted values here.
tbs parameter. This parameter is like a container for more obscure google parameters, like limiting/sorting results by date as well as other filters some of which depend on the tbm parameter (e.g. tbs=app_os:1 is only available with tbm value app). More info here.
-
Other
Additional advanced settings and controls for specialized requirements.
Parameter
Description
Default Value
context:
nfpr
true will turn off spelling auto-correction
false
Context parameters
All context parameters should be added to the context array as objects with key and value pairs, e.g.:
Output sample
google_ads structured output
Output dictionary
google_ads output includes fields like URL, page, results, and more. The table below presents a detailed list of each Google Ads Max element we parse, including description, data type, and relevant metadata.
The number of items and fields for a specific result type may vary depending on the search query.
Key Name
Description
Type
url
The URL of the Google search results page.
string
page
Page number.
integer
results
An object containing all search result types.
object
results.paid
List of paid advertisement results with details like title, description, URL, and sitelinks.
array
results.organic
List of organic (non-paid) search results with title, description, URL, and sitelinks.
array
results.images
Image carousel results displayed on the search page.
object
results.knowledge
Knowledge Graph panel data including title, description, images, factoids, and related searches.
object
results.navigation
Navigation tabs for switching between search types (Images, Videos, News, etc.).
array
results.instant_answers
Special features or instant answer boxes displayed on the page.
array
results.related_searches
Related search suggestions with their queries and position.
object
results.search_information
Metadata about the search including the query and total results count.
object
results.total_results_count
Estimated total number of results for the query.
integer
parse_status_code
Status code of the parsing operation.
integer
created_at
Timestamp when the scraping job was created.
timestamp
updated_at
Timestamp when the scraping job was finished.
timestamp
job_id
ID of the job associated with the scraping job.
string
status_code
Status code of the scraping job. You can see the scraper status codes described here.