Schema.org released version 30.1 on September 16, 2026. It adds vocabulary for linking a product to an EU Digital Product Passport, plus new ecommerce properties for specifications, consumer notices, shipping providers and minimum order values.

The release adds vocabulary and does not switch on a search feature. Your existing Product and Offer markup stays valid, so most stores can leave it as it is today. The new terms matter to stores that hold real passport or product-compliance data.

Start with your product data, not the release notes. Add a term to a page only when the fact behind it is real, visible on the product page and kept current, such as a passport URL, a safety notice or a shipping minimum that applies.

Key takeaways

  1. Vocabulary, not a featureSchema.org released 30.1 on September 16, 2026. It adds vocabulary and does not switch on a search feature, so existing Product and Offer markup stays valid.
  2. A link to the passporthasDigitalProductPassport on Product or Offer takes a URL or a nested DigitalProductPassport. It points to a passport and does not hold the regulated data.
  3. Add only real dataAdd a term only when the fact is real, visible on the product page and current, such as a passport URL, safety notice or shipping minimum.
  4. Google lists none of themGoogle's merchant listing and product snippet guides, last updated September 8, 2026, do not list the new terms as Search feature fields.
  5. Most stores can waitA store with no passport, no product-level compliance data or no way to keep values accurate can wait. Never invent notices or claims.
  6. EU rules come firstThe EU passport follows Regulation (EU) 2024/1781 and product-specific delegated acts. Schema.org terms do not meet or replace any legal requirement.

What schema.org 30.1 added

The release notes describe version 30.1 this way: "Add vocabulary to support discovery of EU Digital Product Passports, Add vocabulary to express common eCommerce product data, Misc. schema, doc, and infra updates." The entry is on the schema.org release notes page, dated September 16, 2026, and the full release summary gives the same publication date.

The new terms fall into three groups. The first group is passport discovery. DigitalProductPassport is a new type, a subtype of Certification, and hasDigitalProductPassport is a property on Product and Offer that takes either a URL or a nested DigitalProductPassport object. The proposal behind it, schema.org issue #4870, describes a lightweight discovery layer, such as a link to a GS1 Digital Link resolver, and not a complete model of the EU rules. Two sibling types, EnvironmentalProductDeclaration and DeclarationOfConformity, arrive with it.

The second group is product data on Product. specification holds structured specifications, usually as PropertyValue entries, and valueGroup on PropertyValue groups them under a label such as "Power". consumerNotice carries a safety warning or mandatory consumer information. recycledContentPercentage takes a number, and substanceOfConcern accepts text, a URL, a DefinedTerm or a ChemicalSubstance. importer and authorizedRepresentative name an Organization or Person, and isOftenBoughtWith points to another Product.

The third group is retail. itemPopularity on Offer describes comparative popularity or sales rank. provider can now be used on OfferShippingDetails to name the shipping provider, and minimumOrderValue on ShippingRateSettings describes an order threshold for a shipping rate. MaximumRetailPrice joins PriceTypeEnumeration, and PropertyValue and QualitativeValue are now accepted as values for variesBy and value.

A central product card surrounded by three clusters of small tiles marked with a chain link, a ruler and gauge, and a delivery truck.
Figure 1. The new terms fall into three groups: passport discovery, product data and retail details.

The retail changes were merged through PR #4880 and PR #4889, and the passport vocabulary through PR #4871.

Schema.org places most of these terms in its pending area, which it describes as work-in-progress vocabulary that may change after implementation feedback (schema.org pending vocabulary guidance). provider on shipping details and the two range extensions are changes to core properties. That status is a reason to keep each value simple and easy to update.

