Serper.dev vs Scrap.io in 2026: Which Google Maps Scraper Actually Wins?

Here's a number to start with. We pointed both tools at the exact same search — real estate agencies in New York City — on the same afternoon. Serper.dev handed back about 20 businesses per call and zero email addresses. Scrap.io returned 3,096 agencies, and 1,708 of them came with a verified email already attached.

Same city. Same query. Wildly different outcome.

That gap is the comparison, honestly. But there's real nuance underneath it — pricing traps, a legal case nobody else is writing about, and the awkward truth that these two tools aren't even playing the same sport. So stick with me.

Quick Verdict: Serper.dev vs Scrap.io at a Glance

Thirty seconds, one table. Here's the whole thing.

Serper dev is a SERP API that happens to cover Google Maps. Scrap.io is a Google Maps data scraper — a business data extractor built from the ground up for lead gen. Two different tools that overlap on exactly one use case. Everything below is just the receipts.

Understanding Serper.dev

Serper.dev is excellent at what it does. What it does just isn't lead generation.

So what actually is Serper.dev? It's a SERP API. You send a query, it returns structured Google results — web, images, videos, news, shopping, places, maps, reviews, scholar, patents, autocomplete. Pretty much every Google surface, delivered as clean JSON in a second or two. The speed is legitimately impressive; most competitors are two to three times slower. If you're a developer who wants google serper dev results piped into an app, it's a genuinely good tool.

For Google Maps specifically, the workflow goes like this: type a query (say, "real estate agency New York"), punch in latitude/longitude coordinates plus a zoom level, and the serper api fires back results. The playground on their site makes testing painless. Moving to production means Python — copy the code, pip install requests, run the script. If you've built with APIs before, this is familiar territory. If you haven't, you're staring at a wall of curly braces wondering what happened. There's a learning curve. I won't pretend otherwise.

Serper.dev pricing in 2026

The serper dev pricing model is pay-as-you-go, and it's refreshingly simple on the surface. Drop $50, get 50,000 credits. Bigger buckets scale down the unit cost. Here's how the tiers line up in 2026:

Two details the pricing page whispers rather than shouts. First, 1 credit buys up to 10 results — but ask for 11 to 100 results and it's 2 credits. Great if you only ever want the top 10. A nasty surprise if your script quietly requests 100 per call and doubles your burn. Second, credits expire after about 6 months, and there are 2,500 free queries to test with (one-time, not monthly). For the full SERP-vs-SERP breakdown, we wrote up Serper vs SerpApi separately — it gets into the serper api vs serpapi cost math in detail.

How to get a Serper API key

