Website visibility and page rules of the SEO plugin
Check blanket locks on wp-content and plugin directories. You can hit CSS or JavaScript, which are required for public content.
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: Disallow: /assets/ locks the stylesheets and scripts that represent the main content of the page. The HTML itself is available.
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.
Check which blocked resources are necessary for the actual display. Adjust the lock specifically and control rendering and retrieval thereafter.
Derogations and scope
Not every CSS or JS file needs to be publicly available for crawlers. Internal administrative resources are a different 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: Identify resources required for presentation
Configuration and test signal documentation
WordPress: wp_robots and filters