How Blogo works

What Blogo sends to WordPress

Blogo creates a draft post in your WordPress site and stops there. It sends the title, the article body and the address slug, with the status set to draft. It does not publish, and its sending step does not edit or delete anything already on your site. In the current invite-only pilot the sending step is switched off; the rest of this page describes what it does when it is on.

Start with your websiteSee pricing

What is in the draft

One request creates one WordPress post with the status “draft”. Blogo then reads the post back from WordPress to confirm that it really is a draft before it tells you the send worked.

  • The title you reviewed.
  • The body as plain HTML: headings, paragraphs, lists, tables, links and images. Raw HTML written inside the article is not passed through.
  • Each image as a figure with its credit line as the caption.
  • The address slug Blogo suggests for the page.
  • A byline under the title and an “About the author” box at the end, when you have saved author details for the site. The author text is yours; it is never written by a model.
  • A hidden HTML comment at the end of the body. It lets Blogo recognise its own draft later, so a retry does not create a duplicate.

What is not sent

The request carries no excerpt, no featured image, no categories or tags, and no fields for an SEO plugin. Set those in WordPress when you review the draft.

Images are not uploaded to your media library. They are referenced at the address of the source they came from, so a reviewer who wants local copies should add them in WordPress.

Links are written with a fixed rule: links to your own site are left plain, links to a short list of authority sites (government, education and major press domains) are normal links, and every other external link is marked nofollow.

What you approve first

Nothing reaches WordPress because a step finished. A person has to ask for it, and the request is refused unless all of the following are true at that moment.

  • Every pre-send check has passed for this exact text: the writing plan, your brand rules, the facts, the sources, the images and the links.
  • You have confirmed the article you reviewed. The button asks twice, and the confirmation is tied to that exact title and body. If the text changes afterwards, the confirmation no longer counts and you review again.
  • The confirmation also covers your current brand rules and company facts. If someone edits them in between, the send is refused until you review again.
  • The WordPress connection is for the same domain as the site in Blogo, and it uses HTTPS.

Sending the same article twice

If you send an article that has not changed, Blogo does not create a second draft. It checks that the first draft still exists in WordPress and returns that one.

If you changed the article after sending, the next send creates a new draft. The earlier draft is left alone for your editor to keep or remove; Blogo does not overwrite it.

If the first draft was moved to the trash or deleted, the next send creates a fresh one.

When WordPress refuses or does not answer

A clear refusal from WordPress, such as a permissions error, means no draft was created. You see an error and nothing else happens.

A timeout or a server error is ambiguous: the draft may or may not exist. On the next attempt Blogo first searches your drafts for the hidden comment that belongs to this exact article version and adopts that draft if it finds it, instead of creating another.

If WordPress reports the post as published or scheduled rather than as a draft, for example because a plugin changed the status, Blogo does not call that a success. It stops with an error that names the post so you can check it in WordPress.

How the connection works

You connect with a WordPress username and an application password, created in your WordPress profile. No plugin is installed. The application password is encrypted before it is stored, and Blogo refuses to save it if encryption is not available on the server.

The connection test checks that the user can edit posts. Blogo uses the connection to read your existing posts and pages, so it knows what you already cover, and to create draft posts. After a draft is sent, the article is recorded as a pending page; it is offered as an internal link in later articles only after it appears in your live sitemap.

Questions

Can I switch on automatic publishing?
No. There is no setting for it. The only status Blogo sends is “draft”, and publishing is done by a person in WordPress.
Is sending to WordPress available in the pilot?
Not at the moment. Sending is switched off for the invite-only pilot, so the button returns a message and nothing is written to your site. You can still connect WordPress, and you can copy the finished article as Markdown and paste it into your editor.
What can the application password do on my site?
It has the rights of the WordPress user you created it for. Blogo’s article flow uses it to read posts and pages and to create draft posts. If you want a tighter limit, create the password for a user with the Editor role rather than an administrator.
Where do the SEO title and meta description go?
They are not sent to WordPress. The draft carries the title, body and slug; fill in your SEO plugin’s fields during review.

See the draft before it goes anywhere

Add your site and review a finished article in Blogo. Blogo is in a free, invite-only pilot.

Start with your website