Automatic Publishing

Have RankTurn publish each finished article to your connected platforms automatically, with no manual step.

Automatic publishing makes your content truly hands-off. Turn it on and RankTurn publishes each finished article straight to the platforms you chose — no extra clicks, no remembering to hit Publish. It's on by default for AI Content Plans and Series, and you can also switch it on for individual articles.

When auto-publish is off, a finished article simply lands in your library as a draft for you to review. When it's on, writing and publishing happen as one smooth flow.

Enabling Auto-Publish (per article, content plan, or series)

Look for the Auto-publish after generation toggle wherever you start a generation. Switch it on, then choose your destinations.

  • Per article — When you generate a single article, turn on Auto-publish after generation and pick the platforms. As soon as the article is finished, RankTurn publishes it to those platforms right away. (You won't see this toggle for articles that are already scheduled — see Scheduled articles below.)
  • For a Content Plan — A plan keeps its own list of publish destinations. Every article the plan creates uses those platforms and publishes automatically on its scheduled date.
  • For a Series — A series keeps its destinations the same way, so each new issue goes out automatically as it's written.

If you haven't connected any platforms yet, you'll see a short note and a link to set up your connections under Integrations instead of the toggle. You need at least one active connection before you can auto-publish.

Scheduled articles already have a schedule

You won't see the Auto-publish after generation toggle for an article that's already scheduled. A scheduled article simply follows its saved publish date and destinations, going out automatically at its scheduled time — the same way Content Plan and Series articles do.

Selecting Platforms (active connections only)

When auto-publish is on, you choose which connected platforms the article goes to. You can only pick platforms that are connected and active — any connection you've turned off or removed is skipped.

RankTurn decides where to send an article like this:

  1. If the article belongs to a Content Plan, it uses the plan's publish destinations.
  2. If it belongs to a Series (and the plan didn't set any), it uses the series' destinations.
  3. Otherwise — for articles you generate one at a time or in bulk — it uses the platforms you selected for that article.

Each platform publishes with its default publish profile, so an auto-published article carries the same tags, author, category, canonical URL, and image settings as if you'd published it by hand. To learn more about publish profiles, see Credentials & Security and your platform's integration page.

When your article goes live

When an auto-published article reaches your platforms depends on how you created it.

A single article you generate yourself — published right away

When you turn on auto-publish for a single article, it goes out immediately. The moment the article is finished, RankTurn publishes it to the platforms you chose — no waiting, no scheduled date. It's delivered just like a manual publish.

Content Plans, Series, and bulk-generated articles — published around their scheduled time

Articles created by an AI Content Plan, a Series, or a bulk generation go live around their scheduled date instead. Here's what you'll see:

  1. The article finishes. Once written, it's marked Scheduled, with a publish date attached.
  2. It goes live on its date. On (or just after) the publish date, RankTurn marks it Published. Each article is only ever published once — it can't accidentally go out twice.
  3. It's sent to each platform. RankTurn delivers the article to every destination you chose, and records the published web address where the platform provides one.

RankTurn checks for due articles about once an hour, so think of a plan, series, or bulk article's scheduled time as "no earlier than" rather than exact. An article ready at 9:00 usually goes out within the next hour. (This doesn't apply to a single article you generate yourself — that one is published right away.)

Content Plan / Series / bulk  ─▶  Scheduled  ─▶  (around its date)  ─▶  Published on each platform

single article you generate   ─▶  (right away)  ─▶  Published on each platform

Notifications (success and failure)

When an article is auto-published, RankTurn lets you know in the app and (if you've enabled it) by email. The message depends on the outcome:

OutcomeWhat you'll see
Published to every platform successfully"Article '…' has been auto-published"
Published, but some platforms failed"Article '…' auto-published (some platforms failed)" — listing which platforms failed and why.
Every platform failedAn error notice: "Failed to publish article '…'" — with the reason for each platform.
Published with no platforms chosen"Article '…' has been auto-published" (your article is ready in your library).

Both the in-app message and the email follow your notification preferences. You can turn article-published notifications on or off under Notifications.

When something fails

Auto-publish is resilient: if one platform fails, the others still go through. RankTurn tracks the result for each platform separately, so you always have a clear record of what published and what didn't.

When publishing to a platform fails:

  • That platform is marked Failed and the reason is saved, so you can see exactly what went wrong.
  • You'll see the failure on the article itself, where you can review the error and re-publish to that platform once you've fixed the problem.
  • If the failure looks like a sign-in problem — for example an expired connection or a "not authorized" error — RankTurn also emails you to suggest reconnecting the platform under Integrations. (These reconnection emails have their own on/off setting.)

This works the same way for manual and scheduled publishing too, so the statuses — Pending, Processing, Published, Failed — and what happens on a retry are consistent everywhere you publish. See Scheduling Articles for the full list of statuses.

Default Publish Destinations

Rather than picking platforms every time, you can set default publish destinations once and have them pre-selected for new generations. Configure these under Article Settings, and manage the connections themselves under Integrations. For sending the same finished article to several platforms after the fact, see Bulk Publishing & Generation.