How the 30.1 changes arrived

  1. March 19, 2026Schema.org 30.0 added EU Digital Product Passport examples.
  2. July 31, 2026Issue #4870 proposed lightweight Digital Product Passport discovery vocabulary.
  3. August 17, 2026PR #4871, which adds the passport vocabulary, was merged.
  4. August 25, 2026PR #4880, which adds retail and marketplace product properties, was merged.
  5. August 31, 2026PR #4889, concerning variant-dimension specification, was merged.
  6. September 16, 2026Schema.org published version 30.1. The dates show vocabulary development, not search-engine adoption.

What a Digital Product Passport is in the EU

A Digital Product Passport is a digital container for information about a product, component or material. The European Commission describes it as a way to support sustainability, circularity, supply-chain transparency, consumer information and legal compliance. The schema.org terms describe where a passport lives. They do not hold the regulated data themselves.

The rules come from Regulation (EU) 2024/1781, the Ecodesign for Sustainable Products Regulation, known as ESPR. It says product-specific delegated acts decide whether a product group needs a passport, what data the passport contains, which data carrier is used and how customers get access to it. The Commission's Digital Product Passport FAQ adds that being named in a working plan does not make a passport mandatory by itself.

The Commission's timeline lists the DPP Registry as established in July 2026 and operational on July 20, 2026. It names priority groups including iron and steel, energy-related products, textiles, tyres, aluminium, furniture, mattresses and ICT products, and the FAQ excludes food, animal feed, medicines, living plants, animals, microorganisms and products of human origin. For sector timelines, read the Commission's Digital Product Passport page, since each product group follows its own delegated act.

Schema.org 30.1 does not replace the registry, the delegated acts, product identifiers or any legal documentation. If your products fall under an EU rule, the compliance work happens in those places first. The markup comes afterwards, as a way to point machines at a passport that already exists. Earlier, the schema.org 30.0 release had added EU Digital Product Passport examples to the documentation.

Before and after JSON-LD for a product page

The first block is an ordinary product page before 30.1, using a fictional lamp on example.com. It carries the fields Google's merchant listing documentation, last updated September 8, 2026, lists as required for that feature: name, image, offers, price and priceCurrency. It also carries recommended fields such as availability, itemCondition, url, description, brand and sku. Replace every value with your own product data.

json
{
  "@context": "https://schema.org",
  "@type": "Product",
  "@id": "https://example.com/products/terra-lamp",
  "url": "https://example.com/products/terra-lamp",
  "name": "Terra Lamp",
  "description": "Fictional rechargeable desk lamp.",
  "image": "https://example.com/images/terra-lamp-square.jpg",
  "sku": "EX-TL-001",
  "brand": { "@type": "Brand", "name": "Example Brand" },
  "offers": {
    "@type": "Offer",
    "url": "https://example.com/products/terra-lamp",
    "price": 49.99,
    "priceCurrency": "USD",
    "availability": "https://schema.org/InStock",
    "itemCondition": "https://schema.org/NewCondition"
  }
}

The second block adds product-level 30.1 terms to the same page. Keep only the lines your own data supports, and delete the rest. The notice, the specification values, the recycled-content figure, the importer and the representative must all match what the product page shows, and the passport URL must open a real record. The values shown here are fictional demonstrations, so do not paste them as they are.

