User Guide

Recycling posts

A post that worked should not need rewriting to work again. Switch recycling on and DemandBird puts it back in your queue on a cadence you choose.

Overview

Most of your audience never saw your best post. Recycling (evergreen re-posting) keeps a good post working: DemandBird drops a copy back into your queue every so many days after the last one went out, up to an optional number of repeats.

It runs on its own once it is on. There is nothing to remember and nothing to re-approve.

Turning it on

The control lives on the post card in Content, next to the tag picker, not in the composer. That is deliberate: you decide a post is worth running again by looking at one that already went out, not while you are writing it.

  1. Find a published post
    Open the Published tab in Content, or the Published column on the board.
  2. Click Recycle on the card
    The chip reads “Recycle” when it is off, and the cadence when it is on, so you can read the state of a post without opening anything.
  3. Pick a cadence and a stop point
    Repeat every 7, 14, 30, 60, 90, or 180 days. Stop after 1, 2, 3, 5, or 10 reposts, or keep going indefinitely.
  4. Save
    The chip now reads something like “Every 30 days · 2 of 5”: your cadence, and how many repeats have already gone out.
Recycling is only offered on posts that have actually published. The next repeat is measured from the last time the post went live, and a draft has not got one.

Cadence and stop-after

The interval is counted from the last publish, not from when you switched recycling on, and not on a fixed calendar. A 30-day recycle on a post published on the 3rd books the next one for around the 2nd of next month, then 30 days after that one actually goes out.

The menu is a menu, not a rule: any interval from 1 to 365 days is valid. Below a day it stops being a recycle and becomes a queue; past a year, “evergreen” has stopped meaning anything.

Stop after is a repeat count, and the card shows your progress through it. Leaving it on “Keep going” means indefinitely, which is fine for a genuinely timeless post and a slow cadence.

How a repeat is booked

Worth understanding, because it explains what you see on the calendar.

  • The original is never re-scheduled. Each repeat is a fresh copy of the post with its own schedule. Your original keeps its own publishing history intact.
  • One repeat is booked at a time. The next one is only created after the current one has gone out, so your calendar shows what is genuinely coming instead of a wall of identical rows stretching into next year.
  • It goes to the same channels. A repeat publishes to whatever the original actually published to.
  • It uses your queue. The copy lands in your next open slot on or after the earliest allowed date, so repeats respect your posting schedule like anything else.
  • Copies never recycle themselves. The chain is one level deep, so turning recycling off is one switch on the original rather than a hunt through copies.

DemandBird checks hourly. If the next repeat would land beyond your account's scheduling horizon, it is simply left for a later check rather than booked early.

On the calendar

Because only one repeat is booked at a time, a post set to “every 14 days, forever” would otherwise show one row and nothing after it, which is accurate bookkeeping and a bad picture. So the calendar also draws the later cycles as greyed-out Repeat rows.

A Repeat row is a forecast, not a booking. It is not draggable, not clickable, not counted in any total, and nothing is reserved. It is there so you can see that a slot two months out is already spoken for before you plan something else into it. The first upcoming repeat is not drawn this way, because it is a real scheduled post already.

Editing and stopping

Change the cadence or the limit at any time from the same chip; the change applies to the next repeat. Switch recycling off and nothing further is booked. A repeat that is already scheduled stays scheduled, and you can unschedule it like any other post.

When a post has used up its repeats, the card says so, and the setting stops doing anything until you raise the limit.

What to recycle

  • Your best performers. Check Analytics for what actually landed, then recycle those.
  • Posts with no expiry date. A principle, a framework, a story. Not a launch, a deadline, or “this week we”.
  • Posts that hold up out of context. A repeat goes out on its own, months later, with no thread around it.
Recycle a handful of posts on a slow cadence rather than everything on a fast one. Repeats fill real queue slots, so an aggressive setup crowds out the new writing that earns you the next evergreen post.

Common questions

QuestionAnswer
Does it reword the post?No. A repeat is the post you published, unchanged. If you want a different angle, open the copy before it goes out and edit it, or write a new post from the same idea.
Can I recycle a draft?No. The cadence is measured from the last publish, so the post has to have gone out at least once.
Will it double-post?No. Only one repeat exists at a time, and the next is not booked until the current one has published.
What if I delete the original?Nothing further is booked. Any copy already scheduled is independent and keeps its own schedule.
Does recycling use AI credits?No. Nothing is generated: a repeat is a copy of what you already published.