Google News Full Coverage Clusters & Publisher Timeline
Pricing
from $0.49 / 1,000 results
Google News Full Coverage Clusters & Publisher Timeline
Read Google News Full Coverage story clusters with every coverage group, publisher, decoded article URL, exact publish time, thumbnail, source count, top publishers and a monitored timeline of new articles.
Pricing
from $0.49 / 1,000 results
Rating
0.0
(0)
Developer
Xyrelith Data
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
4 hours ago
Last modified
Categories
Features
Share
Read Google News the way the newsroom sees it: one story, every outlet, every coverage group, one row per article. Paste sections, keywords or Full Coverage story links and get publisher names, original article URLs, exact publish times, bylines, thumbnails, coverage-group labels, intra-group positions, source counts, top publishers, publisher speed and share of voice.
This actor is built for media monitoring, PR measurement, competitive intelligence, research and newsroom dashboards. It is not an official Google product and needs no Google account, cookies, API key or proxy setup.
What you get
- Story clusters, not a flat headline list. Each row carries the cluster headline, Story ID, source count, article count, first/latest article time and the top publishers in the cluster.
- Every Full Coverage group Google serves.
Top news,All coverage,Opinion,Posts on X,Personal perspective,In-depth,For context,Interviews,By the numbers, plus legacy names (From the region,Fact check,FAQ,Timeline) when Google returns them. Each row records its group and its position inside that group. - Original publisher URLs. Google News hides the article behind an opaque token; the actor returns the decoded publisher URL and the Google News link side by side.
- Publisher timeline. Publisher article counts, share of voice, the publisher's first article time and how many minutes after the story started that publisher joined.
- Monitoring. Turn on new-article tracking and each run marks which articles are new, when they were first seen, and how many new articles the cluster gained since the previous run.
- Editions. 80+ country + language editions, from US English and UK English to German, French, Spanish, Portuguese, Japanese, Korean, Chinese, Arabic, Hindi and more.
- Modes. Front page/top stories, eight topic sections, keyword searches or direct Full Coverage story links.
Input
| Field | What it does |
|---|---|
mode | sections, keywords or storyUrls. |
edition | Country + language edition, e.g. US:en, GB:en, DE:de, IN:hi, BR:pt-419. |
sections | Any of topStories, us, world, business, technology, entertainment, sports, science, health. |
keywords | News searches. Google News operators work: quotes, OR, -term, site:, intitle:, when:1d, when:7d, after:, before:. |
storyUrls | Google News Full Coverage URLs or story tokens. |
coverageSections | Keep only selected coverage groups. Leave empty for all. |
maxStories | Story clusters to process. |
maxArticlesPerStory | Article rows per cluster. Story statistics still cover the whole cluster. |
maxItems | Hard cap on dataset rows. |
trackNewArticles | Mark new articles and compute the cluster's new-article count per run. |
resetTracking | Forget the stored history for the clusters in this run. |
decodePublisherUrls | Resolve Google News RSS links to publisher URLs in keyword mode. |
Examples
Top stories in the US edition, five stories, all coverage groups:
{ "mode": "sections", "edition": "US:en", "sections": ["topStories"], "maxStories": 5 }
World and business in the UK edition, only opinion and analysis groups:
{"mode": "sections","edition": "GB:en","sections": ["world", "business"],"coverageSections": ["Opinion", "In-depth", "For context"],"maxStories": 10}
Keyword monitoring with new-article tracking:
{"mode": "keywords","edition": "US:en","keywords": ["electric vehicles when:7d", "\"supply chain\" when:1d"],"maxStories": 20,"trackNewArticles": true}
One Full Coverage story:
{"mode": "storyUrls","storyUrls": ["https://news.google.com/stories/CAAqNggKIjBDQklTSGpvSmMzUnZjbmt0TXpZd1NoRUtEd2k2NXNLd0VoRklaRFlGaXlxVTFTZ0FQAQ"]}
Defaults
| Field | Default |
|---|---|
mode | sections |
edition | US:en |
sections | ["topStories"] |
keywords | [] |
storyUrls | [] |
coverageSections | [] |
maxStories | 20 |
maxArticlesPerStory | 10 |
maxItems | 100 |
trackNewArticles | false |
resetTracking | false |
decodePublisherUrls | true |
Output fields
| Field | Meaning |
|---|---|
storyId, storyUrl, storyHeadline, storyImage | The Full Coverage cluster. storyId is Google's edition-specific story token. |
clusterKey, clusterSource | Stable key for monitoring and where the cluster was discovered (storyPage, rssSearch, rssSection). |
edition, language, country | Requested edition and its parts. |
section, discoveredSections, keyword | Where the story was found. |
sourceCount, articleCount | Unique publishers and articles Google served for the cluster. |
firstArticleAt, latestArticleAt | Earliest and latest article time in the cluster. |
topPublishers | Up to five publishers with article count and share of voice. |
coverageSection, position | The coverage group and the row's position inside it. |
isStoryLead | Whether this is the first article of the cluster. |
publisher, publisherDomain, title, url, googleNewsUrl, urlResolved | Publisher identity and both links. |
publishedAt, author, thumbnail | Exact publish time, byline when Google shows one, image when available. |
articleId | Stable article token used by monitoring. |
publisherArticleCount, publisherShareOfVoice, publisherFirstArticleAt, publisherDelayMinutes | Publisher timeline inside the cluster. |
isNew, firstSeenAt, storyNewArticleCount | Present when trackNewArticles is on. |
scrapedAt | When this row was collected. |
Empty fields are omitted, never sent as null. A byline or thumbnail simply does not appear
when Google does not show one.
FAQs
Does it need cookies, a Google account or an API key? No. Story and section pages are public. Keyword mode uses the public Google News RSS search feed.
Why does keyword mode sometimes return a small coverage list? Google's web search page blocks datacenter traffic. The public RSS search feed is the reliable cookieless path; it returns up to 100 items and often includes a short list of other outlets on the same story. Sections and direct story URLs return the complete Full Coverage page.
How many articles are in a story?
Google typically serves 7–62 articles per Full Coverage page; there is no pagination. The actor
returns all of them (subject to maxArticlesPerStory).
Can I monitor publisher speed?
Yes. publisherDelayMinutes is how long after the first article in the cluster that publisher's
first article appeared; publisherShareOfVoice is its share of the cluster's articles.
Does monitoring require an Apify schedule? A schedule is the easiest way to use it. The actor stores seen article IDs in its key-value store between runs; run it manually and the same fields still work.
Are all Google coverage groups supported? The parser reads every coverage heading Google serves, so new groups appear automatically. The legacy names from older Google News layouts are accepted in the filter and match when present.
Which editions are supported?
80+ country + language pairs, including the editions that use es-419, pt-419, zh-Hant and
zh-Hans. Story IDs are edition-specific; run one edition per task for consistent monitoring.
Can I export to CSV or Excel? Yes. The dataset is flat one-row-per-article with repeated cluster fields, so CSV, Excel, Google Sheets, webhooks and the Apify API all work without nested parsing.
Notes and limits
- Google News pages are unofficial and can change. If a page changes shape the actor reports a warning and still returns the rows it can parse.
- The Full Coverage page is the source of truth for cluster size; keyword RSS results can be smaller than the full cluster.
- Publisher URLs are decoded from Google's own page data; if one cannot be decoded, the row
keeps
googleNewsUrlandurlResolved: falseinstead of inventing a URL. - Respect Google's terms and the publisher's rights when storing or republishing article content.