Bone

Bone is a AnatomicalStructure subtype. Rigid connective tissue that comprises up the skeletal structure of the human body.

Full example of schema.org/Bone json-ld markup

The markup is verified as valid with Rich Results Test from Google.

schema.org/Bone

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Bone",
  "name": "Example Bone"
}
</script>

Minimal valid version

The smallest markup that still produces a valid Bone 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.

schema.org/Bone (minimal)

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Bone",
  "name": "Example"
}
</script>

Google rich results this unlocks

Bone 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). Bone becomes the trunk that the primary type branches off viamainEntityorbreadcrumb. Include it on every page as the backbone of your markup.

Common Bone 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 AnatomicalStructure instead of the specific Bone subtype
Wrong
```
"@type": "AnatomicalStructure"
```
Right
```
"@type": "Bone"
```
Specific subtypes carry domain context consumers use; reach for the narrowest applicable type.

Schema properties in this example

Bone AnatomicalStructure

About the example data

Reference entry in the Xoo Code schema.org catalogue.

Comments

Loading comments...