Integrations
Where the finished article goes
An autopilot that stops at the draft is a writing tool with extra steps. These are the destinations we publish to, and what each one constrains.
Publishing is where the differences between destinations stop being cosmetic. Some platforms let you control head markup; some do not. Some already emit their own Article schema and will happily emit a second, conflicting one. Some need a collection schema to exist before anything can be written to it at all.
Every page below documents the connection steps, exactly which article fields map onto which platform fields, how the JSON-LD travels, and a limitations section listing what the platform makes harder. That last section is the one worth reading before you commit a content program rather than after.
- WordPress
CMS
Publishes to self-hosted WordPress over the core REST API using an application password, with taxonomy terms, a media-library featured image and JSON-LD attached to every post.
- Webflow
Visual CMS
Writes finished articles into a Webflow CMS Collection, mapped field by field, with a separate publish step and a plan for where the JSON-LD lives.
- Shopify
Ecommerce platform
Publishes articles into a Shopify blog through a custom app, with tags, a featured image and structured data, plus a straight account of what a store blog can and cannot do.
- Ghost
Publishing platform
Publishes through the Ghost Admin API using a custom integration key, filling the post fields Ghost already has — including per-post code injection for structured data.
- Wix
Site builder
Publishes into the Wix blog through an authorized app, with a candid account of where the platform's control over head markup limits what any external tool can do.
- Blogger
Blog platform
Google's own blogging platform. Free hosting, an OAuth-based API, and a template that owns more of the page than most CMSs do.
- Notion
Workspace
No first-party connector. Articles reach Notion through the webhook or Zapier path, which makes Notion an excellent staging surface and a questionable public blog.
- Webhooks
Custom destination
A signed publish event delivered to an endpoint you own, carrying the article, its metadata and the generated JSON-LD graphs. Everything after that is your code.
- Zapier
Automation
Route published articles to destinations without a native connector. No code, wide reach, and a hop in the middle that can fail without telling you.
Not listed?
Anything with an API can take a webhook.
The webhook destination carries the full payload — body, meta, author entity and every JSON-LD graph — so a custom front-end or an unsupported CMS is a receiver away from being supported.
3
Free articles on signup
- No credit card
- Published to your own site
- JSON-LD and a named author
- Cancel anytime