schemas

Structured Data & Rich Results 2026 Guide: Schema.org, UCP, AI

2026 structured data guide: Schema.org vs Google rich results, JSON-LD, UCP Product schema, AI Mode citation, FAQ/HowTo retirement. Practical implementation with code examples.

Structured data in 2026 operates in two parallel universes: the ever-expanding Schema.org vocabulary and Google’s increasingly restrictive rich-result eligibility. As of March 2026, only 31 schema types retain active rich result support, down from nearly 40 in early 2024 (Digital Applied). Meanwhile, Schema.org v30.0 released six new classes on March 19, 2026, and Google’s AI Mode now reads schema—especially sameAs—for entity resolution and citation probability, even when no visual rich result is triggered (Digital Applied; Google Search Central). This guide covers everything you need to implement structured data for both traditional SERP features and AI-driven search in 2026.

Section 1: Schema.org vs. Google Rich-Result Eligibility — The Two Diverging Paths

Schema.org is a collaborative vocabulary maintained by Google, Microsoft, Yahoo, and Yandex. It defines what markup is possible. Google’s rich-result eligibility is a proprietary algorithmic filter that determines which markup gets visual display in Google Search. The distinction is critical: Schema.org vocabulary continues to expand regardless of Google’s display decisions, and markup that never triggers a visual rich result (like FAQPage) is still read by AI systems for entity resolution and claim verification (Digital Applied; Google Search Central).

Key 2025–2026 Changes

May 7, 2026: FAQ rich results permanently retired for all sites (Google Search Central; Passionfruit). Search Console filter removed June 2026; API support ends August 2026.
June 2025: Seven structured data types retired: Book Actions, Course Info, Claim Review, Estimated Salary, Learning Video, Special Announcement, Vehicle Listing (Passionfruit).
September 2023: HowTo rich results retired on desktop; mobile retired August 2023. As of May 2026, no HowTo rich result remains (Digital Applied; Webiano).
Schema.org v30.0 (March 19, 2026): Added Credential, Error, floorLevel classes and jobDuration property. The Quantity type now inherits from DataType instead of Intangible (schema.org releases; Digital Applied).
Universal Commerce Protocol (UCP) enforcement began January 11, 2026, making hasMerchantReturnPolicy and shippingDetails effectively required for AI agent commerce compatibility (Reddit r/TechSEO).

Why It Matters for SEO Practitioners

Content and e-commerce sites must treat Schema.org markup as infrastructure for AI systems, not just visible SERP decoration.
AI Mode (Gemini 3) does not display schema as a rich result but reads it for entity resolution. Pages with structured data saw a +73% selection boost in AI Overviews in a Wellows observational study, and up to +317% with multimodal integration (Digital Applied—third-party, not Google-confirmed).
Ahrefs study (Feb 2026): Only 38% of pages cited in AI Overviews rank in the top 10 of traditional search (The HOTH). Schema can be a bridge to citations even without high organic positions.

Section 2: JSON-LD Implementation Best Practices for 2026

JSON-LD remains Google’s unequivocally recommended format. Use <script type="application/ld+json"> tags separate from HTML markup. Microdata and RDFa are still supported but offer no increase in efficacy (Google Search Central; Digital Applied; ClickForest). Place JSON-LD in the document <head> whenever possible; for dynamic content, generate schema in server components (e.g., Next.js) rather than client-side JavaScript to ensure reliable crawling (Digital Applied; Google Search Central).

Universal Commerce Protocol (UCP) Compliance

UCP is designed for “Agentic Commerce”—AI agents (Gemini, ChatGPT) transacting on behalf of users. The critical requirement is a nested hasMerchantReturnPolicy object inside the Offer. Without it, products are “essentially invisible to AI shopping agents” and Google downgrades listings in Rich Results (Reddit r/TechSEO).

Valid JSON-LD structure for UCP-compliant Offer:

