WordPress publishing handoff: access, taxonomy and previews
Prepare a WordPress publishing connection, map categories and tags, and check the final article and media before distribution.
By the Postly Team
Before you start
Use the correct site URL and an authorized WordPress user. Application passwords provide API authentication over HTTPS; the user's capabilities still determine what actions are allowed.
Prepare and review the release
- Have the site owner prepare the authorized connection. Keep application credentials out of article drafts and team notes, and record who can revoke or replace them.
- Choose the article's title, body, category and tags. Check that taxonomy choices exist on the destination site instead of assuming another site's names will match.
- Review featured media, inline images and destination links. Preview on the site's actual theme because the editor preview may not reveal theme styling issues.
- Publish or schedule using the supported workflow, then inspect the final URL. Use that confirmed URL when preparing social posts about the article.
Worked example
A nonprofit prepares a volunteer story in its News category. The reviewer confirms the subject's approved wording, image description and donation link on the WordPress preview. Social distribution begins after the public article is readable and its main image appears correctly.
If something goes wrong
- Authentication fails: check the site URL and application credential with the site owner.
- Access succeeds but publishing fails: inspect the user's publishing capabilities and any site-level restrictions.
- Image absent: check the media upload result and the rendered article separately from the text publication result.