Fernando Tellado

Ayuda WordPress

NoIndexer gives you full control over which content gets a <code>noindex</code> robots directive, telling search engines not to include it in their results. No bloated SEO plugin needed — just clean, focused noindex management.
Features:
<ul>
<li>Bulk noindex by content type — Set entire post types (pages, posts, products, etc.) as noindex with a single checkbox.</li>
<li>Bulk noindex by taxonomy — Set entire taxonomy archives (categories, tags, product attributes, etc.) as noindex with a single checkbox. Works with all public taxonomies, including WooCommerce product categories, tags, and attributes (requires “Enable Archives?” in WooCommerce attribute settings).</li>
<li>Smart exclusions — When a content type or taxonomy is set to noindex, exclude specific posts or terms that should remain indexed.</li>
<li>Individual noindex — Set noindex on specific posts or taxonomy terms without affecting the entire content type or taxonomy.</li>
<li>Instant search — Find content and terms quickly with a live search field in the settings page. Click to add, click to remove.</li>
<li>Editor integration — Noindex checkbox available in both the Classic Editor and Block Editor sidebar.</li>
<li>Quick Edit — Toggle noindex directly from the post list table without opening the editor.</li>
<li>Bulk actions — Set or remove noindex on multiple posts at once from the post list.</li>
<li>Index? column — See at a glance which posts are noindexed in your content lists.</li>
<li>Search results noindex — Prevent internal search result pages from being indexed.</li>
<li>404 pages noindex — Keep 404 error pages out of search indexes.</li>
<li>Date archives noindex — Noindex daily, monthly, and yearly archive pages.</li>
<li>Paginated archives noindex — Noindex /page/2/, /page/3/ and beyond for all archives.</li>
<li>Attachment pages noindex — Noindex media attachment pages created by WordPress.</li>
<li>Author archives noindex — Noindex author archive pages.</li>
<li>Native sitemap integration — Automatically excludes noindexed content from the native WordPress sitemap. Posts, post types, taxonomy terms, and taxonomy archives marked as noindex are removed from the sitemap without needing any additional plugin.</li>
<li>Lightweight — No unnecessary features, no frontend scripts, no database tables. Just a meta tag when needed.</li>
</ul>
How it works:
NoIndexer adds a <code><meta name="robots" content="noindex, follow"></code> tag to the <code><head></code> of posts and taxonomy archives set as noindex. This tells search engines not to index the page while still following its links.
Priority logic for posts:
<ol>
<li>Individual noindex always applies.</li>
<li>Post type bulk noindex applies unless the post is specifically excluded.</li>
<li>Exclusions override the bulk setting for specific posts.</li>
</ol>
Priority logic for taxonomy archives:
<ol>
<li>Individual term noindex always applies.</li>
<li>Taxonomy bulk noindex applies unless the term is specifically excluded.</li>
<li>Exclusions override the bulk setting for specific terms.</li>
</ol>
Do you really need a full SEO plugin?
Most WordPress sites don’t need a 100-feature SEO plugin just to manage noindex rules or customize a sitemap. WordPress already generates a native sitemap and a robots.txt file — the two core pieces search engines need to crawl your site properly.
NoIndexer handles the noindex side: decide which content should stay out of search results. It also automatically excludes noindexed content from the native WordPress sitemap, so search engines won’t find it there either. If you need additional sitemap customization beyond noindex — like excluding specific content that is indexed but shouldn’t appear in the sitemap — <a href="https://wordpress.org/plugins/native-sitemap-customizer/" rel="ugc">Native Sitemap Customizer</a> is the perfect companion. Together with the robots.txt that WordPress generates automatically, you have everything essential for technical SEO — no bloat, no unused features, no performance overhead.
Third-party integration:
Developers can check noindex status using:
<ul>
<li><code>Noindexer_Frontend::is_noindex( $post_id )</code> — returns <code>true</code> if a post should not be indexed.</li>
<li><code>Noindexer_Frontend::is_term_noindex( $term_id, $taxonomy )</code> — returns <code>true</code> if a taxonomy term archive should not be indexed.</li>
</ul>
Both methods resolve the full priority logic (individual meta, bulk rules, and exclusions).
<h3>Support</h3>
Need help or have suggestions?
<ul>
<li><a href="https://servicios.ayudawp.com" rel="nofollow ugc">Official website</a></li>
<li><a href="https://wordpress.org/support/plugin/noindexer/" rel="ugc">WordPress support forum</a></li>
<li><a href="https://www.youtube.com/AyudaWordPressES" rel="nofollow ugc">YouTube channel</a></li>
<li><a href="https://ayudawp.com" rel="nofollow ugc">Documentation and tutorials</a></li>
</ul>
Love the plugin? Please leave us a <a href="https://wordpress.org/support/plugin/noindexer/reviews/#new-post" rel="ugc">5-star review</a> and help spread the word!
<h3>About AyudaWP.com</h3>
We are specialists in WordPress security, SEO, AI and performance optimization plugins. We create tools that solve real problems for WordPress site owners while maintaining the highest coding standards and accessibility requirements.

NoIndexer

Lightweight SEO noindex manager for WordPress. Control which content search engines should not index.

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.

NoIndexer vs Sitelinks Search Box