Sends HTTP 410 (Gone) responses for deleted content, telling search engines the page is permanently removed.
As of April 2026, HTTP 410 (Gone) responses is a WordPress gone plugin with 4.0K+ active installations and a 4.6/5 rating from 21 reviews. It has been downloaded 68K+ times in total. Requires WordPress 3.7+ and PHP false+. Available on WordPress.org since 2011. Recently updated within the last 3 months. Download volume is stable this week. Top alternative: 410 Delete Pages SEO.
This plugin issues an HTTP 410 response for URLs corresponding to content that has been permanently removed from your site. Originally created by Samir Shah, now maintained by Matt Calvert. When a post or page is deleted, the plugin logs the old URL and returns a 410 response when that URL is requested. You can also manually manage the list of obsolete URLs.
The HTTP Specification defines the 410 Gone response for resources that have been permanently removed. It informs search engines and crawlers that the content will not return, improving crawl efficiency and SEO clarity.
This plugin is actively maintained by Matt Calvert as a personal project, informed by previous professional experience with similar 410-handling logic. No proprietary or employer-owned code has been used.
I use the plugin for Micropub protocol, to tell another site I have deleted my contribution.
It is 2020 and it still works.
In the plugin settings, I use a wild card to return a 410 rather than a 404 from posts.
https://mydomain.com/*/
The plugin return a 410 in the header.
BRAVO.
I removed this plugin based on help text from Google Webmaster Tools:
If you have permanently deleted content without intending to replace it with newer, related content, let the old URL return a 404 or 410. Currently Google treats 410s (Gone) the same as 404s (Not found). Returning a code other than 404 or 410 for a non-existent page (or redirecting users to another page, such as the homepage, instead of returning a 404) can be problematic.
very good plugin
Install, activate and it works! simple and effective solution! … BTW: I’m using Comet Cache PRO and have no problems
| WordPress | 3.7+ requiredTested up to 6.9.4 |
| PHP | false+ required |
Plugin data sourced from WordPress.org. Analysis and metrics by PluginSift.