Auto Post & Dripfeed
Set the rhythm once and let posts and photos publish themselves, for as long as you want.
A dripfeed publishes from a pool of content on a rhythm you set. It rotates through the pool rather than using it up, so publishing carries on without anyone reloading a queue each month.
What it does
Scheduling fixes the publishing problem but not the refilling problem. Somebody still has to sit down each month and load the queue. When that person is busy the queue empties, publishing stops, and the profile drifts back to looking dormant. The failure has just moved one step upstream.
A dripfeed removes that step. You build a pool of content and set a rhythm, and publishing carries on for as long as you want, rotating through the pool rather than using it up. The queue does not empty because it is not a queue. It is a rotation, and rotations do not run out.
This is genuinely hands off in a way scheduling is not, which makes it right for the baseline layer of publishing and wrong for anything time sensitive. Evergreen content about your services, your facilities, common questions and what makes each site different rotates well. A limited offer running this week does not.
The one thing it asks of you is a look every so often. Content left running and forgotten will eventually publish something that has aged badly. A quarterly read of the pool is the whole maintenance job.
Everything you get
A pool, not a queue
Publishing draws from a pool and rotates, so it never runs out and nobody has to reload it.
Set the rhythm once
Choose the frequency and publishing carries on without anyone touching the schedule each month.
Repetition control
The rotation is managed so the same item does not come back round too soon at one location.
A pool per location
Different sites can draw from different pools, so what publishes stays relevant instead of generic everywhere.
Posts and photos together
Both rotate, so the profile stays varied rather than showing one format over and over.
Pause and restart
Pause a location or the whole estate without taking the setup apart.
Pool too small warnings
An alert when a pool is too small for the rhythm you picked, which is what causes visible repetition.
Review reminders
A prompt to read the pool again now and then, so nothing ages badly in public.
Activity log
Every automatic publish recorded, so this is not a black box.
From setup to first result
- 1
Pick evergreen content only
Services, facilities, common questions, what makes each site different. Nothing with a date in it.
- 2
Build a pool big enough
Too small and the repetition becomes obvious. The warning tells you when it is.
- 3
Set a pool per location where it matters
Generic everywhere is the failure mode. A site with its own character should have its own pool.
- 4
Choose the rhythm
Weekly suits most. This is a baseline layer, not a campaign.
- 5
Let it run
This is the point. No monthly reload and no reminder in the diary.
- 6
Read the pool each quarter
Take out anything that has aged. This is the entire maintenance job.
- 7
Use scheduling for anything dated
Offers and events belong in the scheduler, not the rotation.
What changes when you use it
- Putting dated content in the pool
- A pool too small for the rhythm
- One generic pool for every site
- Setting it and never reading it again
- Automating the judgement work
- Scheduling still needs somebody
- A rotation does not run out
- A baseline is worth more than a campaign
- It frees attention for the work that needs it
- Repetition is the real risk
Scheduling still needs somebody
A queue has to be refilled. When the person refilling it gets busy, publishing stops and you are back where you started.
A rotation does not run out
Because it draws from a pool rather than working through a list, publishing carries on for as long as you want.
A baseline is worth more than a campaign
A profile that always has something recent beats one with a great month followed by silence.
It frees attention for the work that needs it
Automating the routine layer is what leaves time for replies, offers and anything that needs a person.
Repetition is the real risk
A pool too small for the rhythm shows the same item too often, and readers notice.
Dated content ages in public
A rotation will happily republish something that made sense last year. A quarterly read prevents that.
What it measures
- Items in each pool
- Publishing frequency per location
- How often an item comes back round
- Locations with a pool too small for the rhythm
- Days since the pool was last reviewed
- Automatic publishes that failed
Reports you can send
Every output can be exported and carries your branding, never ours.
Content pool
What is in rotation, by location.
Publishing schedule
What goes out where, and when.
Rotation history
What has published and how recently.
Pool health warning
Where the pool is too small for the rhythm.
Review prompt
A reminder to read the pool for aged content.
Activity log
Every automatic publish, dated.
Who this is built for
Keep every client profile publishing without a monthly reload for each one.
A baseline layer running at every site, including the quiet ones.
Approved evergreen content rotating at every franchisee profile.
Set it up once and have a profile that always looks current.
Get more out of it
- Only put evergreen content in the pool. Anything with a date belongs in the scheduler.
- Make the pool big enough for the rhythm, or the repetition becomes obvious.
- Give a site its own pool where it genuinely differs from the rest.
- Read the pool every quarter and take out anything that has aged.
- Use the dripfeed for the baseline and the scheduler for offers and events.
- Act on the pool health warning rather than ignoring it.
Putting dated content in the pool
A rotation will happily republish an offer that ended last spring. Anything with a date belongs in the scheduler.
A pool too small for the rhythm
Weekly publishing from six items shows the same thing every six weeks, and readers notice.
One generic pool for every site
The point of the rotation is that it keeps running. If what it publishes is generic, it keeps running and says nothing.
Setting it and never reading it again
Content left alone for two years will eventually publish something that has aged badly in public.
Automating the judgement work
Replies, complaints and anything sensitive need a person. The rotation is for the baseline layer only.
By hand, or with this
| Doing it manually | With Auto Post & Dripfeed |
|---|---|
| A queue somebody reloads each month | A pool that rotates and never empties |
| Publishing stops when somebody is busy | Publishing carries on regardless |
| The same generic content everywhere | A pool per location |
| Repetition nobody spots until a customer does | A warning when the pool is too small |
| Content that quietly ages in public | A quarterly review prompt |
| A black box | Every automatic publish logged |
- Gather evergreen content only
- Check the pool is big enough for the rhythm
- Set separate pools where locations really differ
- Choose a weekly rhythm to start
- Turn on the pool health warning
- Put a quarterly read of the pool in the diary
- Keep offers and events in the scheduler instead
One of 42 tools on the same plan
Every tool below is on the same plan at the same price. Nothing here is an extra, an upgrade or a separate subscription.
Rank & Visibility
Manage Profiles
Posts & Automation
Reviews & Reputation
Reports & White-Label
Questions people ask
What is a dripfeed?
Publishing that draws from a pool of content on a rhythm you set, rotating through it rather than using it up. The queue never empties because it is not a queue.
How is this different from scheduling?
A schedule is a list somebody refills each month. A rotation carries on by itself. Scheduling is right for dated content, and a dripfeed is right for the baseline layer.
What should go in the pool?
Evergreen content only. Services, facilities, common questions, what makes each site different. Nothing with a date attached.
How big does the pool need to be?
Big enough that items do not come back round quickly at your chosen rhythm. You get a warning when it is too small, which is the usual cause of visible repetition.
Can different locations publish different things?
Yes. Give a site its own pool where it genuinely differs. One generic pool everywhere keeps publishing and says very little.
Do I ever have to touch it?
Once a quarter. Read the pool and take out anything that has aged. That is the whole maintenance job.
What should never be automated?
Anything needing judgement. Review replies, complaints and anything sensitive. The rotation is for routine publishing only.
Every tool. One price. Nothing extra to buy.
$5.33 per location per month gets you Auto Post & Dripfeed and the other 41 tools.