WordPress
WordPress
Connect to WordPress to scan posts and pages.
- Category
- Web & UGC
- Source type
- WORDPRESS
- Produces
- postimage
A public site is a published surface — and the things that shouldn’t be on it are usually in a draft, a private page, or a post that was published before anyone reviewed it.
What you need to connect
The site URL. That’s all, if you only want published content — the WordPress REST API serves it publicly.
To reach drafts, pending, future-dated and private posts, add a username and an application password (generated per user in the WordPress admin, and revocable without changing the account password).
What Classifyre reads
Posts and pages, filtered by status: published, draft, pending, scheduled, private. Images referenced by the content are captured as image assets.
Metadata on every asset
Asset kind · post
| Field | Type | Always present | What it is |
|---|---|---|---|
| wp_id | string | Yes | WordPress object id |
| title | string | Yes | Title of the post |
| links_count | integer | Yes | Number of linked or related assets |
| slug | string | No | URL slug |
| status | string | No | Post status |
| post_type | string | No | Post type (post/page) |
| author | string | No | Author id or name |
| tags | string[] | No | Tag ids |
| categories | string[] | No | Category ids |
Asset kind · image
| Field | Type | Always present | What it is |
|---|---|---|---|
| referenced_by | string | Yes | Hash of the referencing post asset |
Lineage
Lineage
This source records no lineage. Nothing in the system it reads describes data moving from one place to another, so no FLOW edges are produced. Related items are still linked — see Lineage & Relationships for what those links mean and how they differ from lineage.
Worth knowing
- Drafts are the interesting part. Published content has usually had a pair of eyes on it; a three-year-old draft has not.
- Multisite installations are scanned one site at a time — add a source per site URL.
Configuration
Beyond the fields below, every source also has the settings shared by all of them: the sampling strategy, the detectors to run, the scan schedule, and the compute limits for its scan jobs.
Required
Without these, the source will not save.
| Field | Type | Required | What it does | Default |
|---|---|---|---|---|
| required | object | Yes | —no extra properties | — |
| url | string | Yes | Base URL of the WordPress site (e.g., https://example.com)format uri | — |
Secrets
Stored encrypted and never shown again after you save them. See Configuration & Fields.
| Field | Type | Required | What it does | Default |
|---|---|---|---|---|
| masked | object | Yes | —no extra properties | — |
| application_password | string | No | WordPress application password for authentication (optional) | — |
| username | string | No | Username for authentication (optional for public content) | — |
Optional
Everything you can tune. Sensible defaults apply when you leave them alone.
| Field | Type | Required | What it does | Default |
|---|---|---|---|---|
| optional | object | No | —no extra properties | — |
| content | object | No | Content scope and filters for WordPress ingestion.no extra properties | — |
| content.fetch_pages | boolean | No | Whether to fetch pages | true |
| content.fetch_posts | boolean | No | Whether to fetch blog posts | true |
| content.post_status | array | No | Post status filters (requires authentication for non-public statuses) | ["publish"] |
| content.post_status[] | enum | No | WordPress post status Allowed: publish, future, draft, pending, private | — |