How to use AI to schedule evergreen posts without spamming: a rotation system
Short answer: Evergreen posts are ones that stay true and useful for months. To reuse them without spamming, keep them in a rotation sheet, set a minimum gap between repeats, have an AI rewrite the opening line each time, cap the share of your calendar they fill, and retire a post that stops earning attention. Platforms treat very high frequency and copied content as spam, so check each one's current rules. Blotato, a software subscription that schedules and publishes social media posts, has no documented recycle feature, so the rotation lives in your sheet.
You have posts that still work months later and you want a system that puts them back in front of people without looking like a bot or breaking a platform rule.
I'm Ranjit, and I run Blur Studio: 15+ years building software, 120 apps taken live, and clients who have gone on to raise $10M+. I build AI systems and processes that help businesses do a lot more with a lot less time. I also work differently from most of what else is out there, more on that further down this page. Say hello.
Reposting old content is one of the best uses of a scheduler, and one of the easiest ways to look careless. The risk is not that repeats are banned. The risk is sameness: the same words, the same picture, the same day each week, from an account that otherwise posts little that is new. This page builds a rotation system you can run in a sheet, with an AI step that changes the opening each time, rules that stop repeats being too close, and a test that tells you after 8 weeks whether it helps. It is a different job from the quarterly review in repurposing your best posts every quarter, which is about choosing winners. This page is about running the queue week after week. The build is a plan to test.
Prices are in US dollars as of November 2026. Blotato's pricing page lists Starter at $29 a month, billed monthly, with a 200-post scheduled queue. The API (the way other tools talk to Blotato) is for paid plans only, and the 7 day trial excludes it.
This page may contain affiliate links from which Blur Studio earns commissions.
What evergreen means, and what is not evergreen
A post is evergreen if it will be true and useful in six months and does not depend on a date, a price, a trend or a news item. Good candidates: a how-to, a checklist, a myth and the fact, a short story about how you work, a plain explanation of a term, an answer to a question customers ask every month.
Not evergreen: a sale, an event, a holiday message, a price, a feature of a tool that may change, a statistic with a date on it, anything about a person who has since left. Mark those "one-off" and keep them out of the pool. If a post names a price or a platform rule, give it a review date, since those change.
The rotation sheet
One row per evergreen idea. The sheet, not the scheduler, decides what is next.
| Column | Purpose |
|---|---|
| Post ID | Stable key |
| Topic tag | So two posts on one topic do not run back to back |
| Core message | One sentence. The AI rewrites around it. |
| Last version used | Paste the last published text. |
| Last used (date) and times used | Drives the gap rule and the retirement rule. |
| Next eligible date | Last used plus the minimum gap. |
| Review by | The date after which a human must check it is still true. |
| Status | Active, Paused, Retired. |
| Best result so far | Reach or clicks of its first run, for comparison. |
The flow, in n8n or Make (visual workflow tools), runs once a week. It reads rows that are Active, past their Next eligible date and not past Review by, picks the one with the oldest Last used, and passes it on. See the n8n node guide and the Make guide for the Blotato connection.
Rotation rules that stop spam signals
- Minimum gap per post: 60 days. A reasonable start, and my own suggestion, not a platform rule. A longer gap is safer for a small audience, since most of them will remember it.
- Maximum 3 appearances a year, then retire the post or rewrite it into a new post.
- Share cap: evergreen fills at most 1 in 4 slots on any platform. If every slot is a repeat, the account looks automated and the audience gets nothing new.
- No two posts with the same topic tag within 10 days.
- Change the hook every time. The first line is what people see before "see more" and what a repeat check is most likely to match. Rewrite it, and change the visual or format as well.
- Vary the day and the time. Do not post a repeat at exactly the same time each week.
- Update anything that aged. A repeat with an old statistic is worse than no post.
- Review by date. A human checks the claim before it goes out again.
- Retire on a clear rule. If a repeat gets less than half the reach of the first run, twice in a row, retire it.
Platform rules on repeated content
Rules change and I give attributed pointers, not quotes of legal text. Check each platform's page the day you set this up.
- Meta (Facebook and Instagram). Meta's Community Standards on spam ban posting or engaging, whether by hand or automatically, at very high frequencies, and say lower-frequency activity can still be restricted when other spam signals appear. Meta does not publish thresholds. Read Meta's spam policy.
- TikTok. TikTok's integrity and authenticity guidelines say unoriginal or reused content is not eligible for the For You feed, and ban automation tools designed to get around its systems. Read TikTok's guidelines. Posting through an approved scheduling tool is not the same thing as a bypass tool, but read the page yourself.
- X. X (formerly Twitter) has rules on spam and platform manipulation, and a separate automation page. Read the current X Rules and automation pages before you repeat text word for word.
- LinkedIn. LinkedIn's prohibited software page says it does not permit third-party software that automates activity on the site. It does not name schedulers, so read it yourself and check how your tool connects.
The common thread is repetition at volume and identical or unoriginal content. A rewritten hook, a new format and a long gap are your protection. They are not a guarantee, and nobody publishes a safe number. If an account is warned, stop the rotation and ask the platform what it saw.
The AI step: rewrite the hook, keep the facts
AI is useful here because it is good at fresh first lines and bad at being trusted with facts. Give it the core message, the last version and a ban on repeating it, and keep the rest as you wrote it.
Here is a post we ran before, and its core message.
Core message: CORE_MESSAGE
Last version: LAST_VERSION
Write a new version of the opening line only, in a different style:
a question, a number, a short story or a plain statement.
It must not reuse the first 8 words of the last version.
Keep the body unchanged. Do not add facts, numbers or claims.
Return the opening line and nothing else.
Check each output by eye until you trust it. Compare the new first line to the last one, and stop the flow if they match in the first 8 words. Where the AI invents a number, remove the post from the rotation until you have fixed the prompt.
Scheduling in Blotato
Blotato's help pages describe recurring weekly time slots in its calendar and a next-free-slot option that uses the slots you define. They do not describe an evergreen or recycle feature, so use the sheet for the choosing and Blotato for the timing. Blotato accepts a scheduled time or the next free slot when you create a post through its API, and the time sits beside the post in the request, not inside it:
{
"post": {
"accountId": "ACCOUNT_ID",
"content": {
"text": "NEW_HOOK_PLUS_UNCHANGED_BODY",
"mediaUrls": [],
"platform": "linkedin"
},
"target": { "targetType": "linkedin" }
},
"useNextFreeSlot": true
}
A next-free-slot post needs a slot that matches the platform and account. If none is free, the call fails, so read the error. After each create call, save the submission ID, check it after at least 10 seconds, and write Last used only when Blotato says published or scheduled. A scheduled post is not yet used. Blotato has no idempotency key (a unique key that makes a repeat call harmless), so a retry after a timeout needs a look at the Posts list first, or one rotation row can post twice.
Plan limits: Starter queues up to 200 scheduled posts and allows 20 accounts, Creator 1,000 and 40, Agency 3,000 and 100 (as of November 2026). Scheduling a month ahead for 4 platforms at 3 posts a week is about 48 queued posts, well inside Starter. Per-platform daily caps are separate, see Blotato's posting limits page.
A worked example with made-up numbers
You post 4 times a week on one platform, and the evergreen share cap is 1 in 4, so 1 evergreen post a week and 3 new ones. With a pool of 18 evergreen posts, one per week, each post returns every 18 weeks, which is 126 days. That is well over the 60 day minimum, but it only gives 3 appearances a year, the maximum, so after a year you need new material.
To run 2 evergreen posts a week and keep the 1 in 4 cap, you need 8 posts a week in total: 2 evergreen and 6 new. With a pool of 18, each post returns every 9 weeks, which is 63 days. That clears the 60 day gap, but it is about 5.8 appearances a year, over the cap of 3. Three appearances a year means a gap of at least 122 days, or about 17.4 weeks, so at 2 a week you need a pool of at least 35 posts, and 36 is a round number: 36 divided by 2 is 18 weeks, or 126 days. The lesson is that the appearance cap, not the gap, decides your pool size. If you cannot build a pool that large, post 1 evergreen a week or raise the cap after your 8 week test.
Measuring: an 8 week test
Run the rotation on one account for 8 weeks and compare with the 8 weeks before. Log weekly:
| Week | New posts | Evergreen posts | Average reach, new | Average reach, evergreen | Unfollows or complaints | Platform warnings |
|---|---|---|---|---|---|---|
| 1 | ||||||
| 2 to 8 | Same columns | |||||
Pass: evergreen posts reach at least half of what a new post does, followers are stable, and there are no warnings. Fail: evergreen reach under a third of new posts, any warning, or comments saying "you posted this already". Stop and retire the offending posts if any fail. Blotato's analytics on Starter record 4 updates per post over 30 days, so read results on a fixed day, such as day 7, for every post, to compare fairly.
Who should skip evergreen automation
Skip it if you have fewer than about 12 truly evergreen posts, since the pool is too small to keep gaps. Skip it if your audience is tiny and sees every post: repeats will be noticed at once. Skip it if your topic changes fast, such as pricing, regulation or news. And skip the automation, not the idea, if you are new: a monthly manual review of your best posts, as in this weekly plan for solopreneurs, does the same job.
How this page was checked
Blotato facts come from its pricing page and its help centre on scheduling, publishing and plan limits. Platform pointers come from Meta's spam policy and TikTok's integrity and authenticity guidelines, and the LinkedIn page and the X pointers should be confirmed on their own pages. The gap and share numbers are my suggestions, not platform rules. Last checked on 21 November 2026 and refreshed every 90 days. Blur Studio has not run the tool itself, so test with the 8 week plan and use Blotato's 7 day trial for the web app before building.
How I'd approach this
I would start by hand, then automate the part that is boring. A sheet and a Monday check is enough for the first month. If you are weighing a tool for the timing side, see Blotato's site for how it handles slots. Week one: on day one pick 12 to 18 evergreen posts and drop anything with a date or price, on day two fill the sheet with core messages and review dates, on day three write the hook prompt and test it on five posts, on day four load the next 2 weeks into your scheduler by hand, and on day five set up the 8 week log. Add the automation in week three, only after the manual run has shown you the gaps work. If you want to talk it through, there are free tools at /free and a free AI brainstorm call at /ai-strategy.
Questions people ask
How often can I repost an evergreen post?
No platform publishes a safe number. As a starting rule I suggest at least 60 days between repeats, no more than 3 appearances a year, and a new opening line each time. Watch your own results and any platform warnings.
Is reposting the same content against platform rules?
It depends on the platform and the volume. Meta bans very high frequency posting, and TikTok says unoriginal or reused content is not eligible for its For You feed. Check each platform's current rules. See the quarterly repurposing guide.
Does Blotato have an evergreen or recycle feature?
Blotato's documentation describes recurring weekly slots and next-free-slot scheduling, but no recycle feature. Keep the rotation in a sheet and use Blotato for timing. See the n8n node guide.
Can AI rewrite my old posts?
Yes, for the opening line. Give it the core message and the last version, and ban new facts. Check every output, since AI can invent numbers.
How many evergreen posts do I need?
Enough that each one returns no sooner than your gap. At 2 a week and a 60 day gap you need at least 18, since 18 divided by 2 is 9 weeks, or 63 days. If you also cap each post at 3 appearances a year, you need about 36.
How do I know a repeat is working?
Compare its reach with the first run and with new posts for 8 weeks. Retire a post whose reach falls below half of its first run twice in a row.
Do I need a paid Blotato plan for this?
For the API flow, yes. Starter is $29 a month, billed monthly, as of November 2026, and the 7 day trial excludes the API. You can also schedule by hand in the web app.
More in this topic: Social media: automation with n8n, Make and Zapier (27 guides) →