该插件尚未通过WordPress的最新3个主要版本进行测试。 当与较新版本的WordPress一起使用时,可能不再受到维护或支持,并且可能会存在兼容性问题。

Replytocom Controller

描述

Hate duplicate content? Hate wasting server resources?

Replytocom Controller gives you the option to remove “?replytocom” from comment urls and optionally redirect visitors & bots who try to use it anyway to a destination of your choice.

For those concerned about duplicate content for SEO purposes, the benefits should be obvious.

If you want to speed up your WordPress server, the redirection will let you stop wasting resources serving up the same page over and over again to a crawler bot. Even worse, pages with a question mark in the url aren’t typically cached by caching plugins like WP Super Cache. That means that those bot crawls are eating up way more resources then a normal url would. Now you can send them to a cached copy of that page, a less resource intensive page, or any other url.

Of course, the cost of all this is that visitors can’t have JavaScript turned off if they want to leave replies in threaded comments.

Borrows code from:
* https://wordpress.org/extend/plugins/all-in-one-seo-pack/
* https://wordpress.org/extend/plugins/replytocom-redirector/

安装

  1. Upload the plugin to the /wp-content/plugins/ directory
  2. Activate the plugin through the ‘Plugins’ menu in WordPress
  3. Go to Settings->Replytocom Controller if you want to override default settings

评价

2017年2月8日
It works like a charm for those who use the regular commenting system from WordPress. It removes the ?replytocom and we see only #commentXX It is very useful especially for me because i got rid from the canonical URL & by the past in the parameter URL of google webmaster tools i systematically saw the replytocom parameter. Still today Googlebot still wonder wether replytocom is a dumb parameter or a url to a new page. This plugin fixes it all and it is very lightweight.
阅读所有2条评价

贡献者及开发者

“Replytocom Controller” 是开源软件。 以下人员对此插件做出了贡献。

贡献者

将“Replytocom Controller”翻译成您的语言。

对开发感兴趣吗?

您可以浏览代码,查看SVN仓库,或通过RSS订阅开发日志

更新日志

2016/12/11 – 1.2

  • Fixed parse error php < 5.4

2016/12/10 – 1.1

  • Brought code up to date

2013/03/20 – 1.0

  • Initial release