Article Content Extractor

Paste 1 article URL and Start. Charged $0.008 per useful row only.

First paid run

Start with one public article URL. Keep generateReport and emitExport false. One URL is ≈ $0.008 per useful row. The From $2500 Store card is the audit-report price, not the first-run price.

{
  "urls": ["https://example.com/news/example"],
  "outputFormat": "markdown",
  "includeImages": false,
  "generateReport": false,
  "emitExport": false,
  "dryRun": false
}

Use this first proof to confirm the useful article row, source URL, and warning fields before adding any downstream deliverable.

Store Quickstart

Run the low-cost extraction with a single authorized URL and image extraction disabled:

{
  "urls": ["https://example.com/news/example"],
  "includeImages": false,
  "delivery": "dataset",
  "dryRun": false
}

Run the next report

Turn a small extraction into a decision-ready Site QA workflow:

• Run a content QA report for source-linked title, metadata, thin-content, and page-quality issues.

• Run an indexability and AI crawler report for robots, sitemap, canonical, noindex, schema, and crawler-access findings.

• Run a website RAG readiness report for retrieval structure, coverage, and source-linked readiness findings.

This follow-on actor uses user-supplied public URLs only. It does not provide ranking guarantees, legal advice, or automated messaging workflows.

Content teams and QA teams provide public article URLs they own or are allowed to audit. Use the extracted URLs as the source step for a Site QA report or export, then review source-linked issues rather than raw HTML alone.

The report actors below produce the buyer-facing deliverable; this actor remains the bounded extraction step.

High-value Site QA/RAG handoff

Use this actor as the low-cost source step, then send the same URLs to one linked Site QA or RAG report actor. Keep extraction and the buyer-facing report as separate runs so the first cost and the high-value deliverable are clear.

Input examples

Article URLs

{
  "urls": ["https://example.com/news/example"],
  "includeImages": true,
  "delivery": "dataset",
  "dryRun": false
}

Press pages

{
  "urls": ["https://example.com/press/release"],
  "includeImages": false,
  "delivery": "dataset",
  "dryRun": false
}

Value path output preview

The report/export output is the buyer-facing result. The extraction row below is only the source step:

{
  "actorName": "site-qa-content-report-scraper",
  "rowType": "site_qa_report",
  "billingEventName": "site-qa-report-generated",
  "sourceUrl": "https://example.com/news/example",
  "issueCount": 2,
  "reportStatus": "action_needed"
}

Article value events

Use generateReport=true to emit one article-content-audit-report row at $2.50, or emitExport=true to emit one article-batch-export row at $5.00, when at least one article is usable. These are the buyer-facing batch deliverables; raw article rows remain source context.

Output fields

• rowType
• url
• headline
• author
• publishedAt
• articleText
• excerpt
• heroImage
• sourceUrl

Rows also include source URLs, fetch timestamps, warnings when a source is partial, and stable IDs when the workflow supports recurring change detection.

Pricing and no-change runs

$0.00005 actor start, $0.008 per useful article row, $2.50 per article content audit report, and $5.00 per batch export. Failed/no-content rows stay out of the default dataset.

The default dataset is the canonical billable surface. Dry runs, validation-only runs, error-only runs, and no-usable-row recurring polls do not write payable rows. A webhook is sent only after dataset billing succeeds and is best effort; a failed webhook is not retried and never creates a second charge.

Request limits are bounded at 300 URLs, 3 redirects, and 5 MiB per HTML response by default. maxRedirects and maxResponseBytes can be lowered for stricter runs; the runtime never permits more than 10 redirects or 10 MiB.

Compliance guardrails

• Fetch public article pages supplied by the user.

• Do not imply content ownership transfer or publisher endorsement.

• Use output for research, QA, and internal workflows.

• Do not use provider emblems or wording that implies approval by an upstream data provider.

• Only fetch public HTTP(S) URLs that you own or are authorized to audit. Loopback, private, link-local, metadata, reserved, and DNS-resolved private targets are rejected, as are non-HTML responses, excessive redirects, and oversized responses.

See Also

The three report paths in Run the next report are the complete Site QA/RAG handoff for this actor. Use one of those paths instead of adding more raw extraction volume.

💾 Save it for later: click the bookmark icon at the top of the Apify Store page if you'd like to come back to it. Bookmarks help other engineers find this actor via Apify's discovery surfaces.

Feedback

Use the Apify Store rating and issue controls on the actor page for feedback. The three report paths above remain the only cross-actor workflow links.