Google SERP Scraper

Google SERP Scraper returns one structured record per query for a Google result page in a selected country, language, and device context. It accepts free-text search queries and outputs the query context, SERP URL, timing fields, and the Google feature blocks you request, including organic results, ads, AI Overviews with citations, People Also Ask, Featured Snippet, Knowledge Panel, Local Pack, videos, images, shopping results, top stories, and related searches. Each record represents one query in one Google context, which makes the output useful for SERP analysis, brand visibility review, paid-search review, and Apify Actor workflows through MCP.

Best fit and connected workflows

This Actor fits workflows that start with a Google query list and continue into structured analysis. It is a natural fit when you want the page context around a search term, not only blue links.

Typical routes include:

• SEO and SERP monitoring when you need organic results together with AI Overviews, ads, and local features.
• AI-search research when you want AI Overview citations and the source domains Google surfaced.
• Brand visibility tracking when Knowledge Panel, Featured Snippet, or Local Pack presence matters.
• Paid search review when sponsored ads and extensions are part of the query context.
• Agent pipelines that need one compact query-level SERP record through Apify MCP.

Connected workflows that often follow this Actor:

• Use Google Maps Reviews Scraper after a Local Pack result when the next step is collecting review context for a business listing.
• Use Google Ads Scraper - Live Search Sponsored Ads after you identify sponsored placements and want a focused ad-only capture for the same market and query style.
• Use Google Ads Transparency Scraper - Creatives & Run Dates after you identify an advertiser and want creative history or run-date context for the ads that appeared on the SERP.

Practical scenario

Maya, an SEO specialist, starts with the query "apify google scraper" for the United States in English on desktop. The returned record includes the query context, organic results, ads, AI Overview citations, People Also Ask questions, and a Knowledge Panel when Google shows it. Maya uses the organic domains and cited sources to decide which pages to compare in her content brief, then sends the ads from the same query into a Google Ads-focused Actor for a separate review.

Input fields

The Actor accepts these fields:

Field	Type	Purpose
queries	array of strings	Free-text Google queries to run. One query becomes one dataset record.
countryCode	string	Google gl country code.
languageCode	string	Google hl language code.
device	string	Desktop or mobile SERP layout.
extractFeatures	array of strings	Which feature blocks to include in each record.
maxOrganicResults	integer	Maximum organic links per query.
forceCamoufox	boolean	Uses only the Camoufox browser path.
maxRetries	integer	Retry attempts per query.
proxyConfiguration	object	Apify proxy settings, with Residential prefilled.

Focused input example:

{
  "queries": [
    "suitable ai search tools 2026"
  ],
  "countryCode": "us",
  "languageCode": "en",
  "device": "desktop",
  "extractFeatures": [
    "organic",
    "ads",
    "aiOverview",
    "peopleAlsoAsk",
    "featuredSnippet",
    "knowledgePanel",
    "localPack",
    "relatedSearches",
    "videos",
    "images"
  ],
  "maxOrganicResults": 10,
  "maxRetries": 3,
  "forceCamoufox": false,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ]
  }
}

Output fields

The dataset contains one record per query. Each record includes the query context, extraction backend, SERP URL, and the feature blocks present for that query context.

Field	Type	Purpose
query	string	Original search query.
countryCode	string	Country code used.
languageCode	string	Language code used.
device	string	Desktop or mobile layout.
source	string	Extraction backend used for the record.
serpUrl	string	Google URL that produced the result.
totalResultsEstimate	integer or null	Google result-count estimate.
searchTimeSeconds	number or null	Google-reported search time.
organic	array	Organic result links in display order.
ads	array	Sponsored ads.
aiOverview	object or null	AI Overview answer and citations.
peopleAlsoAsk	array	PAA questions, answers, and sources.
featuredSnippet	object or null	Featured Snippet content and source.
knowledgePanel	object or null	Knowledge Panel entity card.
localPack	array	Local Pack businesses.
relatedSearches	array	Related search queries.
videos	array	Video carousel entries.
images	array	Image pack entries.
shoppingResults	array	Shopping results.
topStories	array	Top Stories items.
scrapedAt	string	UTC extraction timestamp.
warnings	array	Non-fatal execution warnings.

