SEO13 min read

Structured Data SEO 2026: Rich Results Guide

A guide to JSON-LD for Google Search features, with Article, Product, LocalBusiness and BreadcrumbList examples and current eligibility guidance.

Published · Updated
13 min read
4

Google-Recommended Schema Types

JSON-LD

Google's Recommended Format

Key Takeaways

JSON-LD is the only format Google recommends: Embed structured data as a JSON-LD script tag in the document head or body. Avoid Microdata and RDFa — they are error-prone and harder to maintain. JSON-LD keeps schema markup cleanly separated from your HTML structure.
Rich results require eligibility, not just correct markup: A page can be eligible if it satisfies the requirements for a currently supported Google feature. Google stopped showing its FAQ rich result in May 2026.
Article markup describes the article and its author: Article markup can help Google understand the headline, publication dates, author and representative images. Google retired the separate sitelinks search box in November 2024.
Product requirements depend on the search feature: For product snippets Google requires name and at least one of review, aggregateRating or offers. Merchant listings have separate image and offer requirements and apply to pages where customers can buy the product.
Test with Rich Results Test before deploying any schema changes: Use the Rich Results Test to check supported features and required fields. Verify that the markup matches the visible content and follow the relevant feature policies.

Structured data describes facts on a page in a machine-readable form. On eligible pages it can help Google show details such as a product price or an article date. Appearance can vary by query and device. Measure what changes on your own URLs. Google’s introduction to structured data.

This guide covers every practical aspect of structured data SEO in 2026: the JSON-LD format Google recommends, the specific schema types that drive rich results, the eligibility restrictions that prevent many common schemas from working, and the testing tools that validate your implementation before you deploy. We also cover the eligibility constraints that trip up most SEOs — including why Google ended FAQ rich results in May 2026.

Structured Data Impact on SEO

Google may use structured data to create an enhanced search appearance when content meets feature requirements. Google’s current Search gallery describes the appearances and types Google currently supports. Inspect the results for queries that matter to your pages before using rich-result performance in business forecasts.

Compare observed click-through rates among comparable pages, queries, devices and positions. When the query mix changes, a before-and-after comparison can exaggerate the impact of the template change.

Schema TypeRich ResultEligibility
ProductPrice, ratings, availabilityAll sites
ArticleAuthor, date, headlineAll sites
HowToStep carousel (deprecated)Deprecated Sep 2023
BreadcrumbListURL path in result snippetAll sites
FAQPageFormer expandable Q&ARetired May 2026

Start with the requirements for each eligible feature and add relevant recommended fields where you have accurate content. Product snippets can use an offer without review data. Article markup has recommended properties, including author, to help Google understand the page. For a full technical audit covering structured data alongside all other SEO factors, see our 2026 technical SEO audit checklist.

JSON-LD Implementation Basics

JSON-LD (JavaScript Object Notation for Linked Data) is the structured data format Google recommends. It embeds schema markup as a standalone <script> tag with type="application/ld+json", keeping your structured data entirely separate from your HTML structure. This separation makes it dramatically easier to add, update, and maintain schema without touching your page markup.

Basic JSON-LD Structure
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "Structured Data SEO 2026: Rich Results Guide",
  "author": {
    "@type": "Person",
    "name": "Richard Szakacs",
    "url": "https://www.digitalapplied.com/about"
  },
  "publisher": {
    "@type": "Organization",
    "name": "Digital Applied",
    "logo": {
      "@type": "ImageObject",
      "url": "https://www.digitalapplied.com/logo.png"
    }
  },
  "datePublished": "2026-02-22",
  "dateModified": "2026-02-22"
}
</script>
JSON-LD
Google recommended

Separate script tag, easy to maintain, fully supported by all major search engines. Can be injected dynamically.

Microdata
HTML-embedded attributes

Mixes schema into HTML markup, making maintenance difficult. Prone to errors when HTML changes.

RDFa
XML-derived attributes

Complex syntax, requires modifying HTML structure. No practical advantage over JSON-LD for SEO purposes.

JSON-LD in Next.js App Router

In Next.js App Router, inject JSON-LD structured data directly inside your page component JSX using a <script> tag with dangerouslySetInnerHTML. The Metadata API only generates <meta> tags — it cannot inject script tags. Create a reusable server component that accepts a schema object and serializes it safely.

Next.js Structured Data Component
// components/structured-data.tsx
interface StructuredDataProps {
  schema: Record<string, unknown>;
}

export function StructuredData({ schema }: StructuredDataProps) {
  return (
    <script
      type="application/ld+json"
      // biome-ignore lint/security/noDangerouslySetInnerHtml: Sanitized schema object
      dangerouslySetInnerHTML={{ __html: JSON.stringify(schema) }}
    />
  );
}

// Usage in page.tsx
import { StructuredData } from "@/components/structured-data";

