Google Search Scraper & SERP Results API
Under maintenancePricing
from $2.70 / 1,000 api request attempts
Google Search Scraper & SERP Results API
Under maintenanceCollect Google search result pages as JSON for SEO research, keyword tracking, and competitor discovery. Control language, country, and result offset; batch up to 20 queries. $0.0027/request attempt + $0.002/run. Paid Apify plan required.
Google Search Scraper & SERP Results API
Collect Google search result pages as structured JSON for SEO research, keyword tracking, and competitor discovery.
Use the Apify input form or API to send 1–20 requests per run. Each successful request saves one complete response page in the dataset. No proxy setup or separate API key is needed.
What can you use it for?
- Collect query snapshots to compare search visibility over time.
- Discover competing pages and domains for selected keywords.
- Feed localized search results into a research or content planning pipeline.
Quick start
- Use a paid Apify account and set a spending limit that covers your batch.
- Paste the example below into the input form, then replace the query values.
- Start the Actor and open its dataset when the run finishes.
{"requests": [{"q": "coffee beans","num": 10}]}
Input parameters
Wrap query objects in the requests array. Each object requests one page.
| Parameter | Meaning |
|---|---|
q | Required search query. |
num | Optional requested result count, 1–100; actual totals may vary. |
start | Optional result offset. |
hl, gl | Optional language and two-letter country code. |
location | Optional human-readable search origin. |
safe | Optional active or off adult-content filter. |
fast_mode | Optional organic-only mode, excluding other result groups. |
Output and pagination
Each successful request creates one dataset record with:
| Field | Meaning |
|---|---|
requestIndex | Zero-based position of the request in your batch. |
queryParams | The query parameters used for that request. |
upstreamRunId | Request receipt identifier, when returned. |
output | The complete response page, including returned result arrays and pagination metadata. |
Result arrays stay nested inside output; individual results are not flattened into separate dataset rows. JSON is the recommended export format for preserving the full response. Available fields depend on the query and returned page. Output order can vary: use requestIndex to match records to inputs.
Supply start in a new request to fetch a subsequent offset. Results vary with query and localization; there is no automatic ranking history.
Pricing
$0.0027 per request attempt + $0.002 per valid run. All data returned in a page is included in that request fee; there is no separate per-result fee.
| Batch | Actor event charges |
|---|---|
| 1 request | $0.0047 |
| 10 requests | $0.029 |
| 20 requests | $0.056 |
Empty pages and failed request attempts also incur the request fee. The Actor charges before calling the data API. Invalid input, an unacceptable price quote, or an insufficient batch spending limit stops paid requests. A batch stops on an error; already attempted requests remain billed, and another in-flight request may still be charged.
Requirements and limits
This Actor collects search result pages. It does not crawl the linked websites, guarantee an exact result count, or guarantee that any particular rich result appears.
- External customers on paid Apify plans only. Free-plan, owner, platform test, development, CI, and standby runs are disabled.
- Run with 128 MiB of memory. A batch contains at most 20 requests, with two concurrent workers.
- Pagination is manual. Requested result counts are best-effort limits, not guaranteed totals.
- Each response is limited to 4 MiB. Paid request attempts are not automatically retried.
Frequently asked questions
Do I need my own API key or proxy?
No. Supply only the supported query parameters. Connection settings are managed by the Actor.
Is there a free trial?
No. This Actor requires a paid Apify plan and bills per request attempt.
Can I call it from my application?
Yes. Use the Actor's API button in Apify Console for its run endpoint and authenticated code examples. Paying customers can schedule or automate purchases using Apify.
Why is a page one dataset row?
A row preserves the complete response and its pagination metadata. Process the nested result arrays in your application if you need one row per result.
Related data APIs
- Google Maps Scraper & Business Search API
- Google Shopping Scraper & Product Search API
- Instagram Posts Scraper & User Posts API
- TikTok Video Search Scraper & Keyword API
Support
For input or output questions, use the Actor's Issues tab when available. Include the run ID and a description of the problem; omit credentials and private data.
This is an independent Xtech tool, unaffiliated with or endorsed by the named platform.

