Pro feature · Content Scheduling
Plan a steady publishing rhythm—and know when WordPress needs help.
Turn an approved article batch into a clear publication calendar. Choose the frequency, distribution and local timezone, preview every slot, and let SitePublisher AI monitor the result after it reaches WordPress.
SitePublisher AI Pro · Timezone-aware planning · Missed-schedule recovery
A calmer content calendar
Publish consistently without assigning every date by hand
Content Scheduling converts editorial rules into exact WordPress publication times. The same approved plan always produces the same preview, so what you review is what enters the queue.
Choose the right frequency
Schedule from one to thirty articles per day, week or month and let the planner create enough slots for the complete batch.
Work in the local timezone
Define each scheduling block in the timezone that matters to the audience. SitePublisher AI converts the approved times for WordPress delivery.
Control the distribution
Spread articles evenly across each period or use a stable varied distribution for a less mechanical publishing pattern.
Change pace over time
Add multiple scheduling blocks when a launch phase, seasonal campaign or long-term editorial calendar needs a different frequency later.
Preview exact dates first
See the publication time for every title and the calculated finish date before any article is generated or sent to WordPress.
Plan per destination
Combine scheduling with a separate Website Profile and WordPress category for each connected website.
Explore Multi-Site Management →Date-range scheduling
Describe the rhythm. Let the planner calculate the calendar.
Scheduling is part of Bulk Content Automation. Every block starts a publication rule; a later block replaces the previous rule, and the final block continues until every approved title has a slot.
Choose WordPress scheduling
Prepare the article titles and destination, then select date-range scheduling when WordPress should receive future posts with approved publication dates.
Add the first schedule block
Set its local start date and time, timezone, number of articles, period—day, week or month—and even or varied distribution.
Add later phases when needed
Use another block to change the publishing pace from a specific moment. SitePublisher AI orders the rules and calculates a unique slot for every title.
Preview and approve the calendar
Review every title, WordPress time and final finish date. Any form change invalidates the old preview and requires a fresh approval.
Generation and WordPress delivery begin only after you explicitly approve and add the exact previewed plan to the Priority queue.
Two timing controls
Schedule the work—or schedule the WordPress publication
SitePublisher AI separates queue timing from the public publication date. That distinction keeps manual review workflows and automatic editorial calendars equally clear.
Control when generation runs
Choose a starting time and interval between queue jobs. Results remain available for review and publication decisions after processing.
- Useful for paced background generation
- Priority still controls due-job order
- Publication can remain manual
Assign public publication slots
Use date-range rules to generate the articles and create them as future posts on the selected WordPress destination.
- Exact dates visible before approval
- Website timezone handled explicitly
- Reliability status stays in the queue
Scheduled Publication Reliability
A second layer after WordPress receives the schedule.
WordPress future posts normally publish through its cron system. SitePublisher AI adds destination-level serialization, status monitoring and controlled recovery when that normal event is missed.
Protect simultaneous schedules
- Final post writes are serialized per destination
- Other destinations can continue independently
- Approved publication times stay attached to jobs
Check after publication time
- A watchdog waits through a ten-minute grace period
- Normal, pending and failed checks stay visible
- Automatic connection retries are limited
Publish only when appropriate
- An overdue future post can be recovered
- A later manual reschedule is respected
- Every non-future WordPress status remains authoritative
Queue visibility
See the real publication state, not just the original plan
The Priority queue shows the intended WordPress time alongside the observed result. This makes normal publication, delayed checks, manual changes and recovered schedules distinguishable.
Published normally
WordPress completed the future-post event and the queue records that the scheduled article is live.
Still scheduled
The remote post remains a valid future post—for example because its date was deliberately moved later—and no forced publication occurs.
Recovered
The approved date passed while WordPress still reported an overdue future post, so the recovery service published it and recorded the outcome.
Frequently asked questions
Scheduling, clearly explained
Plan publication with confidence while keeping WordPress and human editorial changes in control.
Is Content Scheduling included in Free?
No. Automatic scheduling and recovery are Pro features. Free supports creating and publishing a Single Article on the local WordPress website.
Can I use different publishing frequencies in one batch?
Yes. Add later schedule blocks to change the frequency, period, distribution or timezone from a specific start moment. Up to twelve valid blocks can be used in one plan.
What is the difference between even and varied distribution?
Even distribution spaces the available publication slots predictably across each period. Varied distribution uses a stable randomized spread, so the preview remains reproducible after approval.
What happens if WordPress misses a publication?
After a ten-minute grace period, SitePublisher AI can check the remote status. If the article is still an overdue future post, it can publish it and record the schedule as recovered.
Will recovery override a manual WordPress change?
No. A later scheduled date is respected, and any status other than future is treated as an intentional WordPress-side change rather than something to force.
Does the watchdog replace reliable WordPress cron?
No. It is an additional safety layer. For time-sensitive publishing, a real server cron on the central and destination websites remains the strongest foundation.
Plan with confidence
Turn a content backlog into a dependable publishing calendar.
Choose SitePublisher AI Pro to combine bulk creation, flexible WordPress scheduling and visible recovery controls across your connected websites.