json
{
  "@context": "https://schema.org",
  "@type": "Product",
  "@id": "https://example.com/products/terra-lamp",
  "url": "https://example.com/products/terra-lamp",
  "name": "Terra Lamp",
  "description": "Fictional rechargeable desk lamp.",
  "image": "https://example.com/images/terra-lamp-square.jpg",
  "sku": "EX-TL-001",
  "brand": { "@type": "Brand", "name": "Example Brand" },
  "consumerNotice": "Use only with the supplied charging cable.",
  "specification": [
    { "@type": "PropertyValue", "valueGroup": "Power", "name": "Battery capacity", "value": "4000 mAh" },
    { "@type": "PropertyValue", "valueGroup": "Power", "name": "Charging time", "value": "3 hours" }
  ],
  "recycledContentPercentage": 35,
  "substanceOfConcern": "Fictional trace material listed for demonstration.",
  "authorizedRepresentative": { "@type": "Organization", "name": "Example EU Representative" },
  "importer": { "@type": "Organization", "name": "Example Importer" },
  "isOftenBoughtWith": {
    "@type": "Product",
    "name": "Terra Lamp Replacement Cable",
    "url": "https://example.com/products/terra-lamp-cable"
  },
  "hasDigitalProductPassport": {
    "@type": "DigitalProductPassport",
    "@id": "https://example.com/passports/terra-lamp-001",
    "url": "https://example.com/passports/terra-lamp-001",
    "name": "Terra Lamp Digital Product Passport",
    "description": "Fictional product lifecycle, sustainability, and compliance record.",
    "datePublished": "2026-09-16"
  },
  "offers": {
    "@type": "Offer",
    "url": "https://example.com/products/terra-lamp",
    "price": 49.99,
    "priceCurrency": "USD",
    "availability": "https://schema.org/InStock",
    "itemCondition": "https://schema.org/NewCondition"
  }
}

If you only have a resolver link and no passport details to describe, hasDigitalProductPassport can be a plain URL string instead of the nested object. The third block shows that shorter form on the Offer, together with the shipping terms. provider names the shipping provider, and minimumOrderValue describes an order threshold that a shipping rate depends on. Use them only when your shipping rate really works that way.

json
{
  "@context": "https://schema.org",
  "@type": "Product",
  "@id": "https://example.com/products/terra-lamp",
  "name": "Terra Lamp",
  "image": "https://example.com/images/terra-lamp-square.jpg",
  "offers": {
    "@type": "Offer",
    "url": "https://example.com/products/terra-lamp",
    "price": 49.99,
    "priceCurrency": "USD",
    "availability": "https://schema.org/InStock",
    "hasDigitalProductPassport": "https://example.com/passports/terra-lamp-001",
    "shippingDetails": {
      "@type": "OfferShippingDetails",
      "provider": { "@type": "Organization", "name": "Example Shipping Provider" },
      "shippingDestination": { "@type": "DefinedRegion", "addressCountry": "US" },
      "shippingRate": {
        "@type": "ShippingRateSettings",
        "minimumOrderValue": {
          "@type": "PriceSpecification",
          "price": 35,
          "priceCurrency": "USD"
        }
      }
    }
  }
}

The third block shows only the 30.1 fields. Google's merchant listing guide documents the required Product, Offer, shipping and return-policy fields on its own, and the new terms do not replace any of them. The JSON-LD schema examples guide has copyable patterns for the established page types, and the Product schema generator builds the baseline Product markup that these additions sit on.

What 30.1 changes for product markup

Hover over or tap a row to highlight it. On small screens the table scrolls sideways.

TopicBefore 30.1After 30.1
PassportsProduct markup describes name, image, brand, offers, price and availability.The same markup can link a product or offer to a passport.
SpecificationsRepeated PropertyValue entries or additionalProperty.specification and valueGroup give a more direct structure.
Consumer informationGeneral descriptive fields carry safety or mandatory information.consumerNotice is a dedicated property.
ShippingDestinations, rates and delivery information.provider names the shipping provider; minimumOrderValue sets a rate threshold.

Google's merchant listing guide and product snippet guide, both last updated September 8, 2026, define the fields for Google's product features, so keep those complete. Google's AI features documentation says no special schema.org markup is required for AI Overviews or AI Mode, and that structured data should match the visible page.

Bing's structured data guidance says it supports schema.org in JSON-LD and product and offer annotations, so the same block serves both. Microsoft says web search in Microsoft Copilot may fetch information from Bing, so keep the product page crawlable with clear visible content. Yandex's product information guide documents Product, Offer and AggregateOffer fields. For crawler access by Perplexity, see its crawler documentation. For the full comparison, see whether AI systems use schema markup.

Who should add the terms now and who can wait