Getting a serper api key takes about a minute. Sign up on serper.dev, open your dashboard, generate the key, drop it into an environment variable (SERPER_API_KEY if you're following most tutorials). That's the serper dev api key done. From there the serper dev documentation walks you through the endpoints, and there's an active serper dev github presence plus community examples in serper api python if you'd rather learn by copy-paste.

Where's the free tier catch? There isn't a hidden one, exactly — the serper dev free tier is those 2,500 one-time queries. Plenty to kick the tyres. Not enough to build a business on.

What data fields does Serper.dev return?

This is where it gets interesting — or disappointing, depending on what you came for.

Everything Google Maps shows natively? Serper nails it. Everything that requires actually visiting the business website — emails, Instagram handles, tech stack, whether they run Meta Ads? Missing. Completely. That's not a bug. It's just not what Serper was built for. But if you're assembling a cold outreach list, a business name without an email is basically dead weight. (If phones are your thing, our phone number scraping tutorial covers that angle.)

Is Scraping Google Search Still Legal in 2026? The Google v. SerpApi Case

In December 2025, Google sued a SERP API company. Seven months later, a judge threw the case out. If you're buying SERP API credits in 2026, you should know how that ended — because none of the other "serper alternative" articles will tell you.

Here's the timeline, minus the legalese.

The original filing was blunt. In Google's own blog post, General Counsel Halimah DeLaine Prado accused SerpApi of "circumventing security measures protecting others' copyrighted content" — cloaking, giving crawlers "fake and constantly changing names," and reselling licensed material like Knowledge Panel images. Search Engine Land covered it the same day, and SerpApi's counsel fired back that "public search data should be accessible," calling it protected by the First Amendment.

Then on July 21, 2026, the court sided with the public-data argument. Google doesn't own public search results, so it couldn't show the kind of harm the claim needed. Google immediately signaled it would refile — this time aimed narrowly at the licensed Knowledge Panel content, which is a genuinely different question.

So where does that leave a Scrap.io user? I'll be careful here, because the honest answer matters more than the flattering one. The SerpApi fight is about reselling Google search results and licensed Search features. Scrap.io extracts something else entirely: public business listing data — names, addresses, phones, the emails published on a company's own website — every point traceable back to its source, and handled in line with GDPR and CCPA. Different data, different risk profile. The older US precedents the industry leans on — hiQ v. LinkedIn, Meta v. Bright Data, Van Buren v. United States — all still stand. But "the case got dismissed, so everything's legal now" would be a lie, and I'm not going to sell it to you. Read the filing, know your jurisdiction, and if you're doing something spicy, ask a lawyer instead of a blog.

Scalability: Where Serper.dev Hits Its Limits

Twenty leads from one city? Trivial. But 3,096 real estate agencies in New York? That's roughly 155 paginated API calls — and still zero emails at the end of it.

Do the arithmetic. Serper returns about 20 results per Maps call, so covering all 3,096 NYC agencies means paginating ~155 times. And that's one category in one city. Want dentists and plumbers and lawyers? Loop through categories. Want to cover a whole state? Build a coordinate grid and query each point separately, because every city needs its own lat/long. Your tidy little script just became a small engineering project — one that ends with a spreadsheet of names and no way to email any of them.

One Hacker News commenter flagged the math on exactly this: at $2 per 1,000 queries for 100-result calls, costs stack up fast the moment you're scanning multiple regions. Now stack the pagination limits of SERP-style sources on top. This next video documents that ceiling nicely — it's about a different platform, but the structural problem is identical.

It's absolutely doable, to be clear. But "doable with two days of Python" and "ready for the sales team by Friday" are not the same sentence. Our DIY vs professional scraping comparison breaks down exactly when coding it yourself stops making sense.

Scrap.io: The No-Code Alternative

Marcus runs a four-person agency. He needed 3,000 real estate leads by Friday — with emails, because a list of names doesn't close anything. Two days of Python wasn't on the menu. So here's the other path.

Scrap.io does one thing: it extracts business data from Google Maps. No web search API, no scholar results, no image search. Just Google Maps lead generation, done properly. Log in. Pick a category from 4,000+ options — or leave it blank and pull everything in a given area. Select your location: country, state, county, or city. Hit search. See a live preview with an exact result count. Filter before you spend anything. Export to CSV or Excel.

Scrap.io search interface: pick a category, select a location, get an exact count instantly.

The killer detail is the filtering — and it happens before a single credit is spent. Only businesses with an email. Only those with 10+ reviews. Only the ones currently open. On our NYC test, that meant exporting the 1,708 agencies that actually had an email instead of all 3,096 — you don't pay for contacts you can't use. A SERP API charges you for every query whether it's useful or not. There are 17 filters in total.

Scrap.io's filters run before extraction, so you only ever pay for leads that match.

The output? Seventy columns. Not a typo. Name, address, phone — the basics, yes. But also email addresses (classified into main, individual with first/last name extracted, contact, sales, marketing, finance, administration), Facebook, Instagram, LinkedIn, YouTube, TikTok, X, contact form URLs, meta title, meta description, the CMS behind the site, ad pixels, and more. If a business has a website, Scrap.io crawls it. That's the whole difference in one sentence.

And the scale is real, not marketing. One documented customer export pulled 11,734 businesses in 45 minutes — a single job, no code. A different customer told us they'd once pulled around 200,000 US restaurants in one export; a fat file, obviously, but the point holds: nobody wrote a line of Python. The database behind all this now sits at 225,676,406 businesses indexed across 195 countries and 4,000+ categories, refreshed in real time on every extraction. (That corrects the "over 200 million" figure you'll still see floating around older write-ups.)

