RSS & Atom feeds

Parse known-publisher RSS and Atom XML into filtered item URL lists

Job: parse public RSS/Atom XML you already have into filtered item URL lists (title, link, dates, summary) before a downstream extractor runs.

Not Google News queries. Not article HTML cleanup. Not a site crawl / sitemap.xml inventory.

Try Input: 1 feed × maxItemsPerFeed 1 = $0.001 if one item is parsed. $1.00 / 1,000 items. No Actor start event. Store Quickstart is 2 publisher feeds.

Open RSS & Atom Feed Extractor → one public feed URL, maxItemsPerFeed 1 → Start ($0.001 if one item parses) → send useful links to Article or Website Content Extractor.

Open taroyamada/rss-feed-aggregator on the Apify Store · Newsroom RSS first paid path

Discover item URLs here - clean page bodies elsewhere

Step Actor Input
1. Known feeds This hub / RSS & Atom Feed Extractor feedUrls (max 50)
2a. News/blog bodies Article Content Extractor returned article URLs
2b. Docs/policy pages Website Content Extractor returned non-article URLs
Discovery without feeds Google News Scraper queries - different job

Cheapest first paid:

{
  "feedUrls": ["https://blog.google/rss/"],
  "maxItemsPerFeed": 1,
  "deduplicate": true,
  "delivery": "dataset",
  "dryRun": false
}

Live required field is feedUrls. Do not send feeds, onlyNewSinceLastRun, or snapshotKey (not live schema). Unsuccessful fetches are not billed as items.

Feed XML you already have, not Google News queries and not article HTML

Use this page when you already have public RSS or Atom feed URLs and need a filtered list of new item links. Use Google News Scraper when you search Google News by keyword and do not yet have publisher feed URLs. Use Article Content Extractor to clean discovered article, news, and blog pages. Use Website Content Extractor to clean discovered docs, pricing, policy, or product pages. Those extractors fetch page HTML. This Actor reads feed XML.

RSS & Atom Feed Extractor Google News Scraper Article Content Extractor Website Content Extractor
Intent Discover fresh URLs from known publisher and blog feeds Discover current article URLs by query Clean discovered article, news, and blog pages Clean discovered docs, pricing, policy, or product pages
Input Public RSS/Atom URLs in feedUrls (max 50) Search queries (max 50) Article-shaped page URLs (max 300) Site page URLs that are not article-shaped (max 200)
What it reads Feed XML — no site crawl, no browser automation Google News RSS for those queries Live article HTML Live page HTML
Localization Not a search surface language and country Not a search surface Not a search surface
Primary output Feed items: title, link, dates, summary, encoded content when present Headline, article URL, publisher, timestamps, snippet, originating query Article body, byline, date, excerpt, hero image Cleaned markdown or text plus page metadata
HTML cleanup No. Feed discovery only No. Clean pages afterward with an extractor Yes — bounded article extraction Yes — broader site-page extraction

This page is also not the podcast-RSS comparison. For show catalogs versus iTunes Search, see RSS feed vs iTunes Search API. Feed XML here is RSS or Atom item feeds, not sitemap.xml URL inventories.

Use cases

Those four bullets are the published README use cases. The README positions the Actor as a lightweight feed-to-scraper feeder for recurring monitoring of publisher blogs, company newsroom updates, and tech newsrooms. Start with a small set of high-trust feeds.

What public RSS and Atom XML does this Actor parse?

Public RSS and Atom XML feeds you already have. Required input is feedUrls (maximum 50 per run; schema description: Public RSS/Atom URLs to monitor). The Actor parses feed XML and returns feed items — titles, item URLs, publication timestamps, summaries, encoded content when available, and categories or tags. It does not crawl website HTML, it does not query Google News, and it does not extract full article bodies from those item links. Authenticated or HTML-only pages are not feed input.

How is known-publisher feed XML different from Google News query RSS and from article HTML cleanup?

