Schema Type Explorer
Browse six curated Schema.org types with common properties, illustrative JSON-LD examples and official documentation links.
Explore common types
Six curated types, reviewed against official Schema.org pages on November 3, 2026. Common properties are a selection, not required-field rules. Examples are fictional and do not establish Google rich-result eligibility.
6 curated types found
Article
An editorial article or report. Choose the more specific subtype when appropriate.
Common properties
headline- Text: the article headline
author- Person or Organization: genuine authorship
description- Text: a summary
url- URL: the article page
Example JSON-LD
{
"@context": "https://schema.org",
"@type": "Article",
"headline": "Example notebook guide",
"author": {
"@type": "Person",
"name": "Example Author"
},
"description": "A fictional article example.",
"url": "https://example.com/notebook-guide/"
}Organization
An organization such as a business, school or association; not a substitute for verified business details.
Common properties
name- Text: the organization name
url- URL: its website
logo- URL or ImageObject: its actual logo
description- Text: a factual description
Example JSON-LD
{
"@context": "https://schema.org",
"@type": "Organization",
"name": "Example Association",
"url": "https://example.com/",
"description": "A fictional organization for demonstration."
}Person
A person. Use accurate identity and affiliation information rather than inferred credentials.
Common properties
name- Text: the person's name
url- URL: a relevant page
jobTitle- Text or DefinedTerm: actual job title
worksFor- Organization: actual employer
Example JSON-LD
{
"@context": "https://schema.org",
"@type": "Person",
"name": "Example Person",
"url": "https://example.com/people/example/"
}Product
An offered product or service. Offers, reviews and availability are separate facts and must not be fabricated.
Common properties
name- Text: product name
description- Text: product details
sku- Text: merchant-specific identifier
brand- Brand or Organization: associated brand
Example JSON-LD
{
"@context": "https://schema.org",
"@type": "Product",
"name": "Example Notebook",
"description": "An illustrative notebook, not a real offer.",
"sku": "DEMO-A5",
"brand": {
"@type": "Organization",
"name": "Example Brand"
}
}Event
An event at a time and place, such as a workshop. Recurring occurrences can require separate Event objects.
Common properties
name- Text: event name
startDate- Date or DateTime: start with applicable timezone
location- Place, PostalAddress, Text or VirtualLocation: where it happens
description- Text: event details
Example JSON-LD
{
"@context": "https://schema.org",
"@type": "Event",
"name": "Example Workshop",
"startDate": "2027-02-10T10:00:00+00:00",
"location": {
"@type": "Place",
"name": "Example Hall"
},
"description": "Fictional event for vocabulary demonstration only."
}WebApplication
A web application, inheriting properties from SoftwareApplication and CreativeWork.
Common properties
name- Text: application name
url- URL: application page
applicationCategory- Text or URL: category of software
browserRequirements- Text: human-readable browser requirements
Example JSON-LD
{
"@context": "https://schema.org",
"@type": "WebApplication",
"name": "Example Text Utility",
"url": "https://example.com/tool/",
"applicationCategory": "DeveloperApplication",
"browserRequirements": "Requires JavaScript and a modern browser."
}Understand your results
For authors choosing a common Schema.org type and developers checking a small set of property examples.
The explorer filters six curated entries by type name, description or property name and by editorial category. Each entry links to its official Schema.org page, lists selected property ranges and supplies a fictional JSON-LD example. Inherited properties are included where useful; this compact reference intentionally avoids downloading the full vocabulary or calling a search API.
How to use this tool
- Search for a type or property, or select an editorial category.
- Read the description and common properties; consult the official page for the complete inherited vocabulary.
- Copy the illustrative JSON-LD and replace every fictional fact with information supported by your own visible content.
What the observations mean
Each card shows a curated type, selected inherited properties and a syntactically valid demonstration. The example is not a template satisfying every publisher's or search engine's requirements.
Worked example
Search for an inherited property when the appropriate type name is not yet familiar.
Search: headline
Category: All
Example: {"@context":"https://schema.org","@type":"Article","headline":"Example guide"}The Article entry matches its headline property. Copy its full fictional example, consult the official Article documentation and replace example facts before publishing.
Limits and processing
A six-type static selection, reviewed November 3, 2026. It is not the full vocabulary, an update feed, a required-property checklist or a Google eligibility assessment. Searching and copying require no API; opening an official reference leaves the site.
Common problems and practical fixes
- A type is missing from search
- Search is limited to six entries. Use the official Schema.org site for the full vocabulary.
- A property seems required
- The card lists common properties and expected ranges, not mandatory fields. Check the official type and actual consumer's rules.
- An example does not produce a rich result
- Vocabulary support is separate from a search feature, content quality and eligibility. The explorer makes no rich-result promise.
Best practices
Choose the most appropriate type for real content, consult the linked official reference, then test the actual page and keep examples factual.
Practical tips
- The categories organize this small dataset; they are not a formal Schema.org class hierarchy.
- Common properties are examples, not a universal list of mandatory fields.
- A valid vocabulary type does not imply a Google rich-result feature. Check the intended consumer separately.
Frequently asked questions
Practical answers for using the Schema Type Explorer.
Does this include every Schema.org type?
No. It contains Article, Organization, Person, Product, Event and WebApplication, reviewed against their official type pages. No external search is performed.
Can I publish an example unchanged?
The examples are fictional demonstrations. Replace names, URLs, affiliations, identifiers and event details with real facts, and add the fields your page and consumer actually need.
Are these Google's required properties?
No. These are selected Schema.org vocabulary properties and ranges. Google eligibility, supported features and consumer-specific requirements are separate and can change.