Illustrative output record:

{
  "query": "suitable ai search tools 2026",
  "countryCode": "us",
  "languageCode": "en",
  "device": "desktop",
  "source": "serpapi-managed",
  "serpUrl": "https://www.google.com/search?q=suitable+ai+search+tools+2026&hl=en&gl=us&num=10",
  "totalResultsEstimate": 18400000,
  "searchTimeSeconds": 0.42,
  "organic": [
    {
      "position": 1,
      "title": "Top 10 AI Search Engines in 2026",
      "url": "https://example.com/ai-search-2026",
      "domain": "example.com",
      "displayedUrl": "example.com/blog",
      "snippet": "A ranked list of the most-used AI search engines...",
      "date": null,
      "sitelinks": [],
      "richSnippet": null
    }
  ],
  "ads": [
    {
      "position": 1,
      "block": "top",
      "title": "Perplexity Pro",
      "url": "https://www.perplexity.ai/pro",
      "displayedUrl": "perplexity.ai",
      "advertiser": "Perplexity AI",
      "description": "AI search subscription.",
      "sitelinks": [],
      "extensions": []
    }
  ],
  "aiOverview": {
    "present": true,
    "text": "AI search tools combine large language models with web retrieval.",
    "textBlocks": [
      "AI search tools combine large language models with web retrieval."
    ],
    "citations": [
      {
        "position": 1,
        "domain": "perplexity.ai",
        "url": "https://perplexity.ai/",
        "title": "Perplexity AI"
      }
    ],
    "citationCount": 1,
    "uniqueDomainCount": 1
  },
  "peopleAlsoAsk": [
    {
      "position": 1,
      "question": "What are AI search tools used for?",
      "answer": "They combine search retrieval with generated answers.",
      "source": {
        "title": "Top 10 AI Search Engines in 2026",
        "url": "https://example.com/ai-search-2026",
        "domain": "example.com"
      }
    }
  ],
  "featuredSnippet": {
    "type": "paragraph",
    "text": "AI search tools often combine retrieval and generated summaries.",
    "list": null,
    "source": {
      "title": "Top 10 AI Search Engines in 2026",
      "url": "https://example.com/ai-search-2026",
      "domain": "example.com"
    }
  },
  "knowledgePanel": null,
  "localPack": [],
  "relatedSearches": [
    "suitable free ai search tools",
    "ai search tools comparison"
  ],
  "videos": [],
  "images": [],
  "shoppingResults": [],
  "topStories": [],
  "scrapedAt": "2026-06-13T12:50:00Z",
  "warnings": []
}

How it works

This Actor uses a hybrid Google extraction setup with a managed SerpApi backend by default and an optional Camoufox browser path.

1. The Actor accepts free-text Google queries and runs them in the selected country, language, and device context.
2. The managed backend returns structured SERP page data, including organic results and the feature blocks requested for that query.
3. The Camoufox path is available as an optional browser-based route.
4. Each query produces one dataset record, which keeps the SERP context and feature blocks together.
5. The output also includes a summary record in Key Value Store with Pay per event counts and cost details.

The dataset schema makes the record shape explicit for organic links, AI Overview citations, PAA, Knowledge Panel attributes, Local Pack entries, and the other SERP blocks supported by this Actor.

Pricing

This Actor uses Pay per event plus Apify platform usage. Open the live Pricing tab on the Apify Store for current event pricing and platform usage details.

The primary charge is for each managed SERP page returned. The Actor also charges a small actor-start event, and the Camoufox path has its own per-page event when used.

