XooCode(){

DiagnosticProcedure

DiagnosticProcedure is a MedicalProcedure subtype. A medical procedure intended primarily for diagnostic, as opposed to therapeutic, purposes.

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

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

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

Minimal valid version

The smallest markup that still produces a valid DiagnosticProcedure 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/DiagnosticProcedure (minimal)
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "DiagnosticProcedure",
  "name": "Example"
}
</script>

Google rich results this unlocks

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

Common DiagnosticProcedure 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.

  1. 01

    Using bare MedicalProcedure instead of the specific DiagnosticProcedure subtype

    Wrong
    "@type": "MedicalProcedure"
    Right
    "@type": "DiagnosticProcedure"

    Specific subtypes carry domain context consumers use; reach for the narrowest applicable type.

Schema properties in this example

About the example data

Reference entry in the Xoo Code schema.org catalogue.

Comments

Loading comments...

Leave a comment