Publishing to WordPress

A post written in Generate Blog can be sent straight to a connected WordPress site, as a draft for review or live. Publishing happens in one request while you wait; there is nothing to schedule.

Before you can publish, connect the site once in Integrations. See WordPress for the setup and WordPress connection fails if it does not connect.

Publish a post#

1. Open the Publish sheet

   Open the post and press Publish in the top bar. From the Blog library, the card menu's Publish… opens the post with the sheet already open. If no site is connected, the sheet says so and links to Set up an integration.

2. Choose Draft or Live

   Under Publish as, Draft creates the post as a draft for you to review in WordPress first. Live makes it publicly visible right away.

3. Check the slug and excerpt

   Slug is prefilled from the title and Excerpt from the post's description, or its first paragraph when it has none. Edit either before sending.

4. Send it

   Press Push draft or Publish live. A confirmation appears with a View post link to the post on your site.

What WordPress receives#

• The title, the post body as HTML, the slug, the excerpt and the status you chose.
• Charts, tables, stat callouts and pull-quotes are converted to inline HTML, the same body the Copy HTML export produces.
• The JSON-LD schema is not sent. See below.

WordPress removes charts from posts saved by accounts that may not post unfiltered HTML: every role below Editor, and everyone but super admins on a multisite network. When that happens, Ranqo sends the post again with each chart as a table of its numbers, and sends charts as tables to that site from then on. Connecting the site again lets Ranqo try charts again. If that second send fails, the confirmation says the post went out without its charts; update the post to send them as tables.

The post's status in Ranqo changes to Published only when WordPress puts it live. Pushing a draft, or sending live a post WordPress keeps scheduled, leaves it as a draft in Ranqo.

Update a post you already published#

Once a post has been sent, the button in the top bar reads Published, and the sheet shows where the post is and its status when Ranqo last sent it, Live, Scheduled, Private, Pending review or Draft on CMS, with a View link. Publish as starts on Live for a post that was live or scheduled, and on Draft otherwise.

Publishing again updates the same WordPress post in place, rather than creating a second one; the button reads Update post. Use it to switch a draft to live, or to change the slug or excerpt. An update replaces the post's title, body, slug, excerpt and status in WordPress with Ranqo's version, so Ranqo reads the post first and asks before going ahead when:

• the post was changed in WordPress since Ranqo last sent it, because updating replaces those changes, or
• updating would change a status set in WordPress, for example taking a live post back to draft, or publishing a post someone moved to draft there.

The sheet names the post by its title in WordPress and says which applies. Update anyway goes ahead, Cancel leaves WordPress untouched, and Publish as a new post instead leaves that post as it is and sends Ranqo's version as a new one. If the post changes in WordPress again before you confirm, Ranqo asks again. Switching a draft Ranqo sent to live does not ask, and a scheduled post updated as Live keeps its schedule. If you edit a post in WordPress after pushing it, publish it from WordPress as well.

If the post was deleted in WordPress, or is in its trash, publishing creates a new one.

Why the schema is not sent#

Every generated post comes with JSON-LD schema: an Article, plus an FAQ page when the post has an FAQ. WordPress removes <script> tags from post content saved by accounts that are not allowed to post unfiltered HTML, which usually means every role below administrator, so schema embedded in the body would be stripped without warning. Ranqo keeps it out of the body instead and makes it available to add where WordPress will keep it:

• Download, then Copy JSON-LD on the post page copies it.
• The Complete HTML page and ZIP exports include it.

Paste it into your theme's head or into whatever tool your site uses to manage structured data. See Exporting content.

If publishing fails#

When WordPress refuses the request, the sheet shows WordPress's reason, for example rejected credentials or a site URL where the REST API cannot be found, and the connection is marked as having an error in Integrations. Fix the connection there, then publish again.

If the account can sign in but its role lacks a permission, for example a Contributor sending a post live, the sheet says the account does not have permission and gives WordPress's reason. The connection stays as it is. Publishing live needs a role that can publish posts, such as Author, Editor or Administrator.

If the connected account is not allowed to edit the post, for example one sent from a different WordPress account before you reconnected, the sheet says so and offers Publish as a new post, which leaves that post as it is and sends this one as a new post. Or reconnect with an account that can edit it, such as an Editor or Administrator. The connection stays as it is.

Deleting and disconnecting#

• Deleting a post in Ranqo does not touch WordPress. A post already sent stays on your site.
• Removing a WordPress connection keeps the record of where each post was published. Connect the same site again, with or without https:// or www. in its address, and publishing updates the posts already there instead of creating copies. Connect a different site and publishing creates new posts on it; the first site's posts stay as they are.

Each brand connects one WordPress site. CMS connections are counted across all your brands, up to your plan's limit (Starter: 1, Pro: 3); see Plans and limits. Publishing itself does not count toward any monthly limit.