WordPress Posts Scraper

Fetch public WordPress REST posts and normalize titles, excerpts, authors, publication dates, status, links, slugs, and rendered text.

Content extractionv0.1.0~1 credit/runSource on GitHub

Workspace

Configure

Inputs stay here while results become exportable artifacts.

Start from an example

Results

Preview, inspect, copy, or export the complete output.

Your result will become an artifact

Run the tool to inspect structured rows, raw JSON, execution details, and downloadable JSON, CSV, and Markdown files.

countpostssource_url

Overview

Fetch public WordPress REST posts and normalize titles, excerpts, authors, publication dates, status, links, slugs, and rendered text. This first-party Better Fetch tool turns a focused request into predictable structured output that can be inspected in the web workspace, exported as JSON or CSV, called through REST, or composed by an AI agent over MCP. It is designed for repeatable production research rather than fragile copy-and-paste scraping.

Last validated: Jul 13, 2026

Input

limitintegerdefault: 10

Maximum posts to return.

searchstring

Optional WordPress post search text.

site_urlstring (uri)required

WordPress site base URL.

Output

countintegerrequired

Number of records returned

postsobject[]required

Normalized posts records

source_urlstringrequired

Fetched source URL

Examples

first-run

{
  "limit": 3,
  "site_url": "https://wordpress.org/news"
}

Use cases

Agent research

Give AI agents bounded, normalized wordpress posts scraper results without writing source-specific retrieval and parsing code.

Repeatable monitoring

Save the configuration, rerun it on a consistent source, and export comparable structured artifacts for operational review.

FAQ

What does WordPress Posts Scraper return?

It returns normalized structured fields documented in the output schema, plus the fetched source URL and a record count for receipts and exports.

Does this tool store the retrieved output?

No. Better Fetch records privacy-safe run metadata for reliability and retention analysis, but the output payload itself is not stored by the workspace.

Use it anywhere

MCP (Claude, ChatGPT, Codex)

# After connecting https://betterfetch.co/api/mcp, ask your AI to:
1. Call search_tools for "WordPress Posts Scraper"
2. Call run_tool with:
   name: "wordpress_posts_scraper"
   input: {"limit":3,"site_url":"https://wordpress.org/news"}

REST

curl -sS -X POST "https://betterfetch.co/api/tools/wordpress_posts_scraper/run" \
  -H "Authorization: Bearer bf_your_key_here" \
  -H "Content-Type: application/json" \
  -d '{"input": {"limit":3,"site_url":"https://wordpress.org/news"}}'

Run locally

git clone https://github.com/better-fetch/tools/tree/main/tools/wordpress-posts-scraper && cd wordpress-posts-scraper && npm i
BETTER_FETCH_API_KEY=bf_your_key_here npx bf-tool run --input '{"limit":3,"site_url":"https://wordpress.org/news"}'