Structured Data and Schema.org: Practical SEO Guide 2026

Structured datais code that explains to Google what your page contains. It uses the Schema.org vocabulary and JSON-LD format, officially recommended by Google since 2015.

Implementing it correctly doesn't directly improve rankings. But it enables rich snippets—search results enhanced with stars, FAQs, prices, images, and other visual elements that increase click-through rate.

In this guide, I explain what structured data is, how to implement it in JSON-LD, which Schema.org types are most useful in 2026, how to earn rich snippets, and which mistakes to avoid. Everything updated to Google's latest changes.

What Structured Data Is

Structured data is a standardized way to provide information about a webpage's content. It works as machine-readable labels: it tells the search engine what each page element represents.

Without structured data, Google must interpret content based only on visible text. With structured data, it receives explicit information: this is a recipe, this is a product with a price, this is a FAQ with questions and answers.

The vocabulary used is Schema.org, an open standard created in 2011 by Google, Microsoft, Yahoo, and Yandex. Schema.org defines hundreds of entity types and thousands of properties for describing practically any web content.

As of March 2026, Schema.org is at version 28.0 and includes over 800 entity types. Not all are supported by Google for rich snippets, but the vocabulary is also used by other search engines, voice assistants, and AI platforms.

The key concept is simple: structured data makes content understandable to machines, not just humans. This opens the door to advanced SERP features.

Three available formats

Three formats exist for implementing structured data: JSON-LD, Microdata, and RDFa. Each has different characteristics, but the choice in 2026 is practically predetermined.

• JSON-LD: JavaScript code inserted in a script tag on the page. It doesn't mix with your HTML content. Google's recommended format.
• Microdata: HTML attributes added directly to content tags. Requires modifying existing markup and makes code more complex.
• RDFa: similar to Microdata, uses different HTML attributes. Primarily used in academic contexts and by some CMSs. Rarely used in SEO practice.

Google supports all three formats, but explicitly recommends JSON-LD. Official documentation uses JSON-LD in all examples since 2020.

JSON-LD: Google's Recommended Format

JSON-LD (JavaScript Object Notation for Linked Data) is the preferred format for implementing structured data. The main reason is the separation between markup and data.

With JSON-LD, structured code lives in a separate script block from HTML content. You don't need to modify page tags, don't add attributes to existing markup, and the code is easily readable by both developers and search engines.

Basic structure of a JSON-LD block

A JSON-LD block goes inside a script tag with type application/ld+json. It contains a JSON object with three fundamental properties: @context, @type, and type-specific properties.

The @context property indicates the vocabulary used, namely https://schema.org. The @type property specifies the entity type, such as Article, LocalBusiness, or Product. Other properties describe the entity's characteristics.

Example: to describe an article, you use properties like headline for the title, author for the author, datePublished for the publication date, and description for the summary. Each property has a value corresponding to the actual page content.

Fundamental rule: structured data must reflect the visible content on the page. Including information not present in the text violates Google's guidelines and can lead to penalties or rich snippet removal.

Technical benefits of JSON-LD

Beyond simplicity, JSON-LD offers concrete advantages for managing complex sites. Code can be generated dynamically server-side without touching the HTML template. You can insert multiple JSON-LD blocks on the same page to describe different entities.

With JavaScript frameworks like React or Next.js, JSON-LD integrates naturally into the rendering process. The block is generated as a component and inserted in the head or body without conflicts.

Maintenance is simpler than with Microdata or RDFa. If the page layout changes, structured data remains unchanged. If structured data changes, the layout isn't affected. This separation reduces error risk and simplifies updates.

The Most Useful Schema.org Types for SEO

Schema.org defines hundreds of types, but only some generate rich snippets on Google. Focusing on supported types is the most effective way to get concrete results in search results.

Below are the most relevant types in 2026, with the rich snippet type they can generate.

Article and NewsArticle

The Article type applies to editorial content like blog posts, guides, and deep dives. NewsArticle is specific to news and breaking stories. Both can generate expanded previews with title, image, date, and author.

Essential properties: headline, author (as Person or Organization), datePublished, dateModified, image, and publisher. Google uses this data to show content in the Top Stories carousel and in Discover.

FAQPage

The FAQPage type describes pages with frequently asked questions. It generates rich snippets with expandable accordions directly in the SERP. Each question becomes a clickable visual element below the result.

Google modified FAQPage handling in 2023, limiting visibility to institutional and government sites. For commercial sites, structured FAQs appear only in some markets and for some queries. Despite this limitation, implementing them remains useful for semantic understanding.

LocalBusiness

LocalBusiness is the fundamental type for businesses with physical locations. It describes name, address, phone, business hours, geographic coordinates, and service area. It also supports subtypes like Restaurant, MedicalBusiness, and LegalService.

