AI-generated illustration
Using Structured Data Sensibly: When Schema.org Really HelpsUse markup specifically where it meaningfully supports page type, content and search presentation
Structured data makes existing statements machine-readable. The starting point is therefore the visible content: Which person, organization, performance or product is actually described?
Check syntax, factual accuracy and suitability for a search function separately. Valid JSON-LD alone does not guarantee a rich result.
From statement to data object
First note the information on the page comprehensible. For example, for an organization, these are name, public URL, and contact reference. In the case of a product, specific product information is added. Non-existent reviews or services must not only be invented for a more extensive markup.
Then determine the data source. When editorial content and JSON-LD are maintained manually in different places, conflicting prices, names or dates are easily created.
Describe a simple organization
This is an illustrative minimal example, not a complete template for every search function. Use only applicable values. A stable @id can help consistently reference the same entity in related data objects.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Organization",
"@id": "https://example.org/#organisation",
"name": "Beispiel GmbH",
"url": "https://example.org/"
}
</script>Three exams instead of a green tick
- Check JSON syntax: Characters, data types and structure must be legible.
- Check Scheme Meaning: Properties must fit the type described.
- Compare values with the visible content and the correct page state.
- Check requirements of the actually desired Google search function separately.
- After content changes, re-validate the public edition.
Duplicate sources and false expectations
Theme, SEO extension and rating tool can create multiple objects. Multiple blocks are not fundamentally wrong, but conflicting descriptions of the same entity are problematic. Set responsibilities instead of blanketly deleting everything except the first block.
Not every Schema.org type leads to its own Google results format. Even suitable, correct markup is not a promise for a highlighted ad. The benefit should be based on reliable data, not on a promised ranking bonus.
Frequent questions
Is JSON-LD automatically better than visible text?
It describes existing information in a structured manner and does not replace its comprehensible presentation.
Can I add non-visible reviews?
Do not distinguish invented or incomprehensible reviews. The statements must fit the actual content and the respective use case.