Auto Post & Dripfeed
Set the cadence once and let posts and media publish themselves, indefinitely.
Auto post and dripfeed publishes from a content pool on a defined cadence indefinitely, so profiles keep producing updates without anyone refilling a schedule each week.
What it does
Scheduling solves the publishing problem but not the refilling problem. Someone still has to sit down each month and load the queue, and when that person is busy the queue empties, publishing stops, and the profile drifts back to looking dormant. The failure just moves one step upstream.
Dripfeed removes that step. You define a pool of content and a cadence, and publishing continues indefinitely, rotating through the pool rather than consuming it. 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 appropriate for the baseline layer of publishing rather than for time-sensitive promotion. Evergreen content about services, facilities, common questions and what makes each location distinctive rotates well. This week’s offer does not.
The obligation it creates is periodic review. Content set running and forgotten will eventually publish something no longer true — a service you stopped offering, an opening hour that changed, a claim that has aged badly. A quarterly read of the pool is the price of the automation.
Everything Auto Post & Dripfeed gives you
Content pool rotation
Publishing draws from a pool and rotates rather than consuming a finite queue, so it never runs out.
Indefinite cadence
Set the frequency once and publishing continues without anyone reloading the schedule each month.
Repetition control
Rotation is managed so the same item does not reappear too soon within a single location.
Per-location pools
Different locations can draw from different pools, so publishing stays relevant rather than uniformly generic.
Mixed content types
Posts and media rotate together, keeping the profile varied instead of publishing one format repeatedly.
Pause and resume
Pause per location or across the estate without dismantling the configuration.
Pool health warnings
Alerts when a pool is too small for the chosen cadence, which is what causes visible repetition.
Freshness review prompts
Periodic reminders to re-read the pool, so aged content is caught before it publishes wrongly.
Publish reporting
Per-location record of what published and when, so the automation remains auditable rather than opaque.
From setup to first result
- 1
Build the content pool
Write evergreen items — services, facilities, common questions, what makes the location distinctive. Avoid anything time-bound.
- 2
Size the pool to the cadence
At least eight to twelve items per location for weekly publishing, or repetition becomes visible within two months.
- 3
Assign pools to locations
Shared items can span the estate while location-specific content stays with its own site.
- 4
Set the cadence
Weekly is appropriate for most businesses. Higher frequency accelerates repetition without adding benefit.
- 5
Start the rotation
Publishing begins and continues without further input. Confirm the first few weeks land correctly.
- 6
Diarise a quarterly review
Re-read the pool. This is the step that prevents publishing something that has quietly become untrue.
- 7
Layer scheduled posts on top
Use the post scheduler for time-sensitive promotion while dripfeed maintains the baseline.
What changes with Auto Post & Dripfeed
- Building a pool too small for the cadence
- Putting time-sensitive content in the rotation
- Setting it running and never reviewing
- Using one generic pool for every location
- Treating dripfeed as the whole strategy
- Queues empty, rotations do not
- Baseline publishing should not need attention
- Profiles must not go quiet
- Pool size determines whether it works
- It frees attention for what matters
Queues empty, rotations do not
Scheduling still depends on someone refilling it. Rotation removes that dependency entirely.
Baseline publishing should not need attention
Evergreen content about what you do does not benefit from being written fresh each week.
Profiles must not go quiet
A dormant-looking profile costs choices, and dripfeed is the mechanism that guarantees it never happens.
Pool size determines whether it works
A pool too small for the cadence produces visible repetition, which reads worse than posting less often.
It frees attention for what matters
Automating the baseline leaves the team free to write the timely posts that actually need thought.
Automation still needs review
Content set running indefinitely will eventually publish something no longer true unless someone reads it periodically.
What it measures
- Items in each content pool
- Publishing frequency per location
- Time between repeats of an item
- Pool health against cadence
- Items overdue for review
- Publish success rate
What you get out of it
Publishing that never stops
No queue to refill, ever.
No more dormant profiles
Every location stays visibly active.
Repetition managed
Rotation control keeps items from reappearing too soon.
Relevant per location
Different pools for different sites.
Attention freed
The team writes timely posts, not filler.
Still auditable
Full record of what published where.
What Auto Post & Dripfeed produces
Every output is exportable and white-label, with your branding and none of ours.
Content pool
Everything in rotation, per location.
Rotation schedule
What is due to publish and when.
Pool health status
Whether pool size suits the cadence.
Publish history
What published, where and when.
Freshness prompts
Items flagged for review by age.
Pause status
Which locations are currently paused.
Who uses Auto Post & Dripfeed
Publish for many clients from one calendar rather than logging into each profile.
Keep every branch posting consistently without central bottlenecks.
Supply approved content franchisees can publish without going off-brand.
Keep the profile looking active without adding a daily job.
Get more out of it
- Use evergreen content only. Anything time-bound belongs in the scheduler, not the rotation.
- Size the pool to the cadence — eight to twelve items per location for weekly publishing, minimum.
- Diarise a quarterly pool review. This is the single control that prevents publishing something untrue.
- Layer scheduled posts on top for promotions rather than trying to make the rotation carry them.
- Keep some content location-specific. A pool that is entirely generic reads as generic.
- Check pool health warnings, since visible repetition undoes the credibility the automation was buying.
Building a pool too small for the cadence
Publishing weekly from six items means visible repetition within two months, which reads worse than posting fortnightly would have.
Putting time-sensitive content in the rotation
Offers and events publish again months later when they have expired, which actively damages credibility.
Setting it running and never reviewing
Content ages. Eventually the rotation publishes a service you no longer offer or a claim that is no longer true.
Using one generic pool for every location
It reads as generic because it is, and it discards the local specificity that makes a profile post worth reading.
Treating dripfeed as the whole strategy
It maintains the baseline. Timely, specific posts still need writing, and the rotation cannot substitute for them.
Manually vs with Auto Post & Dripfeed
| Doing it manually | With Auto Post & Dripfeed |
|---|---|
| Queue empties when nobody refills it | Rotation continues indefinitely |
| Publishing stops during busy periods | Cadence survives regardless of workload |
| Repetition happens by accident | Repeat intervals managed deliberately |
| One schedule for every location | Per-location pools stay relevant |
| Automation with no audit trail | Full publish history per location |
| Content ages unnoticed | Freshness prompts flag items for review |
- Write evergreen items only
- Build at least eight to twelve per location
- Keep some content location-specific
- Set a weekly cadence
- Confirm the first fortnight published correctly
- Enable pool health warnings
- Diarise a quarterly pool review
Auto Post & Dripfeed is 1 of 42 tools you get
Every tool below is on the same plan at the same price. Nothing here is an add-on, an upgrade, or a separate subscription.
Rank & Visibility
Manage Profiles
Posts & Automation
Reviews & Reputation
Reports & White-Label
Others vs Local SEO Tool
How the usual pricing and packaging in this category compares with ours.
“Other tools” describes the common pattern across the category, not any one named product.
Auto Post & Dripfeed is included on every plan
One flat price per location covers all 42 tools. There is no higher tier, no add-on, and no per-seat charge.
- All 42 tools on every plan
- No per-seat charges
- No setup fee and no contract
- Cancel or change locations any time
Auto Post & Dripfeed questions
What is auto post and dripfeed?
Publishing that draws from a rotating content pool on a set cadence indefinitely, so nobody has to refill a schedule each month.
How is this different from scheduling?
Scheduling consumes a finite queue that someone must refill. Dripfeed rotates a pool, so publishing continues without further input.
How large should the content pool be?
Eight to twelve items per location for weekly publishing. Smaller pools produce visible repetition within a couple of months.
Will content repeat?
Rotation is managed so items do not reappear too soon, but a pool too small for the cadence will still repeat visibly.
Can I pause it?
Yes, per location or across the estate, without dismantling the configuration.
What content works best?
Evergreen material — services, facilities, common questions, what makes the location distinctive. Anything time-bound belongs in the scheduler.
Can I still schedule one-off posts?
Yes, and you should. Dripfeed maintains the baseline while the scheduler handles timely promotion.
Do different locations need different pools?
Ideally yes. A single generic pool across an estate reads as generic and discards local specificity.
How often should I review the pool?
Quarterly. Content ages, and an unreviewed rotation eventually publishes something that is no longer true.
What happens if the pool is too small?
Pool health warnings fire, because visible repetition undermines the credibility the automation was meant to build.
Does it publish media as well as posts?
Yes. Posts and media rotate together so the profile stays varied rather than repeating one format.
Is there a record of what published?
Yes. Per-location publish history keeps the automation auditable rather than opaque.
Can I set different cadences per location?
Yes, though weekly suits most businesses and higher frequencies mostly accelerate repetition.
Will this look automated to customers?
Not if the pool is well sized and the content is genuinely useful. It looks automated when items repeat too soon.
Does automated posting affect rankings?
Posts rarely affect position directly. They affect whether a profile looks active to someone choosing between options.
What is the biggest risk?
Publishing something that has become untrue. The quarterly review exists specifically to prevent that.
How soon does it start publishing?
From the cadence you set, typically within the first week. Confirm the first fortnight landed correctly.
Can I mix scheduled and dripfeed posts?
Yes, and that combination is the recommended setup — baseline rotation plus timely scheduled posts on top.
Does it work across hundreds of locations?
Yes. Pools and cadences are assigned per location or group, and publishing runs at estate scale.
What should I put in the pool first?
Your services, one item each. That alone usually fills a pool adequately and is genuinely useful content.
Every tool. One price. No add-ons.
$5.33 per location per month gets you Auto Post & Dripfeed and the other 41 tools.