Article content extractor

Article Content Extractor — extract headline, byline, and body from news and blog URLs

Article Content Extractor fetches public news, blog, newsroom, and press pages you already have and returns structured article rows: headline, byline, publish date, body, excerpt, and hero image. Store actor taroyamada/article-content-extractor. It is a bounded HTML cleanup step for research, content QA, and RAG ingestion — not a ranking tool, a full-site crawler, or a Google News search. For docs, pricing, policy, product, and help-center pages, use Website Content Extractor. For the RAG split, see Article Content Extractor vs Website Content Extractor for RAG. For query-based headline discovery, use Google News Scraper.

Open Input → Start. 1 URL ≈ $0.008. From $8.00 / 1,000 useful rows. Leave the $2.50 audit report and $5.00 batch export off.

Open Input → Start Store listing

Cheapest first paid run · URL to Markdown for RAG · Compare with Website Content Extractor

What is Article Content Extractor Apify?

Article Content Extractor Apify is the taroyamada Store actor article-content-extractor. It fetches public news, blog, newsroom, and press URLs you already have and returns structured article rows: headline, byline, publish date, body, excerpt, and hero image. It is not Google News search and not a full-site crawler.

How do I use Article Content Extractor Apify?

Pass a urls list of article-shaped HTTP(S) pages (maximum 300). Keep includeImages false for the cheapest first paid run and leave generateReport and emitExport off. See the cheapest first paid run.

Where is the Article Content Extractor Apify Store page?

The live listing is https://apify.com/taroyamada/article-content-extractor. This page is the English landing.

Articles versus site pages versus news discovery

Use this page when the URLs are article-shaped: news, blog, newsroom, or press. Use Website Content Extractor when the URLs are broader site pages that are not article-shaped. Side-by-side: Article Content Extractor vs Website Content Extractor for RAG. Use Google News Scraper when you still need article URLs from search queries.

	Article Content Extractor	Website Content Extractor	Google News Scraper
Intent	Parse news, blog, newsroom, and press article pages	Clean docs, product, pricing, policy, and help-center HTML	Discover current article URLs by query
Input	Article-shaped page URLs (max 300)	Site page URLs (max 200)	Search `queries` (max 50)
What it reads	Live article HTML	Live page HTML	Google News RSS
Output format	`markdown` (default) or `text` — no HTML emit	`markdown` (default), `text`, or `html`	Headline metadata plus article URL — no full-article text
Sample row	`article`	`web_content`	RSS article row (`title`, `link`, `source`, dates, snippet, `query`)
Optional extras	`includeImages`, `generateReport`, `emitExport`	`includeMetadata`, `maxChargeUsd`	`language`, `country`, `maxItems`, `deduplicate`

None of these Actors is a ranking tool, a full-site crawler, or a claim of publisher endorsement. Fetch public HTTP(S) URLs you own or are authorized to audit. Do not imply content ownership transfer.

Compare: for a side-by-side of article-shaped news, blog, and press URLs versus broader docs and site pages for RAG, see Article Content Extractor vs Website Content Extractor for RAG.

Use cases

Parse news and blog URLs for headline, author, date, body, excerpt, and hero image.
Capture press-release pages as structured article rows.
Source extraction for content QA (title, metadata, thin-content, and page-quality checks).
Source extraction for indexability and RAG readiness work on authorized article URLs.
Optionally request a source-linked content-audit report or batch export when at least one article is usable.
Deliver to a dataset or webhook for research handoff.

Route docs, pricing, policy, product, and help-center pages to Website Content Extractor. Discover URLs first with Google News Scraper or RSS & Atom Feed Extractor. This Actor is for article-shaped pages (max 300 URLs).

Low-cost article extraction

The default path keeps raw article rows. generateReport and emitExport stay false unless you need those value events. outputFormat defaults to markdown. Live Input leaves includeImages false for a low-cost first run.

{
  "urls": [
    "https://en.wikipedia.org/wiki/Web_scraping"
  ],
  "outputFormat": "markdown",
  "includeImages": false,
  "generateReport": false,
  "emitExport": false,
  "delivery": "dataset",
  "dryRun": false
}

That is the cheapest first paid extractor input. Leave generateReport and emitExport off. If one Actor Start event and one useful article row charge, documented PPE is $0.00005 + $0.008 ≈ $0.008. For the event table, see Cheapest first paid run for Article Extractor.

Published output fields: rowType, url, headline, author, publishedAt, articleText, excerpt, heroImage, and sourceUrl. Sample rowType is article. README sample (placeholder article data, not a live coverage guarantee):