This Actor is a known-publisher feed discovery layer: you already have public RSS or Atom URLs and pass them in feedUrls. Google News Scraper is query-based discovery: required input is queries (maximum 50 search terms), localized with language and country, reading Google News RSS rather than publisher feeds you supply. 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. Send this Actor's returned links to those extractors when you need full page text.

What live input does RSS & Atom Feed Extractor require?

The live OpenAPI input schema requires feedUrls. Optional fields are keywords, maxItemsPerFeed, deduplicate, timeoutMs, delivery, webhookUrl, and dryRun.

Field Type Default Notes
feedUrls string[] required Public RSS/Atom URLs to monitor (max 50). Schema prefill is https://blog.google/rss/ and https://openai.com/news/rss.xml.
keywords string[] — Optional include-list keywords. Matching rows return a matchedKeywords field.
maxItemsPerFeed integer 25 Maximum items to keep from each feed; 1–200. Schema title: Max Items per Feed.
deduplicate boolean true Remove duplicate links across feeds
timeoutMs integer 15000 Request timeout in milliseconds; 1000–30000
delivery string dataset dataset or webhook
webhookUrl string — Webhook target used when delivery is webhook
dryRun boolean false Run without saving results

Published README input illustration (schema-valid names):

{
  "feedUrls": [
    "https://blog.google/rss/",
    "https://openai.com/news/rss.xml"
  ],
  "keywords": ["AI", "agents"],
  "maxItemsPerFeed": 10,
  "deduplicate": true
}

Published Store example run input:

{
  "feedUrls": [
    "https://hnrss.org/frontpage"
  ],
  "keywords": [],
  "maxItemsPerFeed": 10,
  "deduplicate": true,
  "delivery": "dataset",
  "dryRun": false
}

The live fields are feedUrls and maxItemsPerFeed. Do not send unpublished aliases.

Cheapest first paid input: one feed URL, maxItemsPerFeed 1 (schema minimum 1–200). The Store Quickstart is two publisher feeds. The Store example run uses maxItemsPerFeed 10.

{
  "feedUrls": [
    "https://blog.google/rss/"
  ],
  "maxItemsPerFeed": 1,
  "deduplicate": true,
  "delivery": "dataset",
  "dryRun": false
}

If one public feed item is parsed, documented PPE is $0.001. There is no Actor start event. Unsuccessful fetches are not billed as RSS or Atom items. Then raise maxItemsPerFeed or add the second prefill feed after the item URL is useful. For newsroom monitoring, see Monitor publisher and newsroom RSS feeds.

Run this 1-feed input on Apify

Which fields does a parsed RSS or Atom item include?

The published README output table lists source (feed URL that produced the row), title, link (item URL for downstream extraction), pubDate (original feed date), pubDateISO (ISO timestamp version of pubDate), description (summary text from the feed), content (encoded content when available), categories (categories or tags from the feed), and matchedKeywords (keywords that matched the row). That table is the published field inventory, not a live coverage guarantee for every feed.

Published README sample:

{
  "source": "https://openai.com/news/rss.xml",
  "title": "The next evolution of the Agents SDK",
  "link": "https://openai.com/index/the-next-evolution-of-the-agents-sdk",
  "pubDate": "Wed, 15 Apr 2026 10:00:00 GMT",
  "pubDateISO": "2026-04-15T10:00:00.000Z",
  "description": "OpenAI updates the Agents SDK with native sandbox execution...",
  "matchedKeywords": ["ai", "agents"]
}

That sample is the published README illustration of a filtered item, not a live coverage guarantee. After you confirm recent item URLs, send article, news, and blog links to Article Content Extractor and docs, product, or policy links to Website Content Extractor.

Does feed XML parsing return cleaned article bodies?

No. This Actor is a feed discovery layer, not a full-content extractor and not an HTML cleaner. It reads RSS or Atom XML. Use Article Content Extractor on returned news, blog, and press links. Use Website Content Extractor on returned docs, product, pricing, policy, or help-center links. Encoded content in the feed row, when present, is still feed XML content, not a cleaned article-body extract.

How does OR-based keyword filtering attach matchedKeywords?

