A regional healthcare system ranked well on traditional search but was consistently omitted from conversational AI responses. This walkthrough shows how restructuring information density and entity connections made its clinical programs legible to AI answer engines.
This is a composite, illustrative scenario built to demonstrate the GEO method, not a real client engagement.
By Matt·Updated June 9, 2026•Hypothetical scenario
Organization profile
Industry
Healthcare & Clinical Services
Org Size
Mid-sized network — 3 hospitals, 12 clinics
Team Size
2 communications specialists
Difficulty
Moderate
Timeline
Variable
Figure 1, the organization profile at a glance
The situation
Why was a well-ranked health system invisible to AI search?
A regional healthcare system ranked well in ordinary Google results for its oncology and sports medicine programs. In conversational AI answers, it was left out almost every time.
Patients increasingly used Large Language Models to evaluate multi-criteria medical options, bypassing traditional local directory listings entirely. The clinical data existed. The models simply could not read it.
The challenge
Patients used to search in keywords: "sports medicine clinic San Francisco." Now they stack several conditions into one question. For example: "Find a sports medicine clinic that accepts Blue Shield, offers minimally invasive knee arthroscopy, and has doctors who specialize in adolescent athletic injuries."
Traditional SEO uses keywords and links to rank a page. AI answer engines work from a knowledge graph instead. That is a map connecting real-world things: people, places, treatments, insurance networks. Your site has to make three links obvious: this doctor performs this procedure, and accepts this insurance. If an engine cannot join those up, it drops you from the answer, however well the page ranks in Google.
What patients are asking AI
"Which hospitals in the East Bay area have an outpatient oncology program with dedicated patient navigators and scalp-cooling treatment options?"
"I need a board-certified orthopedic surgeon who treats rotator cuff tears, takes Aetna PPO, and has an onsite physical therapy clinic."
"Explain the preparation steps for a colonoscopy at this specific health system, and clarify if I can take my morning medications."
Why this matters: These engines do not re-read the web for every question. They rely on relationships worked out in advance. Vague marketing copy gives them nothing to work with, so they cannot confirm your clinic meets the conditions a patient asked about.
Baseline GEO audit
We ran the same set of test questions across the major AI platforms, checking how visible the network was and how clearly each engine understood it.
Ratings are illustrative, not measured.
Audit category
ChatGPT
Gemini
Claude
Perplexity
AI visibility
Missing
Weak
Missing
Moderate
Entity clarity
Weak
Moderate
Weak
Moderate
Program / service pages
Weak
Weak
Missing
Moderate
FAQ content
Missing
Missing
Missing
Weak
Trust signals
Moderate
Strong
Moderate
Strong
Expert profiles
Weak
Moderate
Weak
Weak
ChatGPT
AI visibility
Missing
Entity clarity
Weak
Program / service pages
Weak
FAQ content
Missing
Trust signals
Moderate
Expert profiles
Weak
Gemini
AI visibility
Weak
Entity clarity
Moderate
Program / service pages
Weak
FAQ content
Missing
Trust signals
Strong
Expert profiles
Moderate
Claude
AI visibility
Missing
Entity clarity
Weak
Program / service pages
Missing
FAQ content
Missing
Trust signals
Moderate
Expert profiles
Weak
Perplexity
AI visibility
Moderate
Entity clarity
Moderate
Program / service pages
Moderate
FAQ content
Weak
Trust signals
Strong
Expert profiles
Weak
Trust signals were strong, thanks to years of citations from medical boards and local news. Visibility was not. Perplexity sometimes surfaced the organization, because it retrieves pages live, but never linked a named doctor to a specific procedure. ChatGPT and Claude left the health system out altogether, naming larger academic medical centres instead. Those competitors had one advantage: their sites spelled out these relationships in structured form.
Key issues found
Three structural problems kept the network's clinical data invisible to AI parsers.
1
Ambiguous, narrative provider biographies
Doctor profiles were written as flowing biographies: training, philosophy of care, outside interests. A typical line ran, "Dr. Smith has spent over a decade helping patients regain their mobility and loves spending time outdoors." The facts patients actually filter on sat buried in those paragraphs, or were missing: board certifications, sub-specialties, accepted insurance. An engine reading that biography cannot tell whether Dr. Smith treats a given condition or takes a given insurance plan. So it leaves her out.
2
Clinical data trapped inside PDF patient guides
Treatment steps, pre-op instructions, post-op care, and clinic policies existed only as printable PDFs. Models can read a PDF, but crawlers favour ordinary HTML when they refresh their index. Anything locked in a PDF tends to get skipped, which keeps your clinical guidance out of the answers patients receive.
3
Lack of semantic header hierarchy on program pages
Program pages carried headings like "A New Dawn for Joint Health" and "Compassionate Healing Starts Here." Neither names a symptom or a question a patient would ask. Engines lean on headings to work out how a page is organized. An abstract heading breaks that chain, so no section of the page can be matched to a real question.
Recommended GEO improvements
Three changes that map the network's clinical offerings to the way patients actually ask.
Transforming text for direct answers
Before
At our state-of-the-art Orthopedic Excellence Center, we understand how devastating a sports injury can be to your active lifestyle. Our world-class team of specialists is dedicated to getting you back on the field as safely and quickly as possible. We offer an array of cutting-edge surgical options, including advanced knee arthroscopy procedures, designed with your recovery in mind.
After
"What knee surgeries are available at the Orthopedic Excellence Center?" : answered directly with three named procedures (knee arthroscopy, ACL reconstruction, total knee arthroplasty), each with a one-line objective definition, noting all are performed by board-certified orthopedic surgeons specializing in sports medicine.
Why we chose it: conversational engines look for information layout that mirrors the natural language patterns of user queries. Clear, objective text structures allow models to easily pull clean snippets for AI-generated overviews.
Implementing Physician and MedicalClinic schema
Before
Provider directory pages described a physician's specialty and accepted insurance in a single sentence of prose, leaving the relationships between physician, specialty, and location for the engine to infer.
After
JSON-LD structured data on every provider page, stating how each physician connects to their specialties and hospital locations. It is machine-readable proof, rather than something an engine has to infer.
Why we chose it: structured data sidesteps any ambiguity in the wording of a page. It states the facts in a form crawlers read directly.
Converting PDF resources to semantic HTML FAQ modules
Before
Pre-operative and post-operative patient instruction guides lived exclusively in legacy PDFs designed for print — invisible to crawlers that skip massive downloads due to token constraints and rendering costs.
After
The guides were republished as ordinary web pages with FAQ schema. AI tools can now quote the steps directly when a patient asks how to prepare for a procedure.
Why we chose it: medical instructions in plain HTML can be indexed by live search engines like Perplexity. A common mistake is assuming a text-heavy PDF is enough. Conversational crawlers often skip large PDF downloads, which buries your most useful clinical answers.
Before & after code
The provider-profile transformation, from ambiguous HTML to explicit, machine-readable schema.
Before — standard HTML provider profile
HTML
<div class="doctor-profile">
<h2>Dr. Elena Rostova, MD</h2>
<p>Dr. Rostova specializes in pediatric cardiology at our
Downtown Clinic. She accepts Blue Cross and Aetna.</p>
</div>
After, with Physician schema markup
JSON-LD
{
"@context": "https://schema.org",
"@type": "Physician",
"name": "Dr. Elena Rostova, MD",
"medicalSpecialty": "PediatricCardiology",
"knowsAbout": ["Congenital heart defects", "Pediatric echocardiography"],
"providerAt": {
"@type": "MedicalClinic",
"name": "Downtown Pediatric Health Clinic",
"address": "123 Main Street, San Francisco, CA"
},
"isAcceptingNewPatients": "true",
"medicalInsurance": [
"Anthem Blue Cross PPO",
"Aetna Choice POS II"
]
}
The schema version gives an AI crawler direct, standardized proof of the physician's specialty, the conditions they treat, their clinic, and accepted insurance. No inference required.
Common questions
Does adding physician schema risk any compliance problem?
Not on its own. Provider schema describes information you already publish: a clinician's name, credentials, specialties, and locations. It does not involve patient data. As always, have your compliance team review what you publish, but structured data adds no new category of information.
Should we list which insurance plans we accept on the web page itself?
Yes, in plain text, with a visible date showing when it was last checked. Insurance acceptance is one of the most common things people ask AI tools about, and it is also one of the most commonly wrong answers, because the information usually sits in a portal or a PDF an engine cannot read.
Our physician bios were written by a marketing agency. Do we have to rewrite them?
Not entirely. Keep the narrative biography and add a short factual block above or beside it: board certifications, conditions treated, procedures performed, locations, languages spoken. The facts are what an engine extracts; the narrative still does its job for human readers.
Will this affect how we appear for emergency or urgent-care questions?
It can, and that makes accuracy especially important. Clearly state your hours, which locations handle urgent care, and what someone should do outside those hours. If an engine cannot find that, it may send someone to a competitor, or give advice based on an outdated page.