News Article Extractor: Full Text from Links and RSS

Extract news articles from any publisher. Paste article links, or RSS, Atom and news sitemap feeds to find them. Get title, description, dates, site, section, keywords, language, main text, word count, top image and paywall flag. No author names.

• Pay per result row: the platform usage of the run is included, and a run that finds nothing has no result charges.
• No login, no cookies, no account on the publishers: public pages only.
• Export to JSON, CSV, Excel, XML or HTML, or read the rows through the Apify API.
• Start it from the Console, on a schedule, through the API, or as a tool for agents over MCP.
• Tested every day on its example input, with the rows checked, and repaired when a check fails.

What you can use it for

• Media monitoring: turn RSS feeds of the outlets you follow into full article text on a schedule.
• Datasets for search, analytics or language models: clean main text with title, date and word count.
• Content research: see what a publisher writes about and how long its articles run.
• Archive building: keep the text of articles you cite, with their publication dates.

What you get

Every result is one row in the run's dataset. Download it as JSON, CSV, Excel or HTML, or read it through the Apify API. The main fields:

Field	Meaning
title	Title
publishedAt	Published
siteName	Site
section	Section
language	Language
wordCount	Words
paywalled	Paywalled
url	Link
topImage	Image

Example row:

{
  "url": "https://www.nasa.gov/news-release/nasa-names-stephen-cash-marshall-space-flight-center-director/",
  "canonicalUrl": "https://www.nasa.gov/news-release/nasa-names-stephen-cash-marshall-space-flight-center-director/",
  "title": "NASA Names Stephen Cash Marshall Space Flight Center Director",
  "description": "NASA Administrator Jared Isaacman has named Stephen Cash director of the agency’s Marshall Space Flight Center in Huntsville, Alabama, effective Monday, Oct.",
  "publishedAt": "2026-10-16T20:14:39Z",
  "modifiedAt": "2026-10-16T16:14:41-04:00",
  "siteName": "NASA",
  "section": "Leadership",
  "keywords": [
    "Leadership",
    "Marshall Space Flight Center",
    "NASA Headquarters"
  ],
  "language": "en-US",
  "text": "NASA Administrator Jared Isaacman has named Stephen Cash director of the agency’s Marshall Space Flight Center in Huntsville, Alabama, effective Monday, Oct. 19. Cash, a veteran NASA engineer and aerospace executive, returns to lead the center where he began his career more than four decades ago.\n\n“Marshall contributions to NASA’s missions are historic and it’s no question why it’s the Center of Excellence for propulsion,” said Isaacman. “Steve Cash is a Marshall legend, has spent his career around the hardware, the people and has been in the seat before making the decisions when human spaceflight is on the line. As Marshall continues its critical role in Artemis and takes on new challenges in advanced propulsion, nuclear power, and the systems that will carry us deeper into the solar system, Steve brings the experience, technical judgment, and mission focus needed to lead the center into that next chapter. I am also grateful to Rae Ann Meyer for the leadership she has provided to Marshall during this transition and for her continued service to NASA.”",
  "wordCount": 173,
  "topImage": "https://www.nasa.gov/wp-content/uploads/2026/10/steve-cash-photo.jpg",
  "isAccessibleForFree": null,
  "paywalled": null,
  "sourceFeed": "https://www.nasa.gov/news-release/feed/"
}

How to use it

1. Open the Input tab (or call the actor through the API, see below).
2. Fill in Feeds and sitemaps, Articles per feed; the form opens with a working example.
3. Set Maximum results to cap the size and the cost of the run.
4. Click Start. Rows appear on the Output tab while the run works.
5. Download the dataset, or connect it to Google Sheets, Make, Zapier, n8n or a webhook.

Input

Field	Type	Required	Description
articleUrls	array	no	Links to news articles or blog posts, one per line, at most 1000. Use the address of the article page itself.
feedUrls	array	no	RSS or Atom feed addresses, or news and standard XML sitemap addresses of a publisher, at most 50. Each one is read to find article links, newest first, and those articles are read. Give at least one article link or one feed.
publishedAfter	string	no	Optional date as YYYY-MM-DD, or a date and time such as 2026-10-01T08:00:00Z. Articles that are known to be older are skipped. Articles that show no date are kept.
includeText	boolean	no	Add the main text of each article. Switch it off for a smaller dataset with the other fields only; the word count is still filled in. Default: true.
maxArticlesPerFeed	integer	no	How many of the newest articles to read from each feed or sitemap. Default: 25.
maxItems	integer	no	The run stops after this many result rows. It also caps what one run can cost. Default: 100.
proxyConfiguration	object	no	Leave as is: the run starts on the cheapest network the site accepts and switches to Apify Proxy automatically when the site blocks it. Pick proxy groups here only to force one specific network.

Example input:

{
  "feedUrls": [
    "https://www.nasa.gov/news-release/feed/"
  ],
  "maxArticlesPerFeed": 10,
  "maxItems": 20
}

Pricing

You pay per result row in the dataset (the current price per 1,000 results is on the Pricing tab). A run that finds nothing produces no rows and no result charges. Set Maximum results to cap what a single run can cost.

Limits and notes

