# Website Content Extractor — Docs & Pages to Markdown (`taroyamada/website-content-extractor`) Actor

Website content extractor for docs/pricing/help → markdown. Paste URL and Start. RAG-ready.

- **URL**: https://apify.com/taroyamada/website-content-extractor.md
- **Developed by:** [naoki anzai](https://apify.com/taroyamada) (community)
- **Categories:** AI, Developer tools
- **Stats:** 29 total users, 1 monthly users, 100.0% runs succeeded, 1 bookmarks
- **User rating**: No ratings yet

## Pricing

from $9.00 / 1,000 results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Website Content Extractor

### Run the next report

Turn extracted public pages into capped Site QA report/export runs:

- [Run a content QA report](https://apify.com/taroyamada/site-qa-content-report-scraper) for title, metadata, thin-content, and page-quality issues.
- [Run an indexability and AI crawler report](https://apify.com/taroyamada/site-qa-indexability-ai-crawler-report-scraper) for robots, sitemap, canonical, noindex, schema, and crawler-access findings.
- [Run a website RAG readiness report](https://apify.com/taroyamada/website-rag-readiness-audit) for retrieval structure, coverage, and source-linked readiness findings.

These follow-on actors use user-supplied public URLs only. They do not provide ranking guarantees, legal advice, or automated messaging workflows.

AI builders, content ops, SEO teams, and documentation teams provide public pages 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 findings instead of treating raw markdown as the final deliverable.
The report actors below produce the buyer-facing artifact; this actor remains the bounded extraction step.

### Low-cost source extraction

Run this actor with its supported extraction input, then pass the same URLs to one of the linked report actors:

```json
{
  "urls": [
    "https://example.com/docs",
    "https://example.com/pricing"
  ],
  "outputFormat": "markdown",
  "includeMetadata": true,
  "delivery": "dataset",
  "maxChargeUsd": 1,
  "dryRun": false
}
```

This actor returns bounded source rows. The linked report actor accepts its own report/export controls and produces the buyer-facing result. Do not add report-only fields to this extractor input.

### Store Quickstart

#### Low-cost extractor input

```json
{
  "urls": [
    "https://example.com/docs"
  ],
  "outputFormat": "markdown",
  "delivery": "dataset",
  "dryRun": false
}
```

#### 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.

Recommended first run:

```json
{
  "urls": [
    "https://example.com/docs"
  ],
  "outputFormat": "markdown",
  "delivery": "dataset",
  "dryRun": false
}
```

#### High-value Site QA/RAG report

Use this separate input with the selected Site QA/RAG actor above, not with the extractor:

```json
{
  "urls": [
    "https://example.com/docs"
  ],
  "generateReport": true,
  "emitExport": true,
  "authorizedUseConfirmed": true,
  "emitUnchanged": false,
  "dryRun": false
}
```

See [`docs/value-path-sample.json`](docs/value-path-sample.json) for the source extraction and downstream report examples.

### Input examples

#### Docs pages

```json
{
  "urls": [
    "https://example.com/docs"
  ],
  "outputFormat": "markdown",
  "delivery": "dataset",
  "dryRun": false
}
```

#### Pricing and product pages

```json
{
  "urls": [
    "https://example.com/pricing",
    "https://example.com/product"
  ],
  "outputFormat": "text",
  "delivery": "dataset",
  "dryRun": false
}
```

#### Webhook handoff

```json
{
  "urls": [
    "https://example.com/help"
  ],
  "outputFormat": "markdown",
  "delivery": "webhook",
  "webhookUrl": "https://example.com/webhook",
  "dryRun": false
}
```

### Value path output preview

Show the report/export result first; the extraction row below is only the source step:

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

### Raw extraction sample

```json
{
  "meta": {
    "actorName": "website-content-extractor",
    "actorTitle": "Website Content Extractor",
    "bundle": "Site QA & Content Intelligence Pack",
    "fetchedAt": "2026-05-06T00:00:00.000Z",
    "totalRows": 1
  },
  "rows": [
    {
      "actorName": "website-content-extractor",
      "rowType": "web_content",
      "url": "https://example.com/docs",
      "title": "Example Docs",
      "markdown": "# Example Docs\nUseful content.",
      "wordCount": 240,
      "sourceUrl": "https://example.com/docs",
      "fetchedAt": "2026-05-06T00:00:00.000Z"
    }
  ],
  "warnings": []
}
```

### Output fields

- `rowType`
- `url`
- `title`
- `markdown`
- `text`
- `wordCount`
- `metadata`
- `sourceUrl`
- `fetchedAt`

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.001 actor start and $0.009 per useful content row. Failed/no-content rows should stay out of the default dataset.

The default dataset is the billable surface for this extraction actor. Dry runs, validation-only runs, missing-key warnings, and unchanged recurring polls should not write payable default-dataset rows. The linked report actors have separate report/export events; do not infer those charges from a raw content row.

### Compliance guardrails

- Fetch public pages supplied by the user.
- Respect site policies, rate limits, and robots guidance where applicable.
- Use output for content operations, QA, and RAG workflows.
- Do not use provider emblems or wording that implies approval by an upstream data provider.

### 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.

# Actor input Schema

## `urls` (type: `array`):

Public broad website pages to clean (max 200). Best for docs, product, pricing, policy, and knowledge-base pages; route article/news/blog URLs to article-content-extractor.

## `outputFormat` (type: `string`):

Choose markdown for the strongest first-run proof and easiest downstream reuse.

## `includeMetadata` (type: `boolean`):

Include page metadata such as description, author, language, and published date when available.

## `concurrency` (type: `integer`):

Number of pages to fetch in parallel.

## `timeoutMs` (type: `integer`):

HTTP timeout per page in milliseconds.

## `delivery` (type: `string`):

Select dataset-only output or webhook handoff. Non-dry-run always writes canonical dataset rows first; webhook delivery runs only after dataset/PPE output succeeds.

## `webhookUrl` (type: `string`):

Webhook destination used when delivery=webhook. The webhook is sent after canonical dataset rows and PPE output succeed, and is skipped on dryRun.

## `dryRun` (type: `boolean`):

Validate the setup and write only local output. When true, dataset writes and webhook delivery are disabled.

## `maxChargeUsd` (type: `number`):

Safety cap for this run. Billable rows beyond this cap are returned as no-charge limit\_reached summaries.

## Actor input object example

```json
{
  "urls": [
    "https://docs.apify.com/platform/actors",
    "https://docs.apify.com/platform/storage/dataset",
    "https://docs.apify.com/platform/storage/key-value-store"
  ],
  "outputFormat": "markdown",
  "includeMetadata": true,
  "concurrency": 5,
  "timeoutMs": 15000,
  "delivery": "dataset",
  "dryRun": false,
  "maxChargeUsd": 1
}
```

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "urls": [
        "https://docs.apify.com/platform/actors",
        "https://docs.apify.com/platform/storage/dataset",
        "https://docs.apify.com/platform/storage/key-value-store"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("taroyamada/website-content-extractor").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "urls": [
        "https://docs.apify.com/platform/actors",
        "https://docs.apify.com/platform/storage/dataset",
        "https://docs.apify.com/platform/storage/key-value-store",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("taroyamada/website-content-extractor").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "urls": [
    "https://docs.apify.com/platform/actors",
    "https://docs.apify.com/platform/storage/dataset",
    "https://docs.apify.com/platform/storage/key-value-store"
  ]
}' |
apify call taroyamada/website-content-extractor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,taroyamada/website-content-extractor"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/2SEQ0bWRQ39RCeI0P/builds/1GBHxxvdINsK4K3gd/openapi.json