Google News Scraper — Topic & Brand Monitoring Feed (No API Key)

Normalised topic feeds from Google News RSS for monitoring, dashboards and AI agents. No Google account, no API key, no proxy needed — the same public feed Google News itself is built on.

Give it topic queries (openai, acme competitor, "exact phrase", künstliche intelligenz in the German edition) and get one clean dataset: article title, URL, publisher name + URL, publish time (ISO 8601 UTC), language/geo edition and a snippet — deduplicated across queries. 10 languages out of the box (en/de/fr/es/pl/it/pt/nl/ja/ko/zh), country edition inferred from the language.

Why this one: pay-per-event, not a monthly rental. You are charged once per successfully harvested topic query — a query with zero coverage returns no rows and is never charged. Failed runs are never charged either.

Example input

{
  "queries": ["openai", "\"ai chip export controls\"", "künstliche intelligenz"],
  "language": "en"
}

Sample output (real rows from a live run, 2026-08-20)

Dataset: t0tvcrcvFDiDIZZuG

[
  {
    "query": "openai",
    "title": "Exclusive | OpenAI's Second-Quarter Sales Show Tepid Growth Compared With Anthropic - WSJ",
    "url": "https://news.google.com/rss/articles/CBMiqwFBVV95cUxPOEdPZTRQN2NiUEpURUc2cFBxaGN3QlpNV203c05DczRMdFJDWHRoazgtZGVaQlE0aU9CWW9LcC1JcGJwZ1VXd1lsQ0dnOEQ0MzlDdjJZOV9Oend0M1NON0RnUEZ5UHlMMFhrR09UU3pzSlAwRnl5OXRPbWd3NVljR21NNjBmWkVnWm9fZWkxVmZjbFEyQjJod1ZvMjFqSHNFX0VOb0s1X0puUVk?oc=5",
    "published_at": "2026-08-18T23:47:00Z",
    "source_name": "WSJ",
    "source_url": "https://www.wsj.com",
    "fetched_at": "2026-08-20T16:09:00.787863Z",
    "language": "en",
    "geo": "us",
    "description_snippet": "Exclusive | OpenAI's Second-Quarter Sales Show Tepid Growth Compared With Anthropic WSJ"
  },
  {
    "query": "openai",
    "title": "OpenAI 'will be a public company in 2027' or sooner, CFO Friar tells employees - CNBC",
    "url": "https://news.google.com/rss/articles/CBMidEFVX3lxTFBjVnJGYzVGcWt5c0F3WTY3elk5SkRrSUV3U3Y2OFdIV1dCRm4wVU5PZF8wV1VXT2Q4cFZZU3NZWlRFRTVhMzNYNTZNbEh2bmZ1aDJEWnFINFR6dlVqdGVsQ1RRSmhBV0dKYkFwcTZpQk56MGlZ0gF6QVVfeXFMTnhrRVAzUVl4M3FxY3gxcjdrZFhGODd4X2sxYzRpS1JTaHNJaXNxVEFuSExkOWlNVkYwZnJKX0xXV1hCOUxORnVpLWM1UEszb3BLa1gxMmZVa3dDQ2JNc3hyMERhMXFibThXczd5Y05BRFo5QlRONXdxQ3c?oc=5",
    "published_at": "2026-08-19T19:23:36Z",
    "source_name": "CNBC",
    "source_url": "https://www.cnbc.com",
    "fetched_at": "2026-08-20T16:09:00.787863Z",
    "language": "en",
    "geo": "us",
    "description_snippet": "OpenAI 'will be a public company in 2027' or sooner, CFO Friar tells employees CNBC"
  }
]

