Schema markup that still matters in 2026

Structured data is code, usually JSON-LD, that describes what a page is about in a format machines can read without guessing. It can make pages eligible for rich results such as review stars, product prices, and breadcrumbs. It also helps search engines and AI systems connect your pages to real-world entities: your company, your products, your authors.

Google has trimmed several rich result types over the past few years, so it is worth knowing which markup still earns its keep.

What structured data does (and does not) do

It does:

• Make pages eligible for specific rich result features.
• Help search engines understand entities and relationships on the page.
• Give AI systems clean, unambiguous facts about your organization and offerings.

It does not:

• Directly boost rankings on its own.
• Guarantee a rich result. Eligibility is not the same as display.
• Make up for content that is not on the page. Markup must describe visible content.

The types worth implementing

Organization

Every site should have it, usually on the homepage. Include your name, logo, URL, social profiles (sameAs), and contact details. It is the foundation for brand understanding in search and AI. We cover it alongside llms.txt in making your site legible to AI.

Article / BlogPosting

For editorial content. Include headline, datePublished, dateModified, image, and an author with a name and url pointing to an author page. This supports the authorship signals discussed in E-E-A-T in practice.

BreadcrumbList

Simple and widely supported. It helps search engines understand site hierarchy and can replace the raw URL in search snippets with a readable path.

Product, Offer, and Review

Essential for ecommerce. Product markup with price, availability, and ratings powers merchant listings and product snippets. Keep prices and stock status in sync with the visible page; mismatches can get markup ignored.

SoftwareApplication

For SaaS and apps. Include applicationCategory, operatingSystem, and offers. Ratings can be included if they come from real users and are shown on the page.

LocalBusiness

For businesses with physical locations: address, opening hours, phone, and geo coordinates. Pair it with an accurate Google Business Profile.

Event, JobPosting, Recipe, VideoObject

Use them when the content genuinely matches. These remain among the most visible rich result types in their verticals.

Types that changed

• FAQPage rich results are now limited to well-known, authoritative government and health sites. Markup is still valid and can help machines parse question-and-answer content, but most sites should not expect the expanded snippet.
• HowTo rich results were removed from Google Search. The content pattern is still useful for readers and AI answers; just do not rely on the visual feature.

Implementation tips

• Use JSON-LD in the page <head> or body. It is Google's recommended format and is easier to maintain than inline microdata.
• Generate it from your data, not by hand. Template-level markup stays consistent as content changes.
• Connect entities with @id. Give your Organization and authors stable IDs and reference them from articles and products. This builds a small knowledge graph of your own site.
• Mark up only what is visible. Hidden or misleading markup can lead to a manual action.

Testing and monitoring

1. Validate with Google's Rich Results Test and the Schema.org validator before release. 2. Check the Enhancements reports in Search Console for errors and warnings after release. 3. Re-test after template changes; a small front-end update can silently break markup on thousands of pages.

Common mistakes

• Missing required properties, such as price on an Offer.
• Ratings markup that does not match visible reviews.
• Multiple conflicting Organization blocks across templates.
• Marking up content that only appears for logged-in users.
• Using outdated or misspelled types and properties.

SearchVoro checks structured data during every site crawl, flags missing or broken markup by template, and confirms whether your Organization and author entities are consistent across the site.