Structured Data After I/O: Schema Cheat Sheet

Structured data enters 2026 mid-cycle with two disruptions arriving twelve days apart: Google I/O 2026 on May 19 introduced Universal Cart's feed-layer eligibility model — where thenative_commerceMerchant Center attribute, not schema.org Product markup, gates the Buy button — and on May 7, 2026, Google officially retired FAQ rich results, closing a nine-year era of Q&A chips in the SERP. This post covers both events, the updated schema.org v30.0 spec, and a 7-snippet JSON-LD cheat sheet validated against Google's current documentation.

The stakes for SEO teams are concrete. If your site already has FAQPage markup deployed, that markup is now inert in Google Search — harmless but producing zero SERP lift. If your e-commerce clients are preparing for Universal Cart eligibility, they need to understand that updating their schema.org Product JSON-LD is a necessary but not sufficient step: the actual gate is a Merchant Center feed attribute plus a capability server profile at /.well-known/ucp. And if your content strategy depends on AI Mode citation signals, the emerging picture — observed rather than Google-confirmed — is that structured markup may correlate with citation selection at a measurable rate.

This guide covers the schema.org v30.0 release, the FAQ and HowTo retirement timeline, the Universal Cart eligibility two-pipeline distinction, a 14-row schema eligibility matrix, all 7 paste-ready JSON-LD snippets from the research, AI Mode citation signal analysis, the Article/BreadcrumbList/VideoObject specs, and a prioritized implementation roadmap. For deeper background on the March 2026 structured data landscape, see our post-March-2026 structured data strategies. For the full Google I/O context, see our complete I/O 2026 announcement guide.

Schema.org v30.0 released on March 19, 2026 — the current stable specification at the time of I/O 2026. Release notes at schema.org/docs/releases.html confirm three new classes and several new properties. The prior stable version was v29.4, released December 8, 2025.

For SEO practitioners, the v30.0 additions are mostly relevant to specialized verticals. The new Credential class covers non-educational credentials — certificates, professional licenses, industry designations. The Error class with its errorCode property is a developer-facing type for structured error reporting in APIs. The new floorLevel property applies to LocalBusiness and Residence — useful for businesses with multi-floor locations. The jobDuration property for JobPosting fills a long-standing gap in the employment schema for contract-duration signaling.

The structural change with the broadest downstream effect: Quantity now inherits from DataType rather than Intangible. This is a spec-level reclassification that affects schema validation tooling rather than practitioner-facing markup. If your schema validator is strict about class hierarchies, you may see v30.0-related adjustments in complex e-commerce schemas that use QuantitativeValue nesting.

V29.4 (December 8, 2025) added the more practically interesting classes: ConferenceEvent, PerformingArtsEvent, InstantaneousEvent, and authentication action types (AuthenticateAction, LoginAction, ResetPasswordAction). These are relevant for publishers running events and SaaS products building auth-flow structured data. For the full complete structured data type reference, see our dedicated catalogue post.

Validate your existing schemas at validator.schema.org against v30.0. For Google-specific eligibility, also run through Google's Rich Results Test — the two validators catch different classes of issues.

The structured data graveyard has two major occupants in 2026. Most posts that recommend schema do so from outdated lists — they suggest FAQPage or HowTo without noting that both have lost rich-result support. We publish the retirement dates explicitly so you can update your implementation guides.

FAQPage — removed May 7, 2026. Google's FAQPage structured data documentation carries a banner reading verbatim: “As of May 7, 2026, FAQ rich results are no longer appearing in Google Search. We will be dropping the FAQ search appearance, rich result report, and support in the Rich results test in June 2026.” Search Console API support for FAQ rich results ends August 2026. Search Engine Land confirmed the May 7 retirement date the following day.

FAQPage schema is still valid schema.org markup(no errors at validator.schema.org). Google's documented position: “Structured data that's not being used does not cause problems for Search, but also has no visible effects in Google Search.” The practical guidance: leave existing FAQPage markup in place if removal adds risk or engineering cost; simply stop recommending it for new implementations.

HowTo — retired desktop September 2023. Google's 2023 deprecation blog post removed HowTo rich results from mobile in August 2023 and from desktop in September 2023. As of May 2026, there is no HowTo rich result on any surface. Like FAQPage, HowTo is valid schema.org but produces zero Google SERP lift. The 2023 deprecation set up the 2026 FAQ removal as the second act of a multi-year simplification of Google's rich result portfolio.

The single most important correction this post can publish: most early Universal Cart coverage implies merchants need to update their schema.org Product markup for Buy-button eligibility. That is incorrect. The actual gate is a two-part feed-and-capability-server requirement that sits entirely outside the schema.org layer.

