Post Date Freeze stops small edits from bumping a post’s last-modified date. Freeze dates across your whole site, then let individual posts update their date when you actually mean it.
Before you start
- WordPress 5.8 or later
- PHP 7.0 or later
The per-post toggle lives in the block editor. If you use the Classic Editor, the site-wide setting still applies, but you won’t see the per-post toggle.
Install
- In your WordPress dashboard, go to Plugins → Add New Plugin.
- Click Upload Plugin.
- Choose the plugin zip file.
- Click Install Now.
- Click Activate.
That’s it. As soon as the plugin is active, modified dates are frozen site-wide. Editing and saving a post keeps its existing last-modified date.
How to use
Update the modified date on one post
Made a real update and want the date to show it? Unfreeze that post for one save.
- Open the post in the block editor.
- In the post settings sidebar, find the Date Freeze row. It shows Frozen with a lock icon.
- Click Frozen to open the options.
- Choose Not Frozen (“On the next save only, update the modified date to today.”).
- Save or update the post.
The modified date updates on that save. After the save, the post goes back to following the site-wide setting, so your next small edit stays frozen.
Keep one post frozen when freezing is off
If you’ve turned freezing off site-wide (see Settings below), you can still freeze a single save.
- Open the post in the block editor.
- In the Date Freeze row, click Not Frozen.
- Choose Frozen (“On the next save only, modified date stays the same.”).
- Save or update the post.
Like the other direction, this applies to the next save only. Afterward the post follows the site-wide setting again.
Settings
Go to Settings → Post Date Freeze. You need to be an administrator (the manage_options capability) to see this page.
- Disable Date Freeze: check Allow post modified dates to update (disable freezing) to turn freezing off site-wide, so saves update the modified date like normal WordPress. Default: unchecked (dates are frozen).
Freezing covers every post type that’s available in the REST API, which includes posts and pages.
Developer reference
For developers: hooks and functions you can use from your theme or a code snippet.
post_date_freeze_post_types
Filter. Changes which post types the freeze applies to. Receives an array of post type names. Defaults to every post type that shows in the REST API.
add_filter( 'post_date_freeze_post_types', function ( $post_types ) {
unset( $post_types['page'] );
return $post_types;
} );
post_date_freeze_is_frozen
Filter. Decides, on each save, whether to keep the old modified date. Receives $is_frozen and the post ID. Return false to let the modified date update for that save.
// Let the modified date update when the post is saved with the "updated" tag.
add_filter( 'post_date_freeze_is_frozen', function ( $is_frozen, $post_id ) {
return has_tag( 'updated', $post_id ) ? false : $is_frozen;
}, 10, 2 );
FAQs
Does it change the published date?
No. The plugin only keeps the last-modified date from changing. The published date works as usual.
Does the per-post choice stick?
No, on purpose. A per-post choice applies to the next save only, then the post goes back to the site-wide setting.
Can developers limit which post types are frozen?
Yes. Use the post_date_freeze_post_types filter to change the list of post types. There’s also a post_date_freeze_is_frozen filter that receives the frozen state and the post ID, so you can decide per post in code.