And yes, Scrap.io has an API too — plus an MCP server

Here's the part the developer crowd usually misses. You're reading this because you use Serper inside CrewAI or LangChain — Serper ships as the native SerperDevTool in CrewAI, so I know the profile. Good news: Scrap.io speaks your language too.

There's a full REST API at https://scrap.io/api/v2/ — Bearer token auth, JSON in and out, 300 requests per minute, documented at docs.scrap.io, and included in every plan. No add-on, no enterprise upsell. A call looks like GET /api/v2/map/search?type=restaurant&city=chicago. That's it.

And there's an official Scrap.io MCP server at scrap.io/mcp, compatible with Claude, ChatGPT and Gemini. Your agent builds the radius and the polygon itself from a plain-English instruction, runs the count for free, and pulls the leads back into the conversation. If you already point Serper at Google inside an agent loop, pointing that same agent at a real Google Maps scraper API for enriched local leads is a two-minute swap.

Side-by-Side Comparison: Data Fields, Features, Output

Same query, same day, same city. One tool gave us 20 fields. The other gave us 70+. This is probably the section you scrolled straight to, so let's not waste it.

I ran both on real estate agencies in New York. Serper.dev returned solid basics — names, addresses, phones, websites, ratings, coordinates, hours, category tags. Clean, well-structured, no complaints on quality. Out of the ~3,096 agencies in the city, it can surface them 20 at a time across roughly 155 calls, and not one of those rows carries an email.

Scrap.io returned all of that — plus the enrichment. Of the same 3,096 agencies, 2,184 (70.5%) had a website, and 1,708 (55.2%) had an email address scraped straight off that website. Then the socials across six platforms, contact form URLs, meta title, meta keywords, the CMS, whether they run Meta or Google ads. If a business has a website, Scrap.io reads it. Zoom out to the whole country and there are 281,941 real estate agencies in the US sitting in the same index.

For cold outreach, that gap isn't cosmetic — it's the entire campaign. A list of names and addresses is a starting point. A list with 1,708 verified emails, LinkedIn profiles, and a flag showing who already runs Facebook Ads? That's a campaign ready to launch. (More on scraping emails from Google Maps if that's your endgame.)

Pricing Comparison: Serper.dev vs Scrap.io in 2026

Money talk. This is where most comparisons go vague. I'll be specific.

The serper dev pricing looks cheap in isolation — and then you price the email enrichment you still have to buy. Serper charges pay-as-you-go: $50 for 50,000 credits, about $1 per 1,000 queries at entry, dropping toward $0.30 at bulk. Credits expire after 6 months. Remember the trap from earlier: 100-result calls cost 2 credits, not 1. And none of those results include an email — so if you need contact data, you're bolting on Hunter.io or Snov.io at another $50 to $100 a month. The serper dev pricing per month depends entirely on how heavy your pagination gets, which is a polite way of saying "more than the sticker."

Scrap.io runs flat monthly plans. Emails, socials and tech data are baked into every export — no add-ons, no enrichment tax.

A couple of things worth knowing before you pick a tier. One credit equals one business exported, and re-exporting the same business inside a rolling 30-day window doesn't cost you again. The 7-day free trial gives you 50 searches and 100 export credits (a bank card is required to activate it). Every column is available on every plan — the tiers differ only on search zone, simultaneous categories, and the advanced geo modes.

Now the honest cost-per-lead view, which is the only number that actually matters:

For context on why this whole category is heating up: the web scraping market is worth roughly $1.56 billion in 2026 and is forecast to hit $3.49 billion by 2031, a 17.39% CAGR, according to Mordor Intelligence. Other analysts run hotter — The Business Research Company pegs it nearer $2.28 billion by 2030 at an 18.2% CAGR. The estimates diverge, and I'd rather show you the spread than pretend one number is gospel. Either way, the direction is the same: up and to the right.