LocalBusiness structured data integrates with the Google Business Profile. It doesn't generate a specific rich snippet, but helps Google link your website with the local entity in the Knowledge Panel.

Product and Offer

The Product type describes goods and services with price, availability, reviews, and images. Offer specifies commercial terms. Together they generate rich snippets with price, availability, and star rating.

In 2026, Google requires stricter required properties than in the past: name, image, and offers with price and priceCurrency are the minimum. For star ratings, you also need aggregateRating or review with valid author.

BreadcrumbList

BreadcrumbList describes the page's hierarchical navigation structure. It generates the breadcrumb path in the SERP, showing the page's position in the site structure instead of the full URL.

It's one of the simplest types to implement and has the highest success rate. Nearly every site with hierarchical structure benefits. The itemListElement property contains the ordered sequence of path elements.

HowTo

The HowTo type describes step-by-step procedures with instructions, required tools, and estimated time. It generates rich snippets with individual steps displayed directly in the SERP.

Google reduced HowTo rich snippet frequency in 2023, showing enhanced results on mobile only for many queries. It remains useful for practical guides, tutorials, and technical procedures.

Organization and WebSite

Organization describes the business entity with logo, contacts, and social profiles. WebSite describes the site overall and enables the Sitelinks Search Box in the SERP. Both go in the homepage.

In 2025, Google added support for hasMerchantReturnPolicy on Organization. For e-commerce sites, specifying return policy in structured data improves product card display.

Summary: type, use, and rich snippet

Here's a summary of the main types with their corresponding rich snippet.

• Article: editorial content. Rich snippet: expanded preview, Top Stories, Discover.
• FAQPage: Q&A. Rich snippet: expandable accordions (limited since 2023).
• LocalBusiness: local businesses. Rich snippet: Knowledge Panel, Maps integration.
• Product + Offer: goods and services. Rich snippet: price, availability, stars.
• BreadcrumbList: hierarchical navigation. Rich snippet: breadcrumb path in SERP.
• HowTo: step-by-step guides. Rich snippet: steps in SERP (primarily mobile).
• Organization: business entity. Rich snippet: Knowledge Panel, logo, Sitelinks Search Box.

How to Earn Rich Snippets on Google

Implementing structured data is necessary but not sufficient for earning rich snippets. Google autonomously decides whether and when to show enhanced results. There's no way to force their appearance.

Technical requirements

To be eligible for rich snippets, structured data must meet precise requirements.

1. All required properties for the type must be present and correctly valued.
2. Structured data must match the visible page content.
3. The page must be indexable (not blocked by robots.txt or noindex meta tag).
4. The site must comply with Google Search quality guidelines.
5. The page must not contain deceptive content, spam, or policy violations.

Timing and variability

After implementing structured data, rich snippets can appear within a variable period from days to weeks. No guaranteed timeline exists.

Google may show rich snippets for some queries and not others, even on the same page. The decision depends on search intent, SERP competition, and overall site quality.

An important fact: according to an Ahrefs study updated in February 2026, only 34% of pages with valid structured data actually earn rich snippets. This doesn't mean implementing them is useless. It means you shouldn't expect automatic results.

Impact on click-through rate

When rich snippets appear, the CTR impact is significant. Results with stars have an average CTR 35% higher than standard results. Expandable FAQs increase the visual surface of the result in the SERP.

Even without visible rich snippets, structured data helps Google better understand content. This can indirectly affect perceived relevance for certain queries.

Deprecated or Modified Types in 2025-2026

Google regularly updates supported structured data types. Some features have been removed or downscaled between 2023 and 2026. Knowing these changes prevents wasting time on obsolete implementations.

Major changes

Here are the seven most relevant changes in the past two years.

• FAQPage limited: since August 2023, FAQ rich snippets appear only for institutional and government sites in most markets. Commercial sites no longer see accordions in SERPs for most queries.
• HowTo reduced: since August 2023, HowTo rich snippets appear only on mobile. Desktop version no longer shows expanded steps in the SERP.
• Sitelinks Search Box updated: in 2024, Google replaced WebSite-based markup with an automatic system. The markup remains recommended but no longer essential for the search box in sitelinks.
• Video with SeekToAction: since 2025, Google requires VideoObject markup with SeekToAction for key moments in videos. The old Clip format is deprecated.
• Review snippets more restrictive: Google tightened criteria for showing stars in the SERP. Self-serving reviews (the business reviewing itself) no longer generate rich snippets.
• Proprietor markup deprecated: SoftwareApplication markup with applicationCategory "GameApplication" no longer generates dedicated rich snippets since 2025.
• Event with new requirements: since 2025, Google requires additional properties for events, including eventAttendanceMode and eventStatus. Events without these don't earn rich snippets.

