Schema markup (structured data)

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 shared 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 is easy to maintain and generate automatically.
• Microdata – attributes written directly into the HTML tags of the visible content.
• RDFa – an older variant that also works inline.

In practice, JSON-LD has clearly won out. At its core, a simple product markup in JSON-LD 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 achieves: rich snippets

The most immediate benefit is rich snippets – enhanced search results. Instead of just the title and a text excerpt, with correct markup Google displays, for example, star ratings, price and availability, recipe cooking times, FAQ drop-downs or event dates directly in the search result. 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 eye-catching display – and helps search engines classify the content correctly.

Common schema types in e-commerce

Why schema markup is becoming ever more important for SEO and GEO

Beyond classic rich snippets, structured data is gaining importance through AI-driven search. Google AI Overviews, chatbots and answer engines have to understand content reliably in order to summarise or cite it correctly. Unambiguously 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 answers, clean schema markup is therefore regarded as one of the solid technical foundations. It is not a miracle cure for AI visibility, but it clears ambiguities out of the way.

For Shopware retailers, the good news is that Shopware already provides basic markup for product, category and CMS pages, which can be refined via extensions or theme adjustments (for example with reviews, FAQs or organisation 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 additionally shows "€49.90 · In stock · ★ 4.6 (213 reviews)". If the shop adds FAQPage markup to its guide page "How do I clean a coffee grinder?", Google can display the questions as an expandable list directly in the result. Neither changes the position, but both make the result more visible and informative – which increases the click-through rate.

Validation and common mistakes

Markup should always be tested. For this there is Google's Rich Results Test and the Schema Markup Validator from schema.org. Typical mistakes: markup describes content that is not visible on the page at all (Google treats this as a breach of its guidelines), required fields are missing, or reviews are marked up that the user cannot see. A particularly expensive trap is "rating spam" – marking up invented or self-serving reviews, which can lead to manual penalties.

Common misconceptions

First: schema markup does not directly improve rankings. It influences display and understanding, not position. Second, correct markup does not guarantee rich snippets – Google decides case by case whether and how it serves the enhanced display. Third: more markup is not automatically better; only what is real and visible to the user should be marked up. Fourth, schema.org is often wrongly seen as a Google invention – it is a joint standard spanning several search engines.

Outlook

With the shift from the classic list of links towards AI-generated answers, the machine interpretability of content is becoming even more important. Structured data is the most reliable way of telling a machine what a piece of content means instead of letting it guess. Anyone who maintains clean, validated schema markup today is building a foundation that supports both classic rich snippets and AI search. The authoritative reference for available types is schema.org; Google documents the supported features 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 separate from the visible content and easy to maintain.

What are rich snippets?
Enhanced search results that, thanks to markup, show for example stars, prices, availability or FAQs directly in the Google results list.

How do I test my markup?
With Google's Rich Results Test and the Schema Markup Validator from schema.org. Both report errors and missing required information.