noindex SEO is the #91 ranked seo app on WordPress, with a 5.0 average rating from 2 reviews, as of Aug 31, 2026.
noindex SEO is a WordPress Plugin Directory app by ROBOTSTXT.es. With a rating of 5.0★ from 2 reviews, it currently ranks #91 in the SEO category.
AppRanks data: noindex SEO ranks #91 in SEO on WordPress Plugin Directory, placing it in the top 11% of that category.
AppRanks verdict
Generated from live marketplace data — refreshed daily
noindex SEO is a category-leading WordPress app with a limited review volume. It is listed in the SEO category on WordPress Plugin Directory, which AppRanks treats as the canonical taxonomy node for ranking and competitor comparison. 2 reviews put it in the early-traction tier — useful for early-stage stores willing to be on the leading edge. Early-traction review counts are sensitive to single launch periods or feature events, so a 30-day re-check before bigger commitments often resolves whether the trend is sustained. Paid-only pricing means evaluating fit on the marketplace listing or via the developer's documentation before installing. AppRanks tracks rating, review count, pricing tier, and category position daily — the figures on this page reflect the most recent scrape from the canonical WordPress Plugin Directory listing.
Pros
- +High average rating (5.0★) signals consistent merchant satisfaction
- +Published by ROBOTSTXT.es — established developer track record
Cons
- −Limited review base (2) — ratings can shift significantly with new feedback
Looking to switch from noindex SEO?
See noindex SEO's alternatives ranked by audit score, rating, and review velocity.
How noindex SEO works
Show full descriptionShow less
Fine-grained control over how search engines index and display your WordPress content. Apply 5 independent robots directives to 22 different page contexts with flexible implementation methods.
5 Robots Directives:
noindex: Prevent search engines from indexing the page
nofollow: Prevent search engines from following links on the page
noarchive: Prevent search engines from showing cached versions
nosnippet: Prevent search engines from showing text snippets in results
noimageindex: Prevent search engines from indexing images on the page
Implementation Methods:
HTML Meta Tags: Traditional method, easy to verify in page source (default)
HTTP Headers: More robust, works with all content types including PDFs and images
Both: Maximum compatibility for all scenarios
Control Levels:
Global Settings: Apply directives to 22 different page contexts (posts, pages, archives, etc.)
Granular Control (Optional): Override global settings for individual posts, pages, and custom post types via meta boxes in the editor
Perfect for:
Blocking indexing of attachment pages while allowing link following
Preventing duplicate content issues with flexible directive combinations
Controlling archive page indexing with granular control
Managing pagination SEO with independent settings
Protecting private content from search engine caching
Preventing snippet display while still indexing content
Main pages
Front Page: Block the indexing of the site’s front page.
Home: Block the indexing of the site’s home page.
Pages and Posts
Page: Block the indexing of the site’s pages.
Privacy Policy: Block the indexing of the site’s privacy policy page.
Single: Block the indexing of a post on the site.
Singular: Block the indexing of a post or a page of the site.
Taxonomies
Category: Block the indexing of the site categories. The lists where the posts appear.
Tag: Block the indexing of the site’s tags. The lists where the posts appear.
Dates
Date: Block the indexing when any date-based archive page (i.e. a monthly, yearly, daily or time-based archive) of the site. The lists where the posts appear.
Day: Block the indexing when a daily archive of the site. The lists where the posts appear.
Month: Block the indexing when a monthly archive of the site. The lists where the posts appear.
Time: Block the indexing when an hourly, “minutely”, or “secondly” archive of the site. The lists where the posts appear.
Year: Block the indexing when a yearly archive of the site. The lists where the posts appear.
Archives
Archive: Block the indexing of any type of Archive page. Category, Tag, Author and Date based pages are all types of Archives. The lists where the posts appear.
Author: Block the indexing of the author’s page, where the author’s publications appear.
Post Type Archive: Block the indexing of any post type page.
Pagination
Pagination: Block the indexing of the pagination, i.e. all pages other than the main page of an archive.
Search
Search: Block the indexing of the internal search result pages.
Attachments
Attachment: Block the indexing of an attachment document to a post or page. An attachment is an image or other file uploaded through the post editor’s upload utility. Attachments can be displayed on their own “page” or template. This will not cause the indexing of the image or file to be blocked.
Previews
Customize Preview: Block the indexing when a content is being displayed in customize mode.
Preview: Block the indexing when a single post is being displayed in draft mode.
Error Page
Error 404: This will cause an error page to be blocked from being indexed. As it is an error page, it should not be indexed per se, but just in case.
Important note: if you have any doubt about any of the following items it is best not to activate the option as you could lose results in the search engines.
Using the plugin REST API The plugin exposes two read-only endpoints under /wp-json/noindex-seo/v1/ so headless consumers can read the configuration:
GET /settings: returns the consolidated settings array (contexts and directives plus config). Requires an authenticated user with the manage_options capability.
GET /effective?post_id=123: returns the list of active directives for a specific post, computed with the same precedence used on the front-end (per-post override, then per-post-type default, then the built-in context). Public only for published, non-password-protected posts; everything else requires edit_post capabilities.
On WordPress versions with XML sitemaps (5.5+), URLs that are noindexed are automatically excluded from the core sitemaps.
Compatibility
WordPress: 4.0 – 7.1
PHP: 5.6 – 8.5
Compliance This plugin adheres to the following security measures and review protocols for each version:
WordPress Plugin Handbook
WordPress Plugin Security
WordPress APIs Security
WordPress Coding Standards
Plugin Check (PCP)
Privacy
This plugin does not collect any information about your site, your identity, the plugins, themes or content the site has.
Vulnerabilities
No vulnerabilities have been published up to version 3.1.3.
Found a security vulnerability? Please report it to us privately at the noindex SEO GitHub repository.
Category rankings
As of Sep 4, 2026- SEO#91of 907Top 11%
See 90-day rank history for each category
Track daily rank changes, category shifts, and position volatility.
Competitors & alternatives
noindex SEO doesn't have curated competitor matchups yet. Other tracked seo apps on WordPress:
Where noindex SEO stands in the SEO category
noindex SEO ranks #91 of 907 apps in the SEO category, placing it in the top 11% of the listing.
Frequently asked questions
What is noindex SEO?
noindex SEO is an app for WordPress. It currently holds a 5.0-star rating from 2 merchant reviews, and AppRanks has been tracking its public marketplace data on the refresh cadence published in our methodology. It is listed under the SEO category on AppRanks, where you can see its current category position, review-velocity trend, and how it compares against the top alternatives in the same space. Developed by ROBOTSTXT.es.
Who uses noindex SEO?
Currently around 3,000 active stores have installed noindex SEO. Its review base is still building, which usually maps to early-stage merchants and stores piloting a new workflow. It is part of the SEO category on WordPress.
Where does noindex SEO rank on WordPress?
noindex SEO currently sits at position #91 in the SEO category on WordPress. That places it in the top 10% of 907 apps tracked in the same category. Category positions are read from the live marketplace ranking and refresh on each scrape, so the number you see here reflects the most recent crawl rather than a long-running average.