Indexing in Page Properties and HTTP Output
Compare production context and adopted staging configuration. A globally set noindex must not go unnoticed to the public site.
Check the indexing default in the page dataset and compare it to the meta-robots and X-robots tag of the public response. An own extension, middleware or server rule can set further specifications regardless of the page properties.
Where to check the setting in TYPO3
Open the SEO properties of the affected page and compare the indexing setting with the delivered Robots output. If the result is different, check TypoScript, MetaTag API and HTTP middleware; visibility in the page tree alone does not determine all robots signals.
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 TYPO3
Retrieve the published page without a backend session. For language versions, check the translated properties separately; do not infer all responses from the standard visible language record.
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: TYPO3 13.4 with EXT:seo. For other major versions and own extensions, responsibilities may differ; check the actually installed output.
Classify the general error
Definition, system-independent causes and further correction examples: Exclude a release brake from the test phase