Linux 软件免费装

HTTP 410 (Gone) responses

开发者 solarissmoke
XanderCalvert
更新时间 2026年5月21日 16:26
PHP版本: 7.4 及以上
WordPress版本: 7.0
版权: GPLv2 or later
版权网址: 版权信息

标签

error gone robots

下载

1.1.0 0.1 0.6 1.0.2 1.0.3 0.2 0.3 0.4 0.5 0.6.1 0.7 0.7.1 0.7.2 0.8.1 0.8.2

详情介绍:

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.

安装:

  1. Upload the plugin folder to the /wp-content/plugins/ directory
  2. 通过 WordPress 的的“Plugins”菜单激活插件
  3. The plugin settings can be accessed via the 'Plugins' menu in the administration area

常见问题:

Can I customise the 410 response message?

The default message is a simple plain text message that reads "Sorry, the page you requested has been permanently removed." This is because many people want to minimise the bandwidth that is used by error responses. If you want to customise the message, just place a template file called 410.php in your theme folder, and the plugin will automatically use that instead. Take a look at your theme's 404.php file to see how the template needs to be structured. You can also hook into the mclv_410_response action to trigger any specific events for queries resulting in a 410 response.

Will this plugin work if a caching/performance plugin is active ?

The plugin has been tested with the following caching plugins, and should work even if they are active:

  • W3 Total Cache
  • WP Super Cache
I have not tested it with other caching plugins, and there is a high chance that it will not work with many of them. Most of them will cache the response as if it is a 404 (page not found) response, and issue a 404 response header instead of a 410 response header.

更新日志:

1.1.0 1.0.3 1.0.2 1.0.1 1.0.0 0.9.3 0.9.1 0.9.0 0.8.6 0.8.5 0.8.4 0.8.3 0.8.2 0.8.1 0.8 0.7.2 0.7.1 0.7 0.6.1 0.6 0.5 0.4 0.3 0.2