{
  "meta": {
    "actorName": "article-content-extractor",
    "actorTitle": "Article Content Extractor",
    "bundle": "Site QA & Content Intelligence Pack",
    "fetchedAt": "2026-05-06T00:00:00.000Z",
    "totalRows": 1
  },
  "rows": [
    {
      "actorName": "article-content-extractor",
      "rowType": "article",
      "url": "https://example.com/news/example",
      "headline": "Example Headline",
      "author": "Example Author",
      "publishedAt": "2026-05-06",
      "articleText": "Example article body.",
      "sourceUrl": "https://example.com/news/example",
      "fetchedAt": "2026-05-06T00:00:00.000Z"
    }
  ],
  "warnings": []
}

Rows also include fetch timestamps, warnings for partial or changed content, and stable IDs when the workflow supports recurring change detection. Optional inline images when includeImages is true; heroImage can still be returned separately when available. There is no separate output schema on the Store page.

Run this 1-URL extraction on Apify Input · Cheapest first paid run

Content audit report and batch export

Set generateReport to true to emit one article-content-audit-report row when at least one article is usable. Set emitExport to true to emit one article-batch-export row when at least one article is usable. Raw article rows remain source context. Do not add report-only fields meant for separate Site QA or RAG Store Actors to this extractor input.

{
  "urls": [
    "https://example.com/blog/post"
  ],
  "generateReport": true,
  "delivery": "webhook",
  "webhookUrl": "https://example.com/webhook",
  "dryRun": false
}

Live PPE for those value events is $2.50 per content audit report and $5.00 per batch export. Request limits are bounded at 300 URLs, 3 redirects, and 5 MiB per HTML response by default. maxRedirects and maxResponseBytes can be lowered; the runtime never permits more than 10 redirects or 10 MiB.

Generate an article report on Apify Input

How is Article Content Extractor different from Website Content Extractor?

This Actor parses public news, blog, newsroom, and press pages into article rows: headline, author, publishedAt, articleText, excerpt, and heroImage. Maximum 300 URLs per run. outputFormat is markdown (default) or text — it does not emit HTML. Website Content Extractor cleans docs, product, pricing, policy, and help-center pages that are not article-shaped (maximum 200 URLs) and can emit markdown, text, or HTML. Route broad site pages there. Side-by-side: Article Content Extractor vs Website Content Extractor for RAG.

How is Article Content Extractor different from Google News Scraper and RSS discovery?

This Actor is HTML cleanup for article-shaped URLs you already have. It is not a search surface. Google News Scraper is query-based Google News RSS discovery (queries, maximum 50) and returns headlines and article URLs without full article text. RSS & Atom Feed Extractor parses known-publisher feed XML (feedUrls, maximum 50) and does not crawl page HTML. Discover URLs first, then send news, blog, and press links here.

Which public article URLs can I pass, and what is rejected?

Pass public HTTP(S) news, blog, newsroom, or press URLs you own or are authorized to fetch. Maximum 300 URLs per run. Loopback, private, link-local, metadata, reserved, and DNS-resolved private targets are rejected, as are non-HTML responses, excessive redirects, and oversized responses. Default bounds are 3 redirects and 5 MiB per HTML response; the runtime never permits more than 10 redirects or 10 MiB. Schema prefill is one Wikipedia Web_scraping URL.

What fields does a useful article row include?

The published README field list is rowType, url, headline, author, publishedAt, articleText, excerpt, heroImage, and sourceUrl. Sample rowType is article. Rows also include fetch timestamps, warnings when a source is partial or changed, and stable IDs when the workflow supports recurring change detection. Optional inline images when includeImages is true; heroImage can still be returned separately. The README sample is placeholder article data, not a live coverage guarantee. There is no separate output schema on the Store page.

What published input starts an Article Content Extractor run?

urls is required. The published schema has no maxChargeUsd and no includeMetadata. Live input fields:

Field	Type	Default	Notes
`urls`	string[]	required	Public article, news, blog, newsroom, or press URLs (max 300). Schema prefill is one Wikipedia Web scraping URL.
`outputFormat`	string	`markdown`	Enum: `text` or `markdown`. No `html`.
`includeImages`	boolean	false	Include the inline images array. `heroImage` can still be returned separately. Leave false for the cheapest first paid run.
`concurrency`	integer	5	Parallel article requests (1–10).
`timeoutMs`	integer	15000	Request timeout per article in milliseconds.
`maxResponseBytes`	integer	5242880	Reject HTML responses larger than this limit before parsing (5 MiB default; runtime cap 10 MiB).
`maxRedirects`	integer	3	Maximum public HTTP redirects followed per article (runtime cap 10).
`delivery`	string	`dataset`	Enum: `dataset` or `webhook`.
`webhookUrl`	string	—	POST target when `delivery` is `webhook`. Skipped on `dryRun`.
`generateReport`	boolean	false	Emit one `article-content-audit-report` when at least one article is usable.
`emitExport`	boolean	false	Emit one `article-batch-export` when at least one article is usable.
`dryRun`	boolean	false	Validate input and write only local output. No dataset, webhook, or payable rows.

