Skip to content
busyless
Book a call

Bright Data SERP API review

Best for hard geotargeting

Claim or correct this listing
Reviewed by Eugene SuslovUpdated September 2026No affiliate links
Bright Data SERP API homepage
Bright Data SERP API homepage, captured September 2026. Source: brightdata.com.

Bright Data is a data-collection platform on which SERP is one product among many, and that context explains both its strengths and its price. Underneath sits one of the largest commercial proxy networks in existence, with automated proxy management, full browser rendering and CAPTCHA solving handled for you. The SERP API is what you get when that infrastructure is pointed at search engines and the results are parsed.

The practical differences from a pure SERP API are concurrency and geography. Concurrency is unlimited on every tier, including pay as you go, which means a large batch finishes as fast as your own code can issue requests rather than as fast as a rate limit allows. And the geotargeting reaches city level through a residential network, which is the thing that is genuinely hard to replicate cheaply.

The legal position is worth understanding before you commit, because it is unusual. Bright Data offers no indemnity, unlike SerpApi. What it has instead is precedent: in January 2024 a federal judge granted it summary judgment against Meta, holding that Meta's terms could not be read to prohibit logged-off scraping of publicly available data.

Meta subsequently dismissed its remaining claim and waived appeal. That is a favourable ruling about Bright Data's own conduct, not a shield over yours.

Our scorecard

Our editorial read across six dimensions, scored 1 to 5. This is our own assessment, not an aggregate of user reviews, and it is deliberately kept out of the page's structured data.

  • Data coverage4/5

    Seven engines with parsed JSON, plus city-level geotargeting most competitors cannot match.

  • Pricing3/5

    $1 per 1,000 is mid-market, and you pay only for success. The wider platform gets expensive quickly.

  • Documentation4/5

    Clear, with working examples in several languages and an explicit parsed-JSON flag.

  • Ease of integration4/5

    Pass a Google URL, get JSON back. The account and zone setup is more involved than a bare API key.

  • Reliability5/5

    Unlimited concurrency, sub-second responses claimed, automatic retries and IP rotation. Built for scale.

  • Support4/5

    Expert support on every tier including free, with account managers and an SLA on Enterprise.

An editorial read, not an aggregate of user reviews, and deliberately kept out of this page's structured data.

What you can pull

SERP API, synchronous

$1 per 1,000 requests, pay as you go

Pass a search URL and get the results back in under a second, as raw HTML by default or parsed JSON with one flag

Parsed JSON output

Set brd_json=1 on the request

Structured organic results, ads, knowledge panels and SERP features, rather than HTML you have to parse yourself

Asynchronous requests

Same rate, different collection model

Submit and collect later, which is how you retrieve the top 100 Google results rather than a first page

Search engines

One rate across engines

Google, Bing, DuckDuckGo, Yandex, Baidu, Yahoo and Naver, each with documented engine-specific query parameters

Geotargeting

Included

Country, state and city-level results through the residential network, which is the hard part to replicate elsewhere

Bright Data MCP

Separate product on the same account

Model Context Protocol access so an agent can run collection jobs directly rather than through a bespoke integration

Adjacent products

Same account, separate meters

Unlocker API and Crawl API at $1 per 1,000, Browser API at $5 per GB, Scraper APIs from $0.75 per 1,000 records and prebuilt Datasets from $250 per 100,000 records

Who Bright Data SERP API is for

Teams collecting SERP data at scale where geography and concurrency matter more than unit price. If you need results as seen from a specific city, or you need a very large batch to finish quickly, the residential network and the absence of any concurrency cap are worth paying for and are genuinely hard to reproduce.

It is over-specified for a straightforward national rank-tracking job. At $1 per thousand you are paying platform prices for work a simpler provider handles well, and DataForSEO, at $0.60 per thousand on its Standard queue, will do that job for less.

Strengths and limits

What it does well

  • Unlimited concurrency on every tier including pay as you go, which is rare and is what makes very large batches finish quickly.
  • City-level geotargeting through a large residential network, which is the capability that is genuinely difficult to replicate.
  • You pay only for successful requests, so failures, blocks and retries are the vendor's problem rather than a line on your invoice.
  • Seven search engines with documented engine-specific parameters and an optional parsed-JSON flag.
  • A real free tier of 5,000 records a month with no card and expert support included.
  • Proxy management, browser rendering, CAPTCHA solving and IP rotation are handled rather than being your infrastructure to run.
  • An MCP server, so agent-driven collection is a supported path.
  • A favourable legal precedent about its own model in Meta v. Bright Data, where a federal court granted it summary judgment and Meta waived appeal.

