Google News Scraper — RSS Search & Topics | from $0.90/1K | No Proxy

For media monitoring agencies, market researchers, and AI news pipelines that need structured, multi-language news data at volume without managing proxy infrastructure.

$0.90 per 1,000 articles returned. No proxy cost — Google News RSS is public and free. Most news scrapers charge for proxy usage on top; this one doesn't. No proxy, no API key, 25+ languages, 35+ country editions.

German tech news? Japanese business news? Russian politics? Set language + country and get country-edition Google News in any language — same structured schema.

Tool	Price	Proxy required	Languages
This actor	$0.90/1k	No	25+
NewsCatcher API	$49/mo (commercial)	N/A	Limited
SerpAPI Google News	$50/mo (100 searches/mo)	N/A	Yes
Apify google-search-scraper (news filter)	more expensive	Yes (SERP proxy)	Limited

Extract structured news data from Google News by keyword or topic category. No proxy needed. No API key. Pay only per result.

Pricing example: 200 articles (1 run, 2 queries × 100 each) = $0.18. 1,000 articles = $0.90. 10,000 articles = $9.00.

---

What you get

Field	Description
title	Clean article headline (source suffix stripped)
source_name	Publisher name (e.g. "The Washington Post")
source_url	Publisher homepage URL
source_domain	Bare domain (e.g. washingtonpost.com)
published_at	ISO 8601 UTC timestamp (e.g. 2026-05-29T18:30:00Z)
pub_date_raw	Original RFC 822 date from RSS
rss_link	Google News redirect link (news.google.com/rss/articles/CBM...)
article_id	Unique Google article token (CBM...) for deduplication
query	Which search query or topic produced this result
feed_type	"search" or "topic"
language	Language code used
country	Country code used
scraped_at	ISO 8601 timestamp of the run
parse_confidence	0.0–1.0 quality score; 1.0 = all fields present
warnings	Machine-readable list of any quality issues

---

How to use (4 steps)

1. Choose your input type

• Search queries: ["artificial intelligence", "climate change"]
• Named topics: ["TECHNOLOGY", "BUSINESS", "WORLD"]
• Or both at once.

2. Set language and country (defaults: en-US / US)

Supports 25+ languages and 35+ country editions. Match them for best results: language: "de" + country: "DE" for German news.

3. Optionally filter by time (search queries only)

when: "7d" for the last week. Options: 1h, 7d, 30d, 1y.

4. Run and export

Results stream in real time. Export as JSON, CSV, or Excel.

---

Output sample

{
  "title": "Opinion | How America can remain the world's AI superpower",
  "source_name": "The Washington Post",
  "source_url": "https://www.washingtonpost.com",
  "source_domain": "washingtonpost.com",
  "published_at": "2026-05-29T18:30:00Z",
  "pub_date_raw": "Fri, 29 May 2026 18:30:00 GMT",
  "rss_link": "https://news.google.com/rss/articles/CBMiwwFBVV95...",
  "article_id": "CBMiwwFBVV95cUxP...",
  "query": "artificial intelligence",
  "feed_type": "search",
  "language": "en-US",
  "country": "US",
  "scraped_at": "2026-05-31T10:00:00Z",
  "parse_confidence": 1.0,
  "warnings": []
}

---

Input examples

Search by keyword

{
  "queries": ["artificial intelligence", "climate tech"],
  "language": "en-US",
  "country": "US",
  "maxItems": 200
}

Browse topic sections

{
  "topics": ["TECHNOLOGY", "SCIENCE", "BUSINESS"],
  "language": "en-US",
  "country": "US"
}

German tech news last 7 days

{
  "queries": ["künstliche intelligenz"],
  "language": "de",
  "country": "DE",
  "when": "7d"
}

Combined queries + topics

{
  "queries": ["Tesla", "SpaceX"],
  "topics": ["BUSINESS"],
  "language": "en-US",
  "country": "US",
  "maxItems": 300
}

---

FAQ

Why does rss_link point to news.google.com and not the original article?

Google News RSS returns encoded redirect links, not direct article URLs. This is by design — it keeps our actor zero-cost and zero-proxy. To get the final article URL, follow the redirect in your own code. The article_id field uniquely identifies the article for deduplication.

Can I get the article full text?

Not from this actor. Google News RSS does not include article body text — only metadata. Use a separate article-scraping actor on the destination URLs.

What does parse_confidence mean?

A quality score from 0.0 to 1.0. Score 1.0 means all fields are present and valid. Deductions happen for missing title (−0.50), missing date (−0.15), missing source (−0.10). The warnings array lists which specific issues occurred. This lets you filter low-quality records programmatically.

Does this need a proxy?

No. Google News RSS is a public, officially-supported endpoint. It returns clean XML with no CAPTCHA, no IP blocking, and no authentication required.

How many results can I get per query?

