Google Search Results Scraper — SERP API avatar

Google Search Results Scraper — SERP API

Pricing

from $4.50 / 1,000 results

Go to Apify Store
Google Search Results Scraper — SERP API

Google Search Results Scraper — SERP API

Google Search Results Scraper returns organic titles, real destination URLs and snippets through the Apify GOOGLE_SERP proxy. One row per accepted SERP page; failures go to diagnostics. Verified zero-result pages remain billable pages.

Pricing

from $4.50 / 1,000 results

Rating

0.0

(0)

Developer

Murat Uzun

Murat Uzun

Maintained by Community

Actor stats

0

Bookmarked

41

Total users

17

Monthly active users

9 days ago

Last modified

Features

Limited permissions

Share

What is Google Search Results Scraper?

Google Search Results Scraper is an Apify Actor that fetches Google search result pages (SERPs) and returns organic results with real, ready-to-click destination URLs as one clean, structured row per page. It works through the Apify Proxy GOOGLE_SERP group — the proxy pool Google accepts requests through — asking for Google's &gbv=1 ("basic HTML") rendering, whose links can be a decodable /url?q=<url> redirect or an opaque /url?q=<token> wrapper. The modern page can use opaque /goto?url=<token> click trackers. The Actor decodes clear destinations and follows Google's own redirect for opaque wrappers, so url is the full destination either way, never a domain guessed from the breadcrumb. Priced per accepted SERP page, not per organic listing. Filter by date range, site, file type or exact phrase, and page through up to 10 result pages per query.

