It publishes to the site you already have.
Hoxigen writes the article and publishes it to the site or Notion blog you already run. Your CMS stays your CMS, and articles keep their existing URLs when refreshed.
8 ways to get an article out of Hoxigen and onto your domain. 7 of them are a connector you set up once; the remaining option is an endpoint you write and own. Each page below says what the connector needs from you, exactly what lands on the platform, what happens when an article is refreshed months later, and what the connector cannot do.
- WordPress
Our own plugin turns your site into a signed receiver. Articles arrive as posts and refresh at the same permalink.
How it works - Shopify
Publishes to your store's blog through the Admin API, on your own domain, with the product-adjacent content Shopify stores rarely get around to writing.
How it works - Wix
Publishes to your Wix blog with an API key you generate, converting each article into Wix's own rich content format.
How it works - Webflow
Publishes live CMS items into the blog collection you choose, mapping your existing fields instead of demanding new ones.
How it works - Ghost
Publishes articles to your Ghost publication with a custom integration, including cover and inline images, and refreshes the same post.
How it works - Framer
Publishes articles into your Framer CMS collection, uploads cover and inline images, and refreshes the same article.
How it works - Notion
Sign in with Notion and publish formatted articles with covers to your public blog collection.
How it works - Any site, by signed webhook
One signed HTTP POST per article to an endpoint you own. Next.js, Rails, Astro, Django, a static build — if it can receive JSON, it can receive articles.
How it works
What is true of all of them
The destination changes. The way articles get there does not.
Drafts land in your queue with their images, meta description and internal links, plus a short FAQ where readers need one. You can edit, approve or reject each one. Ignore the queue and it publishes on schedule anyway — that is the point of an autopilot. Prefer to sign off first? Set the connector to Approve first.
Connect two blogs and each gets its own article per publishing slot, written for it. Hoxigen does not syndicate one body to several sites and hope search engines pick a winner.
Each connector verifies access against the real API before you save its publishing destination. OAuth sign-in stores the login first; choosing a collection and saving finishes the connection.
A publish that fails keeps the reason on the article and tries again, up to three times. If it still fails, it stops and tells you, so you can reconnect the site and retry it.
What is deliberately not here
Hoxigen also publishes to connected Facebook, Instagram, LinkedIn, TikTok, X, YouTube and Reddit accounts. These are not article destinations: posts, stories and videos have their own setup in the product's Connectors page. Availability depends on the platform and your account.
We do not offer one. Articles published to a domain we own would build an audience and a search history that you could not take with you, and that is the opposite of what this product is for. Every connector on this page publishes to a URL that is yours.
Running something else — Craft, Sanity, Contentful, a static site generator? The signed webhook covers all of them, and it is the path we would pick ourselves. If you would rather have a first-class connector for your platform, tell us which one at hello@hoxigen.app — the queue is ordered by who asks.
Connect one, and stop writing.
Nothing publishes until you connect a channel, and every item waits in your queue first.