WordPress
Connect WordPress to send completed Sitefire articles to your site’s draft queue. Review and publish them in WordPress.
Supported sites
- Self-hosted WordPress: version 5.6 or later, with HTTPS and Application Passwords enabled.
- WordPress.com: a paid plan with hosting features activated and site-specific Application Passwords available. Free sites and sites without activated hosting are not supported by this connection.
WordPress.com uses the same connection when those requirements are met. See its Application Passwords guide for plan and hosting requirements.
Create a dedicated Contributor account
As a WordPress administrator, open Users → Add New in your site’s wp-admin. Create a user named sitefire with the Contributor role.
The account must be able to edit posts, without permission to publish or edit published posts. Sitefire checks these permissions when connecting and before each push.
Application Passwords inherit the user’s permissions. Administrator, Editor and Author accounts are refused. Use the dedicated Contributor account for this connection.
Create an Application Password
- Log in to WordPress as the Contributor account.
- Open Profile → Application Passwords.
- Enter
Sitefireas the name and click Add New Application Password. - Copy the generated password. WordPress shows it only once.
Use this site’s Application Password, not your login password. For WordPress.com, do not use an account-level password from the two-step authentication settings. Spaces in the generated password are accepted.
If the section is missing, check that your site uses HTTPS and that your host or security plugins allow Application Passwords. See WordPress REST API authentication .
Connect in Sitefire
Open Settings → CMS, select WordPress and enter:
| Field | What to enter |
|---|---|
| WordPress URL | Your final HTTPS installation URL, such as https://example.com or https://example.com/blog |
| WordPress username | The Contributor account’s username, for example sitefire |
| Application password | The password created for that account |
Omit wp-admin and wp-json from the URL. If your original address redirects to a custom domain, use that custom domain. Sitefire does not forward credentials through redirects.
The site must be publicly reachable over standard HTTPS. HTTP, localhost, private-network addresses and custom ports are refused. WordPress installations in a subdirectory and sites using plain permalinks are supported.
Click Connect, then select Posts.
Map your fields
| Article field | WordPress field | Result |
|---|---|---|
| Title | Title | Post title |
| Slug | Slug | Used to find the draft on repeat pushes |
| Body | Content | Markdown converted to HTML |
| Excerpt | Excerpt | Post excerpt |
| Date | Date (UTC) | Optional post date; the post remains a draft |
The Slug mapping is required. Use up to 200 lowercase ASCII letters, numbers or underscores, separated by single hyphens. The slug cannot be 0. For example, use how-to-choose-a-cms.
Save the mapping before pushing an article.
Push and review a draft
Open a completed article and click Push to WordPress. Follow the returned link to open its WordPress editor.
The first push creates a draft. A repeat push updates the draft with the same slug. Sitefire refuses the push if multiple posts match, the matching post is inaccessible, or the matching post is outside draft status.
Review and publish using a separate WordPress account with publishing permission. After publication, Sitefire refuses further pushes to that post. It does not maintain a separate working draft of an already published WordPress post.
What this connection supports
The connection writes standard Posts using HTML content. It does not upload media, create Pages or custom post types, assign categories or tags, or write plugin-specific fields. The article arrives as HTML rather than individual Gutenberg blocks.
Edit in WordPress
In the block editor, imported articles usually appear in a Classic block. You can edit the text there without writing HTML. Select Convert to blocks to edit paragraphs, headings, lists and other supported content as separate blocks. No extra plugin is required. See WordPress’s Classic block guide .
Preview the article after conversion, especially tables, images and custom formatting. Conversion handles supported content types; it does not recreate arbitrary layouts or page-builder widgets.
Finish your Sitefire revisions before making final edits in WordPress. Pushing the draft again replaces the mapped content, including edits and block formatting saved in WordPress. Sitefire does not merge those changes back into the article.
The recommended workflow is: revise in Sitefire, push the final draft, optionally convert it to blocks, then finish and publish in WordPress. Sites using the Classic Editor can edit the imported HTML directly through their visual editor.
Troubleshooting
The URL slug contains an unsupported character. Click Edit URL slug in the push error to open the article’s URL slug field. For a slash such as folder/article, change it to folder-article, then push again.
The URL is rejected or redirects. Use the final HTTPS installation address, without wp-admin, wp-json, a query string or a custom port.
WordPress rejects access. Check the username and Application Password. Ask your host to forward the Authorization header and allow the WordPress REST API.
Sitefire asks for a Contributor account. Check the account’s permissions. Customized roles must allow editing posts but must not allow publishing or editing published posts.
Sitefire cannot confirm the post count. Your host or proxy must preserve the X-WP-Total response header. Sitefire refuses to write when it cannot safely check for existing posts.
A matching post is not a draft or is inaccessible. Review it in WordPress. Choose a different article slug if you intend to create a separate post. Published, scheduled, private, pending-review and trashed matches are refused.
Multiple posts have the same slug. Give the intended draft a unique slug before pushing again.
For the other available providers, see CMS integrations.