Page Properties, PageTitle/MetaTag API and Fluid
Check the PageTitleProvider of the page type and your own head outputs. A set headline in the content does not replace a working title output.
Track the value from the page title or SEO field to the output. Extension detail views can be handled by a separate title provider or a metadata call. A global fluid fragment can overlay or additionally output these values.
Where to check the setting in TYPO3
In TYPO3 13.4, check the SEO title in the page properties and priority under config.pageTitleProviders. The SeoTitlePageTitleProvider can overwrite the page title; a detail extension can use its own provider. Description and Open Graph must be checked separately via metadata or the MetaTag API.
Example of this specific finding
Illustrative control case: The CMS field is filled in, but the title element is missing in the delivered head. The visible H1 does not replace this metadata.
<head>
<title>Fahrradreparatur in Köln – Werkstatt Beispiel</title>
</head>follow-up audit in TYPO3
Compare a default page, an extension detail page, and a record with an empty optional field. Thus, fixed template values and missing fallbacks become visible.
Track the value from the editorial field to the template and possible extension to the HTTP result. Check direct entries and different page types.
Derogations and scope
A title within an SVG is not a document heading in the head. Such graphic descriptions do not count as a replacement or additional document title.
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: Track the title output from CMS field to HTML