What Is Structured Data & Rich Results
Search engines can read the text on your page, but they don't necessarily understand what that text means. A piece of text reading "4.8" doesn't tell the search engine whether it's a rating, a price, or a version number. Structured data uses a standardized format to tell the search engine: this is a rating, out of 5, from 326 reviews. This explicit semantic annotation is the prerequisite for your page to earn Google rich results.
What Is Structured Data#
Structured data is a standardized format used to explicitly describe the meaning of page content to search engines. It doesn't change what users see on the page; instead, it adds an extra layer of semantic annotation in the page code, letting machines accurately understand what the page is about.
Plain HTML tells the browser "this is a heading," "this is a paragraph," "this is an image," but it doesn't tell the search engine the semantic relationships of that content. Structured data fills this gap.
| Plain HTML | With Structured Data |
|---|---|
| Page has a title "Chocolate Cake Recipe" | Search engine knows this is a Recipe named "Chocolate Cake" |
| Page has text "Prep time 30 minutes" | Search engine knows prepTime is PT30M |
| Page has the number "4.8" | Search engine knows this is aggregateRating, ratingValue 4.8, out of 5 |
| Page has a list | Search engine knows this is the recipeIngredient list |
The most mainstream structured data format today is JSON-LD (JavaScript Object Notation for Linked Data). It's written in JSON format, placed inside a <script type="application/ld+json"> tag, fully decoupled from HTML, and doesn't affect page styling or structure. Google officially recommends using JSON-LD.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Article",
"headline": "What Is Structured Data & Rich Results",
"author": {
"@type": "Organization",
"name": "MagicSEO"
},
"datePublished": "2026-06-23"
}
</script>application/ld+json to see them.What Are Rich Results#
Rich Results are enhanced presentations in Google search results that go beyond the standard blue link. They use information from structured data to display richer content directly in the search results page, helping users get key information before clicking.
Common forms of rich results include:
| Rich Result Type | Presentation | Required Structured Data |
|---|---|---|
| Rating stars | Star rating and review count shown beneath the search result | Review / AggregateRating |
| FAQ rich result | Shows questions and answers, only in the few authoritative scenarios Google deems suitable | FAQPage |
| Breadcrumb navigation | The URL position shows a hierarchical path rather than the full URL | BreadcrumbList |
| Recipe card | A card with image, cook time, and rating | Recipe |
| Product info | Shows price, availability, and rating | Product / Offer |
| Event card | Shows date, location, and ticket price | Event |
| Video thumbnail | Shows a video preview directly in the search result | VideoObject |
Rich results are visually more prominent than ordinary search results and may improve click performance. But the effect varies greatly across types, industries, queries, and devices—whether it actually lifts CTR should be verified with real data from Google Search Console.
How Structured Data Works#
The workflow of structured data can be broken into four steps:
- You add structured data to the page: Using JSON-LD format, you describe the semantic information of the page content inside a
<script>tag. - Google crawls and parses: When Googlebot crawls the page, it reads the structured data in the JSON-LD and understands what entity the page describes (article, product, recipe, etc.) and the related properties.
- Google validates and evaluates: Google checks whether the structured data meets format requirements and content policies, whether it's consistent with the page's visible content, and the quality of the page itself.
- Decides whether to show a rich result: If everything passes and the user's search query is suitable for displaying that type of rich result, Google may use the enhanced presentation in search results.
What Structured Data Brings#
The value of structured data shows up on several levels:
- Enhanced search presentation: Rich results are more prominent in the search page and take up more space, creating visual differentiation from ordinary results.
- Improved click performance: Information like ratings, prices, and images helps users judge whether the page matches their need before clicking. Whether it lifts click-through rate should be evaluated against specific queries and Search Console data.
- More qualified traffic: Users get key information (price, rating, time, etc.) before clicking, which means users who click through have clearer intent and higher conversion quality.
- Helps search engines understand content: Even without showing rich results, structured data helps Google more accurately understand what your page is about, which indirectly helps content matching and indexing.
- Future-proofing: AI search (like AI Overviews) increasingly values structured, semantically clear content. Structured data is an important step toward making your content machine-readable.
schema.org vs Google#
schema.org is an open standard co-founded by Google, Bing, Yahoo, and Yandex, defining hundreds of data types (like Article, Product, Event) and thousands of properties. It's the "vocabulary" of structured data.
But in practice, there's a key distinction:
| schema.org | Google Search docs | |
|---|---|---|
| Scope | Defines all available types and properties | Only lists types and properties Google actually supports |
| Requirements | All properties are optional | Distinguishes "required" and "recommended" properties |
| Presentation | Doesn't involve search presentation | Clearly states the rich-result effect of each type |
| Policy | No usage policy | Has strict content policies and quality requirements |
Practical advice: defer to the Google Search Central documentation. schema.org defines what you "can" use; Google's docs tell you what you "need" to use, how to use it, and what happens when you do. For each type, Google's docs list required properties, recommended properties, the presentation effect, and policy requirements.
Where to Start#
If you're new to structured data, learn and implement in this order:
- Start with Article + BreadcrumbList: These two are the most fundamental and widely applicable; almost every content site should implement them.
- Use FAQPage only in real FAQ scenarios: If the page genuinely has FAQ content, you can add FAQPage to help machines understand it; but ordinary content sites shouldn't treat it as a reliable way to earn FAQ rich results.
- Choose more types based on your site type: E-commerce does Product, recipe sites do Recipe, sites with video do VideoObject, and so on.
- Validate with Rich Results Test: After every addition or change to structured data, verify it's correct with Google's testing tool.
- Monitor in Search Console: After launch, track status through GSC's rich results report.
Subsequent articles in this section cover each one in turn: a comparison of the three formats with JSON-LD hands-on practice, using Rich Results Test, Search Console monitoring, and detailed implementation guides for each rich result type.
Core Principles#
Before diving into each type, keep these principles that run throughout:
- Structured data must match the page's visible content: You can't mark up content that doesn't exist on the page. If you declare a 4.8 rating, that rating must be visible on the page.
- Don't mark up hidden or deceptive content: Google takes manual action against violating structured data, removing rich result presentation directly from search results.
- Follow Google's docs, not community speculation: Structured data support status changes (for example, HowTo support was reduced)—always treat official Google documentation as the final authority.
- Correct before complete: One correct Article markup is more valuable than a pile of erroneous complex markup.
Frequently Asked Questions#
Can structured data directly boost rankings?
Structured data itself isn't a direct ranking factor. Its core value is helping search engines understand page content more accurately and qualifying the page for rich result presentation. Rich results may improve search presentation and click performance, but Google doesn't guarantee display and doesn't guarantee a ranking boost.
What's the relationship between structured data and schema.org?
schema.org is a common vocabulary maintained jointly by Google, Bing, Yahoo, and Yandex, defining hundreds of data types and properties. Google's structured data features are based on the schema.org vocabulary but only support a subset of its types and properties, with its own additional requirements and restrictions. In practice, defer to the Google Search Central documentation rather than just the schema.org definitions.
Does adding structured data guarantee rich results will be shown?
Not necessarily. Correct markup is only a precondition; Google also decides whether to show based on page quality, query type, region, device, and other factors. Even with entirely correct structured data, Google may choose not to show it. But without correct structured data, the page has zero chance of earning rich results.
My site is small—do I still need structured data?
Yes. The cost of structured data is very low (especially JSON-LD, fully decoupled from HTML), but the potential upside is clear. Even small sites should implement the two basic types, Article and BreadcrumbList, on every page. If a page genuinely has FAQ content, you can add FAQPage as a semantic marker, but ordinary content sites shouldn't expect it to reliably trigger FAQ rich results.