# WordPress Content Scraper (`bindler/wordpress-content-scraper`) Actor

Scrape posts, pages and content from any WordPress site via the REST API. Clean plain text with authors, categories and tags, ready for LLM training and RAG.

- **URL**: https://apify.com/bindler/wordpress-content-scraper.md
- **Developed by:** [Neil Sangwaiya](https://apify.com/bindler) (community)
- **Categories:** AI, Developer tools, News
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $3.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

## WordPress Content Scraper

Extract posts and pages from **any WordPress site** as clean plain text, with authors, categories, tags and dates. Built for LLM training data, RAG corpora, content migration and competitive research.

WordPress runs a large share of the web, and almost all of it exposes a public REST API. This Actor uses it directly. No HTML parsing, no broken selectors when a theme changes, no login. Paste a URL and go.

### What you get

| Field | Description |
|---|---|
| `id` | WordPress post ID |
| `title` | Plain-text title |
| `url` | Canonical link |
| `slug` | URL slug |
| `publishedAt` / `modifiedAt` | UTC timestamps |
| `author` | Resolved author name |
| `excerpt` | Plain-text excerpt |
| `content` | **Full article body as clean plain text** |
| `wordCount` | Words in the body |
| `categories` / `tags` | Taxonomy names, not IDs |
| `featuredImage` | Image URL |
| `commentCount` | Comments, where exposed |
| `site` | Source site |
| `scrapedAt` | ISO timestamp |

### Why the output is different

**Plain text, not HTML.** Most WordPress scrapers hand back `content.rendered`, which is raw HTML full of blocks, shortcodes and inline styles. Feeding that to a model wastes tokens on markup. This one strips it properly, including entity decoding, so records drop straight into a vector store.

**Authors actually resolve.** Sites handle authorship in different ways: some embed it, some expose Yoast metadata, some use Co-Authors Plus, some block the `/users` endpoint entirely. This Actor tries all four, so you get a name where other scrapers return `null`.

**Category and tag names, not IDs.** A number like `17` is useless without a second lookup. This returns `["Education"]`.

### Filters

- **Content type** — posts or pages
- **Search query** — only matching content
- **Category slug** — one category, resolved to its ID for you
- **Published after** — a date cutoff for incremental runs
- **Max items** — caps the run so cost is predictable

### Example input

```json
{
  "siteUrl": "https://techcrunch.com",
  "contentType": "posts",
  "dateFrom": "2026-01-01",
  "maxItems": 500
}
```

### Notes

- Uses only the public, unauthenticated WordPress REST API. No login, no private content.
- Retries with backoff on rate limits and reports clearly when a site has the REST API disabled.
- Pages are kept small deliberately, because embedded author and media data makes large pages time out on big sites.
- Works on self-hosted WordPress and on WordPress.com sites that expose the REST API.

# Actor input Schema

## `siteUrl` (type: `string`):

Any WordPress site, e.g. https://techcrunch.com. Works on self-hosted and WordPress.com sites with the REST API enabled.

## `contentType` (type: `string`):

Which WordPress collection to pull.

## `searchQuery` (type: `string`):

Optional. Only return content matching this term.

## `categorySlug` (type: `string`):

Optional. Filter to one category, e.g. 'news'.

## `dateFrom` (type: `string`):

Optional. Only content published after this date, e.g. 2026-01-01.

## `maxItems` (type: `integer`):

Stop after this many. Controls your cost.

## `includeAuthors` (type: `boolean`):

Look up author names where the site does not embed them.

## Actor input object example

```json
{
  "siteUrl": "https://wordpress.org/news",
  "contentType": "posts",
  "maxItems": 100,
  "includeAuthors": true
}
```

# Actor output Schema

## `items` (type: `string`):

One record per post or page, with full plain-text content, author, categories and tags.

# 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 = {
    "siteUrl": "https://wordpress.org/news"
};

// Run the Actor and wait for it to finish
const run = await client.actor("bindler/wordpress-content-scraper").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 = { "siteUrl": "https://wordpress.org/news" }

# Run the Actor and wait for it to finish
run = client.actor("bindler/wordpress-content-scraper").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 '{
  "siteUrl": "https://wordpress.org/news"
}' |
apify call bindler/wordpress-content-scraper --silent --output-dataset

```

## MCP server setup

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

```

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/0YOaE3OYIS2TXHkHS/builds/kYOOQ1of1TtRcvpu8/openapi.json