You type a keyword into Google and get a page of results. Now imagine your program needs that same page, 1,000 times a day, for 1,000 different keywords, from different countries. Doing it by hand is impossible, and doing it with code is harder than it sounds.
That is the job of a SERP API. This guide explains what it is, how it works behind the scenes, what comes back, what seven providers charge, and the Google rules you should know before you build on one. Prices and field names below come from the providers' own pricing, documentation and sample responses as of 5 November 2026.
What is a SERP?#
A SERP is a search engine results page: the page you see after you search. Google's own documentation lists the pieces of that page. A normal result has a title link, a snippet, a visible URL and sometimes a date or sitelinks. Around it you can find image and video results and "exploration" boxes such as related searches and related questions.
| Part of the page | What it is |
|---|---|
| Organic results | The ranked list of web pages |
| Ads | Paid results at the top and bottom |
| Featured snippet or answer box | A short answer pulled from one page |
| People Also Ask | Related questions that expand |
| Knowledge panel | A fact box about a person, place or thing |
| Local pack and maps | Nearby businesses with ratings |
| Images, videos, shopping | Result types with their own layouts |
| AI Overview | An AI-written summary above the results |
What is a SERP API?#
A SERP API is a service that visits the search results page for you and hands back the contents as structured data. You send a keyword, a country, a language and a device type. You get back JSON with each part of the page already separated.
If APIs are new to you, our beginner guide What Is a REST API? takes about ten minutes.
Why not just fetch the page yourself? Because search engines treat automated visitors differently from people. You hit IP blocks, CAPTCHAs, pages that need JavaScript, and layouts that change without warning. A SERP API provider takes on that work and charges you per search.
How a SERP API works#
Providers describe roughly the same pipeline. This is the providers' own description of the process.
- You send a request with the keyword, location, language and device.
- The provider picks a route. It sends the search through an IP address in the right country, from a large pool, so results match what a local would see.
- It loads the page. Some parts of the page need a real browser engine to appear, so providers run browsers on their side.
- It parses the page into fields such as position, title, link and snippet.
- It returns JSON and bills you, usually only for searches that succeeded.
You never see steps 2 to 4. That hidden work is what you are paying for.
What you get back#
A typical response has a small block of information about the search, then one list for each part of the page. Each organic result usually carries a position, a title, a link and a snippet.
The names are where it gets messy. Here are the field names in the public sample responses on three providers' own sites, as of 5 November 2026:
| Part of the page | Serper | SerpApi | SearchAPI |
|---|---|---|---|
| Organic results | organic | organic_results | organic_results |
| Knowledge panel | knowledgeGraph | knowledge_graph | knowledge_graph |
| People Also Ask | peopleAlsoAsk | related_questions | not in the sample |
| Related searches | relatedSearches | related_searches | related_searches |
| Maps and local | places | local_results | not in the sample |
Two things stand out. Serper uses camelCase and the other two use snake_case. And the same box, People Also Ask, is called peopleAlsoAsk at one provider and related_questions at another. If your code reads one provider's field names, changing provider means changing your code.
The fix is a small adapter that turns every provider into one shape you control. This one handles two of them:
def normalise(vendor, data):
if vendor == "serper": # camelCase names
organic = data.get("organic", [])
paa = data.get("peopleAlsoAsk", [])
elif vendor == "serpapi": # snake_case names
organic = data.get("organic_results", [])
paa = data.get("related_questions", [])
else:
raise ValueError("unknown vendor")
return {
"results": [{"rank": r["position"], "title": r["title"], "url": r["link"]} for r in organic],
"questions": [q["question"] for q in paa],
}Run on two small samples that use the field names above, it gives the same output for both. That shows the adapter logic works, so check the field names against the provider's current documentation before relying on it.
What a SERP API costs#
Here are the prices each provider shows on its own pricing page, converted to the price per 1,000 searches so you can compare them.
| Provider | Free plan | Paid example | About per 1,000 |
|---|---|---|---|
| SerpApi | 250 searches a month | $25 for 1,000; $75 for 5,000; $150 for 15,000; $275 for 30,000 a month | $25 down to $9.17 |
| Serper | 2,500 free queries | See provider page | n/a |
| Zenserp | 50 searches a month | $49.99 for 25,000; $149.99 for 100,000 a month | $2.00 and $1.50 |
| VALUE SERP | See provider page | $50 for 25,000 credits a month, billed annually | $1.60 to $1.00 on larger plans |
| SearchAPI | 100 requests | $40 for 10,000; $100 for 35,000 a month | $4.00 and $3.00, as stated by the provider |
| DataForSEO | See provider page | Pay as you go, $0.0006 per SERP in the standard queue to $0.002 live | $0.60 to $2.00 |
| Google Custom Search JSON API | 100 queries a day | $5 per 1,000, closed to new customers | $5 |
Before you pick on price, also check whether the provider returns only the search results or also the text of each page. A SERP API returns titles, links and snippets. If your project needs the full text of those pages, you need a second step on top, and that cost is not on the SERP invoice.
The Google rules you should know#
Google's spam policies define "machine-generated traffic" as sending automated queries to Google, including scraping results for rank-checking, without express permission. They say it violates both the spam policies and the Terms of Service.
SERP API providers sit in that grey area, and the legal fight around them is still moving. We cover the lawsuit and the options in our Google search API guide. Google's official route, the Custom Search JSON API, is now closed to new customers, and existing customers have until 1 January 2027 to move.
Practical advice:
- Use a SERP API for rank tracking, monitoring and research, not as the engine of a product that must never fail.
- Pick a provider that is open about its legal position.
- Keep the adapter above, so you can switch.
- Running this for client reports? Our SEO API guide for agencies compares what each route costs for 25 clients.
- Cache results. Rankings do not change by the minute.
When a SERP API is the right tool#
| You want to... | SERP API? |
|---|---|
| Track where your site ranks for 500 keywords | Yes |
| Watch competitors' ads or local rankings | Yes |
| Collect People Also Ask questions for content ideas | Yes |
| See what shows in AI Overviews for your topics | Maybe, check the provider |
| Add "search the web" to an AI app | Often not; an AI search API may fit better |
| Search only your own website | No; use a site search |
How to choose one#
- Which search engine and which result types do you need? Not every provider covers maps, shopping or AI Overviews.
- How many searches a month? Work out the price per 1,000 at your volume.
- Do you pay only for successful searches? This matters when pages fail.
- How fast must it be? Providers state different response times. Test with your own keywords.
- How are the fields named? Plan the adapter from day one.
- What is the legal position? Read the terms and any legal-protection promise.
Before you decide#
- Prices are from each provider's page on 5 November 2026 and change often. Free tiers and some prices vary, so confirm on the provider's page.
- Speed, accuracy and uptime claims in provider docs are the providers' own, so test with your own keywords.
- Google's own policy says automated queries break its rules, so weigh that risk before you build on a SERP API.
- This is not legal advice.
Sources#
SerpApi's guides "What is a SERP?" and "Getting started with SerpApi", the You.com guide to SERP APIs, OpenWeb Ninja's "What is a SERP API?", Bright Data's SERP API introduction, Semrush, Backlinko and SiteGuru on what a SERP is, the SerpApi, Serper, Zenserp, VALUE SERP, SearchAPI and DataForSEO pricing and product pages, Google Search Central's spam policies and Visual Elements gallery, Google's Terms of Service, and Google's Custom Search JSON API overview. Where a claim is a provider's own, we say so.
Related reading#
- Google Search API: What Works After the 2027 Shutdown
- SEO API for Agencies: What to Buy and What It Costs: which provider fits which agency job, with a worked cost example.
- What Is a REST API?: new to APIs? Start here.
- API Design Principles
- Outdated API Tutorials: How to Spot One Before It Costs You