One Google scraper for 12 search types
One endpoint, 12 search types, clean JSON in about a second.
Every Google surface, one parameter
The whole API is GET /v1/search?type= plus your query. Change the type, get a different Google surface. Same key, same balance, same JSON habits across all twelve.
| type= | What comes back | Worth knowing |
|---|---|---|
| web | Organic results with positions, knowledge graph, people-also-ask, related searches | p50 ~1.2s |
| maps | Business records: name, address, phone, website, rating, review count, categories, hours | ~1s |
| places | A leaner place-result shape when you want less per row | |
| reviews | The actual Google reviews for a place: rating, text, author, date | ~0.3s responses |
| news | Headlines with source, date, link, and image | |
| shopping | Product listings with prices | |
| images | Image results | ~97 images per request (serper returns 10) |
| videos | Video results with titles and thumbnails | |
| scholar | Results from Google Scholar | |
| patents | Results from Google Patents | |
| autocomplete | Google's suggestions for a query prefix | |
| webpage | The content of a URL, fetched and parsed |
Deeper pages exist for the big ones: the Google Search API, the Google Maps scraper API, the Google Reviews API, and the Google Images API.
What data do you get?
One maps query, the first business shown two ways: as CSV for a spreadsheet, then the full JSON. Same call, same values.
That about a second is from the tookMs field in the response itself, on a real query, the day this sample was pulled. No demo environment, no cached answer.
How do you get started?
No code needed for the first run. From zero to real Google data in about two minutes:
- 1
Create a free account. Try it free, no card needed.
- 2
Type a search in the playground. Pick a type like maps or news and run it.
- 3
Export the CSV, or copy your key and run the curl below for JSON.
Code for each type
Every surface works the same way. Here are the ones people reach for first:
Swap type= for shopping, videos, scholar, patents, places, or webpage and the same request keeps working. You can also try any of them without code in the playground, and the full parameter list is in the docs.
How much does scraping Google cost?
Most types bill the applicable price per successful search. Maps bills per business returned; other Google endpoints bill per successful request. Empty and failed requests are free.
| Deposit | Google Search / 1,000 requests | Maps / 1,000 businesses | LinkedIn reads / 1,000 requests | People, Jobs, Refresh / 1,000 units |
|---|---|---|---|---|
| $10+ | $1.00 | $1.96 | $6.00 | $1.96 |
| $149+ | $0.76 | $1.49 | $4.50 | $1.49 |
| $549+ | $0.56 | $1.10 | $3.30 | $1.10 |
| $1,999+ | $0.41 | $0.80 | $2.45 | $0.80 |
| $6,500+ | $0.33 | $0.65 | $1.95 | $0.65 |
| $27,500+ | $0.28 | $0.55 | $1.65 | $0.55 |
| $50,000+ | $0.26 | $0.50 | $1.50 | $0.50 |
| $100,000+ | $0.20 | $0.40 | $1.50 | $0.40 |
Every eligible account gets $6 of free usage monthly. Each deposit keeps its prices until spent; paid funds never expire. People and Jobs bill per successful search, Refresh per accessible profile. Full profiles in People use the read rate per full profile. See all billing details.
Larger deposits unlock lower endpoint prices. Each deposit keeps its prices until spent. See the full deposit table on the pricing page. Prices in USD, ex-tax.
Funds are prepaid and never expire, so a pack you buy for one project waits for the next one.
Who uses a Google scraper?
- AI and RAG builders. Feed agents live web, news, and scholar results as clean JSON, one parameter per surface.
- Lead gen teams. Pull Maps businesses with phone and website, export the CSV, and start calling.
- SEO and marketing tools. Track rankings, people-also-ask, and autocomplete for the queries clients care about.
- Price and brand watchers. Poll shopping, news, and reviews on a schedule and get the same JSON shape every time.
Public data only
Everything CrustAPI collects is on public, logged-out Google pages that anyone can open in a browser. We don't use fake accounts, we don't scrape behind logins, and we don't defeat CAPTCHAs.
Logged-out, public-only collection has repeatedly defeated computer-fraud and contract claims, while Google's own terms restrict automated access. Both sides are worth knowing before you build. Our position, in plain words, is in our terms.
When something else is the better pick: if you need Google's SLA and a Google-billed invoice, use the official APIs; they're built for apps and they're good at that. If you enjoy running your own proxies and headless browsers, open-source scrapers work and cost only your time. And serper.dev is a well-known, solid product in this space; we wrote a side-by-side comparison at serper alternative instead of pretending it's bad.
A Google scraper won't get you emails
Maps records include a phone and a website for most businesses. They do not include email addresses, because Google Maps doesn't show them. Any tool that promises emails from Maps is getting them somewhere else, usually by crawling the business website and guessing.
If verified emails are the point of your list, that data lives on our LinkedIn side: people search, profiles, companies, jobs, and posts, with a verified email attached to people results. Start with the LinkedIn people search API (beta).
Common questions
Stated neutrally: logged-out, public-only collection has repeatedly defeated computer-fraud and contract claims, while Google's terms restrict automated access. We only touch public pages, never anything behind a login, and we don't defeat CAPTCHAs. Our stance is written out in our terms; if your use case is sensitive, run it past your own lawyer.
Twelve: web search, maps, places, reviews, news, shopping, images, videos, scholar, patents, autocomplete, and webpage. All through the same /v1/search endpoint, keyed by the type parameter.
No, and be careful with tools that say otherwise. Maps records carry phone, website, address, rating, reviews, categories, and hours, and Google Maps simply doesn't show emails. Verified emails come from our LinkedIn people endpoints instead, attached to people results.
No. You call an HTTPS endpoint with your key and get JSON. Keeping the data flowing is our job; when Google changes something, we fix it on our side.
Published numbers: maps around 1 second, web search p50 around 1.2 seconds, reviews around 0.3 seconds. The response includes a tookMs field so you can check us on every call.
It costs nothing. You're only charged when a query returns results, and unused paid funds never expire, so a pack lasts across projects.
Clay
Point it at Google
the free plan covers real work across all 12 types. Run one query and read the JSON that comes back.
Try for free