How to Collect Google News Results for Brand and Competitor Monitoring
Description and use
A structured daily news snapshot can be built from the Apify Google News Search Actor: collect title, publisherName, publishedAt, googleNewsUrl, and query metadata, deduplicate links against a local baseline, schedule bounded runs, and review grouped stories before sharing.
Problem
A daily news search becomes more useful when its results are structured. Instead of copying headlines into a spreadsheet, collect the headline, publisher, publication time and source link, then compare the new snapshot with yesterday's records.
Outcome
A structured daily news snapshot can be built from the Apify Google News Search Actor: collect title, publisherName, publishedAt, googleNewsUrl, and query metadata, deduplicate links against a local baseline, schedule bounded runs, and review grouped stories before sharing.
Workflow
- Choose a distinctive company name or specific industry phrase and inspect a small sample before collecting more.
- Open the Apify Google News Search Actor and paste a JSON input with queries, language, country, and maxResults (e.g., five results about one company).
- Run the Actor, open the Dataset, and verify relevance by inspecting the five results and opening their source links.
- Add competitor names or related topics to queries after relevance checks; use SUMMARY and ERRORS in the run's key-value store to distinguish empty results, skipped queries, duplicates, and source errors.
- Download the Dataset JSON as news.json, then run a Python script that compares article links with a local baseline file seen-news-urls.json and writes new rows to new-news.json.
- Schedule a bounded run through Apify, store its Dataset and diagnostics, and compare collected links with the baseline.
- Group related stories for a digest and keep a source link with each entry; review important summaries against the publisher's article before sharing.
- If using n8n or Make, call the standard Apify API using stored credentials, wait for the run to finish, and read its Dataset and diagnostics.
- Record the query, collection time, and configured limits next to your results.
Evidence
Instead of copying headlines into a spreadsheet, collect the headline, publisher, publication time and source link, then compare the new snapshot with yesterday's records.
This tutorial uses our Google News Search Actor on Apify. It is a small starting workflow for company monitoring, industry research and a manually reviewed news digest. It does not promise an exhaustive news archive or automatic factual verification.
Choose a distinctive company name or a specific industry phrase. Common words can return irrelevant results, so inspect a small sample before collecting more.
Set a small spending limit, run the Actor, and open the Dataset. The basic output includes title, publisherName, publishedAt, googleNewsUrl and the query and edition metadata. JSON, CSV and Excel exports are available through Apify.
Use SUMMARY and ERRORS in the run's key-value store to distinguish empty results, skipped queries, duplicates and source errors. A process status of SUCCEEDED alone does not prove that every intended search was completed.
If your workflow needs a direct publisher article link, enable resolvePublisherUrls. If it needs available article text, enable includeFullText and keep maxEnrichedArticles small during testing.
These are best-effort enrichment steps. Publisher restrictions, unavailable pages and resolution failures can leave fields empty. Inspect publisherArticleUrl, publisherUrlStatus, fullTextStatus and the summary's enrichment warnings.
This is link-level deduplication, not story-level clustering. Two publishers may cover the same event under different URLs, and a URL can change. For a shared production workflow, store the baseline in a persistent database and coordinate concurrent runs rather than sharing this local file between workers.
Schedule a bounded run through Apify, store its Dataset and diagnostics, then compare the collected links with your baseline. Group related stories for a digest and keep a source link with each entry. Review important summaries against the publisher's article before sharing them.
As checked on 23 October 2026, the Actor lists article-event rates of $0.35 to $0.50 per 1,000 delivered articles, depending on the Apify tier, plus platform usage. Five metadata rows have an article-event component of at most $0.0025 at those rates; that is not
- Record date: 2026-10-23T00:26:29.703Z