You’ve got an edit ready for a post that’s already live. It might be a price change for Monday, an announcement that can’t go out before an embargo lifts, or a seasonal rewrite. You’d like it to go live at a set time without you sitting at the keyboard. WordPress schedules new posts easily, so it seems like it should handle this too.
It doesn’t. Core WordPress has no way to schedule a change to a post that’s already published. And the obvious workaround, setting a future date on the published post, does something most people don’t expect.
The date trick that takes your post offline
Open a published post, set its publish date to next Monday, and save. You might expect that to mean “apply this edit on Monday.” What WordPress actually does is reschedule the whole post.
When a post’s date is in the future, WordPress gives it the status future instead of publish, and only published posts are shown to visitors. So the moment you save, the post disappears from your blog page, category archives, feeds and search results, and anyone opening its URL gets a “not found” page. It comes back on Monday, carrying Monday as its publish date, so it can also move out of its old place in date-ordered lists. If your permalinks include the date, the URL changes too, and every link pointing at the old one breaks.
For a post that’s getting traffic or has links pointing at it, that’s the opposite of what you wanted. If you’ve already done this by mistake, set the date back to the original and update the post, and it will be published again straight away.
Why WordPress can’t do this on its own
A WordPress post is one record with one current version. Revisions keep a history of earlier versions so you can roll back, but there’s no built-in idea of a pending version that goes live later while the current one stays up. Scheduling only works at the level of the whole post: it’s either published or waiting to be. To schedule an edit, you need something that stores the new version separately and swaps it in at the right time.
Option 1: a plugin that schedules revisions
This is the clean solution. The best-known free option is PublishPress Revisions. You open a published post, make your changes, and save them as a revision instead of updating the live post. The live post stays exactly as it is. You give the revision a future date, and at that time the plugin copies the new content into the original post, on the same URL.
Two details matter. The free version handles standard WordPress content, while fields added by other plugins (page builders, SEO plugins, custom fields, WooCommerce product data) need the paid version, so check that the part you’re changing is covered. And like WordPress’s own scheduled posts, it runs on WP-Cron, WordPress’s built-in task scheduler. If your scheduled posts ever go out late or show “Missed schedule”, scheduled revisions will have the same problem. Our guide to scheduled posts not publishing covers why that happens and how to fix it.
Option 2: schedule a status change, not an edit
Sometimes the change you want isn’t new text. You want a post to disappear on a certain date, move to a different category, or go back to draft when an offer ends. That’s a different job, and a lighter plugin covers it. PublishPress Future lets you set an action and a date on a post: unpublish it, trash it, change its status, or add and remove categories. It doesn’t touch the content itself, which is exactly why it’s simpler to trust for expiring posts.
Option 3: duplicate and swap, and why it usually backfires
A common workaround is to duplicate the post, make the edits on the copy, and schedule the copy. The problem is that the copy is a separate post with its own URL. When it publishes, you have two versions of the same article live at once, and the new one has none of the original’s links, search history or comments. To avoid that you’d have to copy the new content back into the original and delete the duplicate by hand at the right moment, at which point nothing was really scheduled. A revisions plugin does that swap for you, on the original URL.
Option 4: for a one-off, just do it by hand
If this is a single edit you’ll make once, a plugin may be more than you need. Write the updated text somewhere safe ahead of time, set yourself a reminder, and paste it in when the time comes. Don’t park the edit inside WordPress by saving the live post early. There’s no separate draft of a published post in core WordPress, so saving publishes the change immediately.
Before you rely on a scheduled update
- Test it on a low-stakes post first. Schedule a small visible change a few minutes ahead and confirm it appears.
- Check your caching. If your site uses page caching, visitors can keep seeing the old version after the update has applied, until the cache for that page is cleared. Most caching plugins clear a post’s cache when it’s updated, but confirm yours does it for scheduled changes too.
- Check WP-Cron is reliable. On a quiet or heavily cached site, scheduled tasks can run late. A real server cron job fixes that for posts and revisions alike.
Quick picks
- Schedule an edit to a live post, same URL: a scheduled-revisions plugin such as PublishPress Revisions.
- Unpublish, trash, or recategorize a post on a date: PublishPress Future.
- A single edit you’ll only make once: prepare it ahead and paste it in by hand.
- Tempted to change the publish date instead: don’t. It takes the post offline until that date.
Etienne Basson works with website systems, SEO-driven site architecture, and technical implementation. He writes practical guides on building, structuring, and optimizing websites for long-term growth.