Query Google News RSS for localized headlines and article URLs

Discover fresh article URLs by querying Google News RSS. This Actor returns localized headlines, publisher names, timestamps, and short snippets, then deduplicates overlapping links across queries so you can feed URLs into a downstream extraction step. It is a query-driven discovery surface, not an HTML cleaner and not a full-article scraper.

Open Google News Scraper on Apify

Query-based Google News discovery, not publisher feeds or HTML cleanup

Use this page when you search Google News by keyword and need article URLs you do not already have. Use RSS & Atom Feed Extractor when you already know the publishers you trust and have their public feed URLs. Use Article Content Extractor after discovery, when you need cleaned article bodies — this Actor does not clean HTML.

Google News Scraper RSS & Atom Feed Extractor Article Content Extractor
Intent Discover current article URLs by query Discover fresh URLs from known publisher and blog feeds Clean discovered article, news, and blog pages
Input Search queries (max 50) Public RSS/Atom URLs in feedUrls (max 50) Article-shaped page URLs (max 300)
What it reads Google News RSS for those queries Feed XML from publishers you already know Live article HTML
Localization language and country Not a search surface Not a search surface
Primary output Headline, article URL, publisher, timestamps, snippet, originating query Feed items: title, link, dates, summary, encoded content when present Article body, byline, date, excerpt, hero image
HTML cleanup No. Clean pages afterward with an extractor No. Feed discovery only Yes — bounded article extraction

If a discovered URL is a docs, product, or policy page rather than an article, send it to Website Content Extractor instead of Article Content Extractor. The published input schema states those extractors are the cleanup step after this discovery run.

Use cases

The published README also positions the Actor for brand tracking, localized topic and sentiment analysis, weekly topic digests, and a continuous stream of training URLs for AI models. It does not scrape entire news sites blindly; it queries Google News RSS for the keywords you supply.

How is Google News Scraper different from RSS & Atom Feed Extractor?

This Actor is query-based Google News discovery. Required input is queries (maximum 50 search terms). It reads Google News RSS for those queries and localizes with language and country. RSS & Atom Feed Extractor is for known-publisher feeds: you already have public RSS or Atom feed URLs and pass them in feedUrls. Use this Actor when you do not have feed URLs yet and want broader query-based discovery. Use the RSS Actor when you already know the publishers you trust.

Does this Actor clean HTML or extract full article text?

No. Google News Scraper is a discovery layer only. It does not return full article bodies and it does not clean HTML. Each row is metadata plus a direct article URL. Use Article Content Extractor to extract article bodies from those URLs. Use Website Content Extractor when a discovered URL is a docs, product, or policy page rather than an article.

Published first-run buyer path: run Quickstart (company news); confirm the dataset shows real article URLs, not generic homepages; pick the top URLs and send them to Article Content Extractor; if a discovered URL is a docs, product, or policy page, clean it with Website Content Extractor instead.

How do I start a run?

Open the Actor on the Apify Store and supply queries. language defaults to en. country defaults to US. maxItems defaults to 25 (1–100 per query). deduplicate defaults to true. timeoutMs defaults to 15000 (1000–30000). delivery defaults to dataset; set webhook plus webhookUrl when you want webhook delivery. dryRun runs without saving results.

The Store Quickstart (company news) is the published first-run path. Brand Monitoring tracks multiple companies or themes. Google News → Article Cleanup is the handoff when the next step is article extraction. Start with broad terms for the strongest first-run proof; prefer several narrower queries over one overloaded boolean query when relevance matters.

Published input example (matches the schema):

{
  "queries": ["OpenAI", "Google AI"],
  "language": "en",
  "country": "US",
  "maxItems": 25,
  "deduplicate": true,
  "timeoutMs": 15000,
  "delivery": "dataset",
  "dryRun": false
}

Published Store example run input:

{
  "queries": ["artificial intelligence"],
  "language": "en",
  "country": "US",
  "maxItems": 10,
  "deduplicate": true,
  "delivery": "dataset",
  "dryRun": false
}
Field Type Default Notes
queries string[] required Google News search queries (max 50). Schema prefill is OpenAI, Google AI.
language string en Language code (for example en, ja, de)
country string US Country code (for example US, JP, GB)
maxItems integer 25 Max items per query; 1–100. Schema title: Max Items per Query.
deduplicate boolean true Remove duplicate article URLs across queries
timeoutMs integer 15000 Request timeout in milliseconds; 1000–30000
delivery string dataset dataset or webhook
webhookUrl string — POST target when delivery is webhook
dryRun boolean false Run without saving results

The live input fields are maxItems and deduplicate. Do not send unpublished aliases.

Run Google News Scraper on Apify

What does a result row contain?

The published README fields are title (headline), link (direct article URL for downstream cleanup), source (publisher name), pubDate (original RSS publish date), pubDateISO (ISO timestamp), description (short Google News snippet), and query (the search query that surfaced the row). There is no published full-article text field.

Published README sample:

{
  "title": "Codex for (almost) everything",
  "link": "https://openai.com/index/codex-for-almost-everything",
  "source": "OpenAI",
  "pubDate": "Thu, 16 Apr 2026 10:00:00 GMT",
  "pubDateISO": "2026-04-16T10:00:00.000Z",
  "description": "The updated Codex app for macOS and Windows adds computer use...",
  "query": "OpenAI"
}

That sample is the published README illustration, not a live coverage guarantee. After you confirm real article URLs, send news, blog, and press links to Article Content Extractor and docs, product, or policy links to Website Content Extractor.

Why query Google News RSS instead of scraping the Google News UI?

The published README positions the RSS surface as lighter, more stable, and better suited for recurring discovery runs than scraping the Google News UI. This Actor queries Google News RSS, not the Google News HTML interface, and does not require a paid news API. Recurring monitoring is supported by scheduling the Actor, then passing discovered URLs into an article-cleanup step.

How is Google News Scraper priced?

Billing is pay per event. The published Store price is $3.00 / 1,000 google news rss articles. The billed event is Google News RSS article at $0.003, charged only for one successfully parsed public RSS article row. You are not charged for Apify platform usage, only the fixed event price.

$3.00 per 1,000 Google News RSS articles ($0.003 per successfully parsed public RSS article row)

See Google News Scraper pricing on Apify

Limits to keep in mind

Open Google News Scraper on Apify

Related pages