Google Search Results Scraper

What this Actor does

Extract the organic result list from public search-engine results page (SERP) URLs as clean, structured JSON.

It processes user-provided public SERP URLs, optionally checks for JSON-LD / schema.org structured data, and primarily uses a conservative fallback that reads the visible public HTML: for each organic result it captures the title, result URL, displayed URL, snippet, and position. Google redirect links (/url?q=...) are resolved to the real destination, internal search-engine chrome links are skipped, and results are deduplicated by URL before being saved to the Apify dataset.

Why this Actor is useful

Marketers, SEO analysts, and researchers use SERP extraction to turn scattered result pages into a clean, API-ready dataset. It replaces manual copy-paste, supports repeatable rank and visibility monitoring, and feeds spreadsheets, dashboards, and reporting pipelines.

Who this is for

• SEO analysts and consultants
• Content and marketing teams
• Brand and competitor monitoring
• Market and academic researchers
• Data teams building search-intelligence datasets

Common use cases

• Capture the organic result list for a query
• Track which pages rank for a term over time
• Feed SERP data into reporting or BI tools
• Monitor brand or competitor visibility

Input

Field	Type	Description
startUrls	array (required)	Public SERP URLs to extract from. Use only pages you may access without login or bypassing access controls.
maxItems	integer	Maximum rows to save. Default 50, min 1, max 10000.
maxConcurrency	integer	Pages processed in parallel. Default 3, min 1, max 20.
extractionMode	string	structuredDataOnly or structuredDataWithFallback (default). The fallback safely reads the visible public SERP HTML.
requestTimeoutSecs	integer	Maximum time per page. Default 30, min 5, max 180.
proxyConfiguration	object	Optional Apify proxy configuration where permitted by your source review.

Output

Field	Description
resultTitle	Title of the organic result.
resultUrl	Destination URL of the result (Google redirects are resolved).
displayedUrl	Hostname shown for the result.
snippet	Result snippet / description text when present.
position	1-based position of the result in DOM order.
resultType	Result type, organic.
searchQuery	The query parsed from the q= parameter of the SERP URL.
sourceUrl	URL where the data was extracted.
detectedAt	Timestamp when this Actor extracted the row.
extractionMethod	structured_data for schema data, or fallback_public_serp for visible public HTML.
confidenceScore	Heuristic confidence based on structured data availability and completeness.
missingFields	Required fields that were not available from the source page.

Sample input

{
  "startUrls": [
    {
      "url": "https://www.google.com/search?q=web+scraping+tools"
    }
  ],
  "maxItems": 25,
  "maxConcurrency": 3,
  "extractionMode": "structuredDataWithFallback",
  "requestTimeoutSecs": 30
}

Sample output

{
  "resultTitle": "Best Web Scraping Tools in 2026",
  "resultUrl": "https://example.com/blog/web-scraping-tools",
  "displayedUrl": "example.com",
  "snippet": "A practical comparison of popular web scraping tools, libraries, and platforms.",
  "position": 1,
  "resultType": "organic",
  "searchQuery": "web scraping tools",
  "sourceUrl": "https://www.google.com/search?q=web+scraping+tools",
  "detectedAt": "2026-07-09T00:00:00.000Z",
  "extractionMethod": "fallback_public_serp",
  "confidenceScore": 0.8,
  "missingFields": []
}

Pricing

This Actor uses a pay-per-event model: $0.005 per result saved to the dataset. You pay only for the organic result rows you receive.

How to use

Run this Actor on Apify with public SERP URLs, export the dataset as JSON, CSV, or Excel, or pull it through the Apify API. Connect the output to Google Sheets, Make, Zapier, a webhook, or an internal dashboard. Save the input as an Apify task and schedule recurring runs for ongoing monitoring.

Best practices

• Provide fully-formed SERP URLs that include the query string (e.g. ?q=...).
• Use structuredDataOnly for highest precision; use structuredDataWithFallback for typical SERP HTML.
• Keep maxConcurrency low to stay well within polite request rates.
• Review the target search engine's terms before scheduling recurring runs.

Compliance and responsible use

This Actor is for public data only. It must not be used to bypass logins, paywalls, CAPTCHAs, or security systems, to collect private or sensitive personal data, or to support spam or abuse. You must comply with the target search engine's terms of service and only scrape where permitted. Search engines place restrictions on automated access to their results; it is your responsibility to confirm that your use is allowed and to follow applicable laws and each source website's rules.

Limitations

