Hospital Page Best Practices

This support article is intended to help digital marketing and web design teams identify the recommended content for Hospital detail pages. These recommendations support robust schema markup, improve entity understanding, and help ensure page content can be mapped effectively using Schema App tools.

Hospital detail pages should clearly describe the Hospital as a specific medical organization, including its identity, location, contact information, medical services, specialties, staff, and authority signals. Including this content helps search engines understand the Hospital as an entity and supports the creation of comprehensive schema markup.

Note: This article focuses on Hospital detail pages, many of these recommendations may also apply to MedicalClinic, Physician, DiagnosticLab, Pharmacy, and other MedicalOrganization subtypes.

TABLE OF CONTENTS

• Overview: Hospital Detail Page Best Practices
  • How to Read this Document
• Primary Page Components
  • Organization Identity
  • Contact and Location Information
  • Medical Services and Specialties
  • People and Care Providers
  • Potential Actions and Agentic Opportunities
  • Reputation, Trust, and Authority Signals
  • Organization Metadata
• Secondary Page Components
  • Frequently Asked Questions
  • Videos and Rich Media
  • Patient and Visitor Resources
• Common MedicalOrganization Types
  • Hospital
  • MedicalClinic
  • Physician or IndividualPhysician
  • MedicalOrganization
  • DiagnosticLab
  • Pharmacy
• Conclusion

Overview: Hospital Detail Page Best Practices

How to Read this Document

A component is a general term for a sub-section of a WebPage. The size of a component may vary from small (a particular HTML attribute value) to large (a review widget with filters and an aggregate rating). This document groups components into related lists of on-page content that should be considered.

1. Primary Page Components
   These are components that are directly related to the Hospital. and its real world identity. For example, it's name, the services it provides, employees, etc.  
2. Secondary Page Components
   These are components (typically CreativeWorks) that are "about" the Hospital. For example, FAQs, Videos, Articles, or on-page text blurbs. 

Note: To target or include a specific property, the associated content should be present in the HTML of your page

Primary Page Components

The following content is recommended for Hospital detail pages because it helps describe the Hospital as a distinct entity. The more accurate data Schema App can target, the more can be surfaced in your Content Knowledge Graph.

Organization Identity

Hospital pages should clearly identify the organization being described. This helps distinguish the Hospital from similarly named organizations, parent organizations, departments, and affiliated medical facilities.

Best Practices

• Use one official name as the primary name of the Hospital
• Reference former names, abbreviations, or commonly used names in the metadata so that content can be targeted by the Highlighter at scale
• Only use the legalName property if the registered legal name is relevant
• Ensure the logo image URL is indexable and uses a supported image format
• Descriptions will ideally explain who the Hospital serves, and what makes it distinct
• Include idenfier values (e.g. DUN, LEI, taxID, etc) in the metadata so content can be targeted at scale
• Use identifier values that are accurate and associated with the Hospital being described
• Ensure tax identifiers align with the country in the Hospital’s postal address
• Use ISO 6523 properties when available for identifiers such as DUNS, LEI, or Global Location Number
• Confirm identifier values with authoritative internal or external records before adding them to the page content

Contact and Location Information

Hospital detail pages should include complete contact and location information. This allows users and search engines to understand where the Hospital is located, how to contact it, and when it is available.

Best Practices

• Include the country code in telephone numbers whenever possible
• Use separate contact details for distinct departments, such as billing, emergency services, or patient services
• Include complete address components, such as street address, locality, region, postal code, and country
• List opening hours by day rather than relying only on compressed ranges such as “Monday-Friday”
• Structure address and contact details consistently in the HTML so they can be programmatically isolated

Medical Services and Specialties

Hospital pages should describe the medical services and specialties available at the location. This helps clarify what care the Hospital provides and supports connections between the Hospital and related healthcare entities.

Best Practices

• Use internal links when a service or specialty has its own entity home page
• Group services and specialties in consistent HTML components
• Avoid placing all services in an undifferentiated paragraph when they need to be targeted individually
• When possible, align medical specialty names with Schema.org MedicalSpecialty enumeration values

People and Care Providers

Hospital pages may reference employees, physicians, leadership, or care providers. These people can help strengthen the Hospital’s entity relationships, especially when they have their own profile pages.

Best Practices

• Use internal links to provider profile pages whenever possible
• Avoid listing all employees or providers in a single undifferentiated block of text
• Use numberOfEmployees as either an exact value or a QuantitativeValue range when appropriate

Potential Actions and Agentic Opportunities

Most Hospital pages will have one or more call to action components. Use potentialAction~Action markup to describe entry points (e.g. URLs, forms) to Agents.

Best Practices

• Consider the key actions you want users to take on this page

Reputation, Trust, and Authority Signals

Hospital pages may include reputation and authority signals that help users and search engines understand the credibility, recognition, and external identity of the Hospital.

Best Practices