export default function BlogPost() {
  const schema = {
    "@context": "https://schema.org",
    "@type": "Article",
    "headline": "My Post Title",
    "datePublished": "2026-02-22",
  };

  return (
    <>
      <StructuredData schema={schema} />
      <article>...</article>
    </>
  );
}

Article Schema for Blog Posts

Article schema is the foundation for blog post structured data. When properly implemented, it signals to Google the headline, author identity, publication date, modification date, and the publishing organization. Google uses this data for article carousels, author attribution in search results, and freshness signals in its ranking algorithms.

The three Article subtypes — Article, NewsArticle, and BlogPosting — all work for blog content, but BlogPosting is semantically most accurate for editorial blog content. NewsArticle is appropriate for time-sensitive news coverage. Article is the generic fallback. All three share the same required and recommended properties.

Complete Article Schema (BlogPosting)
{
  "@context": "https://schema.org",
  "@type": "BlogPosting",
  "headline": "Structured Data SEO 2026: Rich Results Guide",
  "description": "See how to implement and test eligible Article, Product, and other structured data for Google Search.",
  "image": {
    "@type": "ImageObject",
    "url": "https://www.digitalapplied.com/blog/structured-data-seo-2026-rich-results-guide/opengraph-image",
    "width": 1200,
    "height": 630
  },
  "author": {
    "@type": "Person",
    "name": "Richard Szakacs",
    "url": "https://www.digitalapplied.com/about"
  },
  "publisher": {
    "@type": "Organization",
    "name": "Digital Applied",
    "url": "https://www.digitalapplied.com",
    "logo": {
      "@type": "ImageObject",
      "url": "https://www.digitalapplied.com/android-chrome-512x512.png",
      "width": 512,
      "height": 512
    }
  },
  "datePublished": "2026-02-22T08:00:00+01:00",
  "dateModified": "2026-02-22T08:00:00+01:00",
  "mainEntityOfPage": {
    "@type": "WebPage",
    "@id": "https://www.digitalapplied.com/blog/structured-data-seo-2026"
  },
  "keywords": ["structured data", "JSON-LD", "rich results", "SEO 2026"],
  "articleSection": "SEO"
}
Required Article Properties
  • headline — Article title, max 110 characters
  • image — At least one ImageObject with url, width, height
  • datePublished — ISO 8601 format with timezone offset
  • dateModified — Update this whenever substantive edits are made
  • author — Person or Organization with name and url
  • publisher — Organization with name and logo ImageObject

Product Schema for eCommerce

Eligible Product markup may lead to displays of price, availability or eligible ratings. Choose product snippets or merchant listings based on the page. The example below uses invented catalogue data and omits ratings. Include them only for genuine reviews of the marked-up item.

Illustrative Product and Offer
{
  "@context": "https://schema.org",
  "@type": "Product",
  "name": "Trail Backpack, Blue, 28 L",
  "image": [
    "https://example.com/images/trail-backpack-blue.jpg"
  ],
  "sku": "TRAIL-28-BLUE",
  "offers": {
    "@type": "Offer",
    "url": "https://example.com/shop/trail-backpack-blue",
    "priceCurrency": "USD",
    "price": "84.00",
    "itemCondition": "https://schema.org/NewCondition",
    "availability": "https://schema.org/InStock"
  }
}

Use an ISO 4217 currency code such as USD. Google accepts documented short values such as InStock and the full Schema.org URL. Provide an expiration date only where the price actually expires. Follow Google’s offer documentation.

Aggregate ratings
  • • aggregateRating.ratingValue
  • • aggregateRating.reviewCount or ratingCount
  • • aggregateRating.bestRating for a custom scale
  • • aggregateRating.worstRating for a custom scale
Offer fields
  • • offers.price
  • • offers.priceCurrency
  • • offers.availability (recommended)
  • • offers.priceValidUntil (when applicable)

HowTo and FAQ Considerations

HowTo and FAQPage are two schema types that were once among the most impactful for rich results — but both have been restricted or deprecated. Understanding what happened to these schemas is critical for avoiding wasted implementation effort and for redirecting your structured data strategy toward schema types that still deliver results in 2026.

HowTo Schema: Deprecated Rich Results

Google deprecated HowTo rich results in September 2023. HowTo schema previously enabled Google to display step-by-step carousels directly in search results — an extremely valuable rich result for tutorial and instructional content. That rich result type no longer appears on desktop or mobile. Adding HowTo schema to your pages will not cause a penalty, but it will not produce any visible rich result in Google Search.

FAQPage Schema: Retired Google Feature

Google’s separate QAPage feature can apply to a page focused on one question and its answers where users can submit answers, with documented education-related exceptions. An editorial FAQ is a different format.

Testing and Validation Tools

Validation is non-negotiable before deploying structured data changes. A single missing required property or malformed JSON can silently prevent rich results from appearing for that page — and without testing, you would have no idea. Use multiple tools in combination to catch different categories of errors.

Google Rich Results Test
search.google.com/test/rich-results

