What Is Structured Data Markup? Rich Results and What Changed in 2026
Structured data markup is code added to a webpage that describes its content in a standardized, machine-readable vocabulary — telling a search engine explicitly that a number is a price rather than leaving it to infer that from surrounding text. It's not a ranking factor by itself, but valid markup can make a page eligible for rich results, and 2026 brought the biggest change to that eligibility landscape in years with the retirement of FAQ rich results.
⚡ Key Takeaways
- Structured data markup is the code; schema.org is the vocabulary; JSON-LD, Microdata, and RDFa are the formats that carry that vocabulary onto a page.
- Google supports all three formats but recommends JSON-LD because it's easier to implement and maintain without touching visible markup.
- It's not a direct ranking factor. Its confirmed benefit is rich-result eligibility, which affects visibility and click-through rate, not ranking position.
- FAQ rich results were permanently retired from Google Search on May 7, 2026; HowTo rich results are also no longer supported.
- The eligible schema types depend entirely on actual page content — Product, Article, Event, Organization, LocalBusiness, and others each require the corresponding content to genuinely exist on the page.
- No special schema.org markup is required for eligibility in AI Overviews or AI Mode — those surfaces work from ordinary page content, not a dedicated markup type.
What Is Structured Data Markup?
Structured data markup is code added to a webpage's underlying HTML that explicitly describes its content using a shared, standardized vocabulary — most commonly schema.org — rather than leaving a search engine to infer meaning from visible text alone. Where a human reader sees "Solid oak chair — €249 — 4.6/5 (128 reviews)" and infers the relationships intuitively, structured data spells it out unambiguously: this is a Product, its name is this string, its offers.price is that number, its aggregateRating is this value.
Four terms get used close together and are worth separating: structured data is the organized information itself; schema.org is the vocabulary defining what properties and types mean; a specific format — JSON-LD, Microdata, or RDFa — is how that vocabulary gets written onto the page; and schema markup is the general term for the resulting code, regardless of which format produced it.
The Three Formats
| Format | How it's embedded | Google's stance |
|---|---|---|
| JSON-LD | Self-contained script block, separate from visible HTML. | Recommended — easier to implement, validate, and maintain. |
| Microdata | Attributes embedded directly in visible HTML elements. | Supported, but more error-prone to maintain. |
| RDFa | Attributes embedded in visible HTML, using a different attribute vocabulary than Microdata. | Supported, less commonly used than the other two. |
Rich Results and Eligible Types
Rich results are enhanced search listings that show information beyond a standard title, URL, and description — star ratings, price, stock status, breadcrumbs, event dates, or video thumbnails, depending on the schema type and the page's actual content. These enhancements make a listing more visually prominent and, in aggregate analyses, correlate with meaningfully higher click-through rates than a standard result. Eligibility is type-specific and content-dependent: Product, Article, BreadcrumbList, Organization, LocalBusiness, Event, and VideoObject each require the corresponding content type to genuinely exist on the page — markup describing something not actually present violates Google's guidelines.
What Changed in 2026
The most significant shift: Google permanently retired FAQ rich results from Search on May 7, 2026, following an earlier 2023 restriction that limited them to authoritative government and health sites. FAQPage markup still validates without errors and remains harmless to keep, but it produces zero search-listing benefit going forward. HowTo rich results were similarly deprecated on desktop earlier and are no longer supported. Neither retirement changes the value of writing genuinely useful FAQ or how-to content for readers — it only removes the specific SERP-visibility incentive that used to come with marking that content up in schema.org's terms. Separately, no dedicated schema.org markup is required for a page to be eligible for citation in AI Overviews or AI Mode; those surfaces draw from ordinary page content rather than a specific structured data type built for them.
Audit structured data coverage across your site
Nstdata Crawl can fetch pages at scale and extract their structured data blocks, surfacing missing, outdated, or now-obsolete schema types like FAQPage before you invest more effort in them.
Try Nstdata Crawl →Structured Data Markup vs. Adjacent Concepts
JSON-LD is one specific format for delivering structured data markup, and currently the one Google recommends by default — but it's a format, not a synonym for the broader concept. Structured data markup itself is a subset of the wider on-page technical signals a page can carry; unlike meta tags such as title and description, structured data doesn't change what's visibly rendered to a human reader at all, it only adds a machine-readable layer alongside it.
Limits
Structured data markup is not a direct ranking factor and never has been — it earns eligibility for enhanced display, not a ranking boost, and Google decides independently whether to actually show any given rich result even on fully valid, eligible markup. Markup that doesn't accurately reflect visible page content is treated as a guideline violation, so it should never be used to describe content that isn't genuinely present. And as the 2026 FAQ retirement demonstrates, rich-result eligibility for a given schema type isn't a fixed, permanent benefit — it's a Google product decision that can change, so markup investments are best weighted toward types with a track record of continued support.
Conclusion
Structured data markup gives search engines an explicit, machine-readable description of page content, most commonly delivered as JSON-LD using the schema.org vocabulary — and its confirmed benefit is rich-result eligibility, not a direct ranking effect. 2026's retirement of FAQ and HowTo rich results is a reminder that this eligibility shifts over time, so validate which schema types still produce a visible benefit before prioritizing implementation effort around them.
For teams that want to audit structured data coverage and accuracy across many pages, evaluate Nstdata Crawl for that extraction step.
Further Reading
Sources
Try Nstdata Crawl for structured data audits
Extract and validate schema markup across your site at scale.
Try Nstdata for Free →FAQ
Does structured data markup directly improve search rankings?
No. It's not a direct ranking factor. Its confirmed benefit is eligibility for rich results, which can improve visibility and click-through rate but doesn't change ranking position on its own.
Is FAQPage structured data still worth implementing?
FAQ rich results were permanently retired from Google Search on May 7, 2026. FAQPage markup still validates but no longer produces any visible search-listing benefit, so it's no longer worth prioritizing for that reason.
Which structured data format does Google recommend?
JSON-LD, over the two alternatives Microdata and RDFa, primarily because it's a self-contained script block that's easier to implement, validate, and maintain without touching visible page markup.
Do I need special schema markup to appear in AI Overviews?
No. No dedicated schema.org markup is required for eligibility in AI Overviews or AI Mode — those surfaces draw from ordinary page content rather than a purpose-built structured data type.
What happens if structured data describes content not actually on the page?
Google treats this as a guideline violation. Markup must accurately reflect visible page content — mismatched or "invisible" schema can be ignored or result in a penalty rather than earning a rich result.
Was this guide helpful?
Your choice is saved on this device.


