Force 410 HTTP Status on listed pages, or just articles/pages that no longer exist.
Force 410 HTTP Status on listed pages, or just articles/pages that no longer exist.
The HTTP Specification defines the 410
response header for use when a resource has been permanently removed. It informs robots visiting your site that the requested content has gone, and that they should stop trying to access it.
If you come across any bugs or have suggestions, please use the plugin support forum.
/wp-content/plugins/
directoryThe 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 wp_410_response
action to trigger any specific events for queries resulting in a 410 response.
The plugin has been tested with the following caching plugins, and should work even if they are active:
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.