Guides

Post Scheduling Guide

Blogree's scheduling system lets you write posts now and publish them at the optimal time — across any timezone, across all your connected sites simultaneously. This guide covers everything from basic scheduling to advanced calendar management strategies.

Timezone-aware
Publish at the right local time globally
📅
Bulk scheduling
Queue multiple posts at once
🔄
Auto-retry
Failed deliveries retried automatically

1. Scheduling a Post from the Dashboard

After writing or generating your post, click Schedule instead of Publish Now in the post editor.

  1. In the post editor, click the dropdown arrow next to Publish Now
  2. Select Schedule for Later
  3. Pick a date and time using the calendar picker
  4. Select the timezone (defaults to your account timezone)
  5. Choose which connected site(s) to publish to
  6. Click Confirm Schedule
For best engagement, schedule posts Tuesday–Thursday between 9–11 AM in your audience's local timezone. Blogree's analytics shows delivery-time performance per site.

2. Scheduling via API

Use the scheduled_at field in the Posts API to schedule programmatically. The value must be an ISO 8601 datetime string in UTC.

POST /api/posts Authorization: Bearer <your_jwt_token> Content-Type: application/json { "title": "10 Best AI Blogging Tools in 2026", "body": { "html": "<p>...</p>", "markdown": "..." }, "status": "scheduled", "scheduled_at": "2026-04-10T09:00:00Z", "site_ids": ["site_abc123", "site_def456"], "meta": { "title": "SEO Title Here", "description": "Meta description...", "og_image": "https://cdn.example.com/image.jpg" }, "tags": ["AI blogging", "content automation"] }

Response

{ "id": "post_xyz789", "status": "scheduled", "scheduled_at": "2026-04-10T09:00:00Z", "sites": [ { "id": "site_abc123", "name": "My Tech Blog", "status": "pending" }, { "id": "site_def456", "name": "Agency Client Site", "status": "pending" } ], "created_at": "2026-04-02T14:30:00Z" }

3. Timezone Management

Blogree stores all scheduled times in UTC internally. When you schedule via the dashboard, the UI converts your local time to UTC automatically. Via the API, always send UTC timestamps.

Setting your account timezone

Go to Settings → Profile → Timezone in the Blogree dashboard. This affects how times are displayed throughout the UI.

Per-site timezone targeting

If you're publishing to sites with audiences in different regions, use the site_timezone_override parameter to schedule relative to each site's audience timezone:

{ "scheduled_at": "2026-04-10T09:00:00Z", "site_schedules": [ { "site_id": "site_us", "publish_at_local": "09:00", "timezone": "America/New_York" }, { "site_id": "site_uk", "publish_at_local": "09:00", "timezone": "Europe/London" }, { "site_id": "site_pk", "publish_at_local": "09:00", "timezone": "Asia/Karachi" } ] }
💡
When using site_schedules, the top-level scheduled_at is ignored. Each site publishes at 9 AM in its respective local timezone.

4. Viewing and Managing the Calendar

Navigate to Posts → Calendar in the dashboard to see all scheduled posts laid out on a monthly or weekly calendar view. From the calendar you can:

  • Click any scheduled post to edit the content or reschedule it
  • Drag-and-drop posts to different time slots (Pro and Agency plans)
  • Filter by site to see per-site publishing schedules
  • Export the calendar as a CSV content calendar
  • Identify gaps in your publishing frequency

5. Rescheduling and Cancelling

Rescheduling a post

PATCH /api/posts/:id { "scheduled_at": "2026-04-15T14:00:00Z" } // Response { "id": "post_xyz789", "status": "scheduled", "scheduled_at": "2026-04-15T14:00:00Z" }

Cancelling a scheduled post

PATCH /api/posts/:id { "status": "draft" } // Post is returned to draft state with scheduled_at set to null

6. Bulk Scheduling (Agency Plan)

Agency plan users can schedule up to 50 posts at once via the bulk schedule API endpoint or the dashboard's bulk upload feature.

POST /api/posts/bulk-schedule { "posts": [ { "title": "Post 1", "topic": "AI content strategy", "scheduled_at": "2026-04-10T09:00:00Z", "site_ids": ["site_abc123"] }, { "title": "Post 2", "topic": "WordPress SEO tips", "scheduled_at": "2026-04-12T09:00:00Z", "site_ids": ["site_def456"] } ], "generate_with_ai": true } // Blogree generates AI content for each topic and schedules the posts // Returns array of created post objects
Combine bulk scheduling with our topic discovery API to fully automate your content calendar. Fetch trending topics → generate posts → schedule them — all in one pipeline.

7. Delivery Behavior for Scheduled Posts

When a scheduled post's time arrives, Blogree's delivery engine executes the following:

  1. Finalizes the post content and meta fields
  2. Sends a signed HMAC-SHA256 webhook to each connected site
  3. Waits for 200 OK confirmation from your site
  4. On failure: retries after 30 seconds, then 5 minutes, then 30 minutes
  5. Updates delivery status in your analytics dashboard in real time
  6. Sends email notification if all retry attempts fail

8. Best Practices for Scheduling

  • Space posts at least 2–3 days apart per site to avoid Google crawl budget issues
  • Use the analytics dashboard to find which days/times drive the most traffic per site
  • Schedule evergreen content for off-peak hours; trending content for peak hours
  • Always have at least 2–3 posts scheduled ahead to maintain publishing consistency
  • Test webhook delivery before scheduling with the built-in delivery test tool
  • For agency clients, use per-site scheduling to match each audience's timezone