Publish reviewed articles to WordPress

Prerender Buddy can deliver a reviewed full article to WordPress as a post. The connection sends the article title, body, excerpt and slug. You can send a CMS draft for further editing or explicitly confirm publication through PB.

This connects article generation to WordPress publishing. It does not install a WordPress plugin, edit your theme or repair arbitrary website pages.

Use the public HTTPS root of the WordPress installation, such as https://example.com, rather than a wp-admin URL. Its REST API must be reachable by PB.

Create a dedicated application password for a WordPress user allowed to create posts. Publishing also requires that user's permission to publish posts. Use an application password rather than the password used to sign in to WordPress.

WordPress describes how these revocable credentials work in its application-password guide. If your host or security configuration disables them, resolve that requirement before connecting.

1. Open your website in PB Sites, then open Publishing.
2. Select WordPress.
3. Enter the WordPress site URL, username and dedicated application password.
4. Choose Save destination, then use Check connection to verify access.

Keep the password in the authenticated setup form. Do not put it in article text, browser code or a support screenshot. Saving another publishing platform replaces this website's current destination; review the change before saving.

Generate or open an article in PB, review its factual claims and links, and approve the version you want to deliver. Then choose a CMS draft or explicitly confirm publication.

A WordPress draft remains unpublished and can be reviewed in WordPress. Confirmed publication creates or updates the post through the connection. Generating an article and assigning an editorial calendar date do not publish it.

For a later release, use PB's separately confirmed publication schedule as described in the content calendar guide.

A draft delivery cannot overwrite or unpublish a WordPress post that is already live. To update that post through PB, review the changed article, approve it again and explicitly confirm publication.

Inspect the existing post before retrying a delivery whose outcome is uncertain. A timeout does not establish that WordPress saved nothing.

If connection validation succeeds but delivery fails, inspect the delivery message and the WordPress user's post permissions. Successful authentication does not establish permission for every write.

If WordPress reports publication but the public page shows old content, check the post itself and the relevant host, plugin or delivery cache. Verify the final response before treating a PB status label as proof that visitors see the new version.

Disconnecting PB removes the connection; it does not delete posts already delivered. Revoke the dedicated application password in WordPress when you no longer want it used.