Plugin info

Total downloads: 22,055
Active installs: 300
Total reviews: 1
Average rating: 5
Support threads opened: 0
Support threads resolved: 0 (0%)
Available in: 1 language(s)
Contributors: 3
Last updated: 11/29/2025 (32 days ago)
Added to WordPress: 9/7/2008 (17 years old)
Minimum WordPress version: 6.3
Tested up to WordPress version: 6.9
Minimum PHP version: 7.4

Maintenance & Compatibility

Maintenance score

Actively maintained • Last updated 32 days ago • 1 reviews

61/100

Is Auto-Close Comments, Pingbacks and Trackbacks abandoned?

Likely maintained (last update 32 days ago).

Compatibility

Requires WordPress: 6.3
Tested up to: 6.9
Requires PHP: 7.4

Similar & Alternatives

Explore plugins with similar tags, and compare key metrics like downloads, ratings, updates, support, and WP/PHP compatibility.

No similar plugins found yet.

Description

Spammers target old posts in a hope that you won’t notice the comments on them. Why not stop them in their tracks by just shutting off comments and pingbacks? Auto-Close Comments, Pingbacks and Trackbacks lets you automatically close comments, pingbacks and trackbacks on your posts, pages and custom post types.

You can also choose to keep comments, pingbacks, or trackbacks open on certain posts, pages or custom post types. Just enter a comma-separated list of post IDs in the Settings page.

An extra feature is the ability to delete post revisions or limit their number.

Found a bug or want to contribute? PRs and issues welcome on GitHub. For help, use the support forum or premium support.

Key Features

  • Close (or open) comments on posts, pages, attachments and even Custom Post Types
  • Close (or open) pingbacks and trackbacks as well across all post types. You can also choose to delete them
  • Schedule a cron job to automatically close comments, pingbacks and trackbacks daily
  • Delete all post revisions or limit the number of revisions by post type
  • Exclude specific post IDs from auto-close
  • Block self-pings and custom ping URLs
  • Schedule the closing of comments, pingbacks, and trackbacks for the current post

Installation

WordPress install

  1. Navigate to Plugins within your WordPress Admin Area
  2. Click “Add new” and in the search box enter “autoclose”
  3. Find the plugin in the list (usually the first result) and click “Install Now”

Manual install

  1. Download the plugin
  2. Extract the contents of autoclose.zip to wp-content/plugins/ folder. You should get a folder called autoclose.
  3. Activate the Plugin in WP-Admin.
  4. Go to Settings » AutoClose to configure

Frequently Asked Questions

How do I exclude a post from auto-closing?

Enter the post ID in the settings page under “Exclude posts”.

Will this plugin work with custom post types?

Yes! Auto-Close works with posts, pages, attachments, and any registered custom post types.

Can I delete or limit revisions?

Yes, you can delete all revisions or set a limit per post type from the settings page.

How can I report security bugs?

You can report security bugs through the Patchstack Vulnerability Disclosure Program. The Patchstack team help validate, triage and handle any security vulnerabilities. Report a security vulnerability.

Review feed

No reviews available

Screenshots

  1. Autoclose Settings - General

    Autoclose Settings - General

  2. Autoclose Settings - Comments

    Autoclose Settings - Comments

  3. Autoclose Settings - Pingbacks/Trackbacks

    Autoclose Settings - Pingbacks/Trackbacks

  4. Autoclose Settings - Revisions

    Autoclose Settings - Revisions

  5. Autoclose Tools

    Autoclose Tools

Changelog

3.0.0

Release post: https://webberzone.com/announcements/auto-close-v3-0-0/

Completely rewritten the plugin to use autoloading, namespaces and classes.

  • Features:

    • Added block ping URLs feature and self-pings feature.
    • Introduced a new meta box allowing users to schedule the closure of comments, pingbacks, and trackbacks for the current post.
  • Bug fixes:

    • Fixed PHP error/warnings about loading translations too early.

For older changes, refer to changelog.txt