Google News Scraper

Search Google News and download structured article listings: title, URL, snippet, source, and publish time.

Built for Apify Console, API, MCP agents, and integrations (Make, Zapier, n8n). One dataset row per article — ready for CSV, Excel, or JSON export.

What you get

Field	Example
title	Adidas reports quarterly results
url	https://www.reuters.com/business/adidas
description	Adidas said sales rose in the latest quarter…
source	Reuters
published	1 day ago
type	news
position	1

Default is one page per query. Extra stories from the “additional” strip are written after the main list.

Sample output (live)

{
  "query": "adidas",
  "type": "news",
  "position": 1,
  "page": 1,
  "title": "AS Roma and adidas unveil the new third kit for the 2026/27 season",
  "url": "/goto?url=…",
  "description": "AS Roma e adidas unveil the new Third kit for the 2026/27 season, inspired by Fides, the virtue associated with loyalty and unity.",
  "source": "AS Roma",
  "published": "1 day ago",
  "rankOverall": 2
}

Article url is often a Google /goto path, not the publisher’s final URL.

How to run

1. Open the Actor in Apify Console.
2. Enter one search term per line under Search queries.
3. Optional: pages, location, language, max results.
4. Click Start. Open the Output tab when the run finishes.

Example input

{
  "queries": ["adidas"],
  "pages": 1,
  "maxResults": 10
}

API

curl -X POST "https://api.apify.com/v2/acts/datacortex~google-news-scraper/runs?token=YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"queries":["adidas"],"pages":1}'

Replace YOUR_TOKEN with an Apify API token.

Use with MCP / agents

This is a normal Apify Actor. Agents call it through Apify MCP — you do not run a separate MCP process.

Pin this Actor as a tool (after it is public):

{
  "mcpServers": {
    "apify": {
      "url": "https://mcp.apify.com?tools=datacortex/google-news-scraper"
    }
  }
}

The agent should fetch-actor-details on datacortex/google-news-scraper, then run it with the same JSON as Example input above. Running Actors requires an Apify token (OAuth in the client, or Authorization: Bearer <APIFY_TOKEN>).

Pricing

$0.50 per 1,000 results + $0.001 per run.

Event	When it fires	Price
apify-actor-start	Once when the run starts	$0.001
apify-default-dataset-item	Once per dataset row (one article)	$0.0005 ($0.50 / 1,000)

Job	Rows	You pay
1 query, 10 articles	10	$0.001 + $0.005 = $0.006
10 queries	~100	$0.001 + $0.050 = $0.051
20 queries	~200	$0.001 + $0.100 = $0.101
70 queries	~700	$0.001 + $0.350 = $0.351

Set a max total charge per run so a long list cannot overrun budget. The Actor stops when that limit is reached.

Input reference

Field	Required	Default	Notes
queries	yes	—	One term per line, max 1,000
pages	no	1	1–10; each extra page is another lookup
geoLocation	no	—	City, state, country, or coordinates
locale	no	—	Accept-Language value
maxResults	no	all	Hard cap across every query

Limitations

• Article url is often a Google /goto path, not the publisher’s final URL.
• Publish times are relative strings from the results page (1 day ago), not ISO timestamps.
• Failed queries write one type: "error" row so you can see which term failed.

Changelog

See CHANGELOG.md.