• Output quality depends on the public HTML structure of the source page, which search engines change frequently.
• Fallback extraction is intentionally conservative and focuses on organic result links; it does not claim to parse ads, knowledge panels, or every SERP feature.
• Search engines rarely expose JSON-LD result lists, so the visible-HTML fallback is the primary extraction path.
• Some fields may be empty when the source does not publish them; these appear in missingFields.
• The Actor does not bypass anti-bot protections; blocked or CAPTCHA-gated responses will yield no results.

Troubleshooting

• Empty output usually means the page returned a consent, CAPTCHA, or block page instead of results, or the HTML layout changed.
• Invalid URL errors mean one or more input URLs are malformed.
• Slow runs can usually be improved by lowering maxConcurrency.
• Missing fields are source-data limitations, not inferred values.

Changelog

• v0.1.0: Initial release with structured-data check, conservative public SERP HTML fallback, Google redirect resolution, position tracking, and confidence scoring.

Use Google Search Results Scraper with AI agents (MCP)

Give Claude, ChatGPT, Cursor, VS Code or any MCP client this Actor as a tool through the hosted Apify MCP server. The agent sees the input fields with descriptions and example values, runs the Actor, and reads the results.

MCP server URL (this Actor only):

https://mcp.apify.com/?tools=technicaldost/google-search-results-scraper

Claude Code:

$claude mcp add --transport http apify "https://mcp.apify.com/?tools=technicaldost/google-search-results-scraper" --header "Authorization: Bearer YOUR_APIFY_TOKEN"

Cursor, VS Code, Claude Desktop and other clients (mcp.json or the client's MCP settings):

{
  "mcpServers": {
    "apify": {
      "url": "https://mcp.apify.com/?tools=technicaldost/google-search-results-scraper",
      "headers": { "Authorization": "Bearer YOUR_APIFY_TOKEN" }
    }
  }
}

Clients that support sign-in (such as Claude.ai connectors) can use the URL without a token and log in to Apify instead. Get your token in Apify Console → Settings → API & Integrations, or generate a ready config for your client at mcp.apify.com. In the agent the tool is named technicaldost--google-search-results-scraper; ask it, for example, to "run Google Search Results Scraper with {"startUrls": [{"url": "https://www.google.com/search?q=web+scraping+tools"}]}".

AI agents without an Apify account can also run and pay for this Actor per request with x402 agentic payments.

Run Google Search Results Scraper via API

Run the Actor and get its results in one call (replace YOUR_APIFY_TOKEN):

curl -X POST "https://api.apify.com/v2/acts/technicaldost~google-search-results-scraper/run-sync-get-dataset-items?token=YOUR_APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"startUrls": [{"url": "https://www.google.com/search?q=web+scraping+tools"}]}'

Python (pip install apify-client):

from apify_client import ApifyClient

client = ApifyClient("YOUR_APIFY_TOKEN")
run = client.actor("technicaldost/google-search-results-scraper").call(run_input={"startUrls": [{"url": "https://www.google.com/search?q=web+scraping+tools"}]})
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item)

JavaScript / TypeScript (npm install apify-client):

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: 'YOUR_APIFY_TOKEN' });
const run = await client.actor('technicaldost/google-search-results-scraper').call({"startUrls": [{"url": "https://www.google.com/search?q=web+scraping+tools"}]});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

Long runs: start them with POST /v2/acts/technicaldost~google-search-results-scraper/runs and fetch the dataset when the run finishes, or receive a webhook.

Related Actors

• Google Autocomplete Keyword Scraper — Expand seed keywords into hundreds of long-tail keyword ideas from Google Autocomplete. Alphabet, number and q
• Google Shopping Scraper & Price Monitor — Scrape public Google Shopping results by keyword into normalized product, price, merchant, delivery, rating, a
• Google Trends Daily Scraper API — Get daily Google trending searches (RSS) and interest-over-time timelines for keywords. For SEO, content and m
• Google Jobs Scraper & Fresh Lead Monitor — Scrape public Google Jobs results by query and location into structured job leads with employer, source, posti

FAQ

Can I use Google Search Results Scraper with AI agents like Claude or ChatGPT?

Yes. Connect the Apify MCP server with ?tools=technicaldost/google-search-results-scraper (see above) and the agent can run the Actor and read its results on its own.

Can I call Google Search Results Scraper from my own code?

Yes. Use the REST API, or the official Python and JavaScript clients shown above. Results are available as JSON, CSV, Excel, XML or HTML.

How do I run it on a schedule?

Save your input as a task in Apify Console and add a schedule (for example, daily). Use webhooks or integrations to send each run's results onward.

Is it legal to use this Actor?

It works with publicly available data. Make sure your use complies with the source website's terms and with data protection laws such as GDPR, especially for personal data.

Something doesn't work or I need a feature. What should I do?

Open an issue in the Issues tab on this Actor's page with an example input, and we'll look into it.