The test for each term is the same. The information exists in your authoritative product data, the same information is visible or reachable on the product page, the site can update the markup when the data changes, and your team can validate and monitor the result. A term that fails any of those four points can wait. Pick the terms in this order if the data is real:

  • hasDigitalProductPassport, for products that have a real passport URL or resolver.
  • consumerNotice, for safety warnings or mandatory consumer information shown on the page.
  • specification, for technical specifications you already keep in structured form.
  • recycledContentPercentage, substanceOfConcern, importer and authorizedRepresentative, when the data is accurate and relevant.
  • provider on OfferShippingDetails, when the shipping provider is known, and minimumOrderValue, when a shipping rate really depends on a threshold.
A white-haired man in a navy work jacket holds a clipboard and inspects a label on a boxed lamp on a packing line.
Figure 2. A term belongs on a product page only when the fact behind it is real and kept current in the product data.

A typical store can wait if it has no passport, no product-level sustainability data, no retail feed that needs the new fields, or no way to keep the values accurate. The same goes for any case where filling in a term would mean guessing. Do not invent safety notices, certifications, popularity rankings, reviews or environmental claims to make a product look complete. Manufacturers and sellers who already publish a passport, and platforms or data publishers that describe specifications, notices, popularity or shipping providers across many products, are the ones with a real reason to move first.

Check the markup in five steps

Run these checks in order after you add any of the terms, on the page where the markup lives.

  1. Compare the visible page with the JSON-LD, and confirm that every fact in the code appears on the page or at the passport URL.
  2. Check JSON syntax with the Schema Nova validator, then confirm each property name and value type matches the schema.org term page.
  3. Test Google's Product requirements on their own, because Google defines its feature fields separately from the 30.1 vocabulary.
  4. Check Bing and Yandex against the fields each documents, in Bing Webmaster Tools and Yandex Webmaster, if traffic from them matters to you.
  5. After deployment, confirm the page is crawlable and that the passport link opens without a login.

A passing test shows that the code is written correctly. It does not show a rich result, a ranking, an AI citation or traffic. Valid markup is an accurate description of the page, and that is its whole job here.

Questions people ask

What did schema.org 30.1 add?

It added Digital Product Passport vocabulary, including DigitalProductPassport and hasDigitalProductPassport. It also added ecommerce terms such as specification, consumerNotice, isOftenBoughtWith, itemPopularity and minimumOrderValue, and allowed provider on OfferShippingDetails.

Is schema.org 30.1 the same as an EU Digital Product Passport?

No. The EU passport is a record governed by Regulation (EU) 2024/1781 and product-specific delegated acts. The schema.org terms only describe where that record can be found, and they do not meet or replace any legal requirement.

Does Google support the new Digital Product Passport properties?

Google's merchant listing and product snippet guides, last updated September 8, 2026, define their own fields for Search features. The new terms are valid schema.org vocabulary, so keep your Google Product and Offer fields complete and add the new terms only for accurate data.

Can hasDigitalProductPassport point to a URL?

Yes. It accepts a URL, such as a GS1 Digital Link resolver, or a nested DigitalProductPassport object. Use a real, reachable address, and use the nested object only when you have details about the passport to describe.

What should a store do if it does not have a passport yet?

Leave hasDigitalProductPassport out and keep the existing Product and Offer markup complete. Check the Commission's Digital Product Passport page for your product group's timeline, and add the property once a real record exists.

Quick check: vocabulary, compliance or feature?

Choose an answer to see feedback. Nothing is scored or saved.

Question 1 of 3

A valid schema.org property automatically creates a Google rich result.

Question 2 of 3

A product has no passport. Should it add hasDigitalProductPassport because the property is new?

Question 3 of 3

Does a passport link in schema.org replace EU compliance work?

Terms used in this release

Select a term to see its definition.

Digital Product Passport. A digital record of product lifecycle, sustainability and compliance information.