schema.org
The shared structured-data vocabulary (JSON-LD) that gives agents machine-readable entities and relationships to read off a page — the noun layer the agentic web is built on.
- name
- schema.org
- full_name
- Schema.org structured data vocabulary (for agents)
- layer
- discovery
- creator
- Schema.org founding sponsors (Google, Microsoft, Yahoo, Yandex)
- status
- active (the agentic-web data foundation)
- year
- 2011
- one_liner
- The shared structured-data vocabulary (JSON-LD) that gives agents machine-readable entities and relationships to read off a page — the noun layer the agentic web is built on.
- spec_url
- https://schema.org
- snippet
<script type="application/ld+json">{ "@context": "https://schema.org", "@type": "Product", "name": "..." }</script>- abbreviation
- schema.org
- also_known_as
Schema.orgschema.org for agentsstructured data vocabulary- canonical_spec_url
- https://schema.org/docs/schemas.html
- entity_uri
- https://en.wikipedia.org/wiki/Schema.org
- taxonomy_layer
- discovery
- sub_layer
- structured-data-vocabulary
- protocol_type
- declaration
- central_problem
- Gives the web a shared vocabulary for describing entities and relationships in machine-readable JSON-LD, so an agent can read off a page's meaning instead of inferring it from layout.
- maintainer
- Schema.org community (W3C Schema.org Community Group; founding sponsors Google, Microsoft, Yahoo, Yandex)
- governance_body
- Schema.org Community Group (under W3C)
- license
- Schema.org terms (vocabulary is openly usable; see schema.org/docs/terms.html)
- maturity_tag
- standard
- current_spec_version
- 30.0 verify-against-primary-at-build ↗ https://schema.org/docs/releases.html
- spec_date
- 2026-03-25 verify-against-primary-at-build ↗ https://schema.org/docs/releases.html
- launch_date
- 2011-06-02
- last_verified
- 2026-06-15
- transport
- JSON-LD (also Microdata / RDFa) embedded in HTML
- core_mechanism
- Schema.org defines a hierarchy of types (Product, Organization, FAQPage, Person, etc.) and properties; a page embeds JSON-LD using @context https://schema.org so crawlers and agents extract structured entities and relationships. It is the noun/vocabulary layer that NLWeb is built on and that WebMCP's verbs act over; there is no separate 'schema.org-for-agents' spec — agentic use reuses the existing vocabulary.
- discovery_endpoint
- In-page <script type="application/ld+json"> blocks (and /docs/ vocabulary)
- settlement_type
- —
- adoption_metric
- — verify-against-primary-at-build ↗ https://schema.org
- notable_adopters
{"value":"Google, Microsoft, Yahoo, Yandex (founding sponsors)","source":"https://schema.org/docs/about.html"}- relationships
{"predicate":"foundation_for","target":"nlweb","note":"NLWeb -built_on-> schema.org (research §2 seed triple, inverse): NLWeb grounds its answers in a site's schema.org data."}{"predicate":"complements","target":"llms-txt","note":"schema.org gives agents structured entities; llms.txt gives them a curated content map — paired discovery-layer declarations."}- ideal_use_case
- Marking up a page's entities (products, articles, organizations, FAQs) so agents read structured meaning directly.
- when_to_use
- When you want agents and AI answer engines to extract precise entities/relationships from your pages — the baseline structured-data step.
- when_not_to_use
- When you need agents to take actions or call functions (use MCP/WebMCP/agents.json) rather than read structured nouns.
- code_example
- <script type="application/ld+json"> { "@context": "https://schema.org", "@type": "Product", "name": "Acme Widget", "offers": { "@type": "Offer", "price": "19.99", "priceCurrency": "USD" } } </script>
- source
- Schema.org vocabulary as the agentic-web data foundation (v30.0 reported 2026-03-25), JSON-LD: https://schema.org and https://schema.org/docs/releases.html . Seed triple (NLWeb built_on schema.org): research §2. Honesty note: there is no distinct 'schema.org-for-agents' spec; this records the existing vocabulary applied to agentic use.
- agent_readiness_link
- agent-readiness/discoverability
- layer_legacy
- content