Blocks and captchas
Your own scraper works for a week, then gets blocked, and somebody spends nights fixing it.
Send a query, get structured results back. The request bodies and response schemas match Serper, so moving an existing integration means changing the base URL.
Your own scraper works for a week, then gets blocked, and somebody spends nights fixing it.
Google changes its markup without warning, and the parser silently returns empty fields.
When every request is written for one provider's format, switching means rewriting the integration.
The same request bodies and response fields as Serper. Existing code keeps working after you change the address and the key.
Images, news, videos, shopping, scholar, patents, autocomplete, maps, places, reviews and a page-to-text endpoint.
Send many queries in one batch and pin results to a country, language and location.
One request costs credits only when it returns results. Your balance and usage are visible in the account and through the API.
Create an account and copy the key from the developer console.
POST the query as JSON to the endpoint you need.
Organic results, links, snippets and extra blocks arrive as structured JSON.
Request bodies and response schemas follow the same format, so an integration written for Serper works after you change the base URL and the API key.
search, images, news, videos, shopping, scholar, patents, autocomplete, maps, places, reviews and webpage, plus batch requests, account balance and a list of locations.
In credits per request. A request that returned no results because of an error on our side is not charged.
In the developer section of the account: a quickstart, the list of endpoints and a console where you can try a request.
Create an account, copy the key and try the API from the console.
Try 7 days free