Google's Merchant Center documentation states verbatim: “Only product listings using the native_commerce product attribute will display the ‘Buy’ button for this checkout experience.” The native_commerce attribute is a Merchant Center feed flag — set inside your product feed, not in the page's JSON-LD. The Merchant Center help article for UCP-powered checkout is the canonical source for this requirement.

Beyond the feed attribute, Universal Cart requires a UCP profile at /.well-known/ucp on your merchant domain. This JSON document declares the protocol version, REST or MCP service endpoints, capability namespaces, Google Pay configuration, and JWK signing keys. The four UCP capability namespaces in v1 are: dev.ucp.shopping.checkout, dev.ucp.shopping.fulfillment, dev.ucp.shopping.discount, and dev.ucp.shopping.order. Source: Google Developers — UCP profile guide.

Universal Cart launched at I/O 2026 on May 19, 2026 in three markets: US, Canada, and Australia. UK rollout is planned for a later date. The Shopping Graph powering Universal Cart reportedly contains 60 billion product listings, with Google reporting more than a billion shopping interactions per day. Launch partners include Nike, Sephora, Target, Ulta Beauty, Walmart, Wayfair, and Shopify merchants Fenty and Steve Madden. For the full technical UCP implementation walkthrough, see our UCP multi-item cart expansion guide, and for merchant preparation specifically, see our Universal Cart merchant preparation guide.

The schema.org Product layer is still relevant — Google recommends Merchant listing structured data on the product page for crawl and index purposes. It helps Google understand the product's price, availability, and condition, and it qualifies for the traditional Merchant listing rich result in organic search. But it is a separate pipeline from Universal Cart, not the same one.

No published competitor matrix crosses Universal Cart eligibility, AI Mode citation signal strength, traditional rich result status, and implementation effort in a single table. The 14 rows below draw on Google Search Central documentation (retrieved May 24, 2026), Wellows' observational citation studies, Launchcodex AI Mode analysis, and schema.org v30.0. Note: AI Mode citation signals are observational (third-party research), not Google-confirmed ranking factors. For the broader AI citation context, see our 1,000-AI-Overviews citation pattern study.

Each snippet below was verified against schema.org v30.0 class definitions and Google's Rich Results Test requirements as documented on Google Search Central (retrieved May 24, 2026). Re-validate every snippet at validator.schema.org and Google's Rich Results Test before deploying to production — especially for Merchant listing schemas where offers nesting has changed in recent spec updates.

Render as <script type="application/ld+json"> in your <head> — not as <pre><code>. Google parses the script tag; the code blocks below are teaching examples only.

Snippet 1: Product (Merchant listing) — minimal required

{
  "@context": "https://schema.org/",
  "@type": "Product",
  "name": "Example Product",
  "image": [
    "https://example.com/photos/1x1/product.jpg",
    "https://example.com/photos/4x3/product.jpg",
    "https://example.com/photos/16x9/product.jpg"
  ],
  "offers": {
    "@type": "Offer",
    "price": "49.99",
    "priceCurrency": "USD",
    "availability": "https://schema.org/InStock",
    "itemCondition": "https://schema.org/NewCondition",
    "url": "https://example.com/products/example-product"
  }
}

Snippet 2: Product (Merchant listing) — full recommended

{
  "@context": "https://schema.org/",
  "@type": "Product",
  "name": "Example Product",
  "description": "A 1-2 sentence description suitable for indexing.",
  "sku": "EX-PRODUCT-001",
  "gtin13": "0123456789012",
  "mpn": "EX-PRODUCT-001-MPN",
  "brand": {
    "@type": "Brand",
    "name": "Example Brand"
  },
  "image": [
    "https://example.com/photos/1x1/product.jpg",
    "https://example.com/photos/4x3/product.jpg",
    "https://example.com/photos/16x9/product.jpg"
  ],
  "offers": {
    "@type": "Offer",
    "price": "49.99",
    "priceCurrency": "USD",
    "availability": "https://schema.org/InStock",
    "itemCondition": "https://schema.org/NewCondition",
    "url": "https://example.com/products/example-product",
    "hasMerchantReturnPolicy": {
      "@type": "MerchantReturnPolicy",
      "applicableCountry": "US",
      "returnPolicyCategory": "https://schema.org/MerchantReturnFiniteReturnWindow",
      "merchantReturnDays": 30,
      "returnMethod": "https://schema.org/ReturnByMail",
      "returnFees": "https://schema.org/FreeReturn"
    },
    "shippingDetails": {
      "@type": "OfferShippingDetails",
      "shippingRate": {
        "@type": "MonetaryAmount",
        "value": "0.00",
        "currency": "USD"
      },
      "shippingDestination": {
        "@type": "DefinedRegion",
        "addressCountry": "US"
      },
      "deliveryTime": {
        "@type": "ShippingDeliveryTime",
        "handlingTime": {
          "@type": "QuantitativeValue",
          "minValue": 0,
          "maxValue": 1,
          "unitCode": "DAY"
        },
        "transitTime": {
          "@type": "QuantitativeValue",
          "minValue": 2,
          "maxValue": 5,
          "unitCode": "DAY"
        }
      }
    }
  }
}

