HTTP 410 (Gone) responses
Sends HTTP 410 (Gone) responses for deleted content, telling search engines the page is permanently removed.
The facts
- Rating
- 4.6★ from 21
- Active installs
- 4k+
- Price
- Free
- Last updated
- 5 Aug 2026
- Added
- Jan 2011
- Requires WP
- 5.0
- Tested up to
- WP 7.0.4
- Requires PHP
- 7.4
- Downloads
- 75,596
Our analysis
AI-assistedThe HTTP 410 (Gone) responses plugin for WordPress issues a 410 response for URLs of content that has been permanently removed from your site. It logs deleted URLs and returns a 410 response when those URLs are accessed, which helps inform search engines that the content will not return.
This plugin is suitable for website owners looking to improve their site's SEO clarity and crawl efficiency by properly managing obsolete URLs. It is maintained by Matt Calvert and is based on established HTTP specifications.
Best for: This plugin is best for website owners who need to manage permanently removed content effectively.
What it does well
- ✓Issues HTTP 410 responses for permanently removed content
- ✓Logs deleted URLs for management
- ✓Improves SEO clarity and crawl efficiency
- ✓Actively maintained by Matt Calvert
Where it falls short
- •Limited feature information provided
- •No additional functionality beyond managing 410 responses
Verdict
The plugin serves a specific purpose in managing obsolete URLs and can enhance SEO. It is a straightforward tool for those needing to implement 410 responses.
From the developer
Matt Calvert's own description of HTTP 410 (Gone) responses, lightly tidied.
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.