Write and plan in Bloggable, publish onto the site you already own. Posts are pushed to WordPress, Ghost or your own endpoint, and your site keeps the canonical URL — so the SEO accrues to your domain, not ours.
This is different from a custom domain. A custom domain points at a blog Bloggable hosts. This publishes into a site you host, which happens to be where the rest of your marketing already lives.
Which one do you need?
- WordPress — self-hosted WordPress, over the REST API with an application password. No plugin.
- Ghost — Ghost Pro or self-hosted, with an Admin API key.
- Webhook — a signed POST to your own endpoint, for anything else: a headless CMS, a static site generator, your own app.
One blog has one destination. That's deliberate — two would mean two canonical URLs for the same article, which is you competing with yourself in search results.
Setting one up
It's per blog, in Blog settings → General → Site address, on the row that reads Your own platform. Not in the Integrations page — connecting involves probing your site and mapping its categories, so it lives next to the blog's other addresses because that is what it becomes.
Integrations → Publishing shows you which blogs are connected, whether pushes are working, and a link straight to that blog's setup.
What happens to your Bloggable address
Once a site is connected you choose between two behaviours with the Keep the Bloggable address live switch:
Off (the default) — your Bloggable addresses redirect to the connected site. There is one copy of each post, at your address.
On — Bloggable keeps serving its own pages, with a canonical tag pointing at your site and the posts excluded from Bloggable's sitemap. Useful if you want a working preview or a fallback. Search engines are told plainly which copy is the original.
Either way the redirect only starts once at least one post has actually reached your site. Connecting is not publishing, and redirecting readers to an empty site would be worse than not connecting at all.
Automatic or manual
Publish new posts automatically is off by default. With it off, a post publishes to Bloggable and waits — you push it when you're ready. With it on, publishing here publishes there.
Start with it off until you've seen a couple of posts land the way you expect.
What we will never do
We never delete from a site we don't own. Unpublishing a post sets it back to draft on your site. That's the whole behaviour — there is no code path in Bloggable that issues a delete against your CMS.
We never touch posts we didn't create. Only posts Bloggable published are ever updated by Bloggable.
Disconnecting doesn't unpublish anything. Detach the connection and your posts stay exactly where they are, live on your site. Reconnecting later picks up where it left off rather than publishing 400 duplicates.
Editing after publishing
Edit in Bloggable and the change is pushed to your site — not on every keystroke, but as a sweep after the edit settles. Editing on the far side is fine too, but the next push from Bloggable will overwrite it, so pick one place to edit and stay there.
When something fails
The connection row shows the state: Connected, Failing, Reconnect needed or Paused. Failures name the actual problem rather than "publish failed" — an expired key, a security plugin blocking the request, a post too large for the remote server.
Retries happen on their own for anything transient. Anything that needs you (a revoked key, a site that moved) says so and stops retrying.
Plan availability
Publishing to your own platform is on the paid tiers rather than every plan — see Plans and billing, or the row in Settings → Add-ons, which shows what your account has today.