Personal demonstration · fictional article · no WordPress connection
Check the draft before it reaches WordPress.
Turn structured article data into a reviewable WordPress REST API payload. Inspect the title, HTML and category/tag IDs, then download the JSON. Every output is a draft.
This is the field-mapping step of a possible content workflow. It does not generate an article, call Make or WordPress, or publish anything.
1. Article input
Use fictional data. IDs 12, 31 and 32 are examples; they are not checked against any site. An empty ID array is allowed. The demo limits titles to 300 characters and content to 100,000.
2. Payload for review
The download is a file, not a WordPress post. Editing the input clears the prepared result until you prepare it again.
What the checks cover
- Required non-empty title and content; positive integer taxonomy IDs; unknown fields rejected.
- Repeated IDs are deduplicated. A supplied status such as publish is replaced by draft.
- HTML is shown as text, never executed in this page. It is preserved in the export, not sanitized.
For a real integration, verify the site's taxonomy IDs, permissions, supported HTML and SEO plugin fields. This demo does not prove API acceptance, layout in a theme, duplicate prevention, keyword generation or SEO results.
The field names and draft status follow the official WordPress Posts REST API reference (checked 17 September 2026). The intended endpoint is POST /wp/v2/posts; this page never calls it.
Reproduce the checks
Download the source package and run node --test test.cjs using Node.js 18 or newer. No dependencies, credentials or network access are needed.