Recycle rules
Your best posts come back on their own. With a cooldown, so nobody notices the repeat.
Most of what you publish is still true a month later, and almost nobody sees it the first time. A recycle rule is a tag pool, a set of channels, a recurrence, and a cooldown — the smallest thing that keeps evergreen content circulating without turning your feed into a loop.
Runs on a cadence you control.
How it works
Evergreen recycling, step by step.
- 1
Tag the keepers
Mark posts that stay true over time — tips, FAQs, case studies.
- 2
Attach a rule
Choose the tag pool, the channels, and a recurrence like Tue/Thu at 10:00.
- 3
Set the cooldown
The minimum gap before the same post can be reused. Defaults to 30 days.
- 4
Watch the calendar
Recycled posts appear in the queue ahead of time, so you can move them.
Capabilities
What you get with Evergreen recycling.
- The rule is the queue
- A rule is a tag pool crossed with channels, a recurrence, and a cooldown. There is no separate evergreen queue object to keep in sync — which means there is no second place for your content to go stale.
- Per-post cooldown, set on the rule
- The cooldown belongs to how aggressively a rule reuses, not to the post. So an aggressive rule and a slow one can draw from the same pool without fighting each other.
- Nothing repeats invisibly
- Recycled posts land on the calendar before they publish, with indicators showing what is coming back. You can move or remove one like any other scheduled post.
- Runs out gracefully
- When every post in the pool is still inside its cooldown, the rule advances to its next slot instead of reusing something too soon or failing loudly.
A rule, in full
Four parts, and nothing else:
| Part | What it does |
|---|---|
| Tag pool | Which posts are eligible. Tag something once and every rule using that tag can draw on it. |
| Channels | Where the recycled post goes. |
| Recurrence | When the rule fires — for example, Tuesday and Thursday at 10:00. |
| Cooldown | Minimum days before the same post may be reused. Default 30. |
That is the smallest closed system that produces useful behaviour, which is why there is no separate evergreen library to maintain. Your tagged posts are the library.
Why the cooldown lives on the rule
It reads like an odd detail and it is the one that matters most in practice.
Say you have a #tips pool. You want a fast rule pushing tips to X several times a week, and a slow one putting the same tips on LinkedIn monthly. If the cooldown were a property of the post, those two rules would interfere — the fast rule would lock every post and starve the slow one.
Attaching the cooldown to the rule means each rule has its own idea of how aggressively to reuse, and they can share a pool without coordination.
Tag as you publish rather than in a big sorting session later. A post is easiest to classify as evergreen the moment you write it.
What it does not do
- No per-platform variants on recycle. The post is reused as written. Reshaping per platform is auto-repurposing.
- No infinite loop guarantee. If your pool is three posts and your rule fires daily, the cooldown will hold most slots empty. Small pools want slow rules.
- No publishing on a free workspace. Recycling creates live schedules, so it needs a subscription. Tagging and rule setup work either way.
On honesty about the category
Evergreen recycling is not a Postonus invention. SocialBee's content categories and RecurPost's libraries both do a version of it, and both do it well. Buffer added a recurring-post option too.
What differs is the shape: tags instead of categories means a post can belong to several pools without being duplicated, and the cooldown-on-the-rule design means overlapping rules do not have to be kept apart by hand.
Found this useful? Pass it on.
Questions
Frequently asked questions Everything the first evaluation usually needs.
- How do recycle rules work?
Tag the posts you consider evergreen, then create a rule that names a tag pool, the channels to publish to, a recurrence, and a minimum gap before the same post can be reused. At each firing the rule picks an eligible post from the pool and schedules it.
- Will my audience see the same post twice in a row?
Not unless you configure it that way. Each rule carries a minimum number of days between reuses of the same post, 30 by default, and a post inside its cooldown is not eligible.
- What happens when every post in the pool is on cooldown?
The rule skips that slot and moves to the next one. It does not publish something too early and it does not error.
- Can I edit a recycled post before it goes out?
Yes. A recycle firing creates a normal scheduled post on your calendar, so you can edit, move, or delete it before the publish time.
- Does recycling rewrite the post for each platform?
No — a recycle reuses the post as it is. If you want the content reshaped per platform, that is auto-repurposing, which is a separate feature.
- How is this different from SocialBee or RecurPost?
The mechanics are comparable: all three cycle a pool of saved content on a schedule. Postonus organises the pool by tag rather than by content category or library, and carries the reuse cooldown on the rule, so two rules can share one pool at different intensities.
Keep reading
- Auto-repurposePoint a Growth Autopilot at a platform you already win on and a channel you want to grow. Postonus mines your top posts and drips reshaped drafts in for review.Read
- Queue & reliabilityA queue that flags a post at risk before its publish time, refuses to send something an hour late, and turns a crashed worker into a retryable failure.Read
- vs SocialBeeCompare Postonus and SocialBee on pricing, platforms, recycling, and API access — including where SocialBee has no public API and its queue can stall.Read