Compare

CrawlerData vs Serper

Same pack prices, same credit amounts, same 6-month validity. On top of Google Search, CrawlerData gives you Google Shopping product details, every seller for a product in one request, async queues with webhooks and a remote MCP server.

Last checked October 13, 2026 against Serper's public pages. Sources

Get 50 free credits See pricing

The short version

How they differ

Serper's published packs and ours have the same prices and credit amounts, $1.00 down to $0.30 per 1,000, valid 6 months. Neither is cheaper on a plain Google search.

With prices equal, the difference is what comes with them. CrawlerData has Google Shopping product details and a sellers endpoint that returns every seller in one request, Fast and Regular queues that post results to your webhook at the live price, and a remote MCP server with 8 tools on the same API key.

At a glance

CrawlerData vs Serper, as of October 13, 2026
	CrawlerData	Serper
Pricing model	Prepaid credit packs, no subscription. Credits valid 6 months	Prepaid credit packs. Credits valid 6 months
Cost per 1,000 at entry	$1.00 per 1,000 requests (Starter, $50 for 50k credits)	$1.00 per 1,000 (Starter, $50 for 50k credits)
Cost per 1,000 at volume	$0.30 per 1,000 requests (Ultimate, $3,750 for 12.5M credits)	$0.30 per 1,000 (Ultimate, $3,750 for 12.5M credits)
Free tier	50 free credits with a verified work email, valid 30 days	2,500 free queries, no credit card
Google Shopping sellers	Yes. Every seller for a product in one request, 1 credit per 10 sellers returned (rounded up, minimum 1)	Not published. A Shopping search endpoint is listed, no product or sellers endpoint
Async and webhooks	Live (synchronous), plus Fast and Regular queues with polling or a webhook (postbackUrl). Same price on every queue	Not published. Its site quotes results in 1 to 2 seconds
MCP server	Yes. Remote server at api.crawlerdata.com/mcp, 8 tools, same API key	Not published by Serper (community-built servers exist)
Failed requests	Not charged. A failed job costs 0 credits	Credits are deducted for successful responses (per its FAQ)
Rate limit	100 requests per minute and 20 per second per API key	50 to 300 queries per second, by pack

List prices in USD, excluding tax, as published on October 13, 2026. "Not published" means we could not find it on Serper's public pages. Per-1,000 figures marked "our arithmetic" divide a plan price by its volume.

Where CrawlerData fits best

Choose CrawlerData if…

You need Google Shopping beyond search results: product details with specs, and every seller for a product in one request at 1 credit per 10 sellers returned.
You run scheduled batches: Fast and Regular queues deliver by webhook (postbackUrl) or polling, at the same price as Live.
You build AI agents: our remote MCP server at api.crawlerdata.com/mcp exposes 8 tools with the same API key, alongside an OpenAPI spec.
You want organic results with real destination links, AI Overview with its sources and People Also Ask, and a desktop or mobile switch on Search.
You want Google Shopping data from a team that runs its own e-commerce price-monitoring product on the same crawler, every day.

Migration

Moving from Serper

Serper takes a JSON body with an X-API-KEY header. Ours takes a JSON body with a Bearer token, with the search parameters nested under params and the endpoint named in the body.

Serper	CrawlerData
POST google.serper.dev/search	POST api.crawlerdata.com/v1/jobs with "endpoint": "google-search"
X-API-KEY header	Authorization: Bearer YOUR_API_KEY
q	params.query
gl	params.country
hl	params.language
page	params.page (1 to 10)
organic[]	result.organic_results[]

Before: Serper

curl -X POST https://google.serper.dev/search \
  -H "X-API-KEY: YOUR_SERPER_KEY" \
  -H "Content-Type: application/json" \
  -d '{"q":"best crm software","gl":"us","hl":"en"}'

After: CrawlerData

curl -X POST https://api.crawlerdata.com/v1/jobs \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"endpoint":"google-search","params":{"query":"best crm software","country":"us","device":"desktop"},"queue":"live"}'

Organic results keep the same core fields (position, title, link, snippet) under a different key: organic_results instead of organic.
For batches, send jobs on the fast or regular queue with a postbackUrl instead of holding a connection open per query. Results are posted to you when ready, at the live price.
Keep the X-API-KEY header out of your new code: our API reads only the Authorization header.

Full request and response schemas are in the OpenAPI spec, with runnable code in the examples repo. AI clients can connect to the MCP server at https://api.crawlerdata.com/mcp with the same API key.

FAQ

Questions

How do CrawlerData and Serper prices compare?

They are the same. As of October 2026 both publish packs from $50 for 50k credits down to $3,750 for 12.5M, $1.00 to $0.30 per 1,000, valid 6 months. The difference is in what you get: Google Shopping product and sellers data, async queues with webhooks and a remote MCP server.

Does Serper return Google Shopping sellers?

Serper lists a Shopping search endpoint. We did not find a product or sellers endpoint on its site. CrawlerData's sellers endpoint returns every seller for a product in one request, at 1 credit per 10 sellers returned.

Can I get results by webhook?

On CrawlerData, yes. Send a job on the fast or regular queue with a postbackUrl, and the result is posted to you when it is ready, at the same price as a live request. Serper does not publish an async or webhook option.

Does CrawlerData return Google's AI Overview?

Yes. When Google shows an AI Overview for the query, the Google Search response includes ai_overview with its text and cited sources, next to organic results, ads, People Also Ask and the local pack.