# Schema.org

> Schema.org is a collaborative, community-driven project that maintains a shared vocabulary
> for structured data on the web. Founded in 2011 by Google, Microsoft, Yahoo and Yandex, it
> defines 830+ Types and 1,500+ Properties that publishers embed in web pages as JSON-LD,
> RDFa or Microdata so search engines, agents and applications can understand page content.
> Schema.org publishes a vocabulary, not a callable API: everything it serves is an anonymous
> GET of a static, versioned file. Current release 30.0, published 2026-03-19.

Generated by API Evangelist on 2026-08-13 from this repository's artifacts and live probes of
schema.org. Schema.org does not publish its own /llms.txt (probed https://schema.org/llms.txt,
https://validator.schema.org/llms.txt and https://blog.schema.org/llms.txt — all 404).

## How to consume Schema.org

- No authentication, no API keys, no accounts, no rate limits, no cost. CC BY-SA 3.0.
- Pin to an immutable release path — https://schema.org/version/30.0/ — not the floating
  https://schema.org/version/latest/, which changes contents on every release.
- Term IRIs exist in both https:// and http:// forms and consuming applications are expected
  to accept both. The JSON-LD context file itself uses the http form.
- Per-term content negotiation is NOT supported: requesting https://schema.org/Person with
  Accept: application/ld+json returns HTML. Parse the JSON-LD embedded in the term page, or
  use the bulk release files.
- Responses carry `cache-control: public, max-age=600` and a strong ETag. Poll with
  If-None-Match rather than re-downloading.
- CORS is wide open (`access-control-allow-origin: *`, methods GET), so browser clients can
  fetch the context directly.

## Vocabulary distribution files

- [JSON-LD context](https://schema.org/docs/jsonldcontext.json): the canonical context —
  unversioned, always current.
- [Current vocabulary, JSON-LD](https://schema.org/version/latest/schemaorg-current-https.jsonld):
  all current terms. Also published as .ttl, .nt, .nq, .rdf and .csv.
- [Pinned release 30.0](https://schema.org/version/30.0/schemaorg-current-https.jsonld):
  the reproducible form of the same file.
- [All terms including retired](https://schema.org/version/latest/schemaorg-all-https.jsonld):
  current terms plus everything in the attic.
- [http:// flavour](https://schema.org/version/latest/schemaorg-current-http.jsonld): identical
  definitions with http term IRIs, for deployed installations.
- [OWL rendering](https://schema.org/docs/schemaorg.owl): experimental; the project states the
  OWL mapping is an approximation and not authoritative.
- [Type tree](https://schema.org/docs/tree.jsonld): experimental D3-shaped single-inheritance
  simplification of the hierarchy.
- [Version manifest](https://raw.githubusercontent.com/schemaorg/schemaorg/main/versions.json):
  machine-readable map of every release number to its publication date.

## Documentation

- [Developers](https://schema.org/docs/developers.html): machine-readable representations.
- [Full type hierarchy](https://schema.org/docs/full.html)
- [Schemas index](https://schema.org/docs/schemas.html)
- [Data model](https://schema.org/docs/datamodel.html): why Schema.org uses domainIncludes /
  rangeIncludes rather than rdfs:domain / rdfs:range.
- [Getting started](https://schema.org/docs/gs.html)
- [FAQ](https://schema.org/docs/faq.html) — see #19 for the http vs https question.
- [How we work](https://schema.org/docs/howwework.html): release process and governance.
- [Releases](https://schema.org/docs/releases.html): all 53 dated releases, each linked to the
  issues and pull requests that produced it.
- [Attic](https://schema.org/docs/attic.home.html): retired terms, kept resolvable.
- [Terms and licence](https://schema.org/docs/terms.html)

## Core types

- [Thing](https://schema.org/Thing): root of the hierarchy. Twelve direct branches —
  Action, BioChemEntity, CreativeWork, Event, Intangible, MedicalEntity, Organization,
  Person, Place, Product, Taxon.
- [Person](https://schema.org/Person), [Organization](https://schema.org/Organization):
  the two most referenced types in practice.
- [CreativeWork](https://schema.org/CreativeWork): 74 direct subtypes including Article,
  BlogPosting, Book, Course, HowTo, Recipe, SoftwareApplication, WebPage, WebSite.
- [Product](https://schema.org/Product), [Offer](https://schema.org/Offer),
  [Order](https://schema.org/Order), [Invoice](https://schema.org/Invoice): commerce.
- [Event](https://schema.org/Event), [Place](https://schema.org/Place),
  [PostalAddress](https://schema.org/PostalAddress), [LocalBusiness](https://schema.org/LocalBusiness)
- [WebAPI](https://schema.org/WebAPI): how Schema.org describes an API itself —
  documentation, termsOfService, provider, and the APIReference / EntryPoint relationships.
- [MedicalEntity](https://schema.org/MedicalEntity) branch: MedicalCondition, MedicalProcedure, Drug.

## Validation

- [Schema Markup Validator](https://validator.schema.org/): a browser tool run and hosted by
  Google as a contribution to the project. It extracts JSON-LD, RDFa and Microdata.
- There is NO public validation API. A project maintainer states in
  [discussion #3261](https://github.com/schemaorg/schemaorg/discussions/3261): "Do not try to
  scrape validator.schema.org ... There are no resources or plans for Google to make an API."
  The service has anti-scraping safeguards that return 429.
- For programmatic validation the project points at
  [schemarama](https://github.com/google/schemarama) — SHACL/ShEx validation over JSON-LD,
  RDFa and Microdata parsers — to be run yourself.

## Source and community

- [GitHub organization](https://github.com/schemaorg)
- [Main repository](https://github.com/schemaorg/schemaorg): vocabulary sources (Turtle),
  site software, examples. Apache-2.0 for the software, CC BY-SA 3.0 for the vocabulary.
- [Issues](https://github.com/schemaorg/schemaorg/issues) ·
  [Discussions](https://github.com/schemaorg/schemaorg/discussions)
- [Staging site](https://staging.schema.org): 1:1 view of the development branch.
- [Blog](https://blog.schema.org/)
- [W3C Schema.org Community Group](https://www.w3.org/community/schemaorg/)

## Client libraries

Schema.org publishes no first-party SDKs on any package registry. The closest thing is
[schema-dts](https://www.npmjs.com/package/schema-dts) (TypeScript types generated from the
vocabulary, v2.0.0 released 2026-03-23) — published by Google, a founding sponsor, not by the
Schema.org project itself. Treat the versioned distribution files above as the real dependency.

## What Schema.org does not have

Recorded so an agent does not go looking. Probed 2026-08-13, all 404 across schema.org,
validator.schema.org and blog.schema.org: /openapi.json, /openapi.yaml, /swagger.json,
/api-docs, /llms.txt, /.well-known/security.txt, /.well-known/openid-configuration,
/.well-known/oauth-authorization-server, /.well-known/api-catalog, /.well-known/ai-plugin.json,
/.well-known/agent-card.json, /.well-known/agent.json. There is no OpenAPI, no AsyncAPI, no
GraphQL endpoint, no official MCP server, no A2A agent card, no status page and no SLA.