Note on aggregateRating and review: both are Google-recommended Product properties. They are forbidden on Digital Applied's own pages per internal policy (CLAUDE.md). When implementing on your client's e-commerce site, both are valid and recommended.

Snippet 3: Article (editorial content)

{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "Article Title Here",
  "image": [
    "https://www.example.com/article/image-1x1.jpg",
    "https://www.example.com/article/image-4x3.jpg",
    "https://www.example.com/article/image-16x9.jpg"
  ],
  "datePublished": "2026-05-24T09:00:00-04:00",
  "dateModified": "2026-05-24T09:00:00-04:00",
  "author": {
    "@type": "Organization",
    "name": "Digital Applied",
    "url": "https://www.digitalapplied.com"
  },
  "publisher": {
    "@type": "Organization",
    "name": "Digital Applied",
    "url": "https://www.digitalapplied.com",
    "logo": {
      "@type": "ImageObject",
      "url": "https://www.digitalapplied.com/logo.png"
    }
  }
}

Snippet 4: BreadcrumbList

{
  "@context": "https://schema.org",
  "@type": "BreadcrumbList",
  "itemListElement": [
    {
      "@type": "ListItem",
      "position": 1,
      "name": "Home",
      "item": "https://www.example.com"
    },
    {
      "@type": "ListItem",
      "position": 2,
      "name": "Blog",
      "item": "https://www.example.com/blog"
    },
    {
      "@type": "ListItem",
      "position": 3,
      "name": "Current Page Title"
    }
  ]
}

Note: the last ListItem at position 3 omits the item URL — Google recommends omitting it for the current page. The minimum is two ListItem objects.

Snippet 5: VideoObject (post-Veo 3 era)

{
  "@context": "https://schema.org",
  "@type": "VideoObject",
  "name": "Video Title",
  "description": "1-2 sentence description of the video.",
  "thumbnailUrl": "https://example.com/thumbs/video-thumbnail.jpg",
  "uploadDate": "2026-05-24T09:00:00-04:00",
  "contentUrl": "https://example.com/videos/video.mp4",
  "duration": "PT5M30S",
  "interactionStatistic": {
    "@type": "InteractionCounter",
    "interactionType": { "@type": "WatchAction" },
    "userInteractionCount": 0
  }
}

Critical: use interactionStatistic for view count — NOT interactionCount, which is deprecated per Google's Video documentation (last updated 2026-02-13).

Snippet 6: Organization (brand entity)

{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Digital Applied",
  "url": "https://www.digitalapplied.com",
  "logo": "https://www.digitalapplied.com/logo.png",
  "sameAs": [
    "https://www.linkedin.com/company/digitalapplied",
    "https://github.com/digitalapplied"
  ]
}

Snippet 7: FAQPage — DO NOT IMPLEMENT (schema graveyard, for reference only)

{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "Example question?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Example answer."
      }
    }
  ]
}
/* WARNING: FAQ rich results were removed from Google Search on May 7, 2026.
   This markup is valid schema.org but produces zero SERP lift.
   Do not implement for new pages. Retain on live pages only if
   removal creates engineering risk. */

Google has not published an AI-Mode-specific schema specification. There is no dedicated structured data type for AI Overviews or AI Mode citation eligibility. The canonical structured data you implement for organic search purposes is the same markup that Gemini-powered AI Mode reads — just with a different downstream effect.

What is observed, from third-party research: AI Overviews reportedly appear on 48% of Google queries as of April 2026 (up from 31% in February 2025), per Averi.ai's measurement panel. Third-party observational studies indicate that pages with structured data may be cited in AI Overviews at a higher rate — Wellows' research suggests a +73% selection boost for structured-content pages versus unmarked pages, and up to a +317% citation lift for pages combining multimodal content with structured data. These numbers come from third-party panels, not Google, and should be framed accordingly.

