---
title: "Introduction"
manual: "schema"
version: "main"
permalink: "https://docs.typo3.org/permalink/brotkrueml/schema:introduction@main"
source: "Introduction/Index.rst"
rendered: "2026-09-18T07:29:46+00:00"
---

# Introduction {#introduction-1}

**Table of Contents**

-   [What does it do?](https://docs.typo3.org/permalink/brotkrueml/schema:what-does-it-do@main)
-   [The schema.org vocabulary](https://docs.typo3.org/permalink/brotkrueml/schema:the-schema-org-vocabulary@main)
-   [Release management](https://docs.typo3.org/permalink/brotkrueml/schema:release-management-1@main)

## What does it do? {#what-does-it-do}

Structured data is essential for Search Engine Optimisation (SEO) and Generative
Engine Optimisation (GEO) nowadays. This extension allows the easy integration
of structured data based on the [schema.org vocabulary](https://schema.org/) on a TYPO3 website. A
good introduction to the topic is provided by Google:
[Understand how structured data works](https://developers.google.com/search/docs/guides/intro-structured-data).

The defined structured data is embedded on a web page in [JSON-LD](https://json-ld.org/) markup and
can be checked with the [Schema Markup Validator](https://validator.schema.org/) and Google's
[Rich Results Test](https://search.google.com/test/rich-results). The JSON-LD generated by this extension can also be
reviewed in the [Admin Panel](https://docs.typo3.org/permalink/brotkrueml/schema:admin-panel@main).

> [!TIP]
> There is a Slack channel [#ext-schema](https://typo3.slack.com/app_redirect?channel=CV36M73D5) on [typo3.slack.com](https://typo3.slack.com/) for questions,
> suggestions, feedback, etc.

## The schema.org vocabulary {#the-schema-org-vocabulary}

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** section provides all default types and properties, like
    `Person` or `Organization`.
-   The **pending** section is a staging area for work-in-progress terms which
    have yet to be accepted into the core vocabulary. [Pending terms](https://schema.org/docs/pending.home.html) 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](https://schema.org/docs/auto.home.html).
-   The **bib** section provides additional terms related to [bibliography](https://schema.org/docs/bib.home.html).
-   The **health-lifesci** section provides additional terms related to
    [health and lifesciences](https://schema.org/docs/health-lifesci.home.html).

> [!NOTE]
> This TYPO3 schema extension provides the terms for the core section. To
> use terms from other sections you can extend the vocabulary on your own as
> described in the [according chapter](https://docs.typo3.org/permalink/brotkrueml/schema:extending-vocabulary@main) or use one
> of the additional TYPO3 extensions provided by the author of this extension:
>
> -   [schema_auto](https://extensions.typo3.org/extension/schema_auto)
> -   [schema_bib](https://extensions.typo3.org/extension/schema_bib)
> -   [schema_health](https://extensions.typo3.org/extension/schema_health)
> -   [schema_pending](https://extensions.typo3.org/extension/schema_pending)

The schema.org vocabulary is evolving, several times a year a new version is
[released](https://schema.org/docs/releases.html). The TYPO3 extensions are updated when relevant changes are made to
the according vocabulary. The classes for the type models and view helpers are
generated by the [schema-generator](https://github.com/brotkrueml/schema-generator) library.

You can browse through a [list of types](https://docs.typo3.org/permalink/brotkrueml/schema:available-types@main) available
in a TYPO3 installation.

## Release management {#release-management-1}

This extension uses [semantic versioning](https://semver.org/) which basically means for you, that

-   Bugfix updates (for example, 1.0.0 => 1.0.1) just includes small bug fixes or
    security relevant stuff without breaking changes.
-   Minor updates (for example, 1.0.0 => 1.1.0) includes new features and smaller
    tasks without breaking changes.
-   Major updates (for example, 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](https://docs.typo3.org/permalink/brotkrueml/schema:changelog@main).