Skip to content
BENIBIX Learn

Structured Data and Schema

Level 4 · The technical layer

A small block of labels in a page's code that tells the engine exactly what the page holds. How it can turn a plain link into a rich result.

Course contentsLesson 11 of 15

After this lesson you can

  • Say what structured data does
  • Read a small JSON-LD block
  • Know which pages can earn a rich result

11 mincovers 1 glossary entries

Worth reading first: Core Web Vitals and Speed

How labels in the code earn a rich result

Structured data is a block of labels in a page's code that tells a search engine exactly what the page holds. A recipe page can label its cooking time, its rating and its calories. With those labels, the engine can show a rich result: the plain link plus stars, a time or a price. Readers never see the labels themselves.

The labels come from a shared list called Schema.org, made by the big search engines together. It has types for recipes, products, events, reviews, jobs, local businesses, articles and many more. Each type has its own fields, such as price or start date.

Google asks for the labels in a format called JSON-LD. It is a short block of text in the page's code, apart from what readers see. That makes it easy to add without touching the design.

The labels must match what is on the page. A product marked as 5 stars must show those reviews to readers. Marking up things the reader cannot see breaks the rules, and the engine can remove rich results from the whole site.

Structured data does not move a page up the rankings on its own. It changes how the result looks. A link with stars and a price stands out, so more people click it, even at the same position.

Not every type earns a rich result. Google shows them for a set list, and it changes that list over time. Labels still help the engine understand the page, even when no extras appear.

The common mistake is adding the labels and never testing them. A missing comma can break the whole block. Google's Rich Results Test shows whether a page's labels are read and which extras it can earn.

json
{
  "@context": "https://schema.org",
  "@type": "Product",
  "name": "Wide-Fit Hiking Boot",
  "offers": { "@type": "Offer", "price": "89.00", "priceCurrency": "GBP" },
  "aggregateRating": { "@type": "AggregateRating", "ratingValue": "4.6", "reviewCount": "212" }
}
A product labelled in JSON-LD. The engine reads the name, the price and the rating, and can show them under the link.
The labels are invisible on the page. In the results they become stars and a price that catch the eye.

Worked example

A cooking site adds recipe labels

A cooking site has 300 recipes with no structured data. Its results show only a title and a line of text.

It adds recipe labels for time, rating and calories. Rankings stay about the same. But clicks from search rise by about a third, because the results now show stars and cooking times.

The words for this lesson1

Check yourself

What does structured data on a page usually change?

Finished this lesson?

Marking it complete also marks its 1 glossary entries learned, which updates your roadmap and your saved page. 0 are already marked.