Website visibility and page rules of the SEO plugin
After a staging move, check global search engine visibility and page-related SEO rules first. A global change must deliberately not publish private areas.
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: The new offer page was taken over from a staging template and still bears noindex after publication.
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 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.
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: Exclude a release brake from the test phase
Configuration and test signal documentation
WordPress: wp_robots and filters