Google SERP Scraper

Google SERP Scraper extracts clean organic Google Search results for one or more queries. Use it to collect SERP positions, titles, URLs, and snippets by country, language, and page range without running a browser.

The Actor is built for lightweight Google results monitoring, SEO research, lead generation, content research, and competitor analysis. It stores one dataset item per organic result and can also include People Also Ask data when Google returns it.

What can Google SERP Scraper do?

• Scrape Google organic search results for one or many queries.
• Target Google by language with language and country with country.
• Collect pages 1-10 of Google results.
• Return clean fields: query, page, position, title, url, and description.
• Save People Also Ask data as extra context when available.
• Run without Playwright, Puppeteer, Selenium, or a headless browser.
• Use managed proxy infrastructure configured by the Actor owner.
• Retry blocked, rate-limited, empty, or degraded responses automatically.
• Re-run failed pages at the end of the run with a recovery pass.
• Export results from Apify Dataset as JSON, CSV, Excel, HTML, RSS, or through the API.

Use cases

Google SERP Scraper is useful when you need structured Google results at scale:

• SEO rank tracking for keywords and markets.
• Competitor research and SERP analysis.
• Content gap and topic research.
• Lead generation from search results.
• Monitoring changes in organic results over time.
• Building datasets for marketing, SEO, or research workflows.
• Enriching internal tools with Google result URLs and snippets.

Input

Configure the Actor in the Input tab. The main fields are:

Field	Type	Required	Default	Description
queries	array of strings	Yes	none	Search queries to scrape. Enter one query per line.
startPage	integer	No	1	First Google results page to scrape.
endPage	integer	No	1	Last Google results page to scrape. Maximum: 10.
language	string	No	es	Google interface/search language code, used as hl.
country	string	No	es	Google country code, used as gl and proxy geolocation fallback.

Example input

{
  "queries": [
    "best web hosting 2026",
    "seo tools for beginners"
  ],
  "startPage": 1,
  "endPage": 3,
  "language": "en",
  "country": "us"
}

This input scrapes two queries, pages 1-3, using English Google results for the United States.

Output

Each organic result is saved as one dataset item.

{
  "query": "best web hosting 2026",
  "page": 1,
  "position": 1,
  "title": "Best Web Hosting 2026 - Full Comparison",
  "url": "https://example.com/best-web-hosting/",
  "description": "Snippet text shown in Google results."
}

Output fields

Field	Type	Description
query	string	The query used for this Google search.
page	integer	Google results page number.
position	integer	Organic result position across the requested page range.
title	string	Result title shown by Google.
url	string	Destination URL extracted from the result.
description	string	Google snippet text when available.

When People Also Ask data is found, the Actor may save one additional dataset item for that query/page:

{
  "query": "best web hosting 2026",
  "page": 1,
  "type": "people_also_ask",
  "people_also_ask": [
    {
      "question": "What is the best hosting provider?",
      "answer": "Short answer extracted from Google.",
      "source_title": "Example source",
      "source_url": "https://example.com/"
    }
  ]
}

People Also Ask items are included as extra context and are not charged as SERP result events.

Pricing

This Actor uses pay-per-event pricing.

Event	What is charged	Price
serp-result	One organic Google SERP result saved to the dataset	$0.15 / 1,000 results

Platform usage is included in the result price. Users should not be charged separate usage costs.

Proxy and infrastructure

Users do not need to configure proxies. The Actor owner manages the runtime proxy setup and platform infrastructure.

The country input still matters: it is sent to Google as the gl parameter and is also used as proxy geolocation when fallback proxy infrastructure is needed.

How retries and recovery work

Google can sometimes return rate limits, empty HTML, degraded HTML, or changed markup. The Actor handles this by:

1. Rotating through tested User-Agent strings.
2. Retrying failed requests with fresh proxy URLs when the proxy provider supports rotation.
3. Retrying blocked, non-200, timeout, degraded, and empty-parse responses.
4. Running a recovery pass at the end for pages that returned 0 results in the first pass.

The run does not stop on the first bad page. It continues, records progress in status messages, and reports the final number of successful and failed pages.

Limits and notes

• The maximum page range is 1-10.
• Ads, shopping boxes, local packs, maps, and knowledge panels are not included in the main output.
• Google result pages can change frequently; two runs with the same input may return different positions or snippets.
• Some results may not include a description if Google does not return a normal snippet for that result.
• Google markup can change over time, so production runs should be monitored.

Troubleshooting

Problem	What it means	What to check
0 results for a page	Google returned a blocked, empty, or unsupported response	Check the final status; the recovery pass may retry and recover it.
Fewer than 10 results on a page	Google returned fewer organic results for that page	This is normal for some queries/pages.
Missing descriptions	Google did not return a normal snippet for that result	The title and URL can still be valid.
Pay-per-event warning	Pricing event is not configured correctly	Contact the Actor owner or check the monetization settings.

API usage

You can run the Actor from the Apify API or Apify client libraries. After the run finishes, read the default dataset items.

Example input payload:

{
  "queries": ["javascript"],
  "startPage": 1,
  "endPage": 10,
  "language": "en",
  "country": "us"
}

The dataset can be downloaded from Apify Console or consumed through the dataset API.

Data responsibility

This Actor extracts publicly visible Google Search result data. Users are responsible for using the output lawfully and respecting applicable regulations, website terms, and privacy requirements in their jurisdiction.