Schema markup is the use of the Schema.org vocabulary to explicitly describe a page’s content to search engines. It is a shared vocabulary that lets a machine understand that a block of text is not just a string of words but the title of an article, the price of a product, the date of an event, or a cake recipe. It is written in one of three formats: JSON-LD, microdata, or RDFa. Without these annotations, the search engine has to infer meaning from context, with a higher margin of error.
In SEO, schema markup is part of on-page optimization and is often associated with rich results, the enhanced presentations that appear in search results with stars, images, prices, or information panels. Its main purpose is not to change ranking position but to improve how content is understood and displayed, increasing the chance of qualified clicks.
Structured data: what it is and what it is for
Schema markup is a form of semantic annotation based on a shared vocabulary maintained by an international community and supported by major search engines. The goal is to provide structured data, meaning information organized according to a recognizable schema, alongside the content visible to the user without altering it.
The annotations are not visible on the page but are read by crawlers during indexing. This allows the search engine to build a more precise representation of the entity described: a person, a company, a product, an article, an event, or a place.
Difference between structured data and visible content
Visible content is what the user reads on the page. Structured data is metadata that describes that content. Search engine guidelines require consistency between the two: the markup must reflect information actually present and verifiable on the page, without adding elements not shown to the user.
Types, properties, and relationships between entities
The vocabulary defines entity types and associated properties. Each type describes a category of object, while properties specify its attributes. An article, for example, can have an author, a publication date, and a main image. A product can have a price, a currency, and an availability.
Properties can be nested, creating relationships between different entities. This allows you to describe complex structures, such as an event with a location, an organizer, and a linked offer.
Implementation formats
The vocabulary can be written in three formats. JSON-LD is a separate block that collects all annotations in a single structure and is the format recommended by Google. Microdata are attributes added directly to HTML elements. RDFa is a third, less-used format, also based on attributes.
The most common types in SEO strategies
Some types appear more frequently in optimization strategies because they correspond to widespread content and rich results that users easily recognize.
Article, product, FAQ, and breadcrumb
The article type describes editorial content and can include author, date, and publisher. The product type collects commercial information such as price, currency, and availability. The FAQPage type groups questions and answers, but since 2023 Google shows the rich result only for authoritative government and health sites (see FAQ schema). The breadcrumb type describes the navigation path and can appear in place of the URL in search results.
| Schema type | Typical content | Main properties | Google result |
|---|---|---|---|
| Article | News, guides, blogs | Author, date, image | Describes the article; no guaranteed rich result |
| Product | E-commerce pages | Price, currency, availability | Can show price, availability, and ratings |
| FAQ | Informational pages | Question, answer | Since 2023 only for authoritative government and health sites |
| Breadcrumb | Navigation paths | Position, item | Can show the path instead of the URL (reduced visibility on desktop) |
| Event | Calendars and venues | Date, location, offer | Can show date and location |
What it offers and what it does not guarantee
The main benefits are semantic clarity and access to enhanced presentations. A well-annotated page is easier to interpret and can gain more visibility in search results, with positive effects on click-through rate.
The limits are the lack of guarantees: search engines are not obliged to show a rich result even when the markup is correct. Also, incorrect or misleading annotation can be ignored and, if it violates guidelines, lead to a manual action on structured data. Markup does not replace content quality and does not guarantee better positions.
Steps to annotate a page
Implementation follows a methodical path, from choosing the type to final verification. Below are the essential steps.
- Define the page’s main entity and choose the most suitable schema type.
- Identify the necessary properties and verify that the data is present in the visible content.
- Choose the annotation format that is most manageable for your publishing system.
- Insert the annotations into the page’s HTML code, avoiding duplication or conflicts.
- Check the syntax with the Schema.org Validator and Google’s requirements with the Rich Results Test.
- Verify compliance with the guidelines of the relevant search engine.
- Monitor performance in search results and fix any reported errors.
- Update the annotations when the page content changes.
Frequently asked questions about schema markup
Does schema markup improve ranking?
It is not a direct ranking factor. It can improve content understanding and increase click-through rate thanks to rich results, with indirect effects on performance.
What formats can be used for annotations?
JSON-LD, microdata, and RDFa. Google recommends JSON-LD but also reads the other two.
Are rich results guaranteed?
No. Search engines decide independently whether and when to show a rich result, even with correct annotations that comply with guidelines.
Can multiple entities be annotated on the same page?
Yes, it is possible to describe multiple entities and link them together, as long as each annotation corresponds to content actually present and consistent.
Is schema markup visible to users?
The annotations are not visible on the page but can influence how the content is presented in search results.
Does it require specialized technical work?
It depends on the publishing system. Some content management systems include automatic features, while in other cases you need to modify the code or use dedicated components.
From glossary to projectDo search engines understand what your site is about?Implementing structured data and Schema markup helps search engines and AI systems interpret content.Discover structured data
Related entries:
Schema.org Offer schema Breadcrumb schema Product schema Review schema