Schema.org invalid @type fix for JSON-LD
Rich results require valid Schema.org types and properties. Typos in @type or unsupported combinations cause warnings or silent drops. Validate structured data before release.
Common causes
- Wrong capitalization or invented @type.
- Required properties missing for a type.
- JSON-LD script not parseable JSON.
How to fix
- Validate JSON syntax with Request Body Validator.
- Cross-check types against schema.org.
- Keep JSON-LD in sync with visible content.
Use our tool
Validate JSONRelated