Search Google Maps places
Input
query requiredSearch terms (e.g. 'tatoueur', 'pizzeria', 'dentist near me').
gl optionalGeo region (e.g. 'fr', 'us'). Empty = Maps default.
hl optionalUI language (e.g. 'fr', 'en'). Empty = Maps default.
cap optionalHard cap on returned records.
Default: 80location optionalOptional location appended to the query (e.g. 'Paris', 'Brooklyn'). If empty, only `query` is used.
maxScrolls optionalMax scroll rounds before bailing on staleness.
Default: 25Output
n optionalNumber of unique records returned.
records optionalcaptured optionalNumber of /search?tbm=map XHRs captured.
FAQ
Search Google
Run a Google search and return the page's organic result cards (title, url, site, byline, meta, snippet), with redirect wrappers already cleaned from urls. Runs logged out by default; if the browser happens to carry Google cookies, results are personalized to that account/IP. Google serves result links as redirects rather than destination addresses, so each one is followed far enough to read the address it points at before the results are returned. That adds a fraction of a second per result, and each destination site sees one request. Supports full Google query syntax: site:, quoted "exact phrases", OR, -exclude, intitle:. Quoted phrases return a smaller, more precise set; dropping quotes broadens recall with some near-miss results mixed in. Use site: to scope a domain/path, e.g. site:www.linkedin.com/in. Each call returns one results page (up to ~10 organic cards, no per-call count option). Use `page` (0-based) to move through further pages, mirroring the search results pager. Pages are reproducible on the same account/IP and are largely non-overlapping (occasional overlap of one result at page boundaries), so different pages can be fetched concurrently and unioned — always dedupe by canonical url. Narrow queries return the same results in the same order across replays on one account/IP; very broad, high-volume queries may reorder between runs. For broader coverage, fetch multiple pages concurrently and/or split the query itself — vary the site: path, phrases/OR-terms, or use `freshness` for disjoint date-bounded windows. Always dedupe by url.
Search Gmail
Search the signed-in Gmail with the native query syntax (from:, to:, subject:, has:attachment, after:/before:, labels…) and return matching threads: threadId (feed it to get_thread / reply_to_email), sender, senderEmail, subject, snippet, date, unread, starred, hasAttachment. Results are threads rather than individual messages, which is Gmail's own search granularity, and only the first page of results is returned (up to 50).
Google Autocomplete unofficial API: get autocomplete keywords
An unofficial Google Search autocomplete suggestion API: the autocomplete keywords Google suggests for a phrase, in its ranking order, for SEO and keyword research. Get the autocomplete suggestions Google offers for a search query, in the order it ranks them — the completions that would appear as you type in the search box. Partial input works well, so "best crm for" returns the ways people finish that phrase, which makes this a quick way to see what an audience actually searches for around a topic. Suggestions are personalised to the signed-in account and its location, and a query Google does not recognise comes back with an empty list rather than an error. Note that Google sometimes reinterprets an unfamiliar term and answers for a similar one, so the suggestions can drift from exactly what was asked.