Structured data is essential for search engine optimisation nowadays. This extension allows the easy integration of structured data based on the schema.org vocabulary on a TYPO3 website. A good introduction to the topic is provided by Google: Understand how structured data works.
The defined structured data is embedded on a web page in JSON-LD markup and can be checked with the Schema Markup Validator and Google’s Rich Results Test. The JSON-LD generated by this extension can also be reviewed in the Admin Panel.
Schema.org is a set of extensible schemas that enables webmasters to embed structured data on their web pages for use by search engines and other applications. The vocabulary is divided into different sections:
- The core vocabulary provides all default types and properties, like
- The pending section is a staging area for work-in-progress terms which have yet to be accepted into the core vocabulary. Pending terms are subject to change and should be used with caution. On the schema.org website they are displayed in a blue colour.
- The auto section provides additional terms related to auto.
- The bib section provides additional terms related to bibliography.
- The health-lifesci section provides additional terms related to health and lifesciences.
This TYPO3 schema extension provides the terms for the core vocabulary. To use terms from other sections you can extend the vocabulary on your own as described in the according chapter or use one of the additional TYPO3 extensions provided by the author of this extension:
The schema.org vocabulary is evolving, approx. every 3-4 months a new version is released. The TYPO3 extensions are updated when changes are made to the according vocabulary. The classes for the type models and view helpers are generated by the schema-generator library.
You can browse through a list of types available in a TYPO3 installation.
This extension uses semantic versioning which basically means for you, that
- Bugfix updates (e.g. 1.0.0 => 1.0.1) just includes small bug fixes or security relevant stuff without breaking changes.
- Minor updates (e.g. 1.0.0 => 1.1.0) includes new features and smaller tasks without breaking changes.
- Major updates (e.g. 1.0.0 => 2.0.0) breaking changes which can be refactorings, features or bug fixes.
The changes between the different versions can be found in the changelog.