(URLs truncated for readability? No — those are the real Google News redirect links, exactly as delivered. They resolve to the publisher's article.)

Use with AI agents (MCP)

Expose this actor as a tool to Claude, Cursor, VS Code or any MCP client — add the Apify MCP server pinned to this actor:

{
  "mcpServers": {
    "apify": {
      "url": "https://mcp.apify.com?actors=halobartku~google-news-feed"
    }
  }
}

Then just ask: "Pull the latest 50 articles about 'anthropic' and summarise the sentiment by publisher."

For AI agents & LLM apps (compact reference)

Compact reference for AI agents calling this actor via the Apify MCP server or the Apify API (actor: halobartku/google-news-feed).

Purpose: One normalised Google News dataset for any set of topic queries — brand mentions, competitor moves, industry keywords — across 10 language editions, without API keys or proxies. Designed as the detection/routing layer of a news pipeline: find what changed, fetch full text in a second pass only where it matters.

Minimal input:

{ "queries": ["your brand", "\"competitor name\""], "language": "en" }

Output: one row per article — query, title, url (Google News redirect, resolves to publisher), source_name, source_url, published_at (ISO 8601 UTC), fetched_at, language, geo, description_snippet.

Behaviors an agent should know:

• queries is an array; all results land in one dataset with one schema, deduplicated across queries by URL.
• language sets the Google News edition (en/de/fr/es/pl/it/pt/nl/ja/ko/zh); query in the same language for best recall. Country geo is inferred.
• Feed order is Google's relevance ranking, not chronological — sort by published_at downstream if you need time order.
• ~100 items per query per fetch is the feed's coverage window; schedule recurring runs for continuous monitoring.
• A query with zero coverage returns zero rows and fires no charge event — safe to probe speculative queries cheaply.
• published_at can be an empty string when the feed carries no date; treat as unknown, not as epoch.

What you get per item

field	notes
query	the topic this item was harvested for
title	article headline
url	Google News redirect URL — resolves to the publisher article
source_name / source_url	publisher
published_at	ISO 8601 UTC (empty string when the feed carries no date)
fetched_at	ISO 8601 UTC harvest time
language / geo	edition used
description_snippet	first 300 chars, HTML stripped

FAQ

How many articles per query? Google News RSS caps a topic at ~100 items per fetch — that is the feed's coverage window, not ours. Items arrive in feed order (Google's relevance ranking), not date-sorted; sort by published_at downstream if you need chronology.

What if my query has zero coverage? No rows, no charge. The feed-harvested event fires only after a query's rows are actually written. A run monitoring 10 brands where 3 have no news costs 7 events.

Do I need a proxy, API key or Google account? No. The feed is public and keyless. Runs work without any proxy configuration in normal conditions.

Can I monitor competitors in other languages? Yes — set language and query in that language; the country edition is inferred (de→Germany, pl→Poland, ja→Japan, …). Exact phrases in quotes work in every edition.

Full article text? Not in this layer — this is the feed layer (headline, publisher, time, link, snippet). Use it to detect and route; fetch full text in a second pass only for the articles that matter.

What does a failed run cost me? Nothing. Failed or empty queries are never charged — that is the core of our per-event pricing.

Pricing

Pay-per-event: one feed-harvested event per successfully harvested topic query ($0.15). A run with 5 topics that all return coverage = 5 events. Empty queries and failed runs are free. No monthly fee, no minimum.

Honest math vs the $19.99/month alternative: pay-per-event wins when you check occasionally or track a handful of topics (4 topics × 1 run/week ≈ $2.40/mo). If you poll 50 topics hourly, a monthly plan is cheaper — use the Pricing tab's calculator for your volume.

Changelog

• 0.1 — initial release: multi-query harvest, 10-language editions, cross-query dedup, per-query pay-per-event pricing.

Disclosure

This actor was built and is operated by an AI agent (Jarvis, for its operator Bartosz). The parsing logic is deterministic, the listing claims are backed by live end-to-end runs, and the human operator reviews and publishes releases.

SEO keywords

google news scraper, google news api, google news rss feed, news scraper no api key, news feed scraper, topic monitoring news, brand monitoring news, competitor news monitoring, media monitoring api, press clipping service, news aggregation tool, google news search api, news dataset for llm, news data for ai agents, multilingual news scraper, google news python, headline aggregator, news by keyword api, google news scraper free, news monitoring without api key