Geo-Targeting: Radius & Polygon Selection

Ever tried to scrape one commercial district but not the residential streets wrapped around it? That's when geo-targeting stops being a footnote and becomes the whole job.

Serper.dev gives you GPS coordinates. Full stop. Type a latitude, a longitude, a zoom level. Want a different area? New coordinates. Want to cover a state? Build a coordinate grid and query each point separately. It works — it's just manual labour wearing an automation costume.

Scrap.io gives you three options, and the third is the one nobody else offers. Administrative divisions (country, state, county, city — no coordinates needed). Radius: drop a pin, set a distance, done. And polygon: trace a custom shape around any zone on the map.

Radius selection: drop a pin, set a distance, and Scrap.io pulls every business inside the circle — up to 500 km on the Company plan.

Polygon selection: trace a custom shape around any neighbourhood or commercial district — up to 1,000,000 km² on the Company plan.

The radius stretches to 500 km and the polygon to a million square kilometres on the top tier, and every filter still applies inside the shape. There's also a trick a SERP API structurally can't do: the catchment-area search with no category at all. Pull every business in a city, county or country without naming an activity — a full economic map of a territory. A SERP API always demands a query; it can never just draw you a region. That polygon feature is the reason agencies with local clients end up on Scrap.io. Our geomarketing guide and our piece on scraping densely populated areas go deeper.

When to Choose Serper.dev (And When to Choose Scrap.io)

Honest take. No tool is right for every situation, and pretending otherwise is how you end up trusting a comparison written by someone selling a third option.

Serper.dev makes sense when:

1. You're a developer building something that needs Google SERP data across multiple products — web, images, news, maps, shopping, scholar.
2. Google Maps is one data source in a larger pipeline and the serper api handles the extraction layer.
3. You want a lightweight, genuinely fast SERP API for an integration or a RAG stack.
4. Email and social data honestly don't matter for what you're building.

Scrap.io makes sense when:

1. You specifically need Google Maps leads — with emails, phones, socials, and enrichment.
2. You're not a developer, or you'd rather not spend a weekend on something that should take five minutes.
3. Scale matters: whole cities, states, countries.
4. Geo-targeting by radius or polygon would save you hours.
5. You are a developer — and you'd rather drive that data through a REST API or an MCP server than hand-roll pagination and email enrichment.

For more angles: Apify, Bright Data, Octoparse, OutScraper, and the SerpApi alternative if you're weighing the whole field. And a fair-warning data point on Serper's reputation: its Trustpilot page sits at a 2.9 / 5 TrustScore — but across just 6 reviews, which is far too small a sample to conclude anything. Treat it as a shrug, not a verdict. The serper dev reddit threads tell a warmer story — r/LocalLLaMA has a long-running one on SERP alternatives where developers mostly praise the speed. Scrapingdog's roundup of Serper alternatives is more useful on the technical limits (no published uptime SLA, thin formal docs), even if it's written by a competitor.

FAQ: Serper Dev, Google Maps Scrapers & Alternatives

What is Serper.dev?

Serper.dev is a SERP API for developers. You send a search query, it returns structured Google results as JSON — web, images, maps, news, shopping. For Google Maps it returns listings with basic fields (name, phone, address, rating) and no email extraction. Pricing starts at $50 for 50,000 queries, responses land in 1–2 seconds. It's infrastructure for people building their own tools, not a ready-made lead gen product.

Is Serper.dev legit?

Totally. It's a well-established SERP API integrated into CrewAI, LangChain and a stack of AI agent frameworks, and the developer community likes its speed-to-cost ratio. Just know what you're buying: raw search data, not finished lead lists.

Is Serper.dev API free?

There's a free tier, but it's a one-time allowance, not a monthly one: 2,500 free queries when you sign up. After that you're on pay-as-you-go credits ($50 for 50,000). So "is serper dev api free" has a precise answer — free to test, paid to run.

