Most social content has a lifespan of about a day. You write something good, it reaches a fraction of your audience, and then it’s gone.
Evergreen scheduling is the response: a library of content that still holds up, republishing on a rotation so it keeps reaching the people who weren’t there the first time.
What “evergreen” actually means
Not “old”. Not “performed well”. It means still true and still useful to someone reading it for the first time today.
That’s a stricter test than it sounds, and applying it honestly is most of the work. A post can be your best-performing ever and completely unsuitable, because it was about something happening that week.
Building the library
Start smaller than you think. Ten to twenty genuinely good posts is a working rotation. A hundred mediocre ones is a feed nobody reads.
Choose by usefulness, not by performance. An old post that got a lot of engagement because of its timing will not get it again.
Group by theme. If a rotation is all the same kind of post, it reads as a loop even when the individual posts are fine. Mix explainers, opinions, invitations and operational facts.
Rewrite as you add. The version you wrote a year ago was written for a moment. Writing it again for a general reader usually produces something better, and it means nobody sees a duplicate.
Setting the rotation
The mechanics are recurring schedules:
| Frequency | Publishes |
|---|---|
| Daily | Every day |
| Weekly | Once a week |
| Biweekly | Every two weeks |
| Monthly | Once a month |
- Free: not included
- Pro: 10 recurring schedules
- Business: unlimited
For most accounts, monthly or biweekly per item, spread so they don’t cluster, keeps a rotation invisible. Daily is almost always too often for the same piece of content.
The overall proportion matters more than any individual frequency: evergreen content should supplement what you’re publishing, not replace it. Once it’s the majority of the feed, people can tell.
The maintenance nobody does
This is where evergreen scheduling goes wrong, and it’s not a technical failure.
A rotation is set up once, works, and then runs unattended for a year. During that year the product changes, the team changes, opinions change, and the rotation keeps publishing the old version.
Put a quarterly review in your calendar. Read the whole set and ask, for each one, whether you’d post it today. Some get rewritten, some get removed.
Never include a number. Prices, limits, headcount, feature counts. A number in a rotating post is a factual error waiting to publish itself, and nobody is watching when it does.
Be able to pause everything. On the day something bad happens, a cheerful automated post is the thing you’ll remember. Know how to stop it, and check you still know.
What belongs and what doesn’t
Belongs: explainers, how-tos, the post that says what you do, standing invitations, opinions you still hold, operational facts.
Doesn’t: announcements, anything with a date, anything referencing news, anything with a figure, replies, and anything you’ve changed your mind about.
Setting it up
Media attached to a recurring post is kept rather than cleaned up after publishing, since the rotation needs it again.
BulkPublish publishes to 15 platforms.
- Recurring schedules: Free: none. Pro: 10. Business: unlimited.
- Channels: Free: 3 (1 per platform). Pro: 30 (2 per platform). Business: 75 (5 per platform).
- Posts: Free: 3/day. Pro: 30/day. Business: unlimited.
The short version
Build a small library of things that are still true, rewrite rather than repost, rotate monthly or biweekly rather than daily, and keep it a minority of your output. Then put a quarterly review in your calendar, because the failure mode isn’t a bad post, it’s a good post that stopped being true while nobody was looking.