"offers": {
  "@type": "Offer",
  "price": "100.00",
  "priceCurrency": "USD",
  "hasMerchantReturnPolicy": {
    "@type": "MerchantReturnPolicy",
    "applicableCountry": "US",
    "returnPolicyCategory": "https://schema.org/MerchantReturnFiniteReturnWindow",
    "merchantReturnDays": 30,
    "returnFees": "https://schema.org/ReturnShippingFees"
  },
  "shippingDetails": {
    "@type": "OfferShippingDetails",
    "shippingRate": { "@type": "MonetaryAmount", "value": "5.99", "currency": "USD" },
    "shippingDestination": {
      "@type": "DefinedRegion",
      "addressCountry": { "@type": "Text", "name": "US" }
    }
  }
}

applicableCountry must use ISO 3166-1 alpha-2 codes.
Most Shopify, WooCommerce, and custom themes currently generate “Simple” Product schema (just Name, Image, Price) and fail to inject the nested hasMerchantReturnPolicy (Reddit r/TechSEO). HikaShop v6.4.1 is one of the first to add UCP compliance (HikaShop Forum).

Validation Tools and Workflow

Rich Results Test: Primary tool for syntax and Google eligibility. Does not support all types (e.g., WebSite schema).
Schema Markup Validator (formerly SDTT): Deep vocabulary-level validation. Validates WebSite schema correctly when Rich Results Test fails.
Search Console Enhancements reports: Site-wide error monitoring. Merchant Listings report now tracks missing hasMerchantReturnPolicy, shippingDetails, returnMethod as persistent warnings (Brodie Clark, Dec 2025; HikaShop Forum).
URL Inspection tool: Tests how Google sees a specific page.
AI Mode citation monitoring: No native tool exists yet; manual sampling and third-party tools required (Digital Applied).

Common Implementation Errors

availability must use full Schema.org URL: https://schema.org/InStock—not plain string “InStock”.
priceCurrency must be ISO 4217 code (USD, EUR)—not currency symbols.
Missing dateModified or date mismatch with visible page last-updated date is a common error flagged by Search Console (GWContent).
Duplicate Organization schema across pages: should be site-wide on homepage or about page only.
JavaScript-generated schema for price/availability: can cause Shopping crawls to be less frequent and less reliable—put in initial HTML (Google Search Central).

Section 3: Product & Merchant Listing Schema — The 2026 Standard

Required Properties for Merchant Listing Eligibility

name (Text): must match visible page content.
image (repeated URL or ImageObject): minimum 50K pixels; preferred aspect ratios 16x9, 4x3, 1x1. Merchant Center 2026 update: image minimum increased to 500x500 pixels for image_link and additional_image_link—warnings from April 14, 2026; enforcement from January 31, 2027 (Merchant Center Help).
offers (Offer): nested with price or priceSpecification.price plus priceCurrency.

UCP-Effective Required Properties (Post-January 2026)

These are technically “recommended” in Google’s documentation but have become de facto required for AI commerce visibility (Reddit r/TechSEO consensus):

hasMerchantReturnPolicy (inside Offer)
shippingDetails (inside Offer)
returnMethod, returnFees, applicableCountry

See full JSON-LD example in Section 2.

Recommended Properties for Enhanced Listings

aggregateRating (AggregateRating): minimum ~5 genuine reviews recommended for display.
brand (Brand): manufacturer or brand name.
Global Trade Item Numbers: gtin14, gtin13, gtin12, gtin8, mpn, sku—at least one strongly recommended for product identification.
hasCertification (Certification): for certifications like CO2 class, EPREL (Google Search Central).
subjectOf (3DModel): link 3D model for product visualization.

Pricing Types and Rules (2026)

Active price: no priceType or validForMemberTier.
Strikethrough price: priceType = https://schema.org/StrikethroughPrice. Transition period: ListPrice also allowed; cannot have validForMemberTier.
Member price: validForMemberTier—cannot have priceType.
Critical rule: Price specifications containing both properties are ignored—only one pricing type per Offer (Google Search Central).
Unit pricing measures: use referenceQuantity with QuantitativeValue, especially important in EU, NZ, Australia for products sold by volume/length/weight.

Universal Cart (I/O 2026) — New Eligibility Model

Launched May 19, 2026, initially in US, Canada, Australia (Digital Applied). Universal Cart Buy button eligibility is not gated by schema.org Product markup alone. Two separate pipelines are required:

