Brand News Monitor
Pricing
from $1.20 / 1,000 results
Brand News Monitor
Monitor brand, competitor, and topic news with repeatable queries. Receive normalized article records containing titles, URLs, publisher domains, timestamps, language, query labels, and stable IDs for SEO and PR reporting.
Pricing
from $1.20 / 1,000 results
Rating
0.0
(0)
Developer
Simon Jessen
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
4 days ago
Last modified
Categories
Share
Brand News Visibility Monitor
Brand News Visibility Monitor helps you find newly published coverage for a brand, competitor, or topic and turn it into a reusable monitoring feed. Each record includes the article title, source URL, publisher domain, timestamp, query, and stable deduplication ID; configure the search query and monitoring window afterward.
Outcome
Track where and how often a brand, competitor, topic, or keyword appears across global news coverage using a commercially reusable open-data search feed.
Use cases
- Use the Actor when you need track where and how often a brand, competitor, topic, or keyword appears across global news coverage using a commercially reusable open-data search feed.
- Build workflows around normalize GDELT news-search results into stable records with source domains, publication timestamps, language, country, article URLs, query labels, and repeat-run friendly deduplication keys for SEO visibility and digital-PR monitoring.
- Designed for SEO agencies, digital PR teams, content marketers, brand-monitoring teams, and publishers.
- Schedule repeat runs: Customers rerun saved brand, competitor, and topic queries daily or weekly to detect new coverage, emerging narratives, and changes in publisher visibility.
- Feed normalized dataset records into APIs, spreadsheets, databases, automations, or AI/agent workflows.
Quick start
- Open the Actor input form.
- Set the filters or query relevant to your workflow.
- Start with a small
maxResultsvalue. - Run the Actor and inspect the default dataset before scheduling larger or recurring jobs.
Example input:
{"query": "renewable energy","mode": "artlist","maxrecords": 10,"sort": "datedesc","timespan": "7d","maxResults": 10}
Inputs
- query (string, required) — Keyword, exact phrase, or supported GDELT query expression such as a brand, competitor, topic, or site-restricted search.
- mode (string, optional) — Article-level results are enabled through the artlist mode.
- timespan (string, optional) — GDELT-supported relative time window such as 1d, 7d, 30d, or 90d.
- maxResults (integer, optional) — Maximum number of article records to return, from 1 to 250.
- sort (string, optional) — Use datedesc for newest-first monitoring or hybridrel for relevance-oriented discovery.
- maxrecords (integer, optional) — Maximum number of article records to return, capped conservatively for reliable operation.
Output example
The example below is taken from the latest validated local live-source sample when available; otherwise it is derived from the bundled dataset schema.
{"id": "https://www.vetogate.com/5725875","title": "بتسهيلات غير مسبوقة .. الكهرباء تكافئ الملتزمين بقوانين التصالح .. تحويل 1 . 2 مليون عداد كودي للاستفادة من نظام الشرائح .. وتكشف حقيقة تطبيق الشريحة الموحدة كإجراء عقابي","url": "https://www.vetogate.com/5725875","domain": "vetogate.com","seendate": "20260905T100000Z","language": "Arabic","query": "renewable energy","source": "GDELT Project"}
Pricing
Store pricing is configured in Apify. The intended primary paid unit is article record. Start with a small result limit while validating your workflow, then scale only when the output and economics fit your use case. The README never hard-codes a price that could drift from the live Store configuration.
Source and limitations
- Source: GDELT DOC 2.0 API.
- Licence/terms: GDELT Project unlimited and unrestricted use terms.
- Reuse condition: GDELT states that datasets may be used commercially and may be redistributed, rehosted, republished, or mirrored, provided every use or redistribution cites the GDELT Project and links to https://www.gdeltproject.org/. Article text, snippets, images, publisher trademarks, and other third-party material remain subject to their respective owners' rights; this Actor should return metadata and source links rather than republish article bodies or images. Do not imply GDELT, Google, or publisher endorsement.
- Automation condition: Use the documented GET API, limit request frequency and result volume, avoid abusive parallel polling, and handle HTTP errors and empty responses. Use maxrecords within documented limits and use the source's timespan parameter for bounded monitoring windows.
- This is adjacent to Google SERP intelligence rather than a Google-ranking replacement; it measures news visibility and article discovery, not general web rankings.
- GDELT coverage and ranking are not equivalent to Google or Bing results, so the product must not claim search-engine-position accuracy.
- Article titles, URLs, snippets, publisher names, and other third-party material may carry separate copyright, trademark, or publisher terms; limit output to metadata and links and preserve source attribution.
- GDELT's public API behavior, result limits, and availability may change; live schema and rate-limit checks are required before publication.
- The source response can contain low-quality, duplicate, syndicated, or inaccessible URLs; expose source metadata and avoid guaranteeing article availability.
This Actor does not bypass authentication, rate limits, robots/API policies, licensing conditions, or upstream access controls. Missing upstream values are not invented.
FAQ
Does this use the approved source contract?
Yes. Runtime requests are restricted to the source contract validated by Market Hunter before build.
Can I schedule repeat runs?
Yes, when the source permits automated access. Use conservative schedules and result limits that respect upstream conditions.
Why can some fields be empty or null?
The upstream source may omit fields for particular records. The Actor preserves missing values rather than fabricating data.
Troubleshooting
- If a narrow query returns no rows, loosen filters and retry with a small result limit.
- If the upstream source returns a rate-limit or temporary server error, retry later instead of increasing request pressure.
- If authentication or source identity is required, verify the protected credential/identity configured for the Actor.
- If the upstream response schema changes, report the failed run so the deterministic mapping can be updated.
Related Actors
- Domain Backlink Discovery from Common Crawl
- News Publisher Domain Monitor
- Brand Mention Change Detector
- Public Web Article Metadata Extractor
Store publication remains an explicit manual action. This product is not affiliated with or endorsed by the upstream source unless the Store listing explicitly states otherwise.