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:

{
  "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:

{
  "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. 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.