Merchant Center feed attribute native_commerce—first eligibility gate.
/.well-known/ucp profile—declares checkout capability server (REST or MCP endpoints), capability namespaces, Google Pay config, JWK signing keys.

Four UCP capability namespaces in v1: dev.ucp.shopping.checkout, dev.ucp.shopping.fulfillment, dev.ucp.shopping.discount, dev.ucp.shopping.order (Digital Applied). Launch partners include Nike, Sephora, Target, Walmart, Wayfair, and Shopify merchants Fenty and Steve Madden.

Full eligibility requires: schema markup + Merchant Center feed attribute + UCP profile—three separate requirements.

Merchant Listings vs. Product Snippets

Product snippets: standard organic listings with extensions (ratings, price, availability) within 10-blue-link results—powered by schema markup alone.
Merchant listings: enriched free listing features (popular product grids, ‘In stores nearby’ carousel, product knowledge panels)—powered by Merchant Center feed data. Also appear in Google Images as of June 4, 2024 (Brodie Clark, Dec 2025).
AggregateOffer issue: Using AggregateOffer instead of Offer within Product structured data prevents eligibility for merchant listings. Google’s docs state AggregateOffer should only be used when a product is sold by multiple merchants, not for product variations (Brodie Clark, Dec 2025). Alternative: use inProductGroupWithID or ProductGroup schema.

Section 4: Organization Schema — Entity Foundation for Knowledge Graph

There are no required properties for Organization schema—add what applies (Google Search Central). However, for maximum entity resolution and AI Mode citation probability, include:

name, url, logo (minimum 112x112px, crawlable).
address (PostalAddress) with addressCountry (ISO 3166-1 alpha-2).
sameAs—the most important property in 2026 for AI Mode entity resolution (Digital Applied). Link to Wikidata, LinkedIn, Crunchbase, GRID.
knowsAbout (Text): topical authority signal for AI systems.
New v29.2 properties: legalAddress, legalRepresentative, companyRegistration (schema.org releases).

Implementation guidance: Place on homepage or single “about us” page—not duplicated across every page (Google Search Central; ClickForest). Use the most specific subtype: OnlineStore, LocalBusiness, Corporation, NGO.

Section 5: Article Schema — Still Essential for AI and Top Stories

No required properties, but recommended for optimal representation:

headline, image (three aspect ratios recommended), datePublished, dateModified (freshness signal), author (with sameAs), publisher (includes logo—required for Google News and Top Stories), mainEntityOfPage.

Use subtypes: BlogPosting for editorial content, NewsArticle for time-sensitive news (triggers Top Stories). Article schema does not directly impact organic ranking but signals topical relevance to AI systems (Digital Applied).

Section 6: BreadcrumbList — Highest ROI for Content Sites

Minimum 2 ListItem objects required for rich result eligibility (Google Search Central; Digital Applied). Each ListItem needs position (Integer), name (Text), and item (URL recommended). Estimated CTR impact +5–10% (Digital Applied). Match breadcrumb order to visible page breadcrumbs.

Section 7: FAQ and HowTo Schema — The 2026 Retirement Guide

FAQPage

May 7, 2026: FAQ rich results permanently removed for all sites (Google Search Central; Passionfruit; The HOTH).
August 2026: Search Console API support ends.
March 2026 Core Update impact: FAQ rich result impressions dropped approximately 47% across tracked sites (Digital Applied).
Post-retirement FAQPage markup: remains valid Schema.org (no errors at validator.schema.org) but produces zero SERP lift. Leave existing markup if accurate; stop recommending for new implementations (Digital Applied; Passionfruit).

HowTo

Desktop retired September 2023; mobile retired August 2023. As of May 2026, no HowTo rich result on any surface (Digital Applied; Webiano). Same guidance as FAQPage.

Section 8: Review & AggregateRating Schema — Increased Scrutiny in 2026

The 2026 Crackdown

Editorial Review schema on non-user-submitted content (e.g., “best of” roundups, top-10 lists) now triggers manual action risk (Digital Applied). Algorithmic demotion or manual actions were applied at scale after the March 2026 Core Update.
Closed-system ratings (behind login walls or JavaScript) face enhanced scrutiny—may be ignored.
aggregateRating.ratingCount must match actual number of visible, verifiable reviews.

