Schema Markup (Structured Data)

Schema markup - also known as structured data or structured data - is additional code that is used to clearly label the content of a website for machines. Where a human being intuitively recognises the product name, price, availability and rating on a product page, a search engine initially only sees text. Schema Markup translates this meaning into a standardised, machine-readable format: "This is a product, it is called X, costs Y euros, is in stock and has 4.6 out of 5 stars." The basis is the common vocabulary of schema.org, which was launched in 2011 by Google, Microsoft (Bing), Yahoo and Yandex.

How schema markup is implemented technically

Structured data can be embedded in a page in three formats:

• JSON-LD - a separate script block in the HTML that describes the data as JSON. This is the format explicitly recommended by Google because it is cleanly separated from the visible content and can be easily maintained and generated automatically.
• Microdata - attributes that are written directly into the HTML tags of the visible content.
• RDFa - an older variant that also works inline.

In practice, JSON-LD has clearly established itself. A simple product markup in JSON-LD essentially looks like this:

{
  "@context": "https://schema.org",
  "@type": "Product",
  "name": "Example product",
  "offers": {
    "@type": "Offer",
    "price": "49.90",
    "priceCurrency": "EUR",
    "availability": "https://schema.org/InStock"
  }
}

What schema markup does: rich snippets

The most immediate benefit is rich snippets - enriched search results. Instead of just the title and text excerpt, Google displays star ratings, price and availability, recipe cooking times, FAQ pop-ups or event data directly in the search result if the markup is correct. Such results stand out more and often achieve a better click-through rate, even without the position itself changing. Important: Schema markup is not a direct ranking factor. It does not automatically improve the position, but increases the chance of a more conspicuous presentation - and helps search engines to categorise the content correctly.

Common schema types in e-commerce

Why schema markup is becoming increasingly important for SEO and GEO

In addition to classic rich snippets, structured data is becoming increasingly important due to AI-driven search. Google AI overviews, chatbots and response engines need to reliably understand content in order to summarise or quote it correctly. Clearly labelled data - price, manufacturer, availability, author, publication date - reduces the risk of a machine misinterpreting the content. In the discipline of Generative Engine Optimisation (GEO), i.e. optimisation for AI responses, clean schema markup is therefore considered one of the solid technical foundations. It is not a miracle cure for AI visibility, but it eliminates ambiguities.

The good news for Shopware merchants is that Shopware already provides basic markup for product, category and CMS pages, which can be refined via extensions or theme customisations (e.g. to include ratings, FAQs or organisational data).

A concrete example

A shop sells coffee grinders. Without markup, Google only shows the title and description text. With correct Product and AggregateRating markup, the search result also shows "49,90 € - In stock - ★ 4,6 (213 ratings)". If the shop adds a FAQPage markup to the "How do I clean a coffee grinder?" guide page, Google can display the questions as a drop-down list directly in the result. Neither changes the position, but makes the hit more visible and informative - which increases the click rate.

Validation and common errors

Markup should always be tested. There is Google's Test for Rich Search Results and the Schema Markup Validator from schema.org. Typical errors: Markup describes content that is not even visible on the page (Google considers this a violation of the guidelines), mandatory fields are missing, or ratings are labelled that the user cannot see. A particularly expensive trap is "rating spam" - the labelling of invented or page-own ratings, which can lead to manual penalties.

Frequent misunderstandings

Firstly: Schema markup does not directly improve rankings. It affects presentation and comprehension, not position. Secondly, correct markup does not guarantee rich snippets - Google decides on a case-by-case basis whether and how to display enriched markup. Thirdly, more markup is not automatically better; only what is real and visible to the user should be labelled. Fourthly, "schema.org" is often mistakenly seen as a Google invention - it is a collaborative, cross-search engine standard.

Outlook

With the shift from the classic link list to AI-generated answers, the machine interpretability of content is becoming even more important. Structured data is the most reliable way to tell a machine what a piece of content means, rather than leaving it to guess. Those who maintain clean, validated schema markup today are building a foundation that supports both classic rich snippets and AI searches. The authoritative reference for available types is schema.org; Google documents the supported functions in its Search Central documentation.

FAQ

Is schema markup a ranking factor?
No, not directly. It helps search engines understand content and enables rich snippets that can increase the click-through rate - it does not directly influence the position itself.

Which format should I use?
JSON-LD. It is the format recommended by Google because it is separated from the visible content and is easy to maintain.

What are rich snippets?
Enriched search results that show e.g. stars, prices, availability or FAQs directly in the Google hit list thanks to markup.

How do I test my markup?
With Google's test for rich search results and the schema markup validator from schema.org. Both report errors and missing mandatory information.