These changes follow a clear trend: Google reduces rich snippets in areas where abuse was frequent and strengthens requirements where quality is verifiable. Monitoring official documentation is essential for staying current.

Common Mistakes in Structured Data Implementation

Even well-intentioned structured data implementations make mistakes that nullify their effectiveness. Some errors prevent rich snippet generation. Others can trigger manual action from Google.

• Data not matching visible content: including in JSON-LD information absent from the page violates guidelines. If markup declares a price of 49 euros but the page shows 59 euros, Google may remove the rich snippet and penalize the site.
• Missing required properties: each Schema.org type has required and recommended properties. Omitting a required property invalidates the entire block. Google's Rich Results Test flags these errors clearly.
• Wrong type for content: marking an "About Us" page as Article or a services page as Product when you don't sell physical goods. The type must match the content's actual nature.
• JSON-LD with syntax errors: missing commas, unclosed braces, unquoted strings. A syntax error makes the entire block unreadable. Always validate code before publishing.
• Conflicting markup: adding both Microdata and JSON-LD for the same entity type with different data. Google may read contradictory information and ignore both blocks.
• Self-serving reviews: adding Review or AggregateRating markup on pages where the business reviews its own products or services. Google explicitly banned this in 2024.
• Not updating structured data: structured data must reflect the current content state. Old prices, outdated hours, or past events in structured data create incongruencies that Google penalizes.
• FAQPage abuse: adding FAQPage markup to pages without actual Q&A. Or creating artificial questions just to gain SERP space. This practice was one reason for the 2023 FAQ rich snippet restriction.

To identify and fix these errors on your site, the most effective solution is checking with a technical SEO audit that examines both markup validity and content coherence.

Tools for Testing Structured Data

Validating structured data before and after publishing is a mandatory step. Free, reliable tools exist that identify errors, warnings, and improvement opportunities.

Google's Rich Results Test

The Rich Results Test is Google's official tool for checking whether a page is eligible for rich snippets. It accepts both a URL and a code snippet. It shows which rich result types are available and flags errors and warnings.

It's the most important tool because it reflects exactly what Google sees. If the Rich Results Test reports no errors, the markup is technically valid. The tool URL is search.google.com/test/rich-results.

Schema Markup Validator

The Schema Markup Validator (formerly Structured Data Testing Tool) is managed directly by Schema.org. It validates markup against the complete Schema.org vocabulary, not just Google-supported types.

It's useful for verifying syntactic and semantic correctness, even for types Google doesn't use for rich snippets. The URL is validator.schema.org.

Google Search Console

The "Enhancements" section of Google Search Console shows the status of structured data detected by Google across all indexed pages. It flags errors, warnings, and the count of valid elements for each type.

It's the best tool for continuous monitoring. Unlike the Rich Results Test, which analyzes a single page, Search Console gives an overall picture of your entire site. It also lets you verify whether Google is actually generating rich snippets.

Lighthouse and developer tools

Lighthouse, integrated in Chrome DevTools, includes a structured data audit in the SEO section. It flags the presence or absence of structured markup and verifies JSON-LD syntactic validity.

For modern frameworks like Next.js or Nuxt, browser extensions also exist that visualize structured data in real time during development. Tools like Detailed SEO Extension and SEO Meta in 1 Click offer quick markup previews.

Best practices for validation

Validation isn't a one-time step. It's an ongoing process integrated into your workflow.

1. Validate every new page with the Rich Results Test before publishing.
2. Check Google Search Console at least weekly for new errors.
3. After any site update, verify structured data is still correct.
4. When Google announces requirement changes, recheck all affected pages.
5. Document the types used and pages where they're implemented for easier maintenance.

If implementation requires advanced technical skills or your site has hundreds of pages to structure, trusting a professional for proper structured data implementation ensures compliance with Google guidelines.

Structured Data in 2026: Investment or Wasted Effort

Structured data isn't a magic solution for rankings. It doesn't replace quality content, authoritative links, or good site architecture. But it's an important piece of a complete SEO strategy.

Their primary value is twofold. On one hand, they help Google understand content more precisely, improving page relevance for the right queries. On the other, they open the door to rich snippets, which increase visibility and CTR.

With the evolution of AI Overviews and AI-generated results, structured data gain an additional role. They provide AI with precise, verified information about your content, increasing the probability that your site gets cited as a source in generated responses.

The recommendation is clear: implement structured data on every page that benefits from it. Start with the highest-impact types (Article, LocalBusiness, BreadcrumbList, Product) and progressively expand coverage. Always validate markup and monitor results in Search Console.

Those who invest time in correct structured data implementation build lasting competitive advantage. Not because structured data is a ranking factor, but because it makes your site more understandable, more visible, and more clickable.