Where it falls short

  • $1 per 1,000 is well above DataForSEO's Standard-queue rate of $0.0006 per SERP, which is $0.60 per 1,000. For plain national SERPs you are paying for capability you are not using.
  • NO INDEMNITY. Bright Data winning its own case does not transfer any protection to you, and it sells no legal cover, unlike SerpApi above Production.
  • The platform is large and the pricing is per product: SERP, Unlocker, Crawl, Browser, Scraper APIs and Datasets all meter separately on one account.
  • Account and zone setup is more involved than a single API key, which lengthens the path to a first successful request.
  • Prices display in local currency but are billed in USD at the transaction-time rate, so a non-US buyer carries the exchange risk.
  • The Scale tier's monthly price is set by a slider rather than published as a figure, so the mid-market rate is not quotable from the page.
  • The residential proxy model attracts scrutiny that a datacentre-only provider does not, and that is a conversation your own compliance team may want to have.

Bright Data SERP API pricing

The SERP API is $1 per 1,000 requests on pay as you go, with no monthly commitment and self-set spend limits. A free tier gives 5,000 records a month with no card. Above that, a Scale plan bundles 380,000 requests a month with additional requests at a lower rate, and Enterprise is quoted with volume discounts, an account manager, a premium SLA and SSO.

Two mechanics matter more than the headline. You are billed only for successful requests, so blocks, retries and CAPTCHA failures cost you nothing, which on hard targets is a substantial hidden saving. And concurrency is unlimited on every tier, so throughput is bounded by your own code rather than by a plan.

Put the rate in context before buying. At $1 per thousand this is above what a metered specialist charges for a plain Google SERP: DataForSEO's Standard queue works out at $0.60 per thousand. That premium buys the residential network, the city-level geotargeting, the rendering and the unblocking, and if your job is a national desktop SERP you are not using any of it.

One practical note for non-US buyers: prices render in local currency for reference only, and the binding charge is in USD at the exchange rate on the day. Bright Data states explicitly that it is not liable for the difference.

Free tier

$0

5,000 records a month

  • No credit card required
  • Expert support included even here
  • Enough to validate the parser and the geotargeting
  • Signup currently matches a first deposit up to $500

Pay as you go

$1 / 1,000

Per successful request

  • No monthly commitment of any kind
  • Monthly spend limits you set yourself
  • Unlimited concurrency, same as every paid tier
  • Failed requests are not billed

Scale and Enterprise

Monthly or custom

380,000 requests included on Scale

  • Lower per-1,000 rate on additional requests
  • Cancel anytime on Scale, quoted terms on Enterprise
  • Enterprise adds volume discounts and an account manager
  • Premium SLA, priority support and SSO at that tier
Check current Bright Data SERP API pricing

Request example

A minimal call against the live endpoint, with credentials read from the environment rather than pasted inline.

Request a Google SERP as parsed JSON · bash
curl -s -X POST "https://api.brightdata.com/request" \
  -H "Authorization: Bearer $BRIGHTDATA_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
        "zone": "serp_api",
        "url": "https://www.google.com/search?q=pizza&hl=en&gl=us&brd_json=1",
        "format": "raw"
      }'

# You pass a real Google URL rather than learning a query DSL,
# which means anything you can express as a search URL works,
# including the engine-specific parameters.
#
# brd_json=1 returns parsed JSON instead of HTML. Leave it off
# and you get the page and parse it yourself.

Rate limits and quotas

  • SERP API pay-as-you-go rate: $1 per 1,000 requests.
  • Free tier: 5,000 records per month, no credit card required.
  • Scale tier includes 380,000 requests, with additional requests at a lower per-1,000 rate.
  • Concurrency is unlimited on all tiers, including pay as you go.
  • Billing is for successful requests only.
  • Responses are claimed at under one second per request for the synchronous endpoint.
  • Asynchronous collection is required for the top 100 Google results.
  • Engines supported: Google, Bing, DuckDuckGo, Yandex, Baidu, Yahoo and Naver.
  • USD pricing is binding; local currency amounts shown are indicative only.

What practitioners say on Reddit

Not enough discussionOur read of public threads, not a review score.

There is not enough usable practitioner discussion to report a sentiment, and the reason is structural rather than a gap in our research. r/webscraping, which is the obvious venue, explicitly removes posts that discuss paid vendor tooling in order to keep proxy-company promotion out of the subreddit.

The one direct Oxylabs-versus-Bright-Data comparison thread we located had been removed by moderators for precisely that reason, with a note that the best provider depends too much on the target site for a poll to mean anything.

