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

This plugin adds the JSON-LD schema.org markup for including the Site Name in Search Results on the homepage.
This new feature was presented on the <a href="http://googlewebmastercentral.blogspot.com.es/2015/04/better-presentation-of-urls-in-search.html" rel="nofollow ugc">Official Google Webmaster Central Blog</a> (Thursday, April 16, 2015 ). There is more info on the <a href="https://developers.google.com/structured-data/site-name" rel="nofollow ugc">Google Developers Website</a>.
Use structured data markup on your public website to indicate the preferred name you want Google to display in Search results. You can also provide more than one possible name for your site, and let Google Search algorithms choose between them. Once Google has crawled and indexed the updated page, we can use the provided name in Search results as shown in the screenshot.
<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://wordpress.org/plugins/include-sitename-in-search-results/faq/" rel="ugc">FAQ section</a> of the plugin.
</blockquote>
<h4>What can I do with this plugin?</h4>
This plugin adds the JSON-LD schema.org markup for including the Site Name in Search Results on the homepage.
After activating the plugin you have to configure the Name you want Google to display in your search results instead of the domain name.
When Google next crawls your page, its indexing algorithms will process the site name specified by your markup and make it eligible to be used in Search results. Note: It can take some time before you see a change to the presentation of your site in Search results. Also, Google’s algorithms might choose not to use the name you provided, or not might choose to show the domain name instead.
<h4>INCLUDE SITENAME IN SEARCH RESULTS in your Language!</h4>
This first release is avaliable in English and Spanish. In the languages folder we have included the necessary files to translate this plugin.
If you would like the plugin in your language and you’re good at translating, please drop us a line at <a href="http://apasionados.es/contacto/index.php?desde=wordpress-org-includesitenamesearchresults-home" rel="nofollow ugc">Contact us</a>.
<h4>Further Reading</h4>
You can access the description of the plugin in Spanish at: <a href="http://apasionados.es/blog/" rel="nofollow ugc">Include Sitename in Search Results en castellano</a>.
<h3>Contact</h3>
For further information please send us an <a href="http://apasionados.es/contacto/index.php?desde=wordpress-org-includesitenamesearchresults-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>.

Include Sitename in Search Results

Adds the JSON-LD schema.org markup for including the Site Name in Search Results on the homepage.

Expire Comment Links vs Include Sitename in Search Results