What is Schema Markup?

Understanding Schema Markup

Schema Markup is a form of structured data that labels important information on a webpage. It can identify an article’s author, a product’s price, or an event’s date. It can also identify an organisation’s contact details. These labels give search engines more context about webpage content. They show more than just words appearing on the page.

Related glossary terms: Structured Data, JSON-LD, HTML.

Schema vocabulary is maintained by Schema.org. It's a shared project supported by major search platforms and other organisations. The vocabulary includes types and properties for entities such as Product, Article, LocalBusiness, Event, and FAQPage. A page can describe several connected entities. The relationships must be accurate and supported by visible content.

Schema Markup doesn't change the wording or visual design visitors see. It adds machine-readable information to the page source. This usually happens through JSON-LD. Search engines can read that information alongside the page. They decide independently whether the page qualifies for an enhanced result.

How Schema Markup Works, Is Measured, or Is Used?

A publisher first selects a suitable schema type. They then add relevant properties and values. For example, a recipe may include preparation time, ingredients, image, rating, and nutrition information. An ecommerce product may include its name, brand, price, availability, and review data. The markup should describe the actual page. It shouldn't add information visitors can't reasonably verify.

JSON-LD is commonly placed in a script element within the page’s source code. Other formats, including Microdata and RDFa, can also express structured data. Their implementation details differ. A typical workflow includes choosing the correct type, mapping visible content to properties, generating the code, publishing it, and checking the result with testing tools.

• Use the Rich Results Test to check eligibility for supported Google search features.
• Use Schema Markup Validator to check general Schema.org syntax and vocabulary use.
• Review search performance reports for detected enhancements and unresolved errors.

Measurement focuses on implementation quality and search appearance. It doesn't focus on one Schema Markup score. Useful checks include valid syntax, required properties, accurate values, detected entities, and eligible rich result types. Search impressions, click-through rate, and indexed pages can show changes after implementation. Other SEO changes may also affect those results.

Why Schema Markup Matters?

Clear structured data can reduce ambiguity for search engines. This helps them interpret complex pages, products, services, and organisations. It can also support enhanced search features. These may display ratings, prices, images, breadcrumbs, or event details. These features can make a result more useful. However, they don't replace useful content, accessible HTML, or strong technical foundations.

Schema Markup also improves consistency on pages with several related entities. For example, an article can identify its author, publisher, image, date, and main topic. Accurate relationships help search systems understand the webpage. They also show which organisation published it. This supports more reliable interpretation. It doesn't guarantee a ranking improvement.

When Schema Markup Matters Most?

Schema Markup becomes especially useful for supported search features. It's also useful when page information could seem unclear. Common examples include online shops, local organisations, publishers, event operators, recipe websites, and software providers. It's also important during website migrations, template changes, and large-scale content updates. Code errors can spread across many URLs.

Accuracy matters more than adding the greatest possible number of types. A page shouldn't use review, event, product, or FAQ markup just to obtain a visual feature. The content must meet the relevant requirements. Regular audits should compare structured data with visible page content. They should check changes in search documentation. They should also remove obsolete or misleading properties.