That moderation policy is itself the most useful finding available. It means the public discussion of proxy and scraping vendors is unusually thin relative to their size, and that the comparisons you do find are disproportionately vendor-adjacent.

What genuinely useful discussion exists is about whether you need this class of product at all, and it is worth hearing: experienced scrapers routinely point out that plain datacentre proxies handle most targets, and that an unblocking platform is the answer to a harder problem than most people have.

  • “We're sorry to let you know that discussing paid vendor tooling or services is generally discouraged, and as such your post has been removed. This includes tools with a free trial or those operating on a freemium model.”
    r/webscraping on Reddit
  • “Removing this otherwise we just end up with too much spam from the proxy companies & their ilk Also because the best proxy provider is dependant on your task & the site you are scraping, so it varies too wildly between use cases for this poll to provide any meaningful outcome”
    r/webscraping on Reddit
  • “My first question is do you even need web unblocker? I find that I can use regular shared datacenter proxies for majority of things I scrape.”
    r/webscraping on Reddit
  • “I would say for that volume and frequency you'd be better to buy proxies directly and build your own pipeline.”
    r/webscraping on Reddit

Verdict

Buy Bright Data when geography or concurrency is the constraint. City-level results from a residential network, unlimited parallelism on every tier and billing only for successful requests is a combination nothing cheaper in this directory offers, and for hard targets the free-failures policy alone can close much of the price gap.

Do not buy it for ordinary SERP volume. At $1 per thousand you are paying platform rates for unblocking infrastructure a national desktop rank-tracking job never touches, and a metered specialist will do that work for a fraction of it. The experienced-scraper advice applies here: check whether you need the unblocker before paying for one.

On the legal question, be precise about what the precedent gives you. Bright Data won summary judgment against Meta in a case about logged-off collection of public data, and Meta waived its appeal. That is genuinely reassuring about the model and it is not protection: Bright Data sells no indemnity, so unlike SerpApi's higher tiers, the legal risk of your own collection stays with you.

Visit Bright Data SERP API

Bright Data SERP API FAQ

  • How much does the Bright Data SERP API cost?
    $1 per 1,000 requests on pay as you go, billed only for successful requests, with no monthly commitment. A free tier gives 5,000 records a month with no card. A Scale plan bundles 380,000 requests monthly at a lower additional rate, and Enterprise is quoted.
  • What does unlimited concurrency actually mean here?
    There is no cap on how many requests you may have in flight at once, on any tier including pay as you go. A large batch is therefore bounded by your own code rather than by a plan's rate limit, which is the main reason Bright Data finishes big jobs faster than metered competitors.
  • Am I charged for blocked or failed requests?
    No. Bright Data bills for successful requests only, so blocks, retries and CAPTCHA failures cost nothing. On difficult targets that is a substantial saving, and it is a large part of why the headline rate is higher than a provider that charges for every attempt.
  • Which search engines are supported?
    Google, Bing, DuckDuckGo, Yandex, Baidu, Yahoo and Naver, each with documented engine-specific query parameters. You pass a real search URL rather than learning a query language, so anything expressible as a URL works, and brd_json=1 returns parsed JSON instead of HTML.
  • Does Bright Data indemnify me legally?
    No. It sells no legal cover, which is a clear difference from SerpApi's Production tier and above. Bright Data has its own favourable precedent, but that concerns its conduct rather than yours, and the risk of what you collect and how you use it remains with you.
  • What was Meta v. Bright Data?
    Meta sued in 2023 over scraping public Facebook and Instagram data. In January 2024 Judge Chen of the Northern District of California granted summary judgment for Bright Data, holding Meta's terms could not be read to prohibit logged-off scraping of publicly available data. Meta then dismissed its remaining claim and waived appeal.
  • Is Bright Data worth it over a cheaper SERP API?
    Only if you use what the premium buys. City-level residential geotargeting, unlimited concurrency and free failures are worth a lot on hard or highly localised jobs, and worth nothing on a national desktop SERP. For the latter a metered specialist such as DataForSEO costs less for the same rows.
  • Does Bright Data have an MCP server?
    Yes, offered as its own product on the same account, so an agent can run collection jobs without a bespoke integration. That sits alongside the wider platform of Unlocker, Crawl, Browser, Scraper APIs and prebuilt Datasets, each metered separately.

This is an independent review. We have no affiliate relationship with Bright Data SERP API, earn nothing if you sign up, and no provider pays for placement in the directory. Prices were read from the vendor's own pages in September 2026 and change without notice.