這個外掛並未在最新的 3 個 WordPress 主要版本上進行測試。開發者可能不再對這個外掛進行維護或提供技術支援,並可能會與更新版本的 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