Publish finished posts straight into your own WordPress site. They arrive as native blocks, images land in your media library, and categories, tags and byline are mapped to what already exists on the site.
No plugin to install. Bloggable uses WordPress's own REST API and an application password, both core features since WordPress 5.6.
Before you start
This is for self-hosted WordPress. Application passwords and REST API writes aren't available on wordpress.com's lower plans, so a wordpress.com site generally can't be connected this way.
You need:
- WordPress 5.6 or later
- The site served over HTTPS — we won't send credentials over plain HTTP
- An account on the site with permission to publish (Editor or Administrator)
Step 1 — check the site
In Bloggable: Blog settings → General → Site address → Your own platform → WordPress.
Enter the site's main address — acme.com, not acme.com/blog — and press Check site.
This step exists so you find out about a blocker now rather than after a round trip through wp-admin. Bloggable looks at the site unauthenticated and names anything in the way:
| What you might see | What to do |
|---|---|
| The WordPress REST API is blocked | A security plugin or your host is blocking /wp-json. In Wordfence: Firewall → Blocking. Some hosts also have a switch in their control panel. |
| Application passwords are turned off | Wordfence disables these by default. Go to Wordfence → Login Security → Settings and untick Disable WordPress application passwords. Other security plugins have the same setting under a different name. |
| Your host is removing the login header | Some shared hosts strip the Authorization header before WordPress sees it. Add this at the top of .htaccess:SetEnvIf Authorization "(.*)" HTTP_AUTHORIZATION=$1 |
| That site is not using HTTPS | Add an SSL certificate — most hosts provide one free — then try again. |
| That doesn't look like a WordPress site | Usually a subpath. Enter the site's main address instead. |
Step 2 — create an application password
Once the check passes, Bloggable sends you to the right page in your own WordPress.
- In WordPress: Users → Profile, and scroll to Application Passwords.
- Type a name — "Bloggable" — and click Add New Application Password.
- WordPress shows the password once. Copy it.
Paste it exactly as WordPress showed it, spaces and all. Application passwords are generated with spaces in them and they are part of the password. Stripping them is the most common cause of "those credentials were rejected".
Step 3 — paste it into Bloggable
Enter the WordPress username (the one you log in with, not the display name) and the application password. Bloggable checks the account can actually publish before saving anything, and the credential is encrypted before it is stored.
Step 4 — map it, then arm it
- Category, tags and author — choose what published posts should use. Bloggable reads the real lists from your site, so you pick from what exists rather than typing names and hoping.
- Keep the Bloggable address live — off by default, so your Bloggable addresses redirect to your WordPress site.
- Publish new posts automatically — off by default. Leave it off until you've watched a post land correctly.
What arrives in WordPress
Native blocks, not a lump of HTML. Headings, lists, quotes, images, buttons and callouts arrive as blocks the editor understands, so the post is editable in WordPress like anything else.
Images in your own media library. Every image is uploaded into your library and the featured image is set. Nothing on your published post hotlinks back to Bloggable.
Meta description, when Yoast or Rank Math is installed to receive it.
Embeds travel as links. A YouTube or Spotify embed becomes an anchor rather than an iframe, because WordPress strips iframes from authors without the unfiltered_html capability — a link that works beats markup that gets silently removed.
Editing, unpublishing, disconnecting
Edit in Bloggable and the change is pushed across. Unpublish and the WordPress post is set back to draft — never deleted. Disconnect and your posts stay live on your site, untouched; reconnecting later resumes by remote id rather than duplicating everything.
Troubleshooting
"Those credentials were rejected." Check the username is the login name, and that you pasted the application password with its spaces.
It worked, then stopped. The application password was revoked in WordPress, or the user's role changed. Create a new one and reconnect — the row will say Reconnect needed.
A post failed with "the post was too large". Some shared hosts cap request size. Splitting a very long post, or reducing very large inline images, usually clears it.
Everything is failing at once after a host migration. Re-run Check site — the address, HTTPS certificate or REST availability may have changed.
Still stuck? Get in touch with the site address and the error shown on the connection row.