Implementation Best Practices

Only implement Review markup for genuine user-submitted reviews—not editorial opinions.
For product comparison pages: use Product schema with offers; do not use Review schema for the editorial text.
Ensure minimum ~5 genuine reviews for AggregateRating display (Digital Applied).

Section 9: AI Mode & Structured Data Interaction

AI Mode (Gemini 3) reads structured data for entity resolution and claim verification but does not display schema as a rich result. Schema types that influence AI Mode citation probability:

sameAs—most powerful for entity resolution (Digital Applied).
knowsAbout—topical authority signal.
Speakable—flags the most citable passage within content.
DefinedTerm—improves citation for definition queries.

Clean entity schema (sameAs to Wikidata, LinkedIn, Crunchbase, GRID) measurably improves Knowledge Graph entity recognition and AI citation frequency (Digital Applied).

Controlled experiment (Search Engine Land, Sep 2025): Only the page with well-implemented JSON-LD appeared in AI Overviews; it achieved the highest organic ranking (position 3). Page with no schema never indexed (GWContent).

Conversion rate data (The HOTH): AI-referred visitors converted at 22.79% vs 2.45% for traditional Google organic—9.3x higher.

Section 10: VideoObject, Event, Dataset — Ongoing Active Support

VideoObject: Required: name, thumbnailUrl, uploadDate. Recommended: interactionStatistic (not deprecated interactionCount), description, contentUrl, duration. Active, no announced changes (Google Search Central).
Event: Required: name, startDate. Recommended: endDate, location, description, image, offers, performer, organizer. Active, no changes.
Dataset: Required: description (50–5000 characters), name. Recommended: identifier (DOI), creator, citation, funder, license, includedInDataCatalog, distribution. Active for scientific/research content.

Implementation Checklist & Governance

Use this checklist for any structured data project in 2026:

Choose relevant Schema.org types based on content type and Google’s active rich result support list (31 types).
Implement JSON-LD in <head> with server-side rendering for dynamic data.
For e-commerce: Ensure UCP compliance—nested hasMerchantReturnPolicy and shippingDetails inside Offer. Add Merchant Center native_commerce attribute if pursuing Universal Cart.
For all sites: Add sameAs links to authoritative external profiles in Organization schema.
Avoid FAQPage and HowTo for new implementations; consider QAPage or Article for structured Q&A content.
Audit existing Review schema: Remove any markup on editorial, staff-pick, or closed-system reviews. Replace with plain text or Product schema for comparison pages.
Validate with Rich Results Test for Google eligibility and Schema Markup Validator for vocabulary compliance. Monitor Search Console Enhancements reports weekly.
Monitor AI Mode citation manually or via third-party tools. Track conversion from AI-referred traffic separately.
Governance: Document schema implementation standards; schedule quarterly audits for new Schema.org releases and Google policy changes.

FAQ

Is FAQPage schema harmful now?
No—it remains valid Schema.org and does not cause penalties. But it produces no Google SERP lift. Leave existing markup if it helps AI systems; do not implement for new pages.

Do I need UCP compliance if I don’t target AI agents?
Yes—UCP compliance is effectively required for Google Merchant Listings eligibility in 2026. Missing hasMerchantReturnPolicy and shippingDetails results in warnings in Search Console and downgraded visibility (Reddit r/TechSEO; Brodie Clark).

Can schema help me appear in AI Overviews or AI Mode?
Yes, but it’s not a guarantee. Schema (especially sameAs, knowsAbout, and clean entity data) increases citation probability but content quality and topical authority remain primary factors (Digital Applied; Search Engine Land).

What’s the best schema for content sites in 2026?
BreadcrumbList (highest ROI), Article with dateModified and author entity, Organization with sameAs, and VideoObject if you have video content.

How often should I update schema for Schema.org releases?
At minimum, review major releases (e.g., v30.0) and Google Search Central updates quarterly. Implement new properties only if they add value for your content type or eligibility.

This guide is part of the SEO1 Library. For broader technical SEO coverage, see our Comprehensive Technical SEO Guide.

Originally published in the EcomExperts SEO library.