Contextractor Apify Actor

Contextractor is distributed as an Apify Actor for extracting content from multiple URLs, crawling entire websites, and running on a schedule. Results are stored in Apify datasets and key-value stores, accessible via API.

Quick start

Open the Actor page on Apify, add your start URLs, and click Start.

From the command line:

apify call glueo/contextractor \
  --input='{"startUrls": [{"url": "https://example.com"}]}'

Or via the Apify API:

curl -X POST "https://api.apify.com/v2/acts/glueo~contextractor/runs" \
  -H "Authorization: Bearer YOUR_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"startUrls": [{"url": "https://example.com"}]}'

Input reference

In the tables below, a blank Default means the parameter has no default — when omitted, the Actor derives the value at run time.

Crawl settings

Crawl filtering

Content extraction

Output destinations

Browser settings

Proxy

Cookies & headers

Output

Each crawled page becomes one dataset record with status: 'success'. Failed requests are stored as status: 'failed' records (with errors, retryCount, and crawledTime) after retries are exhausted; skipped URLs can be recorded as status: 'skipped' records (with a skipReason) when storeSkippedUrls is enabled.

A *-kvs token (default) writes the content as a blob to the key-value store and the dataset record references it by key and url; a *-dataset token inlines the content in the record under content. Every content node always carries an MD5 hash and a bytes length.

{
  "url": "https://example.com/article",
  "status": "success",
  "metadata": {
    "title": "Article Title",
    "author": "Author Name",
    "publishedAt": "2026-01-15",
    "description": "Article description",
    "siteName": "Example",
    "languageCode": "en"
  },
  "crawl": {
    "loadedUrl": "https://example.com/article",
    "loadedTime": "2026-04-11T12:00:00.000Z",
    "httpStatusCode": 200,
    "depth": 1,
    "referrerUrl": "https://example.com/"
  },
  "original": {
    "hash": "f8e6bd335e04d03e1be6798c2c72349c",
    "bytes": 89898
  },
  "markdown": {
    "hash": "c485356090a92c6a45e8c1155c14d8ee",
    "bytes": 4523,
    "key": "markdown-141fbc787408697a5d22735982be532a.md",
    "url": "https://api.apify.com/v2/key-value-stores/<storeId>/records/<key>"
  }
}

Each format saved via a save token produces its own field on the record (txt, markdown, json, html). The original node (raw page HTML before extraction) is always present with hash and bytes; its content is included only when an original-* token is in save.

Example

Crawl all blog posts from a site with glob filtering:

{
  "startUrls": [{"url": "https://example.com/blog"}],
  "globs": [{"glob": "https://example.com/blog/**"}],
  "exclude": [{"glob": "https://example.com/blog/archive/**"}],
  "maxRequestsPerCrawl": 100,
  "maxCrawlDepth": 2,
  "save": ["markdown-kvs", "json-kvs"],
  "mode": "precision",
  "deduplication": "aggressive",
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}

Where to go next

• Help hub — the index of every Contextractor help page.
• Playground — enter a URL and preview extraction results in your browser.
• npm CLI — the command-line tool, flag reference, and JSON config.
• npm library — embed extraction in your own Node.js application.
• PyPI package — extract from Python with the contextractor PyPI wrapper.

Updated: July 5, 2026