Design/robots specifications and filter extensions
Check the scope of the Robots configuration after a staging or store move. An incorrect scope can exclude more than the affected single URL.
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: The new offer page was taken over from a staging template and still bears noindex after publication.
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.
Check page-related settings, templates and possible HTTP headers. After cleanup, check the public response without logged-in session.
Derogations and scope
A deliberately not yet released page may remain excluded. Importance and release must be clarified before the change.
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: Exclude a release brake from the test phase
Configuration and test signal documentation
Adobe Commerce: Page Configuration and Robots Specifications