Structured data and rich results
Structured data describes a page's content in a format engines can read. It may give rise to a rich display, but no markup earns one by right: the documentation says so explicitly, even where the markup is correct. It describes, it does not request.
What is structured data for?
For describing a page’s content in a form a program can read without having to interpret prose. A recipe page contains a cooking time somewhere in its text; the markup says “this is a cooking time”. It is descriptive work, and the vocabulary used is not the property of any one engine.
The schema.org vocabulary is a collaborative activity founded by Google, Microsoft, Yahoo and Yandex, developed through an open process coordinated with the W3C.
officialSource : schema.org, home page, version 30.0 published on 2026-03-19
That shared origin has a practical consequence often overlooked: the vocabulary covers far more cases than any given engine uses for its displays.
The schema.org vocabulary contains far more types than any one engine uses for display, which explains how valid markup can have no visible effect.
hypothesis
Hence the only list that counts when the goal is a rich display:
The engine publishes the list of markup types it actually uses to produce rich displays, organised by category.
officialSource : Google Search Central, “Structured data markup that Google Search supports”
Marking up a type absent from that list is not a fault: it is a valid description, which may serve other consumers. It will simply produce no particular display, and it is better to know that before spending a day on it.

The promise nobody is making you
This is the most important point in the guide, and it is written in plain words:
The engine does not guarantee that your structured data will appear in the results, even if the page is marked up correctly.
officialSource : Google Search Central, “General structured data guidelines”
Any service selling “the stars in the results” or “the recipe carousel” is therefore selling something its own supplier states it does not guarantee. The formula to keep is simple: markup makes a display possible, it never makes one owed. The engine chooses its presentation according to the query, and may judge that an ordinary result serves the reader better.
That does not devalue the work. An accurate description of your content is useful for other reasons: it survives changes of presentation, it serves consumers other than search engines, and it forces you to formalise what the page actually contains.
The rule that costs most when you go around it
Content that is not visible to the readers of the page must not be marked up.
officialSource : Google Search Central, “General structured data guidelines”
A short sentence, an enormous temptation. Marking up an average rating the page does not display, a price that is not the one shown, an invented update date: each of those gestures improves the appearance of the result without touching the page. That is precisely what the rule forbids, and the penalty is not local — what is at stake is the credibility of the whole site’s markup.
Marking up a type actually used, mirroring the visible content
hypothesis
- Effort
- moderate
- Time to effect
- weeks
- Risk
- low
- Durability
- lasting
Risk at level two is not trivial, and it comes from a discreet mechanism:
Describing your data in a separate block rather than in attributes scattered through the HTML makes divergence between the markup and the displayed text easier to introduce, and therefore worth watching.
hypothesis
A data block lives beside the text. The text changes, the block stays. Six months later the page displays one thing and declares another, without anyone having decided it. The defence is to generate the markup from the same data as the display, never to write it by hand in parallel.
Update of 11 August 2026
The generative AI optimisation guide published by the engine on 10 July 2026 states that structured data is not required for its generative features, and that no particular markup needs adding for them. That takes nothing away from what is written above: their documented role remains eligibility for certain rich displays in the classic results. The full record is in the monitoring log.
What do you check, and in which order?
First, that the type you are aiming at is among those actually used. Then, that the markup is syntactically valid, which a validator settles in seconds. Then — and this is the step nobody takes — that every declared value can be found on screen. Finally, if the page depends on scripts, that the markup does exist after rendering: a block injected by a script is read, but it is read at render time, with the lag that implies.
What does not work, or no longer works
Add review markup with a rating of 4.8 out of 5 to all your product pages to show stars in Google and raise your click-through rate.
This site emits no rating or review markup at all, and that is not a legal precaution: it does not score tools out of five stars. It assesses them on four written axes, whose filling-in the method page explains. A single figure hides the reasoning; four named axes expose it, and nobody needs markup for that.
Sources
- General structured data guidelines — Google Search Centralaccessed on
- Structured data markup that Google Search supports — Google Search Centralaccessed on
- schema.org (version 30.0, published on 2026-03-19) — schema.orgaccessed on
- Understand the JavaScript SEO basics — Google Search Centralaccessed on
Block revalidated on
Frequently asked questions
- Does markup guarantee a rich display?
- No, and the documentation writes it bluntly: no rich display is guaranteed, even where the page is marked up correctly. The engine chooses its presentations according to the context of the query, and may judge that an ordinary result serves the reader better. Valid markup is a necessary condition, never a sufficient one.
- Can you mark up a rating or a review the page does not display?
- No. The rule is explicit: content invisible to readers is not marked up. Markup describing something other than what the page shows risks having every rich display on the site withdrawn, not merely the one on the offending page.
- Which format should you use to write structured data?
- The separate-block format is the simplest to produce and to read back, and it is the one the documentation puts forward. Its drawback is living beside the text rather than inside it, and therefore being able to contradict it without that showing on screen.
- Should every page on a site be marked up?
- Only where the content type matches a display the engine actually uses. Marking up for its own sake produces code to maintain with no observable effect, and every piece of markup becomes a second version of the content that has to be kept in step.