Example in words: if you run one hundred queries on the managed path, the run charges one actor start event plus one managed SERP page event for each query.

Use with AI agents (MCP)

This Actor is usable through Apify MCP as a tool that turns Google queries into structured SERP records. The tool returns dataset items plus a run summary record, which lets an agent inspect provenance, feature presence, and query context from the same run.

Actor identity: khadinakbar/google-serp-all-in-one-scraper

Tool description: search Google for one or more queries and return one structured SERP record per query, including organic results, ads, AI Overviews with citations, People Also Ask, Featured Snippet, Knowledge Panel, Local Pack, videos, images, shopping results, and top stories.

Search Google for the query list and return one structured SERP record per query. I need the query context, the SERP URL, the feature blocks present on the page, and the cited source domains so I can summarize the search landscape.

Output interpretation:

• organic is the blue-link result list in display order.
• aiOverview.citations points to the domains and URLs Google cited in the answer block.
• peopleAlsoAsk captures question-and-answer pairs with source links.
• knowledgePanel and localPack appear when Google returns those blocks for the selected query context.
• source shows whether the record came from the managed backend or the Camoufox path.
• warnings can include soft warnings from partial extraction paths.

Provenance and scope:

• Each record maps to one query in one country, language, and device setting.
• serpUrl provides the direct Google search URL for provenance.
• scrapedAt shows when the record was extracted.

Pagination and cost guidance:

• maxOrganicResults above ten can require additional paginated SERP fetches.
• Each additional page is billed separately.
• Trimming extractFeatures changes record size, while pricing follows the live event model shown in the Pricing tab.

Apify API example

Use the Apify API, then read back the dataset items. Set APIFY_TOKEN in your environment.

import { ApifyClient } from "apify-client";

const client = new ApifyClient({
  token: process.env.APIFY_TOKEN,
});

const run = await client.actor("khadinakbar/google-serp-all-in-one-scraper").call({
  queries: ["apify google scraper"],
  countryCode: "us",
  languageCode: "en",
  device: "desktop"
});

const datasetId = run.defaultDatasetId;
const { items } = await client.dataset(datasetId).listItems();

console.log(items);

Best results and outcome guidance

Use concise, search-like queries that match the SERP you want to capture. Keep country and language aligned with the market you are reviewing. Use desktop when you want the denser layout with more visible SERP blocks, and mobile when you want the mobile presentation. Set maxOrganicResults to the number of links you need, since higher values can add paginated page fetches.

For agent use, keep extractFeatures focused on the blocks your workflow actually consumes. That keeps each record compact while preserving the fields your downstream step needs.

Design note

I found that one query produces one dataset record, and that record can include all requested feature blocks for that query, country, language, and device combination.

FAQ

When should I use this Actor instead of a narrower Google scraper?

Use this Actor when you want a full SERP snapshot with organic results, ads, AI Overviews, PAA, Featured Snippet, Knowledge Panel, Local Pack, videos, images, shopping results, and top stories in one record.

How does this Actor connect with Google Maps research?

Use When a returned record includes a Local Pack business and you want review context, send that business into Google Maps Reviews Scraper for the next step in the workflow.

How does this Actor connect with paid search workflows?

When you identify sponsored placements on the SERP and want a focused ad-only capture for the same query theme, use Google Ads Scraper - Live Search Sponsored Ads. If you already identified an advertiser and want creative history or run-date context, use Google Ads Transparency Scraper - Creatives & Run Dates for the follow-up workflow.

What does one query return?

One query returns one dataset record with the SERP feature blocks present for that query context.

Can I use this through Apify MCP?

Yes. This Actor is MCP-ready and usable through Apify MCP as a structured Google SERP tool.

Responsible use

Use the Actor for publicly accessible Google search results and handle the returned data in line with your applicable policies, laws, and data-processing obligations. Keep request volumes proportional to your workflow, and select only the feature blocks needed for the task at hand.