Google Search Results Scraper

Google Search Results Scraper is a BrowserAct Bot template for collecting structured organic search results from public Google Search pages. Configure a keyword, country, language, and result count, then run the Bot to return ranked SERP records for SEO research, content research, competitive analysis, or workflow automation.

What Does BrowserAct Google Search Results Scraper Do?

This template opens Google Search with your query settings, reads organic result cards, skips non-organic modules, paginates when needed, and returns one structured record per search result.

Key Features

Extract organic Google Search results without requiring a Google login.
Capture rank, title, URL, display URL, domain, snippet, sitelinks, and source page URL.
Configure keyword, country, language, and result count.
Continue through result pages until the requested count is reached.
Keep rankings contiguous and deduplicate URLs.

What Data Can I Extract from Google Search?

Field	Description
`rank`	Organic result position returned by the Bot.
`title`	Result title from the search result card.
`url`	Destination result URL.
`displayUrl`	Display URL shown by Google.
`domain`	Parsed source domain.
`snippet`	Visible result snippet.
`sitelinks`	Visible sitelinks when Google displays them.
`sourcePageUrl`	Google results page URL where the result was found.

How to Use Google Search Results Scraper

Click Run task.
Enter the search keyword.
Choose country and language settings.
Set how many organic results to collect.
Run the Bot and review the structured SERP records.

Input Parameters

Parameter	Required	Default	Description
`keyword`	Yes	`browser automation tools`	Search query to run on Google.
`country`	Yes	`US`	Country setting used for localized results.
`language`	Yes	`en`	Interface and result language hint.
`count`	Yes	`20`	Maximum number of organic results to return.

Example Output

{
  "results": [
    {
      "rank": 1,
      "title": "Example Search Result Title",
      "url": "https://example.com/page",
      "displayUrl": "example.com/page",
      "domain": "example.com",
      "snippet": "Visible search result snippet from Google.",
      "sitelinks": [],
      "sourcePageUrl": "https://www.google.com/search?q=browser+automation+tools&hl=en&gl=US"
    }
  ]
}

How Does it Work?

How Google Search Results Scraper runs

BrowserAct constructs a public Google Search URL using the keyword, country, and language inputs. The Bot reads organic result cards from the main results area, maps each result title, link, display URL, domain, snippet, and optional sitelinks, then records the source search page URL.

When the requested count is higher than the first result page, BrowserAct moves through Google pagination and continues collecting unique organic URLs. Non-organic modules such as ads, AI summaries, People Also Ask, maps, image packs, video packs, and shopping modules are not treated as standard organic records.

How to Build a New Scraper Bot with Agent Built

Step 1: Describe the Data You Need

Open BrowserAct and start Agent Built from the Home prompt box or from Create -> Build with Agent. Paste a clear request that includes the website, the records to collect, the filters or search conditions, the fields to return, the result limit, and the inputs you want to reuse later.

Agent Built prompt templates

Step 2: Let BrowserAct Build and Test the Bot

BrowserAct explores the live website, works out the navigation and extraction path, and validates the result. If BrowserAct asks for clarification, reply in the same build conversation with the missing URL, condition, field, example, or expected output.

Agent Built exploration

Step 3: Run the Bot and Review the Result

When the build is complete, run the Bot with the default inputs first. Review the structured records, source URLs, missing fields, and row count before reusing the Bot with new inputs or connecting it to another workflow.

Agent Built run inputs

Agent Built run results

Why Scrape Google Search Results?

Google Search result data helps teams monitor ranking positions, review competitor pages, collect source URLs, research content gaps, and track how public result pages change for important keywords.

Who Can Use This Template?

SEO teams tracking organic search visibility.
Content marketers researching SERP competitors.
Growth teams collecting source URLs for analysis.
Analysts monitoring brand or topic search results.
Automation builders routing SERP data into reports, dashboards, databases, or agents.

How Many Results Can You Scrape?

Use count to control the number of organic results returned. Higher counts require pagination and may take longer than collecting only the first page.

Automation and Export

Automation and export flow

BrowserAct returns structured SERP records first. You can then use the output through API JSON responses, n8n workflows, Make scenarios, Zapier automations, MCP-based agent workflows configured from the Bot's Integrations tab, or manual CSV review.

Need Help?

Discord: Discord Community

E-mail: service@browseract.com

Brief