JSON-LD from Sitepackage and Dataset Extensions
Compare JSON-LD with the data of the rendered data set. Incorrect escaping or hard-coded values in fluid can affect several pages of detail.
Determine which component creates the structured data object. Fields for price, date, author, or image must come from the actual dataset displayed; a second extension can output another object in parallel.
Where to check the setting in TYPO3
Locate the JSON-LD block in the sitepackage or in the dataset extension. Check the field mapping for name, URL, and relevant type information. Values should come from the same records as the visible content and be serialized correctly as JSON.
Example of this specific finding
Illustrative control case: The JSON-LD can be read, but mentions an old product price. It is a content inconsistency, not a JSON syntax error.
follow-up audit in TYPO3
Change a record and compare visible content and JSON-LD after cache update. Record language variants and empty optional fields as separate cases.
Check syntax, schema properties and visible product data separately. After price or inventory changes, also check the generated structured data.
Derogations and scope
A green syntax test does not guarantee correct statements or a highlighted presentation in the search.
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: Correct syntax errors and false statements separately