Language

A Schema.org Type

Thing > Intangible > Language

[more...]

Canonical URL: https://schema.org/Language
Check for open issues.

Natural languages such as Spanish, Tamil, Hindi, English, etc. Formal language code tags expressed in BCP 47 can be used via the alternateName property. The Language type previously also covered programming languages such as Scheme and Lisp, which are now best represented using ComputerLanguage.

Property	Expected Type	Description
Properties from Thing
`additionalType`	Text or URL	An additional type for the item, typically used for adding more specific types from external vocabularies in microdata syntax. This is a relationship between something and a class that the thing is in. Typically the value is a URI-identified RDF class, and in this case corresponds to the use of rdf:type in RDF. Text values can be used sparingly, for cases where useful information can be added without their being an appropriate schema to reference. In the case of text values, the class label should follow the schema.org style guide.
`alternateName`	Text	An alias for the item.
`description`	Text or TextObject	A description of the item.
`disambiguatingDescription`	Text	A sub property of description. A short description of the item used to disambiguate from other, similar items. Information from other properties (in particular, name) may be necessary for the description to be useful for disambiguation.
`identifier`	PropertyValue or Text or URL	The identifier property represents any kind of identifier for any kind of Thing, such as ISBNs, GTIN codes, UUIDs etc. Schema.org provides dedicated properties for representing many of these, either as textual strings or as URL (URI) links. See background notes for more details.
`image`	ImageObject or URL	An image of the item. This can be a URL or a fully described ImageObject.
`mainEntityOfPage`	CreativeWork or URL	Indicates a page (or other CreativeWork) for which this thing is the main entity being described. See background notes for details. Inverse property: mainEntity
`name`	Text	The name of the item.
`potentialAction`	Action	Indicates a potential Action, which describes an idealized action in which this thing would play an 'object' role.
`sameAs`	URL	URL of a reference Web page that unambiguously indicates the item's identity. E.g. the URL of the item's Wikipedia page, Wikidata entry, or official website.
`subjectOf`	CreativeWork or Event	A CreativeWork or Event about this Thing. Inverse property: about
`url`	URL	URL of the item.

Instances of Language may appear as a value for the following properties

Property	On Types	Description
availableLanguage	ContactPoint or Course or LodgingBusiness or ServiceChannel or TouristAttraction	A language someone may use with or at the item, service or place. Please use one of the language codes from the IETF BCP 47 standard. See also inLanguage.
inLanguage	BroadcastService or CommunicateAction or CreativeWork or Event or LinkRole or PronounceableText or WriteAction	The language of the content or performance or used in an action. Please use one of the language codes from the IETF BCP 47 standard. See also availableLanguage.
knowsLanguage	Organization or Person	Of a Person, and less typically of an Organization, to indicate a known language. We do not distinguish skill levels or reading/writing/speaking/signing here. Use language codes from the IETF BCP 47 standard.
language	CommunicateAction or WriteAction	A sub property of instrument. The language used on this action.
subtitleLanguage	BroadcastEvent or Movie or ScreeningEvent or TVEpisode	Languages in which subtitles/captions are available, in IETF BCP 47 standard format.

Examples

Example 1

No Markup JSON-LD Structure

Example notes or example HTML without markup.

This example shows a JSON-LD description of services that do not necessarily have a direct
human-oriented HTML description. It describes a GovernmentService named "Veterans Affairs Emergency Mental Health",
its operator, service area and service details, such as its Veterans Crisis Line (including  phone contact line
hours of operation, language and other details).

Example encoded as JSON-LD in a HTML script tag.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "GovernmentService",
  "name": "Veterans Affairs Emergency Mental Health",
  "serviceType": "Psychiatric Emergency Services",
  "serviceOperator": {
    "@type": "GovernmentOrganization",
    "name": "US Department of Veterans Affairs"
  },
  "areaServed": {
    "@type": "AdministrativeArea",
    "name": "Massachusetts"
  },
  "audience": {
    "@type": "Audience",
    "name": "Veterans"
  },
  "availableChannel": {
    "@type": "ServiceChannel",
    "name": "Urgent Care Clinic",
    "availableLanguage": {
      "@type": "Language",
      "name": "Spanish",
      "alternateName": "es"
    },
    "serviceLocation": {
      "@type": "Hospital",
      "name": "VA Boston -- West Roxbury",
      "address": {
        "@type": "PostalAddress",
        "streetAddress": "1400 VFW Parkway",
        "addressLocality": "West Roxbury",
        "addressRegion": "MA",
        "postalCode": "02132"
      }
    }
  }
}
</script>

Structured representation of the JSON-LD example.

Example 2

No Markup Microdata

Example notes or example HTML without markup.

This example is in microdata only.

Example encoded as Microdata embedded in HTML.

<div itemscope itemtype="https://schema.org/Hotel">
  <h1><span itemprop="name">ACME Hotel Innsbruck</span></h1>
  <span itemprop="description">A beautifully located business hotel right in the
heart of the alps. Watch the sun rise over the scenic Inn valley while
enjoying your morning coffee.</span>
  We speak:
  <ul>
    <li itemprop="availableLanguage" itemscope itemtype="https://schema.org/Language">
      <span itemprop="name">English</span>
    </li>
    <li itemprop="availableLanguage" itemscope itemtype="https://schema.org/Language">
      <span itemprop="name">German</span>
    </li>
  </ul>
</div>