Aaron D. Campbell

Expire Comment Links was inspired by <a href="http://yoast.com" rel="nofollow ugc">Joost de Valk</a> 
in an article he wrote called 
<a href="http://www.searchcowboys.com/columns/764" rel="nofollow ugc">Comment links: an experiment</a>. 
It all started when Matt Cutts talked about how Google changed how it handles no 
follow links in his article on 
<a href="http://www.mattcutts.com/blog/pagerank-sculpting/" rel="nofollow ugc">PageRank Sculpting</a>.
No one knows for sure yet if this will be beneficial or not, but for those that 
want to be on the cutting edge and try this experiment for themselves, this 
plugin automates everything.
Requires PHP5.
You may also be interested in <a href="http://wpinformer.com" rel="nofollow ugc">WordPress tips and tricks at WordPress Informer</a> or general <a href="http://webdevnews.net" rel="nofollow ugc">Web Developer News</a>

Expire Comment Links

Allows you to stop displaying links for old comments. PHP 5+ required.

apasionados

netconsulting

<blockquote>
PLEASE NOTE: Since November 2024 <a href="developers.google.com/search/blog/2024/10/sitelinks-search-box?hl=en" rel="nofollow ugc">Google doesn’t support the schema for the Sitelinks Search Box anymore</a>. After more than ten years Search Advocate John Mueller confirmed that the feature will be retired and the searchbox will not appear in the SERPs anymore.
Since November 2024 there is no need to install this plugin.
Quoting the post from Google Developers: While you can remove sitelinks search box structured data from your site, there’s no need to do so. Unsupported structured data like this won’t cause issues in Search, and won’t trigger errors in Search Console reports.
If you are using tis plugin and reading this readme.txt file, you can uninstall it.
</blockquote>
xxx PLUGIN DESCRIPTION (until November 2024) xxx
This plugin adds the JSON-LD schema.org markup for the “Google Sitelinks Search Box” on the homepage.
This new feature of the Google Search Engine was presented on the <a href="http://googlewebmastercentral.blogspot.com.es/2014/09/improved-sitelinks-search-box.html" title="Official Google Webmaster Central Blog" rel="nofollow ugc">Official Google Webmaster Central Blog</a> (05 Sep 2014 07:44 AM PDT). There is more info on the <a href="https://developers.google.com/webmasters/richsnippets/sitelinkssearch" title="Google Developers Website" rel="nofollow ugc">Google Developers Website</a>.
With Google sitelinks search box, people can reach your content more quickly from search results. Search users sometimes use navigational queries -typing in the brand name or URL of a known site- only to do a more detailed query once on that site. For example, suppose someone wants to find that video about the guilty dog on YouTube. They type YouTube, or you-tube, or youtube.com into Google Search, follow the link to YouTube, and then actually search for the dog video.
The sitelinks search box removes that extra step: a query for youtube displays a site search box in the sitelinks section, letting the user immediately search for that guilty dog video without having to click through to the site first.
<blockquote>
If you use WordPress SEO by Yoast version 1.6 or newer, you don’t need to use this plugin, as this feature has been included in the version 1.6 update. There is more information in the <a href="https://es.wordpress.org/plugins/sitelinks-search-box/faq/" rel="nofollow ugc">FAQ section</a> of the plugin.
</blockquote>
<h4>What can I do with this plugin?</h4>
This plugin adds the schema.org JSON-JD markup for the “Google Sitelinks Search Box” on the homepage.
After activating the plugin you only have to “Wait for Google Search algorithms to identify your site as a candidate for the new sitelinks search box”.
<h4>SITELINK SEARCH BOX in your Language!</h4>
The plugin was released first in English and Spanish (es_ES). In the “languages” folder we have included the necessary files to translate this plugin. Translation to ar_SA, tr_TR, de_DE, fr_FR and ru_RU was added in further versions.
If you would like the plugin in your language and you’re good at translating, please use the <a href="https://translate.wordpress.org/" rel="nofollow ugc">native WordPress Translation</a> functionality.
New to Translating a plugin? First read through the <a href="https://make.wordpress.org/polyglots/handbook/tools/glotpress-translate-wordpress-org/" rel="nofollow ugc">Translator Handbook</a>, then select your locale at <a href="https://translate.wordpress.org/" rel="nofollow ugc">Translating WordPress</a> and finally go to the <a href="https://translate.wordpress.org/projects/wp-plugins/block-ecommerce-assets-via-robots-txt/" rel="nofollow ugc">translation page for this plugin</a> to translate it.
<h4>Further Reading</h4>
You can access the description of the plugin in Spanish at: <a href="http://apasionados.es/blog/marcado-google-sitelinks-search-box-wordpress-plugin-2873/" rel="nofollow ugc">Sitelinks Search Box en castellano</a>.
<h3>Contact</h3>
For further information please send us an <a href="http://apasionados.es/contacto/index.php?desde=wordpress-org-sitelinksearchbox-contact" rel="nofollow ugc">email</a>.
<h3>Translating WordPress Plugins</h3>
The steps involved in translating a plugin are:
<ol>
<li>Run a tool over the code to produce a POT file (Portable Object Template), simply a list of all localizable text. Our plugins allready havae this POT file in the /languages/ folder.</li>
<li>Use a plain text editor or a special localization tool to generate a translation for each piece of text. This produces a PO file (Portable Object). The only difference between a POT and PO file is that the PO file contains translations.</li>
<li>Compile the PO file to produce a MO file (Machine Object), which can then be used in the theme or plugin.</li>
</ol>
In order to translate a plugin you will need a special software tool like <a href="http://www.poedit.net/" rel="nofollow ugc">poEdit</a>, which is a cross-platform graphical tool that is available for Windows, Linux, and Mac OS X.
The naming of your PO and MO files is very important and must match the desired locale. The naming convention is: <code>language_COUNTRY.po</code> and plugins have an additional naming convention whereby the plugin name is added to the filename: <code>pluginname-fr_FR.po</code>
That is, the plugin name name must be the language code followed by an underscore, followed by a code for the country (in uppercase). If the encoding of the file is not UTF-8 then the encoding must be specified.
For example:
<ul>
<li>en_US – US English</li>
<li>en_UK – UK English</li>
<li>es_ES – Spanish from Spain</li>
<li>fr_FR – French from France</li>
<li>zh_CN – Simplified Chinese</li>
</ul>
A list of language codes can be found <a href="http://en.wikipedia.org/wiki/ISO_639" rel="nofollow ugc">here</a>, and country codes can be found <a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2" rel="nofollow ugc">here</a>. A full list of encoding names can also be found at <a href="http://www.iana.org/assignments/character-sets" rel="nofollow ugc">IANA</a>.

Sitelinks Search Box

Adds the JSON-LD schema.org markup for the "Google Sitelinks Search Box" on the homepage.

Expire Comment Links vs Sitelinks Search Box