LiteSpeed Cache vs noindex SEO

LiteSpeed Cache for WordPress (LSCWP) is an all-in-one site acceleration plugin, featuring an exclusive server-level cache and a collection of optimization features. LSCWP supports WordPress Multisite and is compatible with most popular plugins, including WooCommerce, bbPress, and Yoast SEO. LiteSpeed Cache for WordPress is compatible with ClassicPress. Requirements General Features may be used by anyone with any web server (LiteSpeed, Apache, NGINX, etc.). LiteSpeed Exclusive Features require one of the following: OpenLiteSpeed, commercial LiteSpeed products, LiteSpeed-powered hosting, or QUIC.cloud CDN. Why? Plugin Features General Features Free QUIC.cloud CDN Cache Object Cache (Memcached/LSMCD/Redis) Support+ Image Optimization (Lossless/Lossy) Minify CSS, JavaScript, and HTML Minify inline & external CSS/JS Combine CSS/JS Automatically generate Critical CSS Lazy-load images/iframes Responsive Image Placeholders Multiple CDN Support+ Load CSS Asynchronously Defer/delay JS loading Browser Cache Support+ Database Cleaner and Optimizer PageSpeed score (including Core Web Vitals) optimization OPcode Cache Support+ HTTP/2 Push for CSS/JS (on web servers that support it) DNS Prefetch Cloudflare API Single Site and Multisite (Network) support Import/Export settings Attractive, easy-to-understand interface AVIF/WebP image format support Heartbeat control + This service is not provided by the LSCache plugin, nor is it guaranteed to be installed by your service provider. However, the plugin is compatible with the service if it is in use on your site. LiteSpeed Exclusive Features Automatic page caching to greatly improve site performance Automatic purge of related pages based on certain events Private cache for logged-in users Caching of WordPress REST API calls Separate caching of desktop and mobile views Ability to schedule purge for specified URLs WooCommerce and bbPress support WordPress CLI commands API system for easy cache integration Exclude from cache by URI, Category, Tag, Cookie, User Agent Smart preload crawler with support for SEO-friendly sitemap Multiple crawlers for cache varies HTTP/2 support HTTP/3 & QUIC support ESI (Edge Side Includes) support* Widgets and Shortcodes as ESI blocks* (requires Classic Widgets plugin for WP 5.8+) * Feature not available in OpenLiteSpeed LSCWP Resources Join our Slack community to connect with other LiteSpeed users. Ask a question on our support forum. View detailed documentation. Read about LSCWP and WordPress on our blog. Help translate LSCWP. Contribute to the LSCWP GitHub repo. Third Party Compatibility The vast majority of plugins and themes are compatible with LSCache. Our API is available for those that are not. Use the API to customize smart purging, customize cache rules, create cache varies, and make WP nonce cacheable, among other things. Privacy This plugin includes some suggested text that you can add to your site’s Privacy Policy via the Guide in the WordPress Privacy settings. For your own information: LiteSpeed Cache for WordPress potentially stores a duplicate copy of every web page on display on your site. The pages are stored locally on the system where LiteSpeed server software is installed and are not transferred to or accessed by LiteSpeed employees in any way, except as necessary in providing routine technical support if you request it. All cache files are temporary, and may easily be purged before their natural expiration, if necessary, via a Purge All command. It is up to individual site administrators to come up with their own cache expiration rules. In addition to caching, our WordPress plugin has online features provided by QUIC.cloud for Image Optimization and Page Optimization services. When one of these optimizations is requested, data is transmitted to a remote QUIC.cloud server, processed, and then transmitted back for use on your site. QUIC.cloud keeps copies of that data for up to 7 days and then permanently deletes it. Similarly, the WordPress plugin has a Reporting feature whereby a site owner can transmit an environment report to LiteSpeed so that we may better provide technical support. None of these features collects any visitor data. Only server and site data are involved. QUIC.cloud CDN, if enabled, uses LSCache technology to access your site, and serve your content from remote global nodes. Your data is not accessed by QUIC.cloud employees in any way, except as necessary in providing maintenance or technical support. Please see the QUIC.cloud Privacy Policy for our complete Privacy/GDPR statement.

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.