Released
Recurring weekly publishing slots in Blog — available in the admin → Blog → Schedule view as of May 25, 2026.
What changed
Before this release, scheduling a blog post meant opening each draft, picking a date and time manually, and saving. For a team publishing once a week every week, that's a per-post ritual with no shared cadence — and nothing preventing two authors from scheduling on top of each other. There was no calendar surface to show what was queued, what was empty, or whether two posts had been assigned to the same day. The only way to check was to scan the posts list, filter by status, and mentally reconstruct the week.
Recurring slots change the model. Define a slot once — day of week + time — and it repeats indefinitely on the calendar. The slot exists whether or not a draft is assigned to it. Drag a draft post into any open slot and it inherits that date and time automatically. The week-at-a-glance calendar shows every slot — filled and empty — so the full publishing pipeline is visible without any reconstruction work.
The gap becomes as visible as the content. An empty Tuesday slot at 9:00 AM on the calendar is the editorial signal: something needs to go there. The prompt arrives before the Monday-morning scramble, not after.
The workflow
Step 1 — Create a slot
Navigate to the admin → Blog → Schedule view. Select Recurring slots from the top tab row. Click New slot, choose a day of the week and a time, then save.
The slot appears on the calendar immediately. Repeat for as many weekly slots as needed — a multi-author site might run three: Monday morning for news, Wednesday mid-day for how-tos, Friday afternoon for roundups.
Step 2 — Assign drafts to slots
Return to the week-at-a-glance calendar. Drag any draft post card from the left panel into an open slot. The post inherits the slot's scheduled date and time.
A slot occupied by a draft shows the post title, author, and category. An empty slot is a visible gap — the editorial gap, not a hidden one.
Step 3 — Review and publish
Slots with drafts assigned auto-publish at the scheduled time. No further manual action required. The post moves from Draft to Published at the slot's time; the slot clears and is ready for the next assignment.
Who this is for
Editorial teams with a regular cadence. If the answer to "when does this publish?" is always "Tuesday 9 AM," define it once and stop re-entering it.
Multi-author blogs. Slots make the shared calendar visible. Two authors can see which slots are taken before they drag — no more accidental collision, no more "who published on my day."
Multi-site brands with a shared rhythm. Each site in the account has its own slot set. A brand running three regional blogs on the same weekly drumbeat configures the slots per site and manages each calendar independently from the same dashboard.
Managing slots
Slots can be edited or deleted at any time from the Recurring slots tab. Editing a slot (e.g. moving Tuesday 9:00 AM to Tuesday 10:00 AM) updates all future instances. Posts already assigned to future slots update their scheduled time automatically. Posts that have already published are not affected.
Deleting a slot removes it from the calendar going forward. Posts assigned to future instances of that slot revert to Draft status — they are not deleted, and they retain all their content. The posts list flags them with a "slot removed — reschedule" indicator so they surface in the editorial queue.
A slot can also be paused — it stays on the calendar as a placeholder but will not auto-publish even if a post is assigned. Useful for planned breaks (holidays, content freezes) without losing the slot structure.
Permissions
Creating, editing, and deleting recurring slots requires the Editor role or higher. Authors can assign drafts to open slots but cannot create or modify the slot definitions themselves. This keeps the publishing cadence set by editorial leads and lets contributors fill the queue without changing the structure underneath it.
What stays the same
Existing scheduled posts are unchanged. Posts scheduled before this release keep their manually set dates and times — they do not migrate into slots. Recurring slots are opt-in: sites that never define a slot see no change to their Blog workflow.
Manual per-post scheduling (open post → set date → save) still works as before. Slots are an additive layer on top, not a replacement.
Example: SGEN Digital
SGEN roastery blog publishes every Tuesday at 9:00 AM — product spotlights, how-to guides, seasonal releases. Before recurring slots, the editor opened each draft on Monday, manually entered the Tuesday date, and saved. Multiply that by 52 weeks, three active draft writers, and occasional guest contributors who forgot to set a date at all.
With a Tuesday 9:00 AM slot defined, the workflow is: finish the draft, drag it to next Tuesday's slot, done. The calendar shows the next four Tuesdays at a glance. An empty Tuesday is a signal to accelerate a draft in progress, not a surprise discovered on Monday morning.
Where to find it
the admin → Blog → Schedule view → Recurring slots tab.
Recurring slots are available on all plans that include the Blog module.
Related documentation
- Blog reference — full feature catalog for the Blog module, including schedule settings, categories, and author management.
- Publishing lifecycle — concept guide covering draft → review → scheduled → published states and how automated scheduling fits the flow.