Knowledge base

Drip-feeding a run of articles over weeks

Spread a batch of articles across days or weeks instead of posting them all at once, see everything that is queued, and pause, move or cancel any of it.

Posting twenty articles across a network in one afternoon is the clearest sign of automation there is. A campaign writes a run of articles on different subjects and spreads them out over the window you choose, so the network reads like somebody publishing.

Find it at Reach → Content → Schedule.

Setting one up

  1. What should these articles be about? — the standing instruction. Voice, audience, what
  2. the sites are about. It applies to every article in the campaign.

  3. How many articles? — each one is written separately and placed on every site you
  4. choose. Ten articles across twenty sites is two hundred posts.

  5. Topics, one per line — one subject per article. This is what makes a run of ten read
  6. as ten articles rather than ten versions of one. Fewer topics than articles cycles through them; leave it empty and everything is written from the brief alone.

  7. Where should it post? — a site group, read fresh when the campaign is created.
  8. Spread them over how many days? — zero posts them all at once. Anything else spreads
  9. them evenly and shifts each one by a random hour or so.

⭐ The random shift matters more than it looks. Articles landing at exactly 09:00 every three days is a more recognisable pattern than posting them all together — nothing a person does is that regular.

You always see the size of it first

Show me what this will do prices the campaign before anything is created: how many articles, how many sites, how many posts in total, when the first and last land, and every planned article with its subject and its moment. Sites in the group that cannot take a post are listed separately and are not charged for.

Nothing is written until you press Start the campaign, and each article is charged when its turn comes — not all today.

Changing your mind

The queue shows every article and when it lands.

  • Move one to a different day.
  • Pause the queue — everything not yet started is held. Resume whenever you like, and the
  • campaign is re-spread rather than firing its backlog at once.

  • Cancel what is left — the queued articles are dropped.

⚠️ All three act only on articles that have not started. One already being written has already been paid for, and one already published is on your site — pausing or cancelling here does not take a live page down. The screen tells you how many were actually affected, so "paused 8 of 12" is what you see when four were already in flight.

Latest from the blog

What we have been writing about hosting, SEO and running sites at scale.

SEO and Link Building from the Hosting Layer: A 2026 Operator's View

How hosting shapes indexing and link equity in 2026: keeping pages indexed, vetting aged domains before you build on them, link building without a footprint, and an honest line on what infrastructure can and cannot do for SEO.

Read the post →

Making WordPress Fast and Secure: A Performance and Plugin Checklist

A practical checklist for fast, secure WordPress: server-level caching, a per-site object cache, the handful of plugins worth running, keeping the stack current, and the WooCommerce pages you must never cache.

Read the post →

How to Choose Managed Web Hosting in 2026: A Buyer's Guide

What actually separates good managed hosting from a cheap box with a control panel — migrations, backups, isolation, real caching and honest scaling — and how to judge it before you commit.

Read the post →

Read the blog →

Still stuck?

Support is included on every plan, the desk is open 24 hours a day, and you can write to us in any of our 58 languages — we answer you in yours.

Contact support → All articles →