unforgivenhobbies

<p><strong>Multisite search visibility indicator</strong> is a lightweight plugin that keeps you informed at a glance whether your site — or any site in your network — is accidentally blocking search engines.</p>
<p>WordPress has a built-in setting under <em>Settings <span aria-hidden="true" class="wp-exclude-emoji">→</span> Reading</em> called “Search Engine Visibility”. When enabled, it adds a <code>noindex</code> directive that tells search engines not to index your site. This is easy to accidentally leave on after development, and notoriously hard to notice.</p>
<p>This plugin adds a persistent indicator to the WordPress toolbar so you never miss it again.</p>
<h4>Features</h4>
<ul>
<li>Toolbar indicator visible to administrators at all times (front-end and back-end)</li>
<li>Color-coded status: green when search engines are allowed, yellow/red when blocked</li>
<li><strong>Multisite ready</strong>: shows a per-site breakdown across your entire network</li>
<li>Each site in the dropdown links directly to its Reading Settings for a one-click fix</li>
<li><strong>Bulk management page</strong> (Multisite only): allow or discourage search engines across all — or selected — sites in a single action</li>
<li>Zero configuration required — install and it just works</li>
<li>No external dependencies, no tracking, no bloat</li>
</ul>
<h4>Multisite Bulk Management</h4>
<p>On a Multisite installation the plugin adds a <strong>Search Engine Visibility</strong> page under <em>Network Admin <span aria-hidden="true" class="wp-exclude-emoji">→</span> Settings</em>. From there you can:</p>
<ol>
<li>See every site in the network and its current visibility status</li>
<li>Select individual sites or all sites at once</li>
<li>Apply “Allow search engines” or “Discourage search engines” in one click</li>
</ol>
<h4>Who is this for?</h4>
<ul>
<li>Agencies managing WordPress Multisite networks</li>
<li>Developers who frequently spin up and hand off sites</li>
<li>Site owners who want a quick sanity check without digging through settings</li>
</ul>


Multisite search visibility indicator

Adds a toolbar indicator showing which sites discourage search engines. Supports WordPress Multisite with bulk management.

apasionados

<p>This plugin adds the JSON-LD schema.org markup for including the Site Name in Search Results on the homepage.</p>
<p>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>.</p>
<p>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.</p>
<blockquote>
<p>If you use <strong>WordPress SEO by Yoast version 1.6 or newer</strong>, 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.</p>
</blockquote>
<h4>What can I do with this plugin?</h4>
<p>This plugin adds the JSON-LD schema.org markup for including the Site Name in Search Results on the homepage.</p>
<p>After activating the plugin you have to configure the Name you want Google to display in your search results instead of the domain name.</p>
<p>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.</p>
<h4>INCLUDE SITENAME IN SEARCH RESULTS in your Language!</h4>
<p>This first release is avaliable in English and Spanish. In the languages folder we have included the necessary files to translate this plugin.</p>
<p>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>.</p>
<h4>Further Reading</h4>
<p>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>.</p>
<h3>Contact</h3>
<p>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>.</p>
<h3>Translating WordPress Plugins</h3>
<p>The steps involved in translating a plugin are:</p>
<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>
<p>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.</p>
<p>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></p>
<p>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.</p>
<p>For example:</p>
<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>
<p>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>.</p>


Include Sitename in Search Results

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

Multisite search visibility indicator vs Include Sitename in Search Results