What Google has confirmed, via Launchcodex's I/O 2026 AI search analysis: “Schema.org structured data remains valuable for rich results even though no special markup is required for AI responses specifically.” The honest interpretation: schema signals trust and content structure to Gemini the same way it signals structure to Googlebot — the effect is correlation, not causation, and the mechanism is not publicly documented.

For AI Mode citation strategy, a more detailed picture emerges from our AI Overviews Gemini 3 SEO strategy guide and our AI Mode Gemini 3 ranking impact analysis. The broader measurement framework lives in our guide to tracking AI Mode traffic in Search Console.

The forward-looking picture: AI Mode citation overlap with top-10 organic results is reportedly 17–54% in early 2026 (down from 76% in 2025 per Launchcodex). Only approximately 14% of AI Mode citations reportedly overlap AI Overview citations. This divergence suggests AI Mode is developing its own citation graph — one where structured data and entity signals may play a larger relative role than traditional link graph authority.

Three schema types remain the structural backbone of any content-publishing implementation in 2026 — unaffected by I/O 2026's announcements, unaffected by the FAQ retirement, and unaffected by the Universal Cart rollout. Every Digital Applied blog post implements all three via BlogStructuredData.

Article / BlogPosting. Google's Article documentation (last updated 2025-12-10) is unambiguous: there are no required properties. The recommended set — headline, image (three aspect ratios: 1:1, 4:3, 16:9), datePublished, dateModified, author (with name and url), publisher — remains unchanged. Google's framing: “While there's no markup requirement to be eligible for Google News features like Top stories, you can add Article to more explicitly tell Google what your content is about.” The practical implication: Article schema is not a ranking factor; it is a display eligibility signal for Top Stories and image carousels.

BreadcrumbList. Google's BreadcrumbList documentation confirms two requirements: (1) an itemListElement array of ListItem objects, each with position (integer), name, and optionally item (URL — omit for the current page leaf), and (2) at minimum two ListItementries to qualify. Google's framing on intent: breadcrumbs should “represent a typical user path to a page, instead of mirroring the URL structure.” This is a design note, not a technical requirement — but it aligns with editorial best practices for multi-tier sites.

VideoObject. Google's Video documentation (last updated 2026-02-13) has three required fields: name, thumbnailUrl, and uploadDate. The most important deprecation note: use interactionStatistic for view counts, NOT interactionCount — the latter is deprecated as of the 2026-02-13 update. For video producers in the post-Veo 3 era, the hasPart property with nested Clip objects for key moments is the highest-value recommended addition — it enables Key Moments display in search results.

For the full 500+ type structured data catalogue, see our complete structured data type reference. For the implementation patterns that survived the March 2026 core update, see our schema markup implementation guide.

I/O 2026 does not require a wholesale structured data overhaul — but it does require three targeted actions and one deliberate non-action. The May 2026 core update (Day 4 of a ~14-day rollout as of this writing, completion estimated around June 4, 2026) adds urgency to content quality fundamentals, but the schema layer changes are discrete and manageable.

Action 1: Audit FAQPage and HowTo markup. Pull a list of every page on your site with @type: "FAQPage" or @type: "HowTo". Neither schema type harms your site — but both are now inert. Document them. For high-engineering-cost sites, leave them in place and deprioritize removal. For sites with template-level schema generation, update the template to exclude these types from new page generation.

Action 2: Don't conflate Universal Cart prep with schema updates. If your clients are e-commerce merchants, the Universal Cart preparation task is a Merchant Center feed project, not a schema.org project. See our product data prep guide for AI shopping agents for the feed-level checklist. Update the page's Merchant listing JSON-LD as a secondary action to improve organic rich result quality — but do not present it to clients as the Universal Cart eligibility requirement.

Action 3: Validate existing schemas against v30.0. Run your current structured data through both validator.schema.org and Google's Rich Results Test. If you have JobPosting schemas, add the new jobDuration property. If you have LocalBusiness schemas with multiple floors, add floorLevel. For most sites, v30.0 is low-impact — validate and move on.

Non-action: do not add AI-Mode-specific schema — because none exists. The observational correlation between structured data and AI citation rates is not Google-confirmed guidance. The structured data you implement for organic search purposes is the same markup Gemini reads. Implement the established schema types correctly; AI Mode benefits are a downstream effect of good implementation practice, not a separate implementation track.

For a broader measurement framework around the May 2026 core update and I/O combined SEO impact, see this week's SEO pulse covering the core update and I/O combined impact. For the AI-generated schema workflow that integrates with these implementation priorities, see our AI-generated schema markup guide. For more on our structured data services, see our agentic SEO services page — schema implementation is a core component of how we build AI-citeable content architecture for clients.