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.

The post's status in Ranqo changes to Published only when you send it live. Pushing a draft 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, marked Live or Draft on CMS, with a View link.

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. The status you choose is applied too, so choosing Draft on a live post turns it back into a draft in WordPress, while the post stays marked Published in Ranqo.

If the post was deleted in WordPress in the meantime, 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.

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.

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.