Google Search API: Official vs Unofficial vs SERP-API Explained
The “Google Search API” question in 2026 is more confusing than it should be. Three different products share the term and none of them are quite what you probably want. This post walks through what each option actually returns, why Google’s official API is intentionally limited for SERP-scraping use cases, and which approach (official, unofficial scraping, modern SERP API) fits which job. For almost any SEO-adjacent use case, a third-party SERP API is the right answer, not Google’s Custom Search JSON API.
If you’re shopping for the right SERP API specifically, see best SERP APIs in 2026 and SerpApi alternatives.
The three options
| Option | What it returns | Cost | Use case |
|---|---|---|---|
| Google Custom Search JSON API (official) | Results from a custom search engine you configure | $5/1k queries, capped at 10K/day | Embedding search on your own site |
| DIY Google scraping (unofficial) | Real Google.com SERP, but you fight blocks | Proxy + infra costs | One-off projects, learning |
| Third-party SERP API | Real Google.com SERP, parsed JSON, managed infra | $0.40–25 per 1k depending on provider | SEO monitoring, rank tracking, competitive intel |
Most “Google Search API” searches end up wanting option 3, but people spend time evaluating option 1 first because it’s official and Google-branded.
Option 1: Google Custom Search JSON API (official)
Google’s official offering is the Custom Search JSON API. The headline numbers ($5 per 1,000 queries, free tier of 100/day) sound competitive with SERP API pricing. The catch is what you get back.
The Custom Search API returns results from a custom search engine you configure in Google’s Programmable Search Engine console. You define which sites the engine indexes, optionally with weights and filters. The API then returns results from that engine, not from Google.com’s full index.
What this means in practice:
- Not the same as Google.com SERP. The custom engine is a curated subset. Ranking positions, ads, AI Overview, shopping cards, and featured snippets won’t match what a user sees on Google.com.
- Designed for embedded search. The intent is “add a Google-powered search box to your own website”, and for that use case the API is genuinely good.
- Capped at 10,000 queries/day. Even if you’re willing to pay, you can’t scale past ~300K queries/month per project.
For SEO monitoring or rank tracking, the Custom Search API is the wrong tool. The data isn’t comparable to SERP data.
Option 2: DIY Google scraping (unofficial)
You can scrape Google.com directly with requests/puppeteer/playwright against a proxy pool. The result is real Google SERP data with actual ranking positions, real AI Overview, real shopping cards.
The downsides:
- Anti-bot infrastructure. Google fingerprints requests on TLS handshake, headers, behavior, and IP. A naive scraper gets captcha’d or blocked within minutes. We covered the depth of this in proxies for SERP scraping.
- Operational overhead. You’re maintaining proxy pools, handling captchas, parsing dynamic SERPs, and country-level targeting, multiplied by how often Google changes the SERP layout.
- Legal complexity. Scraping public search results sits in a legal gray area. We covered the broader picture in is website scraping legal.
DIY scraping is viable for one-off research or learning exercises. For sustained operations, the proxy and anti-bot infrastructure becomes a side business you have to maintain. Most teams that try this move to a SERP API within 6 to 12 months.
Option 3: Third-party SERP APIs
Modern SERP APIs (cloro, SerpApi, DataForSEO, Serper, ScraperAPI, ScrapingBee, BrightData) handle the scraping infrastructure for you. You make a single REST call. The provider handles proxy rotation, captcha solving, fingerprinting, country targeting, and parsing, then returns clean JSON with the actual Google.com SERP data.
This is what most teams asking about “Google Search API” actually want. The trade-offs:
- Cost. $0.40 to $25 per 1,000 calls depending on provider and feature mix. We compared pricing in cheapest SERP APIs in 2026.
- Provider lock-in. You’re committed to the provider’s response shape and uptime. Multi-provider redundancy is possible but adds complexity.
- No legal cover. The provider scrapes Google on your behalf, but you’re still using the data they return. The legal posture is similar to DIY, except the operational risk shifts to the provider.
For SEO monitoring, rank tracking, competitive intelligence, or anything else that needs real Google.com SERP data at scale, this is the right answer.
Why the confusion exists
The “Google Search API” search term has been around since the original Google AJAX Search API (deprecated 2010), the Google Search Appliance (deprecated 2018), and the various Custom Search products that evolved over the years. Add the modern third-party SERP APIs that compete on the same query, and the term now refers to at least three different things.
When someone asks for “the Google Search API”, the right clarifying question is: do you need actual Google.com SERP data, or do you need to embed search on your own site? The answer picks the option for you.
When the official Custom Search API is actually right
Three legitimate use cases:
- Embedded search on your own site. Your website needs a search box that returns results from your own pages or a small curated set of sites. Custom Search API is purpose-built for this.
- Internal index. You’re indexing a private corpus (internal documentation, intranet) and want Google’s ranking quality without scraping Google.com.
- Light-touch web search. You need basic web search results for a small-volume use case (under 10K queries/day total) and don’t care about specific Google.com ranking signals.
For these, the Custom Search API works well. For everything else, reach for a SERP API.
Decision tree
| Your use case | Pick |
|---|---|
| Embed search on my own site | Google Custom Search JSON API |
| Index a private corpus | Google Custom Search JSON API (or a self-hosted alternative like Elasticsearch) |
| SEO rank tracking | SERP API (cloro, SerpApi, etc.) |
| Competitive intelligence on SERPs | SERP API |
| AI Overview citation tracking | SERP API with AI Overview support (cloro) |
| One-off research project, low volume | DIY scraping (proxies + careful anti-bot work) |
| Sustained scraping operation, high volume | SERP API |
| AI engine coverage beyond Google | SERP API with multi-engine support (cloro) |
Pricing comparison (apples-to-apples where possible)
The Custom Search API and SERP APIs aren’t truly comparable because they return different data. But for the specific case where someone is choosing between them on cost alone:
- Google Custom Search: $5/1k queries, capped at 10K/day, returns custom engine results (not Google.com SERP).
- cloro: $0.40/1k queries, no cap, returns actual Google.com SERP including AI Overview.
- SerpApi: $5 to $25/1k queries, returns actual Google.com SERP.
If the data difference matters (it usually does), the cost comparison is moot. The Custom Search API doesn’t return what you need at any price. If the data difference doesn’t matter (rare), the Custom Search API is still capped at 10K/day, which kills most production use cases.
Bottom line
For 95% of teams asking about “Google Search API”, the answer is a third-party SERP API: cloro for the lowest per-call cost and AI engine coverage, SerpApi for established reliability at premium pricing, or one of the alternatives we compared in SerpApi alternatives.
Google’s Custom Search JSON API is the right call for embedded-search use cases (a search box on your own site), and the wrong call for anything that needs actual Google.com SERP data. The data difference isn’t a coverage limitation that disappears at a higher pricing tier; it’s a different product.
If you’re starting fresh and need real Google SERP data at scale, the cloro SERP API is the cheapest defensible option with full Google feature coverage including AI Overview. For broader context, see best SERP APIs in 2026 and cheapest SERP APIs in 2026.
Frequently asked questions
Is there an official Google Search API?+
Yes, but with major limitations. Google's official Custom Search JSON API ($5 per 1,000 queries, capped at 10,000 queries/day) returns results from a custom search engine you configure, not the full Google.com index. It's designed for embedding search on your own site, not for SEO/SERP scraping. For real Google SERP data — actual ranking positions, ads, AI Overview, shopping cards — you need a SERP API like cloro, SerpApi, or DataForSEO that scrapes Google.com directly.
Can I scrape Google legally?+
Scraping public Google search results sits in a legal gray area that depends on jurisdiction and methodology. The 2022 hiQ Labs vs LinkedIn ruling in the US established that scraping publicly accessible data isn't a CFAA violation, which provides cover for SERP scraping. However, Google's Terms of Service prohibit automated scraping, which creates a contract-law (not criminal) risk. Most teams use a SERP API provider that handles the scraping at scale, which shifts the operational risk to the provider. We covered the broader legality picture in is website scraping legal.
What's the difference between Google Custom Search API and a SERP API?+
Google Custom Search API returns results from a custom search engine — a curated subset of the web you configure. It does not return Google.com's actual SERP. SERP APIs (cloro, SerpApi, etc.) scrape Google.com directly and return the actual SERP — organic positions, ads, AI Overview, featured snippets, shopping cards, exactly what a user would see. For SEO monitoring, rank tracking, or competitive intelligence, you need a SERP API; the Custom Search API does not produce the data you need.
Why is Google's official Search API so limited?+
Google's strategic interest is in keeping users on Google.com, not enabling third parties to replicate or compete with Google's search experience. The Custom Search API is intentionally scoped to embedded-search use cases (your own site search, an internal index) rather than SERP-data use cases (rank tracking, competitive intelligence, AI training). The limitations are by design, not by accident.
How much does the Google Custom Search API cost?+
$5 per 1,000 queries above the free 100/day, capped at 10,000 queries/day. For comparison, SERP APIs that return actual Google.com SERP data cost $0.40-25 per 1,000 calls depending on provider, with no daily cap. The Custom Search API's per-query cost looks competitive on paper, but its data isn't equivalent to SERP API data, so the comparison is misleading.
