Summary
When we ask new clients about schema, we often hear, “Our CMS does it,” or “IT/our web team handles it.” But “handled” doesn’t necessarily mean optimized.
Simply having schema isn’t enough. Schema markup can be present but generic. We’ve found that many marketing teams are unwittingly stuck with default schema from their CMS or plugin that checks the box without providing much value.
If your Spidey senses are tingling and you’re getting the urge to burn it all down, remember: Everyone’s figuring this stuff out at the same time. It’s not too late to take a closer look.
Without further ado:
Our founder, Ahava Leibtag, and Tim Voyles at HealthStack Partners talked all things schema in a webinar recorded by Strategic Health Care Marketing.
WATCH: Demystifying the Power of Schema in Search
Schema markup is a standard language that tells AI and search engines what your content describes and how its entities relate. It uses a shared vocabulary from Schema.org and is often added to pages as JSON-LD, which is Google’s preferred format for structured data.
The information on your website exists in:
Structured content organizes the information. Schema explains its meaning to machines.
An entity is a person, place, service, condition, or organization with its own identity. It can appear in many places across your website — or the web at large — and carries the same meaning everywhere it’s mentioned. Key entities for a health system include physicians, locations, clinical programs, and the organization itself.
Schema markup helps AI and agents understand key facts about your organization and how they relate.
Healthcare websites are often structured so that key facts are disconnected — living on separate pages or all within one text field that machines must parse to interpret meaning. This makes it hard for AI to answer multi-part prompts like “AFib specialist near Bethesda accepting new patients.”
This is where schema markup joins the chat. Schema connects the dots between facts, telling machines: Dr. Jane Smith is a cardiologist who treats AFib, works at Main Street Health, and practices at Bethesda Clinic on Monday-Friday.
Healthcare schema can also connect physicians to the insurance they accept and whether they’re currently seeing new patients. Connecting the right data helps AI answer patient questions, which can improve the appointment booking journey.
Schema.org includes hundreds of schema types, but you only need the ones that accurately represent your website’s content.
Common schema types for healthcare organizations include:
Hint: If your pages follow consistent templates (like condition, treatment, program, and locations pages), implement schema markup on those templates. This can help you scale the process of medical organization schema across your website.
Basic schema is exactly what it sounds like: technically valid but limited in impact. For example, your CMS or plugin might automatically identify a page as a MedicalWebPage and provide its title and URL. While that may be accurate, it doesn’t tell machines much about the information.
Why basic schema doesn’t cut it:
Connected schema adds healthcare-specific entities and expresses the relationships among them. This is the “level” of schema that connects the dots between Dr. Jane Smith, AFib, and Bethesda Clinic for machines.
Connected schema alone doesn’t guarantee AI visibility, but it gives machines clearer information and reduces how much they need to infer about your org.
Schema markup is a shared responsibility. Marketing defines the use case and meaning, while technical teams build the connections and publishing logic.
Marketing’s role:
Simply confirming that schema exists is not enough. Bring these questions to IT to help you understand what your schema actually communicates, whether it reflects the business, and how it’s governed.
Ask for an inventory of the schema produced on representative page types. This will show whether your CMS is generating only generic markup or something more customized.
Confirm whether the schema identifies priority entities such as physicians, services, conditions, and locations, as well as the relationships among them. Having schema on a page does not mean it describes the information patients need.
Find out which system owns each fact. Schema can publish the information it receives, but it can’t resolve internal disagreements between your CMS, provider directory, and scheduling system.
Separate what your CMS already does from the development needed to add fields, connect records, or pull facts from another system. This helps clarify the technical requirements and associated investment.
Assign responsibility for testing the markup and updating it when the information changes. Without an owner, schema can become outdated or stop matching what patients see on the page.
Not sure whether your schema is connected and actually supporting your AI visibility? We can help you run a content inventory, put together a game plan, implement the schema, and build the necessary governance around the operation. Let’s talk about it.
AUTHOR
Ahava is a leading expert in healthcare content strategy and is recognized for her ability to make complex medical information accessible. She has spent nearly two decades transforming how healthcare organizations communicate with their audiences. Ahava is trusted across the industry for her clarity, evidence-based approach, and thought leadership.
Newsletter
In your inbox, twice per month.
