Skip to main content
Send a Google URL or a keyword, get structured JSON back. The Bright Data Google Scraper API covers Maps, Shopping, Search results, AI Mode Search, Flights and Hotels with consistent request and response shapes.
New to Bright Data? Create a free account and get $2 credit to start scraping.

How it works

You send one or more Google URLs, keywords or structured inputs to the Bright Data Google Scraper API. Bright Data handles proxies, CAPTCHAs and parsing, then returns clean JSON.
All requests use a dataset_id to specify the Google product and return results in JSON, NDJSON, JSON Lines or CSV.

Supported data types

Google Maps

Places, reviews, ratings, photos and community stats. Collect by URL or discover by CID, place ID or geographic location.

Google Maps Reviews

Full review text, ratings and reviewer metadata, filtered by a configurable lookback window.

Google Shopping

Product listings, pricing, merchants and specifications. Collect by URL or discover by keyword.

Google Shopping Search US

US-focused product search results with expanded merchant and pricing coverage.

Google SERP 100 Results

Up to 100 organic results per query with language, device and geographic targeting.

Google AI Mode Search

Answers and citations from Google’s AI-powered search experience.

Google Flights

Flight options, pricing and itineraries. Collect by URL or discover by route and dates.

Google Hotels

Hotel rates, availability and amenities. Collect by URL, filter URL or search parameters.

Which dataset IDs to use

Each Google product uses its own dataset_id. Pass the ID as a query parameter on every request.

Request methods

The Google Scraper API supports two request methods. Choose based on your volume and latency needs. Learn more in Understanding sync vs. async requests.

Capabilities and limits

Common questions

Yes. Each request triggers a live scrape against Google. There is no cached or stale data. Response times vary by endpoint: Collect-by-URL requests typically return in 10 to 30 seconds, while discovery requests may take longer depending on result volume.
Collect by URL scrapes a specific Google page you provide, such as a single Maps place, a Shopping product or a SERP URL. Discover finds Google records matching search criteria such as a keyword, a CID or a geographic area, then scrapes the results. Discovery is most useful via async requests when you don’t know the exact URLs up front.
Yes. Most endpoints accept a country parameter (ISO 3166-1 alpha-2 code), and the SERP 100 endpoint also accepts language and uule for geographic targeting. See each endpoint’s reference page for the full parameter list.
When scraping with proxies or Web Unlocker, you still need to write and maintain your own parsing logic and update it whenever Google changes its page structure. The Google Scraper API handles the entire stack: proxy rotation, anti-bot bypassing and parsing. You send a URL or keyword and get clean, structured JSON back with no scraping infrastructure or parser maintenance on your end.

Next steps

Quickstart

Scrape your first Google Maps place in 5 minutes.

Send your first request

Full code examples for every endpoint in cURL, Python and Node.js.

API reference

Endpoint specs, parameters and response schemas.