How much does Serper.dev cost?

Pay-as-you-go: $50 gets 50,000 credits, about $1 per 1,000 queries at the base tier, dropping to roughly $0.30 at volume. Two catches most people miss — a 100-result call costs 2 credits instead of 1, and credits expire after 6 months. That 2-credit rule is what quietly doubles the real bill on Maps work.

Is scraping Google Maps legal?

Scraping publicly available business data is generally legal in the US. The hiQ v. LinkedIn ruling established that accessing public data doesn't violate the CFAA, and Meta v. Bright Data and Van Buren v. United States reinforced it. The 2026 update: Google sued SerpApi in December 2025 over reselling search results and licensed content; the case was dismissed on July 21, 2026 for lack of standing, and Google has signalled an amended complaint focused on Knowledge Panels. That fight is about reselling search results — different from extracting public business listings, which is what tools like Scrap.io do, GDPR and CCPA compliant. But nobody serious should tell you scraping is now "risk-free." Read our full legal breakdown.

Does Scrap.io have an API or MCP server?

Yes to both. The REST API lives at https://scrap.io/api/v2/ — Bearer auth, JSON, 300 requests/minute, included in every plan, documented at docs.scrap.io. And there's an official MCP connector at scrap.io/mcp, compatible with Claude, ChatGPT and Gemini. Counts stay free through the MCP; you only spend credits when you export.

Can I use Serper.dev with n8n or CrewAI?

Both, yes. Serper is a native tool in CrewAI (SerperDevTool) and calls cleanly over HTTP inside n8n — the n8n serper dev combo is a common lead-pipeline pattern. The catch is the same as always: you get SERP data, not enriched leads. To pull enriched Google Maps leads in the same workflow, Scrap.io plugs in via its official Make.com module or its REST API.

What is the best Serper dev alternative for Google Maps scraping?

Depends what you mean. Want another SERP API? Look at SerpApi, SearchAPI or DataForSEO. Want a tool built specifically to extract Google Maps leads with emails and social data — which is what most people mean when they Google "serper dev alternative" — that's Scrap.io. The best serper dev alternative for google maps is the one that hands you contactable businesses, not JSON you still have to enrich.

What's the best Google Maps scraper in 2026?

For developers wanting API-level control across Google products: Serper.dev or SerpApi. For non-technical users wanting leads with full contact data: Scrap.io. For tiny one-off jobs on a budget: a Chrome extension. For maximum control at maximum cost: the official Google Places API at $17–$32 per 1,000 requests — and still no emails.

What data can you pull from Google Maps?

The basics: name, address, phone, website, ratings, reviews, hours, coordinates, categories. Advanced tools like Scrap.io add email addresses (classified by type), social profiles across six platforms, website technologies, ad pixels, contact form URLs and SEO metadata — up to 70+ columns per listing.

How many leads can I get from these tools?

Serper.dev: capped by your API budget and how much pagination you're willing to code — realistically hundreds to a few thousand per session without a serious pipeline. Scrap.io: single exports have hit five and six figures, and country-level extraction is built into the Company plan. One documented run pulled 11,734 businesses in 45 minutes.

The Bottom Line

Both tools work. I'm not going to pretend Serper.dev is bad — it isn't. For fast, cheap SERP data across every Google product, it's one of the best options out there.

But for Google Maps lead generation? It isn't close. On the same NYC query, Serper gives you ~20 fields per call, 155 calls to cover the city, and zero emails at the end. Scrap.io gives you 3,096 agencies in one export, 1,708 with a verified email, plus socials and tech data — no code, no enrichment tool bolted on. Three things decide it: data depth (70 vs 20 fields), email extraction (built-in vs buy-it-elsewhere), and usability (click a button vs write a script). And if you're a developer who assumed no-code meant no API — surprise: there's a REST endpoint and an MCP server waiting for you.

For what comes after the export — feeding a CRM, personalising outreach — see the Make.com automation tutorial and the CRM enrichment guide. Targeting real estate professionals specifically? We've got a playbook for that too.