WordPress

WordPress is a publish integration, not an SDK read. Where the framework SDKs pull articles out of the keyless feed, the WordPress connection lets Ghost Writr push published articles into your WordPress site over its REST API. You connect once in the dashboard and approve an Application Password — there’s nothing to install.

This is a push, not a feed read

The @ghostwritr/next / @ghostwritr/astro / @ghostwritr/react-router SDKs read your articles from the static feed. WordPress is the opposite direction: Ghost Writr writes posts into your WordPress. Use the SDKs for a headless blog; use this integration to publish into an existing WordPress site.

Connecting — Application Passwords (no plugin)

The connect flow rides WordPress core’s built-in Application Passwords (core since 5.6), so it works on a stock self-hosted (.org) site with no plugin and no credential you copy by hand.

1. Enter your site URL on the integrations screen in the Ghost Writr dashboard.

2. Authorize the application. Ghost Writr discovers your site’s authorize endpoint and sends you to your own wp-admin “authorize application” page (named Ghost Writr).

3. Approve. WordPress generates an Application Password — distinct from your login password and independently revocable from your own wp-admin — and redirects back to Ghost Writr.

4. Credentials are sealed. Ghost Writr confirms the connecting user can both publish and edit posts, then seals the password (encrypted at rest) and records the integration. You’re connected.

Requirements are the WordPress defaults: HTTPS and Application Passwords enabled (both on by default in core). You can disconnect at any time — Ghost Writr revokes the Application Password on its end, and you can also delete it directly in your wp-admin.

What gets published

When Ghost Writr publishes a post, it posts through the WordPress REST API and sets the title, body (rendered from Markdown to HTML), excerpt, slug, status, categories and tags, schedule, and the featured image. Publishing modes mirror the rest of Ghost Writr:

• Create draft — stage the post in WordPress for you to review.
• Publish after approval — goes live once you approve.
• Autopilot — carries the change all the way live.

Ghost Writr can also improve your existing WordPress posts in place — it reads your posts in as a knowledge source, then updates a post’s title and body over core REST, gated so it never ships a worse edit and (by default) only with your approval.

SEO meta — optional companion plugin

WordPress core’s REST API does not expose the SEO-plugin fields (Yoast / RankMath SEO title and description), so the no-plugin connect flow publishes the post itself and leaves the search snippet to your site’s own SEO plugin. A small optional companion plugin closes that gap: installed on your site, it writes the correct Yoast/RankMath meta in-process regardless of which SEO plugin you run. It’s an enhancement, not a requirement — the connect flow publishes fine without it.

When you need it

Add the companion plugin only if you want Ghost Writr to manage your search title and meta description inside WordPress. Without it, everything else publishes normally and your SEO plugin keeps owning the meta.

What to reach for next

• Headless instead? If you’d rather render articles in your own app, start with the SDK overview.
• The article shape — what a published article carries. See The article shape.