Google News RSS
Google News Scraper Apify — query Google News RSS for localized headlines
Google News Scraper discovers fresh article URLs by querying Google News RSS. It 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 known-publisher feed XML parsing, not an HTML cleaner, and not a full-article scraper.
Try Input: 1 query × maxItems 1 = $0.003 if one article row is parsed. Store Quickstart is company news. $3.00 / 1,000 articles. No Actor start event.
Try the cheapest first paid Google News run on Apify Input
Open taroyamada/google-news-scraper on the Apify Store · Brand monitoring first paid path
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. Use Website Content Extractor when a discovered URL is a docs, product, or policy page rather than an article.
| 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
- PR teams: find the latest media mentions to hand off for cleanup.
- Competitive intelligence: build newsroom watchlists from search queries.
- Content ops: discover trending stories before enrichment.
- AI / RAG teams: create a steady article URL feed for downstream extraction.
Those four bullets are the published README use cases. The 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 query-based Google News RSS different from known-publisher feed XML and from article HTML cleanup?
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 (default en) and country (default US). RSS & Atom Feed Extractor is known-publisher feed discovery: you already have public RSS or Atom URLs and pass them in feedUrls (maximum 50). Article Content Extractor is HTML cleanup: it fetches article-shaped news, blog, newsroom, and press pages (maximum 300 URLs) and returns headline, byline, publish date, article body, excerpt, and hero image. Website Content Extractor cleans docs, pricing, policy, or product pages that are not article-shaped. Use this Actor when you do not have feed URLs yet and want broader query-based discovery.
Does Google News Scraper return full article bodies or clean HTML?
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. The published README FAQ states: this actor discovers URLs and returns metadata only.
What live input does Google News Scraper require?
The live OpenAPI input schema requires queries. Optional fields are language, country, maxItems, deduplicate, timeoutMs, delivery, webhookUrl, and dryRun.
| Field | Type | Default | Notes |
|---|---|---|---|
queries |
string[] | required | Google News search queries (max 50). Schema prefill is OpenAI, Google AI. Schema description: Start with broad terms for the strongest first-run proof. |
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 |
Published README input example (schema-valid names):
{
"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
}
The live fields are queries, maxItems, and deduplicate. Do not send unpublished aliases.
Cheapest first paid input: one query, maxItems 1 (schema range 1–100). Schema prefill is two queries. The published Store example run uses maxItems 10. The Store Quickstart is company news.
{
"queries": ["OpenAI"],
"language": "en",
"country": "US",
"maxItems": 1,
"deduplicate": true,
"delivery": "dataset",
"dryRun": false
}
If one public RSS article row is parsed, documented PPE is $0.003. There is no Actor start event. Unsuccessful fetches are not billed as Google News RSS articles. Then raise maxItems or add a second query after the article URL is useful. For brand monitoring, see Google News brand monitoring.
Run this 1-query input on Apify
Which fields does a Google News RSS article row include?
The published README output table lists title (article headline), link (direct article URL for downstream cleanup), source (publisher name), pubDate (original RSS publish date), pubDateISO (ISO timestamp version of pubDate), description (short Google News snippet), and query (the search query that surfaced the row). There is no published full-article text field. That table is the published field inventory, not a live coverage guarantee for every query.
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 HTML interface?
The published README FAQ 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. Key features in the README are query-based discovery from Google News RSS without a paid API, localization by language and country, deduplication across queries, and a lightweight feeder step before deeper extraction.
How do language and country localize Google News RSS results?
language defaults to en (schema description: Language code, for example en, ja, de). country defaults to US (schema description: Country code, for example US, JP, GB). Together they tune Google News RSS for a region. The published README Input Examples include a localized JP run with language ja, country JP, and query 人工知能. This page is a search surface; RSS & Atom Feed Extractor has no language or country fields because it reads feed URLs you already have.
Does the live schema accept maxItemsPerQuery or dedupeAcrossQueries?
No. The live required field is queries. Live names are maxItems (Max Items per Query; 1–100, default 25) and deduplicate (Remove duplicate article URLs across queries; default true). README Input Examples that show maxItemsPerQuery or dedupeAcrossQueries are not live input names. Do not send unpublished aliases, feedUrls, or article-page urls lists.
How do dataset delivery, webhookUrl, and dryRun work for Google News discovery?
delivery defaults to dataset (How to deliver results). Live enum values are dataset and webhook; dataset_and_webhook is not a live enum value on this Actor. Set delivery to webhook and supply webhookUrl when you want webhook delivery. The live schema description for webhookUrl is: URL to POST discovery results when delivery=webhook. dryRun defaults to false and runs without saving results. The live schema description for dryRun is: Run without saving results.
How does cross-query deduplicate treat overlapping article URLs?
deduplicate defaults to true. The live schema description is: Remove duplicate article URLs across queries. Keep that default when several search terms surface the same article URL. Set it false only when you need one row per originating query even if the link repeats.
What is the published Quickstart path for company news?
The Store Quickstart section says: start with Quickstart (company news) for a reliable first run; use Brand Monitoring to track multiple companies or themes; use Google News → Article Cleanup when the next step is article extraction.
- 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.
Those four steps are the published first-run buyer path. Start with broad terms for the strongest first-run proof; prefer several narrower queries over one overloaded boolean query when relevance matters.
Can I pass publisher feed URLs or article page URLs into Google News Scraper?
No. Required input is queries: Google News search terms (maximum 50). Known-publisher RSS or Atom XML URLs belong on RSS & Atom Feed Extractor as feedUrls. Article-shaped HTTP(S) pages belong on Article Content Extractor as urls. Docs, pricing, policy, or product pages belong on Website Content Extractor. After this Actor returns article links, send news, blog, and press URLs to Article Content Extractor.
Does Google News Scraper crawl news sites, open a browser, or parse sitemap.xml?
No. It queries Google News RSS for the keywords you supply. It does not scrape the Google News HTML interface, it does not crawl entire news sites blindly, it does not use browser automation, and it does not parse sitemap.xml URL inventories. The published README states: instead of scraping entire news sites blindly, use this tool to discover highly relevant, localized content.
Are unsuccessful Google News RSS fetches billed as Google News RSS articles?
The live Store event Google News RSS article (apify-default-dataset-item) is charged only for one successfully parsed public RSS article row at $0.003. dryRun runs without saving results. There is no Actor start event on the current pricing tab. Platform usage is listed as Included.
Can I schedule recurring Google News monitoring from search queries?
Yes. The published README FAQ states you can run it on a schedule, then pass the discovered URLs into an article-cleanup step. Recurring monitoring is scheduling this Actor, then sending news, blog, and press links to Article Content Extractor and docs, product, or policy links to Website Content Extractor.
How is Google News Scraper priced on the live Store?
Billing is pay per event. The live Store card is $3.00 / 1,000 google news rss articles. Current PPE:
| Event | Price | Emitted when |
|---|---|---|
apify-default-dataset-item (Google News RSS article) |
$0.003 | Charged only for one successfully parsed public RSS article row |
There is no Actor start event on the current pricing tab. The live pricing tab lists Platform usage as Included. Align billing copy to this live PPE only; do not use older README Cost lines that listed actor-start. The cheapest first paid cap is one query × maxItems 1 = $0.003 if one article row is parsed. The Store Quickstart is company news at the same rate.
Try Input: 1 query × maxItems 1 = $0.003 if one article row is parsed. $3.00 / 1,000 articles. No Actor start event.
See Google News Scraper pricing on Apify
Limits to keep in mind
- RSS is a discovery layer only — it does not return full article bodies and it does not clean HTML.
- At most 50 search queries per run.
maxItemsis 1–100 per query (default 25).timeoutMsis 1000–30000 (default 15000). - The required field is
queries. Live schema names only — notmaxItemsPerQueryordedupeAcrossQueries. - Use broad queries for the first run; refine later. Prefer multiple narrower queries over one overloaded boolean query when relevance matters.
- This is query-based Google News RSS, not known-publisher feed XML, not article HTML cleanup, and not
sitemap.xmlURL inventories. - Live PPE is one event: Google News RSS article at $0.003. Platform usage is Included.
Try Input: 1 query × maxItems 1 on Apify
Related actors
- Article Content Extractor Apify — clean discovered article HTML
- RSS & Atom Feed Extractor — known-publisher feeds, not Google News queries
- Website Content Extractor Apify — docs and product HTML
- SAM.gov Scraper Apify — TED/SAM.gov/Grants.gov notices, not news RSS
Related pages
- Content Intelligence pack — choose RSS, Google News, article, or website extraction
- Google News brand monitoring — cheapest first paid path: 1 query × maxItems 1 = $0.003
- Localized Google News headlines — language and country
- RSS & Atom Feed Extractor — known-publisher RSS/Atom feeds, not Google News queries
- Newsroom RSS monitoring
- Article Content Extractor — clean discovered article, news, and blog pages
- Website Content Extractor — clean discovered docs, pricing, policy, or product pages
- Wayback Machine Bulk Checker — Internet Archive availability lookups, not live HTML
- Apple Podcasts Scraper
- Apple Podcasts Chart Scraper
- Apple Podcasts Reviews Scraper
- Shopify App Store Review Scraper
- TED, SAM.gov & Grants Bid Alerts Scraper — TED tenders, SAM.gov opportunities, and Grants.gov notices, not Google News RSS
- HHS Healthcare Data Breach Change Scraper — HHS OCR disclosure changes, not Google News RSS
- Hacker News Stories Scraper — HN stories/comments, not Google News RSS
- Tools