Browse and search Schema.org types and properties with examples, required fields, and hierarchy navigation.
A lookup tool for the Schema.org vocabulary, the shared structured-data standard behind most rich results in search engines. Type a name, such as Movie, isbn, or recipe, and the page returns the matching type or property: where it sits in the hierarchy rooted at the type Thing, the properties it accepts, each property's expected value types, and worked examples in JSON-LD and Microdata. Because the tool mirrors the published vocabulary, the definition it shows is the one any consumer will apply. The usual surprise: Schema.org marks nothing as required. No property is formally mandatory, so a 'required' annotation reflects a consumer such as Google's rich-results documentation, not the schema itself.
A concrete input and expected output from the current implementation.
Input
Movie
Expected output
The Movie entry shows hierarchy Thing to CreativeWork to Movie; direct properties such as actor (Person), director (Person), duration (Duration), genre (Text or URL), productionCompany (Organization), and trailer (VideoObject), plus inherited properties like name and datePublished (Date); and an example JSON-LD block:
{
"@context": "https://schema.org",
"@type": "Movie",
"name": "Inception",
"director": { "@type": "Person", "name": "Christopher Nolan" },
"datePublished": "2010-07-16"
} The entry mirrors schema.org/Movie: the type descends from CreativeWork, and director's expected type is Person, so the example nests a Person object instead of a plain string. The release date is Inception's actual US premiere, July 16, 2010, so the sample validates against the vocabulary.
Every type in the vocabulary descends from the root type Thing, usually through several levels, and opening a type shows that ancestry. The property list then presents direct properties together with inherited ones from supertypes, so the entry reflects exactly what the type accepts in markup. The tree also helps you move down when a general type such as Event is too broad for your content.
Search compares against type and property names, camelCase and exact, and labels each hit as a type or a property. Property hits show the value types they accept, such as Person, Text, or URL, plus the types they belong to. Schema.org assigns properties to types through domainIncludes rather than strict domains, so one property can be valid across many unrelated types, and the entry lists every one.
The Schema.org vocabulary itself has no required properties; nothing in it is formally mandatory, and the schema's own examples are often minimal. Required and recommended lists come from consumers, chiefly Google's rich-results documentation, and they vary by feature. If you need that list, look it up for your specific feature rather than expecting the reference to supply it.
Yes, and that is the better route for anything programmatic. The maintainers publish the complete ontology as machine-readable dumps, including Turtle, N-Triples, and JSON-LD, plus a full hierarchy listing, all linked from the official developers page. A reference browser is for reading; a build that validates or generates markup should consume those files.
The example and behavioral notes were checked against the browser implementation. Standards and primary references below define the relevant format, formula, or platform behavior.
Interactive periodic table - click elements, enter quiz mode, and guess elements from their properties. Gamified learning.
Explore the periodic table with element details, properties, and category filtering.
Browse and search ASCII, Unicode, and binary character codes with copy-to-clipboard.
Test your knowledge of semantic HTML elements with quizzes and best-practice tips.
Structured typing lessons with finger placement guide. Track WPM improvement over time with localStorage persistence.
Timed multiplication drills with accuracy tracking per table (1-12). Progress chart saved across sessions.