The Ultimate Joint
Schema Generator
The anatomical location at which two or more bones make contact.
Magic Build
Paste your URL below and our AI will automatically fill the Joint fields for you.
Configuration
Live GeneratorWhy use Joint?
Output Panel
Want to automate this?
Connect your site to SchemaGen and our AI will automatically extract and deploy schemas for you. No manual coding required.
Launch AI GeneratorWhat is Joint Schema?
The anatomical location at which two or more bones make contact.
Google uses Joint structured data to understand the content and context of your pages. When correctly implemented, this schema can unlock rich results in Google Search — enhancing your listing with additional information that dramatically improves visibility and click-through rates.
Why Add Joint Structured Data?
Appear in Rich Results
Structured data helps Google show enhanced results for your pages in search — including stars, prices, FAQs, and more.
Boost Click-Through Rate
Rich snippets can increase CTR by up to 30% compared to plain search results — more clicks with the same ranking.
Feed AI Search Engines
AI answer engines like Perplexity and Google SGE use structured data to verify and cite facts from your content.
How to Implement Joint JSON-LD
Generate
Use the form above to fill in your details and generate valid Joint JSON-LD markup in seconds.
Copy
Copy the generated JSON-LD output code with one click — it's already formatted and ready to deploy.
Deploy
Paste the code into your <head> tag, or use SchemaGen's SDK to deploy without touching code.
Want to skip steps 2 & 3? Connect SchemaGen's SDK to deploy directly from the dashboard.
Properties You Can Include
Joint schema supports the following schema.org properties. Required fields are the minimum Google needs to consider your markup valid; recommended fields unlock richer search result appearances.
| Property | Description | Expected Type | Status |
|---|---|---|---|
| additionalType | 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. | Text, URL | Optional |
| alternateName | An alias for the item. | Text | Optional |
| associatedPathophysiology | If applicable, a description of the pathophysiology associated with the anatomical system, including potential abnormal changes in the mechanical, physical, and biochemical functions of the system. | Text | Optional |
| biomechnicalClass | The biomechanical properties of the bone. | Text | Optional |
| bodyLocation | Location in the body of the anatomical structure. | Text | Optional |
| code | A medical code for the entity, taken from a controlled vocabulary or ontology such as ICD-9, DiseasesDB, MeSH, SNOMED-CT, RxNorm, etc. | MedicalCode | Optional |
| connectedTo | Other anatomical structures to which this structure is connected. | AnatomicalStructure | Optional |
| description | A description of the item. | Text, TextObject | Optional |
| diagram | An image containing a diagram that illustrates the structure and/or its component substructures and/or connections with other structures. | ImageObject | Optional |
| disambiguatingDescription | 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. | Text | Optional |
| functionalClass | The degree of mobility the joint allows. | MedicalEntity, Text | Optional |
| funding | A Grant that directly or indirectly provide funding or sponsorship for this item. See also ownershipFundingInfo. | Grant | Optional |
| guideline | A medical guideline related to this entity. | MedicalGuideline | Optional |
| identifier | 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](/docs/datamodel.html#identifierBg) for more details. | PropertyValue, Text, URL | Optional |
| image | An image of the item. This can be a URL or a fully described ImageObject. | ImageObject, URL | Recommended |
| legalStatus | The drug or supplement's legal status, including any controlled substance schedules that apply. | DrugLegalStatus, MedicalEnumeration, Text | Optional |
| mainEntityOfPage | Indicates a page (or other CreativeWork) for which this thing is the main entity being described. See [background notes](/docs/datamodel.html#mainEntityBackground) for details. | CreativeWork, URL | Optional |
| medicineSystem | The system of medicine that includes this MedicalEntity, for example 'evidence-based', 'homeopathic', 'chiropractic', etc. | MedicineSystem | Optional |
| name | The name of the item. | Text | Required |
| owner | A person or organization who owns this Thing. | Organization, Person | Optional |
Example Joint JSON-LD
Here's what valid Joint structured data looks like with sample values filled in. Use the generator above to replace these with your own data.
{
"@context": "https://schema.org",
"@type": "Joint",
"name": "Example Joint",
"image": "https://example.com/images/example.jpg",
"url": "https://example.com/page",
"additionalType": "Example additionalType",
"alternateName": "Example alternateName",
"associatedPathophysiology": "Example associatedPathophysiology",
"biomechnicalClass": "Example biomechnicalClass",
"bodyLocation": "Example bodyLocation"
}Validate Your Joint Schema
Once deployed, validate your schema is working correctly with our free audit tool. Paste your URL and we'll check for errors, missing properties, and Google Rich Result eligibility.
Check your Joint schema for errors and Rich Result eligibility