• Ensure reviews and ratings are about the Hospital itself, not a parent organization, department, physician, or separate location
• Only use sameAs for URLs that share the same identity as the Hospital
• Use authoritative external references such as trusted healthcare directories, social profiles, accreditation pages, or other reputable profiles
• Review Google’s current documentation before marking up ratings or reviews

Be judicious with sameAs links. A sameAs URL should describe or identify the same Hospital entity, not merely mention it or describe a related organization.

Organization Metadata

This metadata can help identify the Hospital across external systems and datasets. Unlike most visible page content, some identifier values may be included in schema markup even when they are not prominently displayed in the page content.

Note: Google's stated preference is for iso6523Code with the appropriate prefixes, rather than the specific Schema.org properties.

Secondary Page Components

The following content is not always required, but it can strengthen the Hospital detail page by improving user experience and supporting additional schema markup opportunities.

Frequently Asked Questions

Frequently asked questions can help answer common patient, visitor, or caregiver questions directly on the Hospital page.

Best Practices

• Use a consistent HTML structure for each question and answer pair
• Ensure the full answer is present on the same URL
• Avoid placing answers only in JavaScript-generated pop-ups or inaccessible components
• If FAQs are in an accordion, differentiate the FAQ accordion from other accordions on the page

Videos and Rich Media

Videos and rich media can provide additional context about the Hospital, its services, facilities, and patient experience. These videos will likely not perform as standalone Rich Results unless they have a standalone video watch page.  However, there it may still be valuable to identify it as related content. Review our Video Page best practices for more information on video content.

Best Practices

• Include clear titles and descriptions for video content
• Ensure videos are relevant to the Hospital or services described on the page
• Use consistent placement and HTML structure for repeated video components

Patient and Visitor Resources

Patient and visitor resources can help users complete important tasks and better understand what to expect when engaging with the Hospital.

Common MedicalOrganization Types

Schema.org includes several Types that can describe medical organizations and healthcare entities. Choose the most specific Type that accurately describes the primary entity on the page.

There are two common scenarios for using MedicalOrganization and its subtypes on a website. 

1. A website dedicated to a single MedicalOrganization
   An example of this would be an independent MedicalClinic, or an individual Physician with a private practice. In this case, you will likely want to use the most specific Type on your homepage, to communicate that it is the primary entity of the website.
   
   
2. A website dedicated to a MedicalOrganization that has multiple subOrganizations.
   This is exemplary of a health care system (e.g. AdventHealth) with a multitude of Hospitals, MedicalClinic, and similar entities described on their website. In this case  you will likely want to specify that the MedicalOrganization described on the home page, is the parentOrganization of the other entities described on the website including Hospitals or MedicalClinics.

The recommendations in this document are broad, as we intend to cover both of these use cases. For simplicity, this document will use the term "Hospital", but most (if not all) of the recommendations provided will also apply to MedicalClinic, Physician, and MedicalOrganization types.

Hospital

Use Hospital for pages that describe a hospital facility. Do not use Hospital for pages that describe other types of medical facilities unless the page is primarily about the Hospital itself.

MedicalClinic

Use MedicalClinic for pages that describe a clinic, especially a facility devoted to a specific diagnosis, treatment area, or healthcare domain.  It will typically be associated with a hospital or medical school.

Physician or IndividualPhysician

Use Physician or IndividualPhysician for pages that describe a physician, such as an independent doctor, private practice physician, or individual medical provider.

Note: IndividualPhysician has useful properties like hospitalAffiliation. Historically Physician was the preferred Type because it performed better as a Rich Result. Since May 2026, physician pages no longer achieve a rich result, therefore the recommended Type is now IndividualPhysician.   

MedicalOrganization

Use MedicalOrganization when the organization is medical in nature but does not fit a more specific subtype such as Hospital, MedicalClinic, DiagnosticLab, Pharmacy, or Physician. This is the most appropriate Type for large medical organizations with various locations, or sub Organizations.

If you are using a Highlighter template, the pageset should target pages with the same primary entity Type. For example, avoid using one template for a pageset that mixes Hospital pages with MedicalClinic or Physician pages.

DiagnosticLab

Use DiagnosticLab for pages that describe a medical laboratory offering diagnostic services. This is a relatively rare subtype for most Organizations.

Pharmacy

Use Pharmacy for pages that describe a pharmacy or drug store typically with a physical location.

Note: If you are using a Highlighter template to target pages, your template should target a pageset that has a single primary entity (e.g all pages are about a Hospital as opposed to an MedicalClinic type).

Conclusion

A well-structured Hospital detail page should include comprehensive information about the Hospital’s identity, location, contact details, services, specialties, staff, and authority signals. This content helps users understand the Hospital and supports stronger schema markup for the entity.

When planning or updating Hospital detail pages, use this article as a checklist for recommended page content. If you are unsure which Schema.org Type to use, how to structure HTML for Highlighter targeting, or how to connect related entities, contact your Schema App Customer Success Manager or support@schemaapp.com.