Pricing: Google Search Results Scraper costs $5.00 per 1,000 results (pay per result, no subscription; Apify's free plan credit covers small runs).

What data does Google Search Results Scraper extract?

Google Search Results Scraper extracts the organic result list for every query/page combination you give it:

FieldTypeDescription
query, page, countryCode, languageCode, devicestring, numberThe request that produced this row
searchUrlstringThe exact Google URL fetched through the proxy
organicResults, organicCountarray, number{position, title, url, displayedUrl, snippet, date, sitelinks[]} per organic listing
peopleAlsoAsk, relatedSearches, ads, adCount, featuredSnippet, knowledgePanelTitlearray/object/nullParsed when present — see the FAQ, they are near-always empty on this Actor's leaner rendering
totalResultsText, htmlLengthstring, numberGoogle's own results-count text (rarely present) and the raw HTML size fetched
error, scrapedAtstringNull on accepted result pages; failures are in diagnostics, plus the ISO timestamp

Result quality and billing

Each SERP page uses one proxy attempt, with no automatic paid-proxy retry. That request can wait up to 60 seconds, shortened when the run deadline is closer. Google result-link redirects use at most six direct attempts per unique link, within the same run deadline; they do not fetch a new SERP page. Explicit Google refresh waits up to 30 seconds are honored before following the new link. After two rejected pages in a run, the Actor stops starting queued pages and lets in-flight pages finish. Effective concurrency is capped at 3 (older inputs up to 10 are still accepted). Completed, accepted pages are kept; an all-rejected run fails. Inspect OUTPUT.costGuardTriggered, costSkippedPages, rejectedPages and serpRequestAttempts before retrying skipped queries. These counters describe the current process attempt, not cumulative migration/restart totals. Defaults use 256 MB memory. This limits avoidable usage; unsuccessful requests and in-flight work can still have costs.

Only accepted SERP pages enter the default dataset. resultStatus distinguishes results (organic listings with non-empty titles and real destination URLs), no_results (an explicit Google no-match message), and features_only (useful SERP widgets without organic listings). A verified zero-result page is still a billable SERP page. A small or large unknown page, blocked page, failed fetch or page with missing organic destination URLs is stored as a unique DIAGNOSTIC-* record instead. OUTPUT lists confirmed results, diagnostics and partial/delivery state; inspect it as well as the run status.

Diagnostics do not generate the default-dataset result event. The start fee and applicable platform/proxy usage may still apply. Check the live Pricing tab for your plan. The initial result allowance caps how many source pages are attempted, in query/page order; rejected pages are not replaced with extra proxy requests. All rejected attempts fail the run unless it was deliberately stopped for time or aborted. An empty query list never starts an example search. Counts apply to the current process attempt; migration/restart deduplication is not claimed.

How to use Google Search Results Scraper

  1. Enter your search terms into Search queries, e.g. apify web scraping. One row comes back per query per result page.
  2. Set Max pages per query (up to 10) if you need more than the first ~10 results — Google returns about 10 per page.
  3. Optionally narrow the search with Date range, Only this site, File type or Exact phrase.
  4. Pick Device (desktop or mobile User-Agent), click Start, then export as JSON, CSV, Excel or HTML — every organicResults[].url is the full destination link, ready to open or crawl further (pages with missing organic destination URLs go to diagnostics instead of the paid dataset).

Example input

{
"queries": ["apify web scraping", "best crm for startups"],
"countryCode": "us",
"languageCode": "en",
"resultsPerPage": 10,
"maxPagesPerQuery": 1,
"device": "desktop"
}

Example output

{
"query": "apify web scraping",
"page": 1,
"device": "desktop",
"searchUrl": "http://www.google.com/search?q=apify+web+scraping&hl=en&gl=us&num=10&gbv=1",
"organicResults": [
{
"position": 1,
"title": "Apify: The largest marketplace of trusted tools for AI",
"url": "https://apify.com/",
"displayedUrl": "apify.com",
"snippet": "68,172 tools for your AI ... Apify is the largest marketplace of trusted tools for AI. Get real-time...",
"date": null,
"sitelinks": []
},
{
"position": 2,
"title": "Apify - GitHub",
"url": "https://github.com/apify",
"displayedUrl": "github.com › apify",
"snippet": null,
"date": null,
"sitelinks": []
}
],
"organicCount": 6,
"peopleAlsoAsk": [],
"relatedSearches": [],
"adCount": 0,
"error": null,
"scrapedAt": "2026-09-12T18:23:45.000Z"
}

Input parameters

ParameterTypeDefaultDescription
queriesarray["apify web scraping"]Search queries, one or more result pages per query
countryCodestring"us"2-letter country code (gl)
languageCodestring"en"2-letter language code (hl)
resultsPerPageinteger10Sent as num; Google currently returns ~10 per page anyway
maxPagesPerQueryinteger1Result pages fetched per query (1-10), ~10 results each
dateRangestring—hour, day, week, month or year (tbs=qdr:)
sitestring—Adds site: to every query, e.g. reddit.com or gov
fileTypestring—Adds filetype: to every query, e.g. pdf
exactPhrasestring—Adds a quoted phrase every result must contain
devicestring"desktop"desktop or mobile User-Agent
includePeopleAlsoAskbooleantrueParse People Also Ask when Google renders it (modern page only, see FAQ)
includeRelatedSearchesbooleantrueParse related searches when Google renders them
safeSearchbooleanfalseRequest SafeSearch filtering
maxConcurrencyinteger3Effective parallel pages 1-3; legacy values up to 10 are capped at 3
debugHtmlbooleanfalseSave every fetched Google page as PAGE_<n>.html in the key-value store (for bug reports)

There is no proxy configuration input — every request goes through the Apify Proxy GOOGLE_SERP group automatically, and that proxy cost is already included in the price below.

Search filters and more than 10 results per query

The filters are applied to every query in the run: dateRange sets Google's "Any time" filter (tbs=qdr:h/d/w/m/y), and site, fileType and exactPhrase add site:, filetype: and a quoted phrase to the query. The row's searchUrl shows exactly what was sent.

Measured on Apify on 9 October 2026:

  • climate with exactPhrase: "annual report", site: "gov", fileType: "pdf" and dateRange: "year": page 1 had 10 results, all on .gov sites, all dated between 21 October 2025 and 29 September 2026, with PDF page counts in the snippets.
  • Paging past the first 10: pizza delivery with maxPagesPerQuery: 2 gave 8 results on page 1 and 10 more on page 2, with no title repeated. Each page is one row and one billed SERP page.
  • resultsPerPage above 10 does not help: with resultsPerPage: 100 Google returned 9 results. Pages are therefore requested at start=10, 20, … whatever resultsPerPage says, so no results are skipped between pages; use maxPagesPerQuery for depth.

A page whose proxy request times out is saved to diagnostics, outside the result dataset. Successful pages are retained; an entirely rejected run fails unless it was deliberately stopped.

Pricing

Google Search Results Scraper uses a result event per accepted Google SERP page, rather than per organic listing. The Free-plan rate is $0.005 per page ($5.00 per 1,000 accepted pages); the paid-plan rate is $0.0045 per page in the pricing checked on October 28, 2026. The actor-start event is $0.00005 per event, with one event per GB of memory and a minimum of one. The live Pricing tab is authoritative. Failed, blocked, unrecognised and missing-destination pages go to diagnostics without a result event. Explicitly verified zero-result pages remain billable. Therefore accepted result count can be lower than queries × pages. Set Maximum cost per run (maxTotalChargeUsd); the Actor caps source attempts at the initial result allowance and stops before its timeout where possible.

Google Search Results Scraper vs. apify/google-search-scraper

Both Actors are pay-per-event and bill per Google results page, so the cost is easy to estimate up front either way; apify/google-search-scraper adds optional paid add-ons (such as AI Overview capture) and many more SERP features. Google Search Results Scraper is deliberately simple: one result event per accepted query page, plus the start event, and organicResults[].url is the full destination link on both Google layouts, rather than the opaque click-tracker link many scrapers pass through unresolved. The trade-off is that People Also Ask, ads and related searches are often empty (see the FAQ) — pick this Actor when you need clean organic URLs, not SERP widgets.

Using Google Search Results Scraper with AI agents and MCP

Google Search Results Scraper is pay-per-event with limited permissions — the two requirements for an Actor to be callable through the Apify MCP server at mcp.apify.com. An agent passes queries and gets back structured organic results with real destination URLs per page — ready for competitive research, content-gap analysis, or a lead-generation pipeline that needs to actually visit or crawl the result. The same run works from n8n, Make, Zapier and LangChain through Apify's integrations.

Short timeouts save completed results where possible. Accepted SERP pages are saved in task order as earlier pages finish or are skipped. When the run's timeout is close (the last 10 s, or 5 % of a longer run, at most 2 min) the Actor starts no new pages, saves everything it has and attempts to finish with a status message such as Stopped early before the run timeout: 12 of 40 SERP page(s) done…. Read the run's statusMessage to tell a complete result from a partial one.

Sizing a run. A SERP page takes about 1–3 s (rarely up to ~7 s) and maxConcurrency pages run in parallel, plus ~5 s start-up: 30 pages at the default concurrency of 3 fit comfortably in a 60-second timeout; for hundreds of pages raise maxConcurrency or the timeout. maxTotalChargeUsd caps the cost — the Actor fetches only as many pages as the budget covers (using your plan’s live page rate after the start fee) and says so in the status message.

FAQ

Which Google page does the Actor get, and how does url get the full link? Every request asks for Google's &gbv=1 ("basic HTML") page. Clear /url?q=<url> destinations are decoded. On October 28, 2026, a captured basic page also used opaque CAES… tokens in /url?q=<token>; these are resolved through Google's own redirect, like modern /goto?url=<token> links. Google often ignores that and serves its modern JavaScript page instead: on 9 October 2026, 11 of 16 test fetches came back modern, and which one arrives varies by query and over minutes, not reliably by User-Agent (Lynx, Opera Mini and IE6 User-Agents were tried). On the modern page every result link is /goto?url=<token>, an encrypted token with no destination in the page. For those the Actor uses a bounded sequence of direct requests to Google's own redirect and reads the destination from its answer. In a 9 October cloud check (3 queries, one page each: 2 basic pages, 1 modern page) all 25 organic results had their full URL, including all 7 from the modern page.

What happens if a destination URL cannot be resolved? The whole affected SERP page is saved as a DIAGNOSTIC-* record with its available data, without a default-dataset result event. A breadcrumb is never substituted for the destination URL. An HTTP200 response may instruct a timed refresh to a new Google tracking URL. The Actor waits the stated delay (up to 10 seconds) and follows that wrapper within the existing maximum of three requests per distinct original link. Loops, ambiguous refreshes and unrecognized pages remain unresolved; JavaScript is not executed and the destination website is not fetched. Direct redirect lookups share a maximum of three concurrent requests across the Actor, independently of page-fetch concurrency. OUTPUT records their response-status counts without storing tracker tokens. Check OUTPUT and diagnostics if a run delivers fewer accepted pages than requested.

Why are peopleAlsoAsk, relatedSearches, ads and featuredSnippet often empty? Google's basic &gbv=1 page does not include those widgets at all. The modern page usually carries People Also Ask questions, so peopleAlsoAsk is filled on the pages where Google served it; ads and related searches are rarely parsed. Which layout a page gets is Google's choice (previous question), so do not rely on these fields — pick this Actor for organic results.

Is a page with a cookie-consent banner a failure? No. The modern page sometimes carries a "Before you continue to Google" dialog on top of complete results; the Actor parses the results underneath. Only a consent page with no results is reported as blocked.

What happens if Google shows a CAPTCHA or a consent page with no results? The row's error says so ("Blocked by Google (captcha page detected)...") and the raw HTML is saved to the run's key-value store as DEBUG_<n>.html so it can be inspected; lower Max concurrency and try again later.

What if Google changes its markup? Every selector has 2-3 fallbacks. If a page still comes back with 0 organic results despite being a real (large) response, the row gets error: "Could not parse results (markup changed?)" and the HTML is likewise saved as DEBUG_<n>.html — open an issue with that file attached.

Is this legal to run? Scraping publicly visible search results is generally lower-risk than scraping logged-in content, but you are responsible for complying with Google's Terms of Service and your local laws for your use case.

Can I export to CSV or Excel? Yes, from the Output tab or the API, with a ready-made Overview view.

Part of the webdatatools web-intelligence suite — every Actor is pay-per-event, reads public data without a login, and returns one clean row per entity:

Browse the whole suite at webdatatools, or call ten of these Actors straight from Claude, Cursor or Cline with the webdatatools MCP server.

Website & domain intelligence

Content for AI, LLMs and RAG

Search, video and social

Leads, jobs and company data

Developer, app and research data

Support and feedback

Found a query pattern that returns a parse error, a selector Google changed, or a field worth adding? Open an issue on the Issues tab — attach the DEBUG_<n>.html file from the run's key-value store if you have one.

⌂ 换网址