Website visibility and page rules of the SEO plugin
Compare the global attitude to search engine visibility with the rules of the SEO plugin. A deliberately excluded archive can be correct.
Compare the basic visibility setting of the installation with the specification for the individual contribution or archive. A setup adopted from the test phase can appear wider than a single noindex field.
Where to check the setting in WordPress
Under Settings → Read the search engine visibility and then the indexing rule of the active SEO plugin for the affected page type. For core outputs, the filter wp_robots is relevant. A robots.txt lock and a noindex tag are separate specifications.
Example of this specific finding
Illustrative control case: A published performance page still carries the noindex specification from the preparation. The site is accessible to visitors, but should appear in the search.
<!-- Bewusster Ausschluss, z. B. interne Suche -->
<meta name="robots" content="noindex,follow">follow-up audit in WordPress
Check the homepage, contribution and archive for the actually delivered meta and HTTP specifications. A global change does not derive from a single unintentionally excluded contribution.
Correct the indexing intent in the relevant page or template field and check the public HTML response after cache update.
Derogations and scope
Search results, user accounts or other deliberately excluded pages may keep noindex. The finding requires the page type as context.
Related: WordPress with classic or block theme. SEO plugins and page builders are different; there is no universal menu path for all installations.
Classify the general error
Definition, system-independent causes and further correction examples: Differentiate an unintentional noindex from the intended exclusion
Configuration and test signal documentation
WordPress: wp_robots and filters