# WordPress Content Audit (`conserving_mastodon/wp-content-audit`) Actor

Inventory and score any WordPress site: word counts, thin-content flags, missing excerpts, staleness. Reads only the public REST API. Outcome-based: no charge unless the audit completes.

- **URL**: https://apify.com/conserving\_mastodon/wp-content-audit.md
- **Developed by:** [Chris Arsenault](https://apify.com/conserving_mastodon) (community)
- **Categories:** SEO tools, Automation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$250.00 / 1,000 completed audits

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 Audit

**A structured content inventory of any WordPress site, as a single tool call.** Point it at a URL and get the audit an SEO consultant would start with: every post and page scored for length, thinness, missing metadata, and staleness, plus a summary that tells you in one row whether the site has a content problem.

### Why this exists

Thin content does not rank. Most WordPress sites accumulate it silently: stub posts, empty pages, placeholder excerpts. Finding it by hand means clicking through the whole site. This Actor reads the site's own public REST API and inventories everything in seconds, with no crawling, no credentials, and no guesswork.

We built it for ourselves first. Running exactly this audit across our own ten-site portfolio surfaced 447 thin posts, which we then rewrote. The tool that found them is what you are looking at.

### What you get

One **summary row**:

```json
{
  "ok": true,
  "site": "https://example.com",
  "items_scanned": 109,
  "posts": 46,
  "pages": 63,
  "thin_count": 54,
  "thin_pct": 49.5,
  "avg_word_count": 754,
  "missing_excerpt_count": 5,
  "thinnest": [ { "url": "...", "title": "...", "word_count": 12 } ]
}
```

Plus **one row per post and page**:

```json
{
  "type": "posts",
  "id": 123,
  "url": "https://example.com/some-post/",
  "title": "Some Post",
  "word_count": 287,
  "thin": true,
  "missing_excerpt": true,
  "modified": "2026-04-13T09:46:41",
  "internal_links": 3
}
```

Posts under 400 words are flagged thin. The summary includes the ten thinnest URLs so the rewrite queue is ready the moment the run finishes.

### Input

| Field | Type | Description |
|---|---|---|
| `url` | string | Root URL of the WordPress site (with or without `https://`) |
| `maxItemsPerType` | integer | Cap on posts and pages scanned, each. Default 200, max 1000 |

### How it works

The Actor calls the site's public WordPress REST API (`/wp-json/wp/v2/`), the same interface the site's own admin uses. It sends a handful of polite paginated requests and computes everything else locally. No scraping tricks, no rate-limit games, no credentials, nothing written to the target site.

If the target is not a WordPress site, or hides its REST API, the run reports that cleanly and **you are not charged**. Billing is outcome-based: you pay only when a full audit completes.

### Use cases

- **Agents qualifying SEO or content leads**: the thin-content percentage is a ready-made outreach talking point, produced before you ever speak to the prospect.
- **Agencies prioritizing rewrite queues** across client portfolios: run it on every site, sort by `thin_pct`, start where it hurts.
- **Monitoring your own properties**: schedule it and watch `thin_count` go down as your content program does its job.
- **Due diligence on site acquisitions**: know how much of the content you are buying is real.

### Works with AI agents

The Actor returns clean structured JSON, which makes it a natural tool call for AI agents via the [Apify MCP server](https://docs.apify.com/platform/integrations/mcp). An agent can audit a site, read the summary, and decide what to do next in one loop.

### Limits and honesty

- Only works on WordPress sites with the standard public REST API enabled (the large majority).
- Reads public content only: password-protected and draft content is invisible to it, by design.
- Word counts are computed from rendered HTML with tags stripped; they are accurate to within a few words, not to the character.

Built and used daily by 1450 Enterprises.

# Actor input Schema

## `url` (type: `string`):

Root URL of the WordPress site to audit (e.g. https://example.com).

## `maxItemsPerType` (type: `integer`):

Cap on posts and pages scanned (each). Default 200.

## Actor input object example

```json
{
  "url": "https://launchsmarter.1450enterprises.com",
  "maxItemsPerType": 200
}
```

# Actor output Schema

## `results` (type: `string`):

Dataset items: the first row is the site summary (items scanned, thin count and percentage, average word count, ten thinnest URLs); subsequent rows score each post and page (word\_count, thin, missing\_excerpt, modified, internal\_links).

# 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 = {
    "url": "https://launchsmarter.1450enterprises.com"
};

// Run the Actor and wait for it to finish
const run = await client.actor("conserving_mastodon/wp-content-audit").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 = { "url": "https://launchsmarter.1450enterprises.com" }

# Run the Actor and wait for it to finish
run = client.actor("conserving_mastodon/wp-content-audit").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 '{
  "url": "https://launchsmarter.1450enterprises.com"
}' |
apify call conserving_mastodon/wp-content-audit --silent --output-dataset

```

## MCP server setup

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

```

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/TKd7V8UVRYlx9xAFP/builds/dvVSAIgFhcFESFzMf/openapi.json