Full Google SERPs, in JSON or HTML

Google Search API

Send a keyword, get back the Google results page exactly as a searcher sees it: every block, every result, with its rank, its page and its pixel position.

  • 1,000 free SERPs
  • No credit card

Every block of the SERP

Each block on the page comes back in the JSON under its own type, with its results in display order.

TypeWhat it is
organicOrganic results
paid_top, paid_bottomGoogle Ads, at the top and bottom of the page
local_packLocal pack, with rating, review count, price range and displayed details
people_also_askPeople Also Ask questions
featured_snippetFeatured snippet (position zero)
knowledge_graphKnowledge Graph, the right-hand panel
top_storiesTop stories
videos, imagesVideos and images
shoppingShopping ads
sitelinksSitelinks under a result
ai_overview_citation, ai_overview_citation_source, ai_overview_panelAI Overviews: brands cited in the text, citation sources and source panel
location_sites, recipes, find_results_onLocation sites, recipes, “Find results on” and other blocks

Google's real pagination

Google no longer shows 100 results on a single page. We walk through the pagination page by page, like a searcher, up to 10 pages per keyword (about 100 results). Every result tells you which page it appears on.

Depth of your choice

The depth parameter goes from 1 (about 10 results) to 10 (about 100 results).

Only pages found are billed

10 pages requested, 4 found: only 4 are billed.

Search operators

site:, inurl:, intitle:, allintitle:, filetype: and logical combinations are supported.

Rank, overall rank and pixel

Three measures for every result. rank_type ranks it within its block, rank_serp among every element on the page in real vertical order, and pixel gives its distance from the top of the page. A 1st organic result sitting below a local pack and ads doesn't get the visibility its position suggests.

AI Overviews, even asynchronous

Every SERP is rendered in a real browser. AI Overviews that load after the page are captured, with the brands cited, the citation sources and the source panel.

Request parameters

One POST request to /v1/serp, up to 1,000 keywords per call. Results are then fetched by ID, or delivered to your callback URL. No code needed: the same collection runs from Claude, ChatGPT or Cursor through the MCP server. To feed agents, RAG pipelines or evaluations, see the SERP API for AI. Sending tens of thousands of keywords? See the Bulk SERP API.

ParameterDescription
search_enginegoogle_search
keywordThe keyword, operators included
devicedesktop or mobile
locationGoogle version, e.g. fr for google.fr or us for google.com
languageInterface language (e.g. en)
depthNumber of pages, from 1 to 10
geolocationOptional: city, region and country separated by commas, or a GPS position as latitude,longitude (e.g. 43.7102,7.2620)
priorityOptional: processing priority, from 1 to 10
callback_urlOptional: URL that receives the results once the keyword is processed

Build your request

curl -X POST 'https://api.semscraper.com/v1/serp' \
  -H 'Authorization: Bearer API_KEY' \
  -H 'Content-Type: application/json' \
  -d '[{"search_engine":"google_search","keyword":"restaurant","device":"desktop","location":"fr","language":"fr","depth":1,"geolocation":"Nice, Alpes-Maritimes, France"}]'
Using the Google Custom Search JSON API? It shuts down on January 1, 2027. See how to migrate to Semscraper.

Pay per request

No subscription: you top up your balance, and each SERP retrieved is deducted.

€0.30 per 1,000 keywords, page 1
+€0.20 per extra page, for 1,000 keywords

1 to 10% discount depending on the amount topped up. Your balance never expires.

FAQ

Frequently asked questions

Is this Google's official API?
No. Semscraper is not affiliated with Google: the API collects public search result pages, as a searcher sees them, and returns them structured. Google's own search API, the Custom Search JSON API, is closed to new customers and shuts down on January 1, 2027: see how to migrate to Semscraper.
Do desktop and mobile return the same results?
No, Google doesn't show the same SERP on both. The device parameter lets you choose, and the pixel position is measured on the matching rendering.
Can I get results for a specific city?
Yes, with the geolocation parameter: give the city, region and country separated by commas, for example “Nice, Alpes-Maritimes, France”.
How long does a keyword take to process?
Every account has its own queue, and the robots serve accounts in turn: one request from each account, then the next. Another customer's large batch never jumps ahead of yours. A request takes a median of about twenty seconds of collection for one page, about fifty for 10 pages. The pages of a keyword are opened one after another, as a real user would, never in parallel. If Google shows a captcha, the keyword is restarted from the first page so that all its pages come from the same session. Median collection time measured on 12 million SERPs (5.3 million one-page and 260,000 ten-page) from September 12 to October 10, 2026; add the wait in your account's queue, which depends on the volume you send. If you send a large batch yourself, it flows through gradually: the last requests finish after the first ones, and the priority parameter moves urgent ones to the front.
Are results served from a cache?
No, every request triggers a live collection.
Can I use search operators (site:, inurl:…)?
Yes. Google's operators go straight into the keyword: site:, inurl:, intitle:, allintitle:, filetype:, quotes, OR, or excluding a term with a minus sign. A query with an operator costs the same as any other. One constraint: no comma in a keyword, the API uses it as a separator.

Ready to scrape Google?

1,000 free SERPs, no credit card required.