Indexing Settings and Custom Code
Check page or template settings and additional head code. Then check the published production domain for the effective exclusion.
Compare page settings with additional robots tags in the global or page-related custom code. A staging presence that is not intended for search engines has a different intention than the main public domain.
Where to check the setting in Webflow
Check the indexing settings of the specific page, the site’s SEO settings, and additional custom code. Distinguish between staging subdomain and production domain. An excluded webflow test domain does not say anything about the desired indexing of the customer domain.
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 Webflow
Check main domain and staging/preview address separately. Do not adopt an intended staging lock as a template for all public pages.
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: Websites published on Webflow and CMS Collections. Exported HTML or an upstream own proxy layer may have other responsibilities.
Classify the general error
Definition, system-independent causes and further correction examples: Exclude a release brake from the test phase