When we visit a web page, we interpret its information almost without thinking about it. We recognise a title, the author of an article, a publication date, or whether the content refers to a product, an event or a news story. For a machine, however, this interpretation is not quite so immediate.
Structured data exists precisely for this purpose: it makes it possible to describe explicitly what the information on a page represents. It is not only about displaying content, but about making its meaning explicit.
{
"@context": "https://schema.org",
"@type": "Article",
"headline": "When a Website Speaks to Machines",
"datePublished": "2026-09-19"
}An invisible layer of meaning
A page may contain a name, a date and a title. Structured data makes it possible to specify that the name identifies the author, that the date is the publication date and that the text is the headline of the article.
The reader will probably never see this code. Search engines and other systems that process the page can use it.
Schema.org: a shared vocabulary
Much of the structured data published on the web uses Schema.org, a shared vocabulary that can describe articles, people, organisations, products, books, events, places and many other entities. Schema.org organises this information through types, properties and relationships between entities.
It is a way of making explicit that a particular piece of information is not simply text:
- This is an article.
- This person is its author.
- This is the publication date.
- This is the subject.
Beyond SEO
For years, structured data has been associated mainly with SEO and the possibility of obtaining rich results in search engines. Google, for example, uses structured data to better understand the content of a page and, in certain cases, to present it through specific features in search results. Its implementation, however, does not guarantee that these results will appear.
You can find more information in Google’s official documentation on structured data.
The context is also becoming broader. Web content is processed by search engines, assistants and other automated systems that need to identify entities, properties and relationships in order to interpret information appropriately.
And this is where structure matters. A website should not only be readable.
It should also be interpretable.
Structuring information is also a form of communication
Categories, tags, metadata, authorship, dates, hierarchies and relationships between content may appear to be strictly technical elements. In reality, they are part of the same idea: organising knowledge so that it can be understood, connected and reused.
On a web increasingly dependent on systems capable of interpreting and connecting information, structuring content effectively is no longer only a technical matter.
It is also a form of communication.