Do not send unpublished aliases such as includeMetadata, maxChargeUsd, html as outputFormat, Google News queries, RSS feedUrls, authorizedUseConfirmed, or emitUnchanged. Those belong on other Actors.

Start a run on Apify Input

When do article-content-audit-report and article-batch-export emit?

Set generateReport to true to emit one article-content-audit-report row when at least one article is usable ($2.50). Set emitExport to true to emit one article-batch-export row when at least one article is usable ($5.00). These are this Actor’s published value events. Raw article rows remain source context. The default path leaves both flags false.

How is Article Content Extractor priced?

Billing is pay-per-event. The live Store card is from $8.00 / 1,000 useful article rows because the billed useful-row event is $0.008. Live events:

Useful article row (apify-default-dataset-item): $0.008 ($8.00 / 1,000) for one successfully extracted or partially extracted public article row
Article content audit report (article-content-audit-report): $2.50 for one explicitly requested source-linked batch audit report
Article batch export (article-batch-export): $5.00 for one explicitly requested export-ready article batch handoff
Actor Start (apify-actor-start): $0.00005, one event per GB with a minimum of one event

Platform usage is included. You are not charged for Apify platform usage, only the fixed event prices. Failed or no-content rows stay out of the default dataset. Dry runs, validation-only runs, error-only runs, and no-usable-row recurring polls do not write payable rows. The default dataset is the canonical billable surface.

Open Input → Start. 1 URL ≈ $0.008. From $8.00 / 1,000 useful rows. Audit report $2.50. Batch export $5.00.

See Article Content Extractor pricing on Apify

How does Article Content Extractor deliver dataset, webhook, and dry-run output?

delivery defaults to dataset. A non-dry-run always writes canonical dataset rows first; webhook delivery runs only after dataset and pay-per-event output succeed. A webhook is sent only after dataset billing succeeds and is best effort; a failed webhook is not retried by the Actor and never creates a second charge. webhookUrl is used when delivery is webhook and is skipped on dryRun. dryRun validates input and writes only local output — no dataset writes, webhooks, or payable rows.

Does Article Content Extractor emit HTML output?

No. The published outputFormat enum is markdown (default) or text. This Actor does not emit HTML. Website Content Extractor is the sibling that can return html as well as markdown or text.

Does includeImages replace heroImage or add an inline images array?

includeImages defaults to false and, when true, includes the inline images array in the result. The heroImage field can still be returned separately when available. Leave includeImages false for a low-cost first run. heroImage is in the published README field list either way.

Does Article Content Extractor crawl a full site or rank pages?

No. You supply the URL list. Maximum 300 URLs per run. It is a bounded source extractor for research, content QA, and RAG ingestion — not a ranking tool, a full-site crawler, or a claim of publisher endorsement. It does not imply content ownership transfer. Only fetch public HTTP(S) URLs that you own or are authorized to audit.

Open Article Content Extractor Input on Apify

Are failed or empty article fetches billed as useful article rows?

No. Failed or no-content rows stay out of the default dataset. The billed useful-article-row event is for one successfully extracted or partially extracted public article row ($0.008). Dry runs, validation-only runs, error-only runs, and no-usable-row recurring polls do not write payable rows. The default dataset is the canonical billable surface.

Does Article Content Extractor accept maxChargeUsd or includeMetadata?

No. Those are Website Content Extractor fields. This Actor’s published input has no maxChargeUsd safety cap and no includeMetadata flag. Do not send html as outputFormat, Google News queries, RSS feedUrls, or Site QA-only fields such as authorizedUseConfirmed and emitUnchanged.

Can I send Google News queries or RSS feed URLs into Article Content Extractor?

No. Required input is a urls list of article-shaped HTTP(S) pages. For query-based Google News RSS discovery use Google News Scraper (queries). For known-publisher feed XML use RSS & Atom Feed Extractor (feedUrls). After those discovery runs, send news, blog, and press page URLs here and docs, pricing, policy, or product URLs to Website Content Extractor.