Schema markup, also called structured data, is code you add to a page to describe its content in a standard vocabulary from schema.org. Done well, it makes your pages eligible for rich results in Google and helps machines understand what your content is. The catch is that only some types earn visible features, and Google retires ones that stop being useful, so it pays to focus on what actually works.
What structured data does and does not do
Structured data helps engines interpret your content and can qualify a page for enhanced search appearances like star ratings, event details or breadcrumbs. What it does not do is directly boost your ranking. Google has been clear that adding schema is not a ranking hack, and that no special structured data is required to appear in its AI features. Think of it as improving how your result can look and how clearly it is understood, not as a shortcut up the results page.
Schema types Google actually supports
Google only renders rich results for a defined list of types, and that list changes. As of 2026, well supported types worth considering include:
Article for news, blog and editorial content.
Product and Review snippet for ecommerce, enabling price, availability and star ratings.
Organization to describe your business, logo and contact details.
Local business for physical locations with address and hours.
Breadcrumb to show a clear path in the result.
Event, Job posting, Recipe and Video for those specific content types.
Match the type to what the page genuinely is. Marking up content that does not fit is a common cause of errors and manual actions.
Types that have lost their rich results
This is where honesty saves you effort. FAQ and HowTo markup no longer produce the rich results many guides still promise. Google removed HowTo rich results and heavily reduced then withdrew FAQ rich results for most sites, so adding that markup today will not surface those old features. The FAQPage vocabulary itself is still valid and will not break anything, but do not expect a visible payoff. Always check Google's current documentation rather than trusting an older tutorial.
How to implement it well
A few practical rules:
Use JSON-LD, which is Google's recommended format and the easiest to maintain.
Only mark up content that is actually visible on the page.
Keep the structured data accurate and in sync when the page changes.
Validate with Google's Rich Results Test and the schema.org validator before and after publishing.
Watch the Enhancements reports in Search Console for errors once it is live.
The takeaway
Schema markup is worth doing for the types that still earn rich results and for helping machines understand your content, as long as you apply it honestly and keep it current. Skip the deprecated types, ignore anyone promising rankings from schema alone, and check the official docs when in doubt.
We build structured data into sites correctly as part of development at Urest, matched to what each page actually is. If you want to know which schema would genuinely help your site, Book a discovery call and we will map it out.
B2B SEO: A Playbook That Fits How B2B Buyers Search
B2B SEO is not about the biggest keywords. It is about intent, depth and answering the buying committee. Here is a playbook that fits how B2B works.
Schema Markup That Actually Helps You Get Found
Not all structured data earns rich results. Here are the schema types Google actually supports in 2026 and how to use them without wasting effort.