keywords is an optional include-list. Matching is OR-based: any matched keyword keeps the item. Filtered rows include a matchedKeywords array so you can see which terms triggered the row. There is no exclude list in the published input schema. An empty keywords list does not apply that include filter. The README FAQ states you can see why an item matched via matchedKeywords.

When should I pass feedUrls instead of Google News queries?

Pass feedUrls here when you already know the publishers you trust and have their public RSS or Atom URLs. Use Google News Scraper when you do not have feed URLs yet and want broader query-based discovery. This page is not a search surface: it has no language or country localization fields. Google News Scraper localizes with language (default en) and country (default US).

Does the live schema accept feeds, onlyNewSinceLastRun, or a snapshot key?

No. The live required field is feedUrls. The published OpenAPI schema does not expose a feeds alias, onlyNewSinceLastRun, or snapshotKey. README illustrations that show a feeds array or a delta-only snapshotKey run are not live input names. Send feedUrls, not feeds.

How do dataset delivery, webhookUrl, and dryRun work for this feed Actor?

delivery defaults to dataset (Where to send results: dataset or webhook). Set delivery to webhook and supply webhookUrl when you want webhook delivery. Live enum values are dataset and webhook; dataset_and_webhook is not a live enum value on this Actor. dryRun defaults to false and runs without saving results. The live schema description for dryRun is: Run without saving results.

How does cross-feed deduplicate treat duplicate item links?

deduplicate defaults to true. The live schema description is: Remove duplicate links across feeds. Keep that default when several publishers syndicate the same item URL. Set it false only when you need one row per source feed even if the link repeats.

What is the published Quickstart path for two publisher feeds?

The Store Quickstart section says: start with Quickstart (2 publisher feeds) for a reliable first run; use Multi-Source Monitoring to watch several feeds with keyword filters; use RSS → Article Cleanup when the next step is article extraction.

  1. Run Quickstart (2 publisher feeds).
  2. Confirm the Actor returns recent item URLs plus matchedKeywords.
  3. Send article, news, and blog links to Article Content Extractor.
  4. Send docs, product, or policy links to Website Content Extractor.

Those four steps are the published first-run buyer path. Start with a small set of high-trust feeds.

Can I pass Google News queries or article page URLs into this feed Actor?

No. Required input is feedUrls: public RSS or Atom XML URLs (maximum 50). Google News search terms belong on Google News Scraper as queries. 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 item links, send news, blog, and press URLs to Article Content Extractor.

Does this Actor crawl a site, open a browser, or parse sitemap.xml?

No. It reads public RSS or Atom feed XML from the URLs in feedUrls. It does not crawl a website to find pages, it does not use browser automation, and it does not parse sitemap.xml URL inventories. Podcast catalog RSS versus iTunes Search is a different comparison: RSS feed vs iTunes Search API, not this Actor.

Are unsuccessful feed fetches billed as RSS or Atom items?

The live Store event RSS or Atom item (apify-default-dataset-item) is charged only for one successfully parsed public feed item at $0.001. dryRun runs without saving results. There is no Actor start event on the current pricing tab. Platform usage is listed as Included. The cheapest first paid cap is one feedUrls item with maxItemsPerFeed 1: $0.001 if one item is parsed.

How is RSS & Atom Feed Extractor priced on the live Store?

Billing is pay per event. The live Store card is $1.00 / 1,000 rss or atom items. Current PPE:

Event Price Emitted when
apify-default-dataset-item (RSS or Atom item) $0.001 Charged only for one successfully parsed public feed item

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. The cheapest first paid cap is one feed × maxItemsPerFeed 1 = $0.001 if one item is parsed. The Store Quickstart is two publisher feeds at the same rate.

Try Input: 1 feed × maxItemsPerFeed 1 = $0.001 if one item is parsed. $1.00 / 1,000 items. No Actor start event.

See RSS & Atom Feed Extractor pricing on Apify

Limits to keep in mind

Try Input: 1 feed × maxItemsPerFeed 1 on Apify

Related pages