The opposite of a one-shot campaign is a continuous one: a campaign that keeps generating and publishing articles every day, on a steady cadence, without you opening the dashboard. AI Content Generator handles continuous posting natively through the Base data metabox — set the right combination of Articles per day, Time window, Minimum gap between articles, Active days, Fixed times and Jitter, and the campaign runs forever until you pause it or the title queue runs dry.
This tutorial walks through the continuous posting configuration end-to-end: which fields drive cadence, how to spread posts across the publishing day so the blog index doesn’t go dark for hours, the trade-off between Articles per day and the queue replenishment strategy, the Blackout dates field for holidays and editorial pauses, and the operational habits that keep a continuous campaign healthy for months.
By the end you’ll have campaigns that publish 1, 3, 5 or 15 articles per day automatically, with a predictable rhythm, no clustering at the start of the day, and no surprises during weekends or holidays.
The Base data metabox drives cadence
Open any campaign and locate the Base data metabox. Below the Content type / Output status row you’ll find the entire scheduling stack. Every field here interacts with the others; the order in which you set them matters for getting a clean cadence.
Step 1 — Set Articles per day
The most important field. Set the number of articles you want this campaign to produce per active day. 1 for a daily column, 3 for a steady editorial blog, 5 for a busier news-style site, 15 for a high-volume aggregator.
Don’t pick a number bigger than the editorial workload your AI provider’s rate limits and your wallet can sustain. A Gemini Flash campaign at 15 articles per day costs around $10–$15/month; a Claude Opus campaign at 15 articles per day costs $90–$120/month. Match the volume to the budget.
Step 2 — Set the Time window
The Time window field has two parts: a start hour and an end hour. The campaign only publishes inside this window. Outside it, the cron may fire but no article is actually published.
Three sensible defaults. 09:00–17:00 for a daily editorial blog targeting working hours readers. 06:00–22:00 for a news site covering most of the day. 00:00–23:59 for a fully automated aggregator that doesn’t care about reading windows. Match the window to where your audience reads — there’s no SEO benefit to publishing at 3am.
Step 3 — Set Minimum gap between articles
This field is the spam guardrail. It tells the plugin “never publish two articles within N minutes of each other”. Set it to 90 minutes for a small site, 30 minutes for a news site, 15 minutes for high-volume aggregation.
The minimum gap interacts with Articles per day and Time window: if you ask for 10 articles per day in a 6-hour window with a 60-minute gap, the math doesn’t work (10 × 60 = 600 minutes vs 360 minutes available). The plugin compresses the gap automatically but warns you in the campaign editor. Pick numbers that are mathematically compatible.
Step 4 — Toggle Active days
Seven checkboxes, Monday through Sunday. Tick the days the campaign should publish. For most editorial blogs the right answer is Mon–Fri; for news sites Mon–Sun makes sense; for niche evergreen content twice a week (Tue + Thu) often outperforms daily because the index page feels more curated.
Days you untick are completely skipped. If Saturday is unticked and Saturday brings an editorial topic, you’d need to publish manually or shift to a 7-day schedule for that period — there’s no exception system below Active days.
Step 5 — Optionally set Fixed times
The Fixed times field accepts a comma-separated list, e.g. 09:00, 13:00, 18:00. When populated, the campaign publishes at those exact times regardless of the Time window’s distribution logic. The number of fixed times should match Articles per day.
Fixed times are right for anchored editorial moments: a daily 08:00 briefing, a 12:00 lunchtime column, an 18:00 evening read. They’re wrong for high-volume publishing where the audience expects irregular drops. For evergreen content, prefer the Time window + Articles per day combination and let the plugin spread the posts evenly.
Step 6 — Add Jitter for natural rhythm
The Jitter ± minutes field adds randomness to the scheduled times. Set Jitter to 10 and a fixed time of 09:00 becomes “somewhere between 08:50 and 09:10” each day. The post still feels like a 09:00 anchor but the cadence reads as human rather than robotic.
For SEO content Jitter of 10–15 minutes is the sweet spot. For news content with strict timing (a market-open briefing), set Jitter to 0. For high-volume aggregation, set Jitter to 30 or more — the larger the jitter, the more natural the rhythm.
Step 7 — Configure Blackout dates
The Blackout dates field accepts a list of dates (and optionally date ranges) when the campaign should not publish, even if the schedule says it should. Holiday seasons, editorial pauses, big offline events — anything you want to skip without disabling the entire campaign.
Below the field there’s a Catch up missed articles after pause checkbox. Enable it and the campaign tries to publish skipped articles after the blackout ends; disable it and missed slots are simply lost. For SEO-oriented continuous campaigns, enable it; for news content where stale stories don’t matter post-event, disable it.
Keep the queue full
Continuous posting needs a continuous title supply. Two strategies work in practice. Manual title batches: every Friday, paste a list of 20–30 new titles into the Titles (generation & selection) panel. Auto-generated titles: configure the SEO brief (titles) panel with main keywords and let the plugin propose new titles on demand. Most editorial teams converge to a hybrid: auto-generate a batch, manually approve and prune, save the curated list.
The AI Content Generator Logs panel shows you the “titles remaining” count for each campaign. When it drops below 10, replenish. A campaign with zero titles still has the schedule active but doesn’t publish anything — the cron fires uselessly.
Pair continuous posting with the Content calendar
Open AI Content Generator → Calendar at any time to see the next 30 days of scheduled posts for every active campaign. The Calendar respects every field you set in Base data — Time window, Active days, Fixed times, Jitter, Blackouts — and renders them as a visual editorial backlog.
This is also where you spot mistakes. A campaign accidentally configured with 0 Articles per day shows up as empty days on the calendar; a campaign that exceeded its title budget shows yellow warning tiles for the days it ran out. Five minutes per week scanning the calendar catches these before they become editorial gaps.
Troubleshooting
- Articles cluster at the start of the Time window — Minimum gap is too short. Raise it.
- Some days the campaign doesn’t publish anything — that day is unticked in Active days, or it falls in a Blackout range.
- Fixed times are honoured but Jitter doesn’t apply — Jitter is set to 0. Raise it to 10 or higher.
- Catch up checkbox produces a flood of posts after a holiday — disable Catch up for that campaign; missed posts during blackouts are usually better lost.
- Posts disappear from the calendar without explanation — title queue empty. Check the Logs panel for “no title available” warnings.
You’re done
That’s the full continuous posting configuration: set Articles per day, define a Time window aligned with your audience reading hours, configure Minimum gap as a spam guardrail, tick the Active days, optionally pin Fixed times for anchor moments, add Jitter for natural rhythm, configure Blackout dates for holidays. Keep the title queue replenished. Check the Calendar weekly.
From here the campaign runs continuously — for weeks, months, years if you keep feeding it titles. Every Base data field is a lever; tuned together, they produce the steady editorial drumbeat that automated blogs need to compound traffic over time.