</> Web Validators

Full Schema Hierarchy

Browse every schema.org type: what it inherits from, what inherits from it, and every property it accepts.

Built from schema.org's own machine-readable release -- 939 types and 1538 properties, version 30.1 -- and served from a committed copy, so it works whether or not schema.org is reachable. Each property is shown with the type it was declared on, which is the part that is hard to see on the official hierarchy page.

Based on: Schema.org · Schema.org — Full Hierarchy

About this validation

Browses the schema.org type hierarchy from a committed copy of schema.org's own machine-readable release: supertypes, subtypes, and the properties a type accepts including everything it inherits.

Rules reviewed:
Nov 15, 2026

SEOTechTests methodology: Serves schema.org's type hierarchy from a copy of its own machine-readable release that is generated by a script in this repository and committed, so the page never depends on schema.org being reachable. Supertypes are flattened breadth-first, and the property list for a type is everything declared on it plus everything inherited.

Standards and vendor-documented behavior can change. This reflects the source as last reviewed above, not a permanent guarantee.

ShippingConditions

ShippingConditions represent a set of constraints and information about the conditions of shipping a product.

schema.org/ShippingConditions25 properties0 subtypes

Inheritance

Thing→Intangible→StructuredValue→ShippingConditions

Properties declared on ShippingConditions (12)

depthDistance, QuantitativeValueThe depth of the item.
doesNotShipBooleanIndicates when shipping to a particular shippingDestination is not available.
heightDistance, QuantitativeValueThe height of the item.
numItemsQuantitativeValueLimits the number of items being shipped for which these conditions apply.
orderValueMonetaryAmountMinimum and maximum order value for which these shipping conditions are valid.
seasonalOverrideOpeningHoursSpecificationLimited period during which these shipping conditions apply.
shippingDestinationDefinedRegionindicates (possibly multiple) shipping destinations.
shippingOriginDefinedRegionIndicates the origin of a shipment, i.e.
shippingRateMonetaryAmount, ShippingRateSettingsThe shipping rate is the cost of shipping to the specified destination.
transitTimeQuantitativeValue, ServicePeriodThe typical delay the order has been sent for delivery and the goods reach the final customer.
weightMass, QuantitativeValueThe weight of the product or person.
widthDistance, QuantitativeValueThe width of the item.

Inherited properties (13)

additionalTypefrom ThingText, URLAn additional type for the item, typically used for adding more specific types from external vocabularies in microdata syntax.
alternateNamefrom ThingTextAn alias for the item.
descriptionfrom ThingText, TextObjectA description of the item.
disambiguatingDescriptionfrom ThingTextA sub property of description.
identifierfrom ThingPropertyValue, Text, URLThe identifier property represents any kind of identifier for any kind of Thing, such as ISBNs, GTIN codes, UUIDs etc.
imagefrom ThingImageObject, URLAn image of the item.
mainEntityOfPagefrom ThingCreativeWork, URLIndicates a page (or other CreativeWork) for which this thing is the main entity being described.
namefrom ThingTextThe name of the item.
ownerfrom ThingOrganization, PersonA person or organization who owns this Thing.
potentialActionfrom ThingActionIndicates a potential Action, which describes an idealized action in which this thing would play an 'object' role.
sameAsfrom ThingURLURL of a reference Web page that unambiguously indicates the item's identity.
subjectOffrom ThingCreativeWork, EventA CreativeWork or Event about this Thing.
urlfrom ThingURLURL of the item.

FAQ

Where does this hierarchy come from?

From schema.org's published machine-readable vocabulary, condensed to the type and property relations and committed to this site. The release version it was built from is shown with the results.[1, 2]

Why does a type list properties it does not declare?

Because it inherits them. Every type ultimately descends from Thing, so name, url, description and image are available everywhere without being declared on each type.[1]

What do pending and attic mean next to a type?

schema.org keeps proposed terms in a pending area before they join the core vocabulary, and moves retired ones to an attic so old markup still resolves. A term in either is real, but not part of the core vocabulary.[1]