Generate a Wix API key with blog access, paste it with your Site ID, and articles publish to your Wix blog as native posts.
Wix blog posts are not HTML documents — they are Ricos rich-content trees. Hoxigen converts each article through Wix's own conversion API rather than guessing at the format, so headings, lists, links and quotes arrive as real Wix blocks that you can keep editing in the Wix editor afterwards.
The featured image is imported into your Wix Media Manager first and waited on until Wix reports it ready, then attached as the post's hero image. An image that never finishes importing costs you the image, not the article.
The post is created as a draft and then published in one pass, so a half-written post never appears on your site. Sites that require posts to be attributed to a member get a member resolved automatically, and are told plainly if the key lacks the permission to do so.
The same steps the connect screen walks you through, so you can see the whole of it before you sign up for anything.
In Wix, open your account menu, choose API Keys, and click Generate API Key.
Name the key Hoxigen and select the site you want articles published to.
Under Blog check Manage Blog; under Media Manager check Manage Media Manager. Confirm the verification code if Wix asks for one.
Wix shows the key exactly once. Copy it before you close the dialog.
The long UUID in your dashboard address after /dashboard/, also shown under Settings. Paste both into Hoxigen and verify.
Field by field, so nothing arrives as a surprise.
Created as a draft and published in the same pass, under the article's slug as its SEO slug.
The article body is converted into Wix's Ricos format block by block, so the post stays editable in the Wix editor.
The article's meta description becomes the post excerpt.
Imported into your Media Manager and attached. A refresh with no new image leaves the hero image already on the post alone.
Yes — the live post is updated and republished, keeping its URL.
Hoxigen finds the post by the slug in the URL, checks the post it found really is the one at that address, and compares its current text against what the refresh was drafted from.
An edit made in the Wix editor since then shows up as a mismatch and the refresh is refused as a conflict. Otherwise the post is patched and republished in place.
Of the four CMS connectors, refresh on Wix is the one we have proved hardest in tests and least in the wild — a fair reason to watch the first one land before you leave it unattended.
Refreshing an article rather than writing a new one is how a page that used to rank keeps ranking. It is rolling out to accounts gradually; publishing new articles is not gated on it.
You would find these out in week two anyway. Here they are in week zero.
This connector carries a Beta pill in the product. It publishes and refreshes articles today, and it is covered by an automated test suite against the platform's API — but it has run on fewer live sites than our webhook pipeline has, and we would rather you knew that before you connected your only blog to it.
Manage Blog alone is not enough: the conversion to rich content and the image import each need their own permission, and a site that attributes posts to members needs Read Members too. Verification names whichever one is missing.
Wix issues API keys at the account level and scopes them to sites you select. If that is broader than you want a marketing tool to hold, this is the connector to weigh carefully.
No Wix Stores product pages, no site pages, no galleries.
Everything on this page describes what the connector does today. Found something that does not match what you see in the product? hello@hoxigen.app — we will correct the page.
Drafts land in your queue with their images, meta description, FAQ schema and internal links. You can edit, approve or reject each one. Ignore the queue and it publishes on schedule anyway — that is the point of an autopilot.
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 its credentials against the real API — a signed test request, a token exchange, a collection read — before Hoxigen saves anything. A connector that cannot publish says so on the day you connect it, not on the day you expected an article.
Connectors are probed on their own schedule. An expired token, a revoked scope or a key that no longer does what publishing needs flips the connector to Reconnect and tells the seats that asked for alerts.
Our own plugin turns your site into a signed receiver. Articles arrive as posts and refresh at the same permalink.
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.
Publishes live CMS items into the blog collection you choose, mapping your existing fields instead of demanding new ones.
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.
Connect Wix when you like what you read — nothing publishes before that.