Up to 100 articles per query (Google News RSS limit). For more results, use multiple queries with different when filters, or use the topics feeds.

What languages and countries are supported?

All locales that Google News supports. Tested: en-US, de/DE, fr/FR, ja/JP and others. Set language to the language code and country to the two-letter country code.

---

Honest limits

• Maximum 100 articles per query (RSS feed limit; no pagination in RSS).
• No article body text — metadata only.
• No images (RSS does not include thumbnail URLs).
• rss_link is a Google redirect, not the final article URL.
• parse_confidence tracks RSS field completeness, not article content quality.

---

Use cases

• Media monitoring — track brand or keyword mentions across news sources
• Competitive intelligence — follow competitors' press coverage by country
• Market research — monitor industry news sentiment in any language
• News aggregation — feed newsletters, dashboards, or alerts with structured data
• Academic research — bulk-collect dated news article metadata

---

parse_confidence trust score

Every record carries a parse_confidence score (0.0–1.0). Score 1.0 means all fields are present and valid. Deductions happen for missing title, date, or source — the warnings array lists specific issues for programmatic filtering.

Use with AI agents (MCP)

Feed live news into your AI agent. This actor works as an MCP tool for any MCP-compatible agent (Claude, GPT-4o). Query by keyword, topic, language, and country — structured JSON back in seconds.

Config: https://mcp.apify.com/?tools=bovi/google-news-scraper

Not affiliated with Google. Data is from Google News public RSS feeds.

Integrations

Built for media-monitoring agencies and AI news pipelines collecting structured multi-language news at volume — the JSON/dataset output drops into the tools you already run, no glue code:

• n8n / Make / Zapier — trigger a run or pipe every new dataset item into 500+ apps (Google Sheets, Airtable, Slack, HubSpot, your database) with no code: n8n, Make, Zapier.
• Webhooks — fire your own endpoint the moment a run finishes, to push results straight into your pipeline (docs).
• MCP server — expose this actor as a tool to Claude, Cursor, or any MCP client so an AI agent can pull this data mid-conversation (guide).
• API & SDKs — fetch the dataset as JSON, CSV, or Excel through the Apify REST API or the Python / JS SDKs.

See all Apify integrations.

Usage statistics

This Actor creates a small, content-free summary at the end of each run. It is used only to monitor reliability and improve this Actor. A copy is saved as USAGE_STATS in your own Apify key-value store, so you can see the exact record created for your run.

Set disableUsageStats to true in the input to opt out. Nothing is sent then; your USAGE_STATS record only says that statistics were disabled.

Only these fields are recorded:

• schema version, Actor name and build number;
• UTC start and finish hour (not a precise timestamp);
• run duration, number of results and time to the first result, each as a coarse range;
• whether the result was empty, the end status, and an error type from a fixed list;
• memory setting and counts of charged events;
• names of the input fields you set, never their values;
• the selected option for input fields that offer a fixed list of choices (for example a sort order).

We do not collect input text, search terms, URLs, domains, usernames, email addresses, names, proxy credentials, tokens, scraped records, output items, raw error messages, stack traces, or hashes of any of those values. Records are kept for no longer than 13 months, used only as aggregated operational statistics, and never sold or shared.

Additional fields (Phase 2)

This Actor also records your Apify user ID, whether Apify marks the account as paying, the size range of list inputs, the selected country when the input offers a fixed list of countries, and one category from a fixed Actor taxonomy. We use these fields only for aggregate reliability, repeat-use and cross-Actor analysis; reports suppress any cell with fewer than five distinct users.

The same disableUsageStats: true input flag turns these fields off too. The user ID is removed after 13 months; we do not export, sell, share, or attempt to re-identify this data.

Run-outcome signals (v2)

To learn whether a run did what it was asked to do, the record also holds a few more coarse ranges and yes/no flags. None of them contains content:

• the result limit you asked for (a range, when the input has one) and what share of it was delivered;
• results delivered per input item you listed (a range);
• output quality as ranges: how fully the result fields were filled, the share of rows that look like errors, the share of duplicate rows, and how many different fields appeared. These are counted in memory while results are saved; no result content is kept;
• how the run was started (console, API, schedule, webhook, another Actor);
• how it ended: stopped by you, timed out, reached the requested limit, stopped by the charge limit, and how many times the platform moved the run;
• if this Actor reports it: how many items to process worked or failed (ranges) and one failure reason from a fixed list;
• a short code made from the names of the input fields you set, never their values.

Repeat-run fingerprint (v2)

When your Apify user ID is recorded (see above), the record also holds an 8-character one-way code made from your input (proxy settings left out) and this Actor's name. It only lets us see that the same account ran the same input again soon after an unsatisfying run; we never see the input itself. It is stored only in the database, never published, and reports use it in aggregate with the same five-user minimum. It is the one exception to the statement above that no hashes are collected, and disableUsageStats: true turns it off.