Medical Audience (MedicalAudience) Schema Generator and How to Guide

MedicalAudience Schema Markup

Target audiences for medical web pages.

MedicalAudience schema is a sub type of:

This schema has more specific sub types.
Would you like to generate a more specific type of MedicalAudience schema?

MedicalAudience Schema Generator in JSON-LD

MedicalAudience schema code:

Guide on How to Create a MedicalAudience Schema


Step 1: Fill out the form above as much as possible.

Note:Use this Schema.org based structured data generator tool to easily create MedicalAudience schema.
The properties are the description of your entity. You don't have to fill in all the properties on this page. Provide what is available and leave what is not. To learn more about each property in your schema type please check MedicalAudience schema properties


Step 2: When complete click the Copy Code button to get your JSON-LD code

Notes:To check if your code is eligible for featured snippets (rich snippets or rich results) test your code with the Rich Results Test tool to learn more about which schema are qualified for rich results check out Google’s search gallery.
To validate your markup code, check your JSON-LD code with the Schema Markup Validator


Step 3: To add a sub-schema, click on the Create Knowledge Graph button

Important Notes: to describe the relationship between your entities you must design a custom schema, this is where the 'creation of knowledge graph' is needed.
For example: if you have a local business and you want to add a service catalogue, or if you have a recipe schema and you want to add a HowTo steps, or if you have a product and you want to add a FAQ about it, to learn more watch this semantic SEO workshop





MedicalAudience Schema Properties

MedicalAudience has 23 properties:

  • 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. In RDFa syntax, it is better to use the native RDFa syntax - the 'typeof' attribute - for multiple types. Schema.org tools may have only weaker understanding of extra types, in particular those defined externally.
  • alternateName An alias for the item.
  • audienceType The target group associated with a given audience (e.g. veterans, car owners, musicians, etc.).
  • description A description of the item.
  • 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.
  • geographicArea The geographic area associated with the audience.
  • healthCondition Specifying the health condition(s) of a patient, medical study, or other target audience.
  • 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 for more details.
  • image An image of the item. This can be a URL or a fully described ImageObject.
  • mainEntityOfPage Indicates a page (or other CreativeWork) for which this thing is the main entity being described. See background notes for details.
  • name The name of the item.
  • potentialAction Indicates a potential Action, which describes an idealized action in which this thing would play an 'object' role.
  • requiredGender Audiences defined by a person's gender.
  • requiredMaxAge Audiences defined by a person's maximum age.
  • requiredMinAge Audiences defined by a person's minimum age.
  • sameAs 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 A CreativeWork or Event about this Thing.
  • suggestedAge The age or age range for the intended audience or person, for example 3-12 months for infants, 1-5 years for toddlers.
  • suggestedGender The suggested gender of the intended person or audience, for example "male", "female", or "unisex".
  • suggestedMaxAge Maximum recommended age in years for the audience or user.
  • suggestedMeasurement A suggested range of body measurements for the intended audience or person, for example inseam between 32 and 34 inches or height between 170 and 190 cm. Typically found on a size chart for wearable products.
  • suggestedMinAge Minimum recommended age in years for the audience or user.
  • url URL of the item.