Install the Hoxigen plugin, paste the token it shows you, and articles publish to your WordPress site as posts — with their featured image, tags, byline and schema.
The plugin registers one REST route on your site, at /wp-json/hoxigen/v1/webhook, and nothing else is exposed. Hoxigen signs every request with the token the plugin generated, and the plugin checks that signature against the raw request body before it reads a single field. An unsigned or mis-signed request is rejected with a 401 and no post is touched.
An arriving article becomes a WordPress post through the normal post APIs, so your theme, your permalink structure, your categories page and your RSS feed all treat it as a post you wrote. The plugin stamps each post with the Hoxigen article id and a content revision, which is how a later refresh finds the same post again instead of publishing a second copy of it.
Because the plugin speaks the full Version 2 webhook contract, WordPress is the one destination where you get refresh-in-place without writing any code yourself.
The same steps the connect screen walks you through, so you can see the whole of it before you sign up for anything.
The Connectors page in Hoxigen serves hoxigen-wordpress.zip. It is our plugin, not a marketplace listing.
In WordPress admin: Plugins, Add New, Upload Plugin, choose the zip, Install Now, then Activate.
Open Hoxigen in the WordPress sidebar. The page shows the receiver URL and a token that starts with hoxigen_whsec_.
Back in Hoxigen, enter your site's address and the token, then Verify. Hoxigen derives the receiver URL from the address and proves it with a signed test before storing anything.
Field by field, so nothing arrives as a surprise.
Title, slug, and the article body as HTML, published through WordPress's own post APIs.
Sideloaded into your media library once per image URL, then attached to the post. If a refresh brings no new image, the one already on the post is left alone.
The meta description becomes the excerpt, article tags become post tags, and the byline resolves to a WordPress author where one matches.
Article and Organization schema is rendered in the page head by the plugin, keeping any FAQ block the article generated.
Off unless you switch it on. When on, published articles carry a small tracking markup so Hoxigen can estimate views. Counts are estimates, and existing articles need republishing to gain one.
Yes — the same post, the same permalink.
A refresh starts with a signed lookup: Hoxigen asks the plugin for the article living at a given URL and gets back its id, title, body and current revision. The refreshed draft is then sent as an update that names the post it is replacing and the exact revision it was drafted against.
If somebody edited that post in WordPress in the meantime, the revision no longer matches — the plugin stamps a new revision on every post_updated — and the update is refused with a 409 rather than silently overwriting the human edit. Hoxigen surfaces that as a conflict and asks you to review a fresh refresh.
Retries are safe by construction: replaying the same update is recognised and acknowledged instead of applied twice, and a late first-publish delivery will not roll back an article that has since been refreshed.
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.
The plugin is installed by zip upload, which WordPress.com's lower tiers do not allow. Your site's REST API has to be reachable from the internet — a firewalled staging site cannot receive a webhook.
The token is the signing secret. Regenerate it in WordPress and Hoxigen's deliveries start failing until you paste the new one back in.
Articles are posts. There is no mapping to custom post types, and no control over categories from Hoxigen's side.
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.
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 to your Wix blog with an API key you generate, converting each article into Wix's own rich content format.
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 WordPress when you like what you read — nothing publishes before that.