The primary tool for structured data validation. Enter a URL or paste raw code to see which rich result types your page qualifies for, which required properties are present, which are missing, and which schema types are detected but ineligible. This is the authoritative source — if the Rich Results Test says your schema is invalid, Google will not generate rich results regardless of what other tools report.

Use for: Pre-deployment validation, debugging missing rich results, checking eligibility restrictions.

Google Search Console Rich Results Report
Enhancements section in Search Console

Shows site-wide structured data coverage, broken down by schema type. Reports errors (schema present but invalid), warnings (schema present with missing recommended properties), and valid items (schema fully implemented). Updated weekly based on Googlebot crawl data. The best tool for monitoring structured data health across your entire site after initial deployment.

Use for: Site-wide monitoring, catching regressions after site changes, tracking coverage trends over time.

Schema.org Validator
validator.schema.org

The official Schema.org validation tool checks your markup against the Schema.org vocabulary specification. It catches invalid property values, unknown property names, and type mismatches that Google's tool sometimes misses. Use it as a secondary check after the Rich Results Test, especially when implementing less common schema types not covered by Google's rich results documentation.

Use for: Deep vocabulary validation, checking custom schema implementations, verifying complex nested schemas.

Advanced Patterns

Once your foundational schema types are implemented and validated, advanced patterns let you extract additional rich result opportunities and improve schema accuracy through cross-referencing and entity linking. These techniques are particularly valuable for sites with large content libraries where manual schema management at scale requires programmatic generation.

Combining Multiple Schema Types

A single page can include multiple JSON-LD script tags, each implementing a different schema type. A blog post page, for example, might include Article schema (for the post itself), BreadcrumbList schema (for navigation), and Organization schema if it is the homepage. Keep each schema type in a separate script tag for clarity and easier maintenance. Never try to combine unrelated schema types into a single JSON-LD object.

Multiple Schema Types on One Page
{/* BlogPosting schema */}
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "BlogPosting",
  "headline": "Post Title",
  "datePublished": "2026-02-22"
}
</script>

{/* BreadcrumbList schema — separate script tag */}
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "BreadcrumbList",
  "itemListElement": [
    { "@type": "ListItem", "position": 1, "name": "Home", "item": "https://..." },
    { "@type": "ListItem", "position": 2, "name": "Blog", "item": "https://..." },
    { "@type": "ListItem", "position": 3, "name": "Post Title", "item": "https://..." }
  ]
}
</script>

Dynamic Schema Generation at Scale

Sites with hundreds or thousands of pages cannot manage structured data manually. Build schema generation into your data model — store the source data (title, author, date, price, rating) in your CMS or database and generate JSON-LD programmatically at build time or render time. For static sites using Next.js, generate schema in server components using the same data you fetch for page content. This ensures schema is always in sync with page content and eliminates the common problem of stale structured data.

Schema Patterns That Work
  • Generate schema from the same data used for page content
  • Use TypeScript interfaces to enforce schema completeness
  • Validate schema in CI/CD pipeline before deployment
  • Use @id to cross-reference entities across schemas
Schema Anti-Patterns to Avoid
  • Schema that does not match visible page content
  • FAQPage markup added to obtain Google FAQ rich results
  • Review schema on editorial comparison content
  • Stale price or availability data in Product schema

For pages implementing structured data alongside a full technical SEO strategy, structured data works best in concert with strong Core Web Vitals performance — both are page experience signals that Google evaluates together. A page with perfect structured data but poor INP scores will still underperform in search because Google's page experience signal combines multiple factors.

Structured Data Implementation Priority Order

  1. 1BreadcrumbList — Pages with a meaningful hierarchy · supported on desktop Search
  2. 2Organization — Homepage only — brand identity signals and sitelinks support
  3. 3Article / BlogPosting — All blog posts — author authority and freshness signals
  4. 4Product — eCommerce product pages — price and rating rich results
  5. 5LocalBusiness — Physical office locations — map pack and knowledge panel results

Our SEO optimization services include full structured data audits and implementation for all eligible schema types — from initial validation to ongoing monitoring in Search Console. If your rich results coverage has dropped or you have never implemented structured data, a structured data audit is one of the highest-ROI technical SEO investments available in 2026.

Ready to Win Rich Results?

Our SEO team runs full structured data audits and implementation for all eligible schema types — from validation to ongoing monitoring in Search Console.

Free consultation
Expert guidance
Tailored solutions

Frequently Asked Questions

Corrections

Correction, : This guide previously described FAQ rich results as available to certain sites, credited Article markup with the sitelinks search box and overstated typical click-through and Product requirements. Google ended FAQ rich results in May 2026 and retired the sitelinks search box in 2024. The corrected types and examples follow the current Search gallery.

Digital Applied newsletter

Deep dives on AI, marketing and development.

Practical guides and fresh insights by email. No recycled takes.

Related Articles

Continue exploring with these related guides