Indexing in Page Properties and HTTP Output
Read the effective robots information in the frontend and compare page fields with TypoScript. Deliberately excluded functional pages do not have to be opened.
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: 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 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.
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: 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: Differentiate an unintentional noindex from the intended exclusion