# How to Recycle Evergreen Social Media Posts Without Spamming

Published: 2026-11-15

**Key takeaways:** Recycle only posts that are still true and useful: label them as a pool and let a rule copy the least recently used one into your queue every few days. Each post returns about every pool size × interval days. Leave X out, since its rules ban repeated content. The run log says why a copy was skipped.

**To recycle evergreen social media posts, label the posts that stay useful, then set a rule that copies the least recently recycled one into your queue every few days. Each post comes back about every *pool size × interval* days, so a pool of twelve posts with one copy a week repeats each post roughly every twelve weeks.** Two things decide whether recycling helps or looks like spam: what you put in the pool, and whether a network accepts the same text twice. X doesn't, so leave it out.

This guide covers which posts to recycle, how to pick the interval, what to do about X, and how to set it up in PostBoost with recycling rules, including how to read the log when a copy is skipped.

## Which posts to recycle

A post is evergreen when it would still be true and useful if someone saw it for the first time today. Good candidates:

- **How-tos and tips:** "How to find your blog's RSS feed", a keyboard shortcut, a setup step.
- **Answers to questions customers keep asking:** shipping times, how to reset a password, what a plan includes (only if it hasn't changed).
- **Templates, checklists and frameworks** that people save.
- **Your best explainers:** what you do, who it is for, why it is different.
- **Links to your evergreen articles,** each with its own post.

Keep these out of the pool: anything with a date, an event, a deadline, a price or a discount, news, trend reactions, "new" announcements, and posts that thank or tag a specific person. A reposted "launching today" or "50% off this week" is the fastest way to make recycling look careless.

Before a post goes in, read it as a stranger: does every link still work, is every screenshot current, does it still say what you would say today?

## Copy, refresh or repurpose

| approach | what changes | use it when |
|---|---|---|
| **Recycle as is** | nothing; the same text and media | the post is short, still accurate and performed well |
| **Refresh, then recycle** | new opening line, updated screenshot or number, same idea | the idea is sound but a detail aged |
| **Repurpose** | a new post in another format (carousel, thread, short video) | you want new material from the same source |

Recycling is the cheapest of the three: once the pool exists, it runs on its own. If the posts in a pool start to feel tired, refresh a few rather than shortening the interval. To turn one article into a batch of new posts first, the free [blog to social media tool](/tools/blog-to-social-media) writes a version per network.

## How often to recycle: work it out from your pool

The networks don't publish a repost interval, and the intervals in scheduling-tool blogs usually come without data behind them. A more useful way to decide is the arithmetic of your own pool:

**Each post returns about every (posts in the pool) × (days between copies) days.**

| posts in the pool | one copy every | each post returns about every |
|---|---|---|
| 6 | 7 days | 6 weeks |
| 12 | 7 days | 12 weeks |
| 12 | 3 days | 36 days |
| 30 | 2 days | 60 days |

This assumes every post in the pool is old enough to be picked (see the tag pool rule below). Then decide from your mix: if you post five times a week and want one in five posts to be a recycled one, one copy a week fits. If a post comes back sooner than you would like, add posts to the pool before you lengthen the interval, so the share of recycled posts stays the same. The free [posting frequency planner](/tools/posting-frequency-planner) gives sourced weekly ranges per network to set the total, and [how often to post on social media](/learn/how-often-to-post-on-social-media) explains where those ranges come from.

## Leave X out of recycling

X's developer rules, under automation and spam, say to "Never post identical or substantially similar content across multiple accounts" ([X restricted use cases](https://docs.x.com/developer-terms/restricted-use-cases)). That rule is about multiple accounts, and X publishes no safe interval for repeating a post on one account either, so an exact copy is the riskiest recycled post you can send to X.

PostBoost leaves X accounts out of every recycled copy for that reason: the rule's account list doesn't show X accounts, and when the source post includes one, the copy goes to the other accounts and the created run notes `x_skipped_identical_text`. If X was the only account on the post, the run is skipped with that same reason. For X, write a fresh version of the idea yourself; the free [X thread maker](/tools/x-thread-maker) helps when the idea deserves a thread instead of a single post.

## Set up recycling in PostBoost

Recycling rules are under **Tools → Recycling & RSS → Recycling rules**, for workspace admins and members. A rule can recycle one post, or rotate every post with a label.

### Recycle a pool of posts with a label

1. **Label the posts.** In the post editor, click **Add label**, type a name such as `evergreen` and choose **Create "evergreen"**. Do this for each post you want in the pool. The recycling page calls labels tags.
2. Open **Tools → Recycling & RSS** and, under **New recycling rule**, choose **What to recycle → Posts with a tag (the least recently recycled one each time)**, then pick the tag.
3. **Every (days, 1 to 365):** the interval between copies.
4. **Stop after (copies, optional):** leave it empty to run until you pause the rule.
5. **Placement:** **Next free queue slot**, **Same time of day as the original**, or **Save as a draft**.
6. **First run (UTC, optional; default: one interval from now):** leave it empty and the first copy is made one interval after you save.
7. **Accounts:** leave all unticked to post each copy to the accounts its source post used, or tick some to limit copies to those (a copy only goes to accounts its source post was on).
8. Click **Create rule**.

Each run picks one post with the tag that is **published**, was published **at least one interval ago**, and has been recycled least recently; posts never recycled come first, oldest first. Copies carry the tag too, but a copy is never picked as a source, so the pool doesn't fill up with copies of copies.

### Recycle one post

Choose **What to recycle → One post** and pick it from the list (your 100 most recent posts, each with its status). The other fields are the same, except that ticked accounts replace the post's own accounts, so you can send an old post to a channel you added later. Use it for a single explainer or pinned-style post you want back every month; use a tag pool for anything more.

### Where the copy goes

| placement | what happens to each copy |
|---|---|
| **Next free queue slot** (default) | goes into the queue at the next free slot of your posting schedule; if no slot is free in the next 14 days, the run is skipped with `queue_full` |
| **Same time of day as the original** | scheduled for the next occurrence of the original's time of day (UTC), today or tomorrow |
| **Save as a draft** | saved as a draft; nothing is scheduled until you open it and schedule it |

A copy is a normal post: it shows in the calendar and the queue, and you can edit or delete it before it goes out. Start with **Save as a draft** for the first few runs, read what the rule picks, then switch the rule to the queue.

## Read the run log when a copy is missing

Every run is logged under the rule as **created**, **skipped** or **failed**, with **view copy** linking the post it made. Only a created run counts toward **Stop after**; skipped and failed runs don't. The reasons you will see:

| reason | what it means | what to do |
|---|---|---|
| `no_eligible_post` | no published post with the tag is old enough | add posts to the pool, or wait |
| `source_unavailable` | the one post was deleted or failed | point a new rule at a working post |
| `queue_full` | no free queue slot in the next 14 days | add slots to the posting schedule, or use another placement |
| `duplicate_post` | a post with the same content was created for that account in the last 24 hours | lengthen the interval |
| `account_daily_cap_reached` | the account hit its daily post limit (scheduled copies only) | spread rules over different days |
| `account_unauthorized` / `account_token_missing` | the account needs reconnecting (scheduled copies only) | reconnect it, then the next run goes through |
| `x_skipped_identical_text` | the source post was only on X accounts | add a non-X account to the post, or use a one-post rule with other accounts |
| `no_accounts` | the source post has no accounts, or none of the rule's ticked accounts were on it | tick accounts the post used, or leave them all unticked |

These are the same guardrails that protect posts made through the API ([guardrails docs](/docs/guardrails)). A one-day interval on a single post sits right at the 24-hour duplicate window, so give a one-post rule at least two days between copies. A run that fails or is skipped still moves the next run one interval on; the rule doesn't retry the same day. If a recycled post was created but didn't publish, [why scheduled posts fail to publish](/learn/why-scheduled-posts-fail-to-publish) walks through the causes.

## Create rules through the API or an AI agent

The same rules are in the [PostBoost API](/docs/api/postboost-api). To rotate a tag pool every 7 days into the queue:

```bash
curl -X POST "https://postboost.co/app/api/$WORKSPACE/recycling-rules" \
  -H "Authorization: Bearer $TOKEN" -H "Content-Type: application/json" \
  -d '{"type": "tag_pool", "tag_uuid": "'"$TAG_UUID"'", "interval_days": 7, "placement": "queue"}'
```

To recycle one post every 30 days, six times, call `POST /app/api/$WORKSPACE/posts/$POST_UUID/recycle` with `{"interval_days": 30, "max_runs": 6}`. `GET /recycling-rules/{uuid}/runs` returns the run log, and `PUT /recycling-rules/{uuid}` with `"active": false` pauses a rule. Tag uuids come from `GET /tags`. With a scoped API key, creating a rule needs the `publish` ability. Details are in the [automations docs](/docs/automations).

On the PostBoost MCP server the tools are `createRecyclingRule`, `recyclePost` and `listRecyclingRuns`; the Claude connector has `create-recycling-rule`. A prompt to try once your posts are labelled: "Create a recycling rule for my evergreen tag, one copy every 7 days, saved as drafts, and show me its runs next week." Read the first drafts before you switch the rule to the queue. The [MCP config generator](/tools/mcp-config-generator) writes the client setup, and [letting an AI agent post safely](/learn/let-an-ai-agent-post-to-social-media-safely) covers the limits that apply.

## Before you switch a rule on

- Every post in the pool is still accurate: links, screenshots, product names, no dates or prices.
- The pool is big enough that each post comes back no sooner than you would like (pool size × interval).
- X accounts get a hand-written version, not a copy.
- The first runs go to drafts; switch to **Next free queue slot** after you have seen a few.
- Your posting schedule has free slots, or queue copies are skipped as `queue_full`.
- Once a quarter, retire posts that went stale and add your newest evergreen posts to the label.

Feeding new articles into the same queue? [RSS feed to social media](/learn/rss-to-social-media) sets up the other half of an automated schedule, and the free [content calendar generator](/tools/social-media-content-calendar-generator) lays out which days carry new and recycled posts.

## Do this in PostBoost

- [Automations](https://postboost.co/features/automations): Add an RSS feed and new articles become drafts or queued posts.

## Free tools for this guide

- [Blog to social media post generator](https://postboost.co/tools/blog-to-social-media): Paste a blog post URL and get AI captions for Facebook, Instagram, X, LinkedIn, Pinterest, YouTube, TikTok and Mastodon, sized for each network. Free.
- [Posting frequency planner](https://postboost.co/tools/posting-frequency-planner): How often to post on Instagram, LinkedIn, TikTok, X and 5 more networks: sourced weekly ranges, your posts split per network and a weekly grid.
- [X thread maker: split long text into numbered posts](https://postboost.co/tools/x-thread-maker): Split long text into numbered posts for X, Threads, Bluesky or Mastodon. Never cuts a word or a link. Free, no signup, runs in your browser.

## FAQ

### What does it mean to recycle a social media post?

Recycling means publishing a post you already shared again, weeks or months later, with the same or lightly edited text and media. It works for evergreen posts: tips, how-tos, FAQs, templates and product basics that are still true. Posts about dates, events, prices or news should not be recycled.

### How often should I repost evergreen content?

Work it out from your pool rather than a fixed rule. If a rule rotates a pool of posts and adds one copy every few days, each post comes back about every pool size × interval days. Twelve posts and one copy a week means each post returns roughly every twelve weeks. Grow the pool before you shorten the interval.

### Can I recycle posts on X (Twitter)?

Not as identical copies. X's developer rules say to never post identical or substantially similar content across multiple accounts, and X publishes no safe interval for repeating a post on one account. PostBoost leaves X accounts out of every recycled copy for that reason. For X, write a new version of the idea by hand.

### Is recycling posts bad for engagement?

Not when the post is still useful and the gaps are long enough that your followers don't see it twice in a row. A repeat reaches people who followed you after the first time or missed it in their feed. Mix recycled posts with new ones, and retire a post when it stops getting reactions or goes out of date.

### What is the difference between recycling and repurposing content?

Recycling posts the same post again. Repurposing turns one piece, such as a blog post or a video, into new posts in other formats. Recycling keeps a proven post working; repurposing creates new material. Many teams do both: repurpose a long piece into several posts, then recycle the best of them.

### Does a recycled post publish without me checking it?

Only if you choose that placement. In PostBoost a rule can put each copy in the next free queue slot, schedule it at the original post's time of day, or save it as a draft for you to review. Nothing is published the moment the rule runs.

## Sources

- [X Developer Platform: Restricted use cases (automation, spam and auto-responses)](https://docs.x.com/developer-terms/restricted-use-cases)
- [PostBoost docs: Automations, recycling and RSS](https://postboost.co/docs/automations/)
- [PostBoost docs: Guardrails (duplicate guard, daily caps)](https://postboost.co/docs/guardrails/)

Canonical: https://postboost.co/learn/recycle-evergreen-social-media-posts