• Give article links, feeds, or both: at most 1000 links and 50 feeds. Feeds and sitemaps are read for their newest links (25 per feed unless you change Articles per feed, at most 500); each article costs one page read.
• RSS 2.0, RSS 1.0, Atom, standard XML sitemaps and Google News sitemaps work, also gzip sitemaps. A sitemap index is followed one level down, into at most 3 of its sitemaps (news sitemaps first).
• Published after skips articles whose date is known to be older. A feed entry is checked before its page is read, so old entries cost nothing.
• Each article is read from its structured data first, then from its page meta tags, then from the page body. Fields a page does not show are empty instead of guessed. The text is the main article body as plain text, paragraphs separated by a blank line.
• Paywalled is true when the page says it is not free to read. You then get what the public page shows, usually a preview. Nothing behind a login or paywall is fetched.
• Author and byline names, profile links, e-mail addresses and phone numbers are not collected, and are removed from titles, descriptions and text.
• Only pages that robots.txt leaves open are read; a closed page is skipped and produces no row. Private or local addresses are refused.
• Article text belongs to its publisher. Some publishers forbid automated copying in their terms, so check the terms of the sites you read and use the text within copyright law.
• Only publicly visible data is collected. No login, no paywalled content, no personal contact details.
• The actor reads only pages that the site's robots.txt leaves open to automated access.
• Sites change their pages from time to time. The actor is checked automatically and repaired when a check fails.
• Each run sends one short usage record to the developer: the Actor and run IDs, the number of results, whether the run succeeded (and if not, the kind of error, such as "blocked" or "input problem"), whether the account is on a paid Apify plan, how the run was started (for example from the Console, the API or a schedule) and a one-way fingerprint of the account (a hash, not the account ID), so that repeat runs of one account count once. It contains nothing from your input or results.

Run it through the API

Python, with the apify-client package:

from apify_client import ApifyClient

client = ApifyClient("<YOUR_APIFY_TOKEN>")
run = client.actor("v0iddo/news-scraper").call(run_input={"feedUrls": ["https://www.nasa.gov/news-release/feed/"], "maxArticlesPerFeed": 10, "maxItems": 20})
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item)

JavaScript, with the apify-client package:

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: '<YOUR_APIFY_TOKEN>' });
const run = await client.actor('v0iddo/news-scraper').call({"feedUrls": ["https://www.nasa.gov/news-release/feed/"], "maxArticlesPerFeed": 10, "maxItems": 20});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

One HTTP call that waits for the run and returns the rows (for runs that finish within 5 minutes):

curl -X POST "https://api.apify.com/v2/acts/v0iddo~news-scraper/run-sync-get-dataset-items?token=<YOUR_APIFY_TOKEN>" \
  -H "Content-Type: application/json" \
  -d '{"feedUrls": ["https://www.nasa.gov/news-release/feed/"], "maxArticlesPerFeed": 10, "maxItems": 20}'

Use it from an agent (MCP)

Claude, Cursor, VS Code and other MCP clients can call this actor as a tool through the Apify MCP server. Add it to the client's MCP configuration:

{
  "mcpServers": {
    "apify": {
      "url": "https://mcp.apify.com?tools=v0iddo/news-scraper",
      "headers": {
        "Authorization": "Bearer <YOUR_APIFY_TOKEN>"
      }
    }
  }
}

Then ask, for example: "Get the full text of today's articles from these RSS feeds."

FAQ

Do I need an account on the publishers, cookies or an API key?

No. The actor reads only what every visitor of the publishers can see, without logging in. You only need an Apify account to start it.

How many results can one run return?

Up to 2,000 rows per run. Without a limit it stops at 100. Set Maximum results to the number you need; large jobs can also be split into several runs or scheduled.

How am I charged?

Per result row in the dataset, at the price on the Pricing tab for your Apify plan. The platform usage of the run is included in that price. A run that finds nothing produces no rows and no result charges, and your spending limit for a run is always respected.

Why did my run return no results?

The status message of the run says why: nothing matched the input, the input was not a page the actor understands, the page is closed to automated access by robots.txt, or the site refused every network the actor tried. Check the input against the example above and run it again with a small limit.

Can I run it on a schedule?

Yes. Save your input as a task and add a schedule in the Apify Console (daily, hourly or with a cron expression). Each run gets its own dataset, so you keep a history.

Which formats can I export?

JSON, CSV, Excel, XML, HTML table and RSS from the Output tab or the API. Integrations send the rows to Google Sheets, Slack, Make, Zapier, n8n or a webhook.

Is collecting this data allowed?

The actor collects only what the publishers publishes to every visitor, without a login, and it reads only pages that robots.txt leaves open. Public data can still be personal data under laws such as the GDPR, and sites have their own terms: make sure your use of the data follows the rules that apply to you.

What happens when the publishers changes its pages?

Automated tests run the actor every day on the example input and check the rows, not only that the run finished. When a check fails, the actor is repaired and rebuilt; the build history on this page shows each update.

Something is missing or wrong. Where do I report it?

Open an issue on the Issues tab of this actor with the run link. Requests for a new field are welcome too.

Related actors

• Substack Posts Scraper: Archive, Reactions, Comments
• Hacker News Scraper
• Medium Scraper
• Substack Scraper: Newsletter Posts by Publication