
WordPress scheduled posts don’t publish themselves. They wait for someone—anyone—to visit your site, trigger wp-cron.php, and check whether any tasks are due. If traffic is light or your server is slow, a post scheduled for 9:00 AM can sit in limbo until 9:47 AM when the next visitor arrives.
This isn’t a bug. It’s how WordPress cron works by default. Understanding the mechanics helps you decide whether to live with the lag or route around it.
Why WordPress cron misses the mark
Traditional cron is a time-based job scheduler built into Unix-like operating systems. It runs tasks at exact intervals regardless of traffic. WordPress cron is a PHP script that simulates cron by checking for due tasks every time a page loads.
When a visitor requests a page, WordPress fires wp-cron.php in the background (technically a non-blocking HTTP request to itself). That script queries the database for any scheduled events—posts, plugin tasks, update checks—with a timestamp earlier than time(), then executes them.
If no one visits between 9:00 AM and 9:47 AM, no cron check happens. Your post waits. The WordPress Plugin Developer Handbook (checked November 2026) describes this as “visitor-triggered cron,” and notes it can cause delays on low-traffic sites.
High-traffic sites rarely notice. A page load every few seconds means wp-cron fires often enough that the delay stays under a minute. Solo operators publishing at dawn before reader traffic starts see the gap widen.
Diagnosing missed schedules
Check whether wp-cron is running at all. Install the free WP Crontrol plugin (available in the WordPress.org repository, checked November 2026). It lists every scheduled event, shows when it last ran, and lets you trigger cron manually.
Look for the publish_future_post hook. If a post is stuck in “Scheduled” status and the hook timestamp is in the past, wp-cron hasn’t fired since the target time.
Three common causes:
- No traffic. Your site got zero page views in the window after publish time.
- Server timeout. wp-cron.php takes too long and your host kills the process before tasks finish.
- Broken loopback. WordPress can’t POST to itself (firewall rules, local DNS misconfiguration, or a security plugin blocking the request).
WP Crontrol will show a warning if it detects a broken loopback. You’ll also see PHP errors in your server logs referencing wp-cron.php if timeouts are the culprit.
Three ways to fix it
Option one: disable wp-cron and use real cron. Add define('DISABLE_WP_CRON', true); to wp-config.php, then set a server cron job to request wp-cron.php every minute. Most shared hosts (including BigScoots) offer cron job panels in cPanel or Plesk.
Your cron command looks like this:
*/1 * * * * wget -q -O - https://yoursite.com/wp-cron.php?doing_wp_cron >/dev/null 2>&1
or with curl:
*/1 * * * * curl -s https://yoursite.com/wp-cron.php?doing_wp_cron >/dev/null 2>&1
This guarantees wp-cron runs every sixty seconds regardless of traffic. The WordPress Advanced Administration guide (checked November 2026) recommends this approach for mission-critical scheduling.
Option two: spawn wp-cron on a delay. If you can’t access server cron, install a plugin like WP Crontrol or Advanced Cron Manager (both free, WordPress.org repository, checked November 2026) and set a recurring event that pings wp-cron.php via HTTP every few minutes. This still depends on some traffic to bootstrap the loop, but reduces lag.
Option three: accept the delay and pre-schedule. If your traffic patterns are predictable—readers arrive after 10:00 AM—schedule posts for 9:50 AM instead of 10:00 AM. The first wave of visits will trigger publication a few minutes early, and readers won’t notice.
When the fix breaks something else
Switching to real cron can expose poorly-written plugins. Some plugins assume wp-cron fires approximately on time and use loose logic to prevent double execution. When cron becomes punctual, race conditions surface: two tasks fire simultaneously, database locks collide, or duplicate emails go out.
Test on staging first. Disable all plugins except WP Crontrol, enable real cron, then reactivate plugins one at a time while monitoring the cron event log. Any plugin that schedules hourly or daily tasks is a candidate for conflict.
You’ll also burn more server resources. wp-cron.php on a busy site can fork dozens of background tasks. Running it every minute via server cron adds consistent load. If your host enforces process limits, you may hit them faster.
Most managed WordPress hosts (Kinsta, WP Engine, Flywheel) already disable wp-cron and run real cron for you. Check your host’s documentation before adding a duplicate cron job—you might already have one running without knowing it.
Have a WordPress ops question we should cover? Reply to this email or subscribe below to catch the next deep dive.
