Language
Language is a Intangible subtype. Natural languages such as Spanish, Tamil, Hindi, English, etc. Formal language code tags expressed in [BCP 47](https://en.wikipedia.org/wiki/IETF_language_tag) can be used via the [[alternateName]] property. The Language type previously also covered programmin
Full example of schema.org/Language json-ld markup
The markup is verified as valid with Rich Results Test from Google.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Language",
"name": "Example Language"
}
</script>Minimal valid version
The smallest markup that still produces a valid Language entity. Use it as the floor. Reach for the advanced example above when you want search engines and AI agents to understand more about your content.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Language",
"name": "Example"
}
</script>Google rich results this unlocks
Language is a structural type. It does not produce a rich result on its own.
Its value comes from combining it with a primary type whose markup earns a rich result (Article, Product, Event, and so on). Language becomes the trunk that the primary type branches off viamainEntityorbreadcrumb. Include it on every page as the backbone of your markup.
Common Language mistakes
Mistakes that pass validation but silently fail to earn rich results or mislead consumers walking the graph. Avoid these and your markup will be ahead of most sites in the wild.
- 01
Using bare Intangible instead of the specific Language subtype
Wrong"@type": "Intangible"Right"@type": "Language"Specific subtypes carry domain context consumers use; reach for the narrowest applicable type.
Schema properties in this example
Also mentioned in 1 other example
Language also appears in CommunicateAction. See the full Language schema page for every reference.
About the example data
Reference entry in the Xoo Code schema.org catalogue.
Comments
Loading comments...