Design/robots specifications and filter extensions
Check the effective Robots configuration and changes through extensions. Functional pages and catalogue pages require different publication decisions.
Compare the default for search engines in the effective store area with additional rules of layered navigation or SEO extension. An inherited setting can affect multiple store views.
Where to check the setting in Magento
Under Content → Design → Configuration, check the affected Store View and its Search Engine Robots. After that, compare additional rules of filter or SEO extensions. A basic setting adopted from the test shop can affect all pages.
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 Magento
Retrieve product, category and filtered view for each affected store view. First determine which page type should be consciously excluded.
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.
Reference: Magento Open Source or Adobe Commerce with classic storefront. Consider store views and extensions; other storefront architectures have their own configurations.
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
Adobe Commerce: Page Configuration and Robots Specifications