News & Brand Mention Monitor (RSS & Atom Feeds) avatar

News & Brand Mention Monitor (RSS & Atom Feeds)

Pricing

from $4.25 / 1,000 mention records

Go to Apify Store
News & Brand Mention Monitor (RSS & Atom Feeds)

News & Brand Mention Monitor (RSS & Atom Feeds)

Find every news mention of your brand, competitors, or keywords in the publisher RSS and Atom feeds you choose. Deduplicated by link and title. Monitor mode delivers only mentions you have not seen before, for PR, SEO, and market alerts.

Pricing

from $4.25 / 1,000 mention records

Rating

0.0

(0)

Developer

ManiGinaM

ManiGinaM

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

7 hours ago

Last modified

Categories

Share

Every news mention of your brand, your competitors, or any keyword, from the publisher RSS and Atom feeds you choose, in one clean and deduplicated dataset with headline, publisher, link, publish time, summary, and the queries each story matched. Turn on monitor mode and schedule it to get only the stories you have not seen before, for PR alerts, SEO link building, competitor tracking, and market research.

Monitor mode

Monitor mode is the way most people use this Actor. Set onlyNewMentions to true and add a schedule, for example every morning at 7 AM or every hour. The Actor remembers every mention it delivered for your queries in a named key-value store. The first run delivers every mention it finds, up to maxResults, as new. Later runs deliver only stories that were not delivered before. Mentions already seen are skipped, and you are not charged for them.

Sample monitor input:

{
"onlyNewMentions": true,
"queries": ["Apify", "\"web scraping\" OR Crawlee"],
"feeds": ["https://techcrunch.com/feed/", "https://www.theverge.com/rss/index.xml"],
"maxAgeDays": 3,
"excludeKeywords": ["jobs"],
"maxResults": 500
}

A few things are worth knowing before you rely on it:

  • A story counts as seen when its link was delivered before, with tracking parameters such as utm_source removed, or when the same headline from the same publisher domain, published on the same day in UTC, was delivered before. A headline the publisher reuses on another day, like a weekly roundup, is a new story. So the same story in two of your feeds, or republished with a new tracking link, is delivered once.
  • The same headline at two different publishers counts as two mentions, because each is a separate piece of coverage.
  • History is keyed on queries, but not on feeds, maxAgeDays, excludeKeywords, or maxResults. Changing the queries starts a fresh history and reports everything as new again. Adding a feed keeps the history, so stories already delivered from another feed are not repeated from the new one.
  • maxResults caps what a run delivers. Mentions past the cap are not remembered, so they are delivered on the next run.
  • The history remembers the most recent 100,000 mention keys (two per mention), so about 50,000 mentions.
  • If the saved history is ever unreadable, the run fails before charging anything rather than reporting every mention as new again. The error names the record to delete from the news-brand-mention-monitor-history store.
  • Two schedules running the same queries at the same time share one history, and the run that finishes last wins.

Every run also saves a summary to the MENTION_SUMMARY record of the run's key-value store, free of charge. It has one entry per feed with the number of entries read, how many matched, how many were duplicates, how many records were delivered, and any error. The run's Output tab links to it.

What does it do?

For each feed link you add, the Actor reads the publisher's RSS 2.0, RSS 1.0, or Atom feed directly and keeps the entries whose title or summary mentions one of your queries and that were published in the last maxAgeDays days. It turns every story into the same record shape, drops duplicates, and delivers the rest. There is no browser, no proxy, no login, and no social network involved.

Queries are written the way you would type them into a news search box:

  • a brand or word, such as Apify,
  • a phrase in quotes, such as "web scraping",
  • alternatives joined by OR, such as Crawlee OR Scrapy,
  • and words to leave out with a minus, such as Apify -jobs.

Each query must appear as whole words in the title or summary, so Apify does not match Apifyer. Search engine operators such as site: are ignored. A feed only holds a publisher's latest stories, often the last 10 to 50, so pick feeds that cover your market and schedule the monitor often enough to catch each story while it is in the feed.

Who is it for?

  • PR and communications teams who want a morning list of new press coverage.
  • SEO teams who look for unlinked brand mentions and link building chances.
  • Marketing and sales teams who track competitors, product launches, and funding news.
  • Founders and analysts who follow a market, a technology, or a list of companies.

How to use

  1. Open the Actor in Apify Console and enter your brand names or search queries.
  2. Add the publisher RSS or Atom feeds to watch. The form starts with TechCrunch, The Verge, Ars Technica, and Engadget.
  3. Adjust the age and excluded keywords under Filters if you need to.
  4. Click Start and wait for the run to finish.
  5. Open the Output tab to preview mentions, then export them as JSON, CSV, Excel, or XML.
  6. For alerts, turn on monitor mode and add a schedule.

Input

FieldTypeDescription
onlyNewMentionstrue or falseMonitor mode. Outputs only mentions not delivered before for the same queries.
querieslistSearch queries, one per line. Up to 100 queries of up to 200 characters each. The same query listed twice is matched once.
feedslistPublisher RSS or Atom feed links, at least 1 and up to 200. A link without https:// is read over https.
maxAgeDaysnumberKeep only mentions published within this many days. Entries without a publish date are always kept. Default 7, maximum 365.
excludeKeywordslistDrop mentions whose title or summary contains any of these words or phrases.
maxResultsnumberMost mention records to deliver in one run. Default 1000, maximum 100,000. The input form starts at 20 so a first run is quick.

