Do AI-Built Websites Still Need Schema Markup? What We Found in 100+ Orthodontic Practice Audits

We are running a study of over 100 orthodontic practices, scoring each one across seven categories using the KAL™ AI Visibility Audit framework. Schema markup came back as the lowest-scoring category in the entire study, and the data points to exactly why that objection does not hold up.
What Is the Objection, Exactly?
The argument goes like this: large language models can read and understand plain text on their own. They do not need JSON-LD or microdata to figure out that a page is about an orthodontist offering Invisalign in a given city. So why bother maintaining schema at all, especially on a site an AI tool helped build?
That first part is true. AI engines do extract meaning from unstructured content, and they are good at it. The conclusion built on top of that fact is where the argument falls apart.
What Did the Audit Data Actually Find?
Schema markup averaged 32.3 out of 100 across the study, the lowest of the seven categories measured, well below Patient Experience at 87.6 and Local Visibility at 75.8. Seventy-four percent of practices scored below the threshold needed for reliable AI recommendation. Here is how those practices broke down by band.
Schema Score Band | % of Practices |
Zero (no schema markup) | 19% |
Very Low | 31% |
Low | 24% |
Fair or above | 26% |
Nineteen percent of practices have no schema markup at all. Half score below 30.
That is not a small technical gap. It is the single largest category gap in the entire study, on a metric plenty of agencies are currently telling practices not to worry about.
Do AI Engines Really Not Need Schema Anymore?
AI engines extract meaning from plain content, and they also use structured data as a confidence signal when deciding whether to cite a source. When two practices have similar content quality but only one has proper Practice, MedicalOrganization, and MedicalProcedure schema in place, the one with schema tends to get cited more consistently. The AI engine has a higher-confidence read on what that source actually represents.
Semantic HTML is not a substitute here. Good heading structure and clean markup help, but schema explicitly declares entity relationships that HTML can only imply. AI answer engines are increasingly built to reward explicit declarations over implicit ones, which is the opposite of what the “schema is legacy” argument assumes.
The short version: AI can often guess what your page is about without schema. It recommends with more confidence when it does not have to guess.
Isn’t Schema Just an Old SEO Thing?
Schema is not standing still. It is currently expanding to add types built specifically for AI answer engines, including specialized citation and evidence schemas designed for exactly the environment this objection claims does not need them. Google’s own guidance continues to treat structured data as a core signal, not a legacy one, which is worth remembering given how much of AI visibility still builds on the SEO foundation underneath it.
Practices that treat schema as a one-time, now-outdated setup task tend to be the same practices carrying stale review counts and outdated service schema for years without noticing, since schema lives in a script tag that is invisible on the page itself. Nobody looking at the site catches the drift. An audit does.
If Your Website Was Built by an AI Platform
More agencies and platforms now offer AI-built websites, and the same “AI reads everything, schema doesn’t matter” logic sometimes gets applied there too. It does not hold up any better for an AI-built site than it does for a human-coded one.
An AI-built website can, and should, include full schema markup from the day it launches. Speed of build has nothing to do with whether the structural layer underneath it is done correctly. That is how we build websites inside the KAL AI Growth System™: AI speeds up the build, but the structural work, schema included, ships with it, not as something bolted on afterward.
An AI-built website without schema is not a modern approach. It is the same old gap, just built faster.
If a practice already has an AI-built site and is not sure whether schema was part of that build, that is a five-minute thing to check, not a reason to start over.
Should Schema Actually Be a Priority?
Across the study, schema was also the single highest-impact category for remediation. Unlike content gaps, which take real writing time to close, schema is largely a technical deployment task. Practices that deploy proper schema in a systematic pass typically improve their composite AI Visibility Score by 15 to 25 points, often enough to move a full band.
For a practice deciding where to spend the next quarter of marketing budget, that combination, lowest current score plus fastest realistic gain, is hard to argue with on the numbers alone.
Frequently Asked Questions About Add Heading
Does adding schema replace the need for good orthodontic content?
No. Schema and content quality measure different things, and the study scores them separately. Schema tells AI engines what your content is. Content quality determines whether that content is worth citing in the first place. An orthodontic practice needs both; schema alone will not fix thin or outdated pages.
Isn't schema markup just for traditional Google search, not AI?
It was originally built for search engines, but AI answer engines read the same structured data and increasingly rely on it as a confidence signal for citation decisions. Schema now serves both traditional SEO and the AEO layer on top of it. That is part of why we frame it as SEO | AEO working together rather than one replacing the other.
A free AI Visibility Audit shows you exactly where your schema stands today, whether your site was built by a human, an AI platform, or some mix of both, and what it would take to close the gap.