Publishing Integrations: One-Click to WordPress, Ghost, Shopify & More

What it does

Publishing Integrations let you send content you generate in humanaizer straight to your live site with a single click, without leaving the dashboard. Instead of copying and pasting, you push content directly to your publishing target.

The WordPress integration connects to your site securely with an Application Password. It supports common builders like Gutenberg, the Classic editor, Elementor, and WPBakery, and auto-detects which one your site uses so the content is written out in the right structure.

Beyond WordPress, there are ready-made integrations for Ghost, Strapi, Webflow, Shopify, and Wix. Each connects through the platform's official API — you enter your key (and, where needed, a collection and field mapping) and publish in one click.

The Custom API target lets you publish to any REST endpoint not on that list. With field mapping and authentication settings you map content into your own title, body, and meta fields, so you can push to any CMS or headless backend. This capability is part of the Pro plan.

Why it matters

The manual copy-paste step between generation and publishing wastes time and invites formatting errors. One-click publishing closes that gap — content lands on your site exactly as it appears, in the correct structure.

WordPress builder auto-detection keeps content consistent with your site's look. Gutenberg blocks, Elementor sections, or classic HTML — whichever is needed is what gets published.

The Custom API target means you are never locked into one platform. Whether it is a system you built, a headless CMS, or a non-standard backend, field mapping lets you send content to any REST API. When you re-publish, the same post is updated rather than duplicated.

How to use it

1. 1

   Open the Integrations page

   Go to the Integrations section in your dashboard. Here you see your connected publishing targets and add new ones.

2. 2

   Connect WordPress with an Application Password

   Add a WordPress target; enter your site address, username, and an Application Password generated from your WordPress profile.

3. 3

   Confirm builder detection

   humanaizer auto-detects whether your site uses Gutenberg, Classic, Elementor, or WPBakery; you can see this on the connection test.

4. 4

   Or connect a platform (Ghost, Strapi, Webflow, Shopify, Wix)

   Connect from the platform card: enter your API key, add a collection and field mapping (Strapi/Webflow) or a blog ID (Shopify) where needed, and verify with 'Test connection'.

5. 5

   Or add a Custom API target

   For any CMS not on the list, create a Custom API target: define your REST endpoint, authentication credentials, and the field mapping your content will be written into.

6. 6

   Publish generated content

   When a piece is ready to publish, pick the publishing target and send it in one click; the content lands on your live site.

7. 7

   Re-publish to update when needed

   When you re-publish a piece, humanaizer updates the same post rather than creating a new copy on your site.

Tips

• For WordPress, always use an Application Password instead of your regular password; it is safer and can be revoked on its own whenever you want.
• On a Custom API target, publish a small test piece first to verify your field mapping.
• If you manage several sites, add a separate target for each and select the right one at publish time.
• Because re-publishing updates the same post, revising and sending content again won't create duplicate records on your site.

Frequently asked questions