New to Translating WordPress? Read through our Translator Handbook to get started. Hide
| Prio | Original string | Translation | — |
|---|---|---|---|
| ↑ | Sends HTTP 410 (Gone) responses for deleted content, telling search engines the page is permanently removed. | Sends HTTP 410 (Gone) responses for deleted content, telling search engines the page is permanently removed. | Details |
Original current
Sends HTTP 410 (Gone) responses for deleted content, telling search engines the page is permanently removed.
You have to log in to edit this translation. |
|||
| ↑ | HTTP 410 (Gone) responses | HTTP 410 (Gone) responses | Details |
Original current |
|||
| 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. | 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. | Details | |
Original current
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.
CommentFound in description paragraph. You have to log in to edit this translation. |
|||
| The <a href="http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.4.11">HTTP Specification</a> defines the <code>410 Gone</code> 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. | The <a href="http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.4.11">HTTP Specification</a> defines the <code>410 Gone</code> 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. | Details | |
Original current
The <a href="http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.4.11">HTTP Specification</a> defines the <code>410 Gone</code> 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.
CommentFound in description paragraph. You have to log in to edit this translation. |
|||
| This plugin issues an HTTP <code>410</code> 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 <code>410</code> response when that URL is requested. You can also manually manage the list of obsolete URLs. | This plugin issues an HTTP <code>410</code> 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 <code>410</code> response when that URL is requested. You can also manually manage the list of obsolete URLs. | Details | |
Original current
This plugin issues an HTTP <code>410</code> 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 <code>410</code> response when that URL is requested. You can also manually manage the list of obsolete URLs.
CommentFound in description paragraph. You have to log in to edit this translation. |
|||
| I have not tested it with other caching plugins, and there is a high chance that it <strong>will not work</strong> 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. | I have not tested it with other caching plugins, and there is a high chance that it <strong>will not work</strong> 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. | Details | |
Original current
I have not tested it with other caching plugins, and there is a high chance that it <strong>will not work</strong> 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.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| The plugin has been tested with the following caching plugins, and should work even if they are active: | The plugin has been tested with the following caching plugins, and should work even if they are active: | Details | |
Original current
The plugin has been tested with the following caching plugins, and should work even if they are active:
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| If you want to customise the message, just place a template file called <code>410.php</code> in your theme folder, and the plugin will automatically use that instead. Take a look at your theme's <code>404.php</code> file to see how the template needs to be structured. You can also hook into the <code>mclv_410_response</code> action to trigger any specific events for queries resulting in a 410 response. | If you want to customise the message, just place a template file called <code>410.php</code> in your theme folder, and the plugin will automatically use that instead. Take a look at your theme's <code>404.php</code> file to see how the template needs to be structured. You can also hook into the <code>mclv_410_response</code> action to trigger any specific events for queries resulting in a 410 response. | Details | |
Original current
If you want to customise the message, just place a template file called <code>410.php</code> in your theme folder, and the plugin will automatically use that instead. Take a look at your theme's <code>404.php</code> file to see how the template needs to be structured. You can also hook into the <code>mclv_410_response</code> action to trigger any specific events for queries resulting in a 410 response.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| 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. | 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. | Details | |
Original current
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.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| WP Super Cache | WP Super Cache | Details | |
Original current |
|||
| W3 Total Cache | W3 Total Cache | Details | |
Original current |
|||
| Will this plugin work if a caching/performance plugin is active ? | Will this plugin work if a caching/performance plugin is active ? | Details | |
Original current
Will this plugin work if a caching/performance plugin is active ?
CommentFound in faq header. You have to log in to edit this translation. |
|||
| Can I customise the 410 response message? | Can I customise the 410 response message? | Details | |
Original current
Can I customise the 410 response message?
CommentFound in faq header. You have to log in to edit this translation. |
|||
| The plugin settings can be accessed via the 'Plugins' menu in the administration area | The plugin settings can be accessed via the 'Plugins' menu in the administration area | Details | |
Original current
The plugin settings can be accessed via the 'Plugins' menu in the administration area
CommentFound in installation list item. You have to log in to edit this translation. |
|||
| Activate the plugin through the 'Plugins' menu in WordPress | Activate the plugin through the 'Plugins' menu in WordPress | Details | |
Original current
Activate the plugin through the 'Plugins' menu in WordPress
CommentFound in installation list item. You have to log in to edit this translation. |
|||
Export as
Comment
Short description.