Feeds are read in the order you list them, so a story found in two feeds keeps the first feed's link and summary. If one feed is down, the run carries on with the rest and notes the error in the summary. The run fails only when no source could be read.

Sample input:

{
"queries": ["OpenAI", "Anthropic", "\"Mistral AI\""],
"feeds": ["https://techcrunch.com/feed/", "https://www.theverge.com/rss/index.xml"],
"maxAgeDays": 1,
"maxResults": 300
}

Output

Each mention is one dataset item. This is a real record:

{
"mentionId": "76b2faac219eab20",
"status": "new",
"matchedQueries": [
"OpenAI"
],
"title": "OpenAI reportedly lowers funding target for new round",
"publisher": "TechCrunch",
"publisherDomain": "techcrunch.com",
"url": "https://techcrunch.com/2026/10/31/openai-reportedly-lowers-funding-target-for-new-round/",
"publishedAt": "2026-10-31T16:12:55Z",
"summary": "OpenAI’s latest funding round doesn't seem to be living up to expectations.",
"source": "publisherFeed",
"feedUrl": "https://techcrunch.com/feed/",
"detectedAt": "2026-11-01T19:03:07Z"
}

You can download results as JSON, CSV, Excel, or XML, or read them through the Apify API.

  • mentionId is stable across runs for the same cleaned link.
  • status is new in monitor mode and notTracked otherwise.
  • matchedQueries lists every query the story answers, not only the one that found it.
  • url is the publisher's own link, and publisher and publisherDomain name the publisher.
  • summary is the feed's own summary as plain text, up to 500 characters.
  • source is always publisherFeed, and feedUrl is the feed the story came from.
  • A title, publisher, or summary that starts with =, +, -, or @ gets a leading apostrophe, so a spreadsheet opening the CSV export shows it as text instead of running it as a formula.

Pricing

This Actor uses pay-per-event pricing.

  • Mention record: $5.00 per 1,000 mentions delivered to your dataset ($0.005 each).
  • Actor start: Apify's standard start event ($0.00005).
  • The summary is free, and there is no separate charge per dataset item.

A publisher feed holds its latest 10 to 50 stories, so a first run over 10 feeds reads at most about 500 entries. Only entries that match a query are delivered, so even that worst case is under $2.50, and a run is usually a few cents. A daily monitor then delivers only the new stories, often a handful per query per day, so a few cents a day. Exclude keywords and a short maxAgeDays cut the cost further. You can cap any run with Apify's maximum charge setting. The Actor stops cleanly at your limit, and you are only charged for mentions that actually reach your dataset.

Estimated compute cost

Default memory is 512 MB, and the Actor uses under 100 MB of it. Each feed is one small request, paced per host, so even 200 feeds finish in a few minutes. The mention records are almost all of the cost. If a run times out, resurrect it and it continues after the last source it finished, without charging a mention twice.

Data sources and freshness

  • Any publisher RSS 2.0, RSS 1.0, or Atom feed whose link you give, read directly from the publisher's site.
  • Nothing else. The Actor does not query any news search engine or aggregator.

Every mention is read live at run time, so the data is as fresh as the sources. Requests are paced and retried with backoff when a site is busy. Feed links that point at private network addresses, directly or through a redirect, are refused. If the platform moves a run to another server, it resumes after the last source it finished and never delivers or charges a mention twice.

The Actor reads public RSS and Atom feeds without logging in, and it delivers headlines, links, publisher names, dates, and the short summaries publishers put in their own feeds, not full articles. Each publisher's feed terms apply to its content, so check them before you republish anything. The data is provided as is, without any guarantee that it is complete, current, or accurate. This Actor is an independent tool and is not affiliated with or endorsed by any publisher whose feed it reads. You are responsible for how you use the results and for following each site's terms that apply to you.

API and integrations

You can start this Actor and read its results with the Apify API, the Apify Python and JavaScript clients, or the Apify CLI. The API returns each run's dataset in the same formats as the Console.

Apify integrations can pass results on when a run finishes, for example to Google Sheets, Slack, Zapier, Make, or your own webhook. Set them up on the Actor's Integrations tab, and pair them with a schedule for a hands-off feed.

FAQ

Do I need an account or API key? No. Publisher feeds are public and need no login.

How do I find a publisher's feed? Many sites link it as RSS in the footer, and most WordPress sites have one at /feed/. Paste the feed link, not the home page. A home page is reported in the summary as not being a feed.

Why did I get no mentions? A feed only holds a publisher's latest stories, so a niche brand may not appear in a given week. Add feeds that cover your market, such as trade press, your competitors' blogs, or a local paper, and check the summary for feeds that failed.

Why did a story come back after I changed my queries? History is kept per set of queries, so new queries start a new history.

Can it read Reddit, X, or LinkedIn? No. This Actor covers news only: publisher feeds.

Feedback and custom requests

Found a bug, a wrong value, or a source that changed? Open an issue in the Issues tab on this Actor's page. Need another field, filter, or source, or a version built for your team? Describe it in the Issues tab as a custom request.