How to Structure a Doctor Profile So AI Can Trust It: A Tijuana Clinic's Guide to Physician Entity Optimization

In late 2024, I sat down and typed three names into ChatGPT. Dr. Alejandro Quiroz. Dr. Juan Carlos Fuentes. Dr. Carlos Castaneda. All three are fellows of Dr. Bruce Connell, the pioneer of the deep plane facelift technique. Between them, they have decades of experience and hundreds of procedures per year at VIDA Wellness and Beauty Center in Tijuana. ChatGPT had never heard of any of them.

Not a single mention. Not a partial reference. Not even a wrong answer. Just nothing.

My first instinct was to blame the AI. Then I looked at our doctor pages. Each one was a beautifully written paragraph bio. A headshot. A list of credentials in narrative form. The kind of page you'd see in a hospital brochure. And that was exactly the problem. A brochure bio is designed for a human scanning a lobby wall. It is not designed for a machine trying to verify identity, parse credentials, and decide whether to recommend a doctor to a patient in San Diego who just asked "who's the best facelift surgeon in Tijuana."

If your doctor profile is not easy for machines to parse and verify, it is much less likely to be surfaced confidently in AI answers. That's the core of everything in this article.

What follows is the workflow and page structure we used to improve it. This is based on implementation, not theory alone. If you manage a clinic, run a practice, or are a surgeon who wants AI to know you exist, this is the implementation guide.

Why Doctor Profiles Matter More in AI Search Now

The shift is now visible in day-to-day patient discovery behavior. OpenAI has reported that ChatGPT is used at very large scale for health and wellness questions, and those usage patterns and retrieval behaviors continue to evolve. Google's AI Mode uses query fan-out to decompose a single question into multiple subtopics and search multiple sources simultaneously. A query like "best facelift surgeon in Tijuana" may be broken into multiple sub-questions by modern search systems: name, specialty, credentials, reviews, location, cost, logistics, safety.

Each sub-question needs a clear answer on a source the system can extract and reconcile.

BrightLocal found that 58% of ChatGPT local recommendation sources are business websites. Not directories. Not social media. Your website. Specifically, the pages on your website where the answers live. For doctor-specific questions, that page is the doctor profile.

The doctor profile is no longer just a bio page. It is the single page where AI, Google, directories, and patients all converge to reconcile one question: who is this person, and can I trust what they claim?

If that information is buried in narrative text, systems may be less likely to extract it reliably. They find the competitor whose credentials are structured, labeled, and extractable. This is what I wrote about in How AI Decides Which Clinic to Recommend: AI doesn't recommend the most experienced doctor. It recommends the most digitally legible one.

The Cascading Confidence Problem: Why Inconsistency Kills AI Visibility

This is where many clinics diagnose the problem incorrectly. They think visibility is about volume. More content. More listings. More press mentions. The Authoritas fake expert experiment should make every practice owner pause: researchers created 11 fictional experts with AI-generated headshots and seeded them into 600+ press articles across UK media. The result? Zero fake experts appeared in any AI recommendation. Not one. Six hundred articles and nothing.

Volume without entity consistency often produces weak or inconsistent AI visibility.

SparkToro's recent research made it even clearer: AI recommendations are highly inconsistent across sessions and platforms. The same prompt asked twice might produce different results.

Search Engine Land introduced a concept that clicked for me when I read it: cascading confidence. The idea is that entity trust builds or decays through every stage of the AI pipeline. If confidence is 90% at each of 10 processing stages, end-to-end confidence drops to roughly 35%. One weak stage, say a directory listing with the wrong specialty, drops the total dramatically. A practical heuristic is to have multiple independent, credible sources corroborating the same facts about a doctor.

For a Tijuana doctor, here's what cascading confidence failure looks like in practice. Your website says "board-certified plastic surgeon." LinkedIn says "cosmetic surgeon." RealSelf says "aesthetic surgeon." Google Business Profile says "doctor." Doctoralia says "cirujano plástico" with a specialty you set up three years ago and never updated. That inconsistency can make it harder for systems to reconcile those references as one entity. Confidence drops. Your surgeon appears sporadically instead of consistently. Or not at all.

That's what happened with our doctors at VIDA. Their credentials were excellent. But their credentials were scattered across platforms in different formats, different name variations, different specialty labels. The information problem wasn't about what they'd accomplished. It was about how that accomplishment was represented.

The 7 Elements Every Tijuana Doctor Profile Needs

We implemented, tested, and refined every element here across the doctor profiles at VIDA. I'm going to be specific because specificity is the entire point of a well-structured doctor page.

1. Full Name and Unique Identity

Pick one name format. Use it everywhere. Not "Dr. Juan Carlos Fuentes" on the website and "Dr. JC Fuentes" on RealSelf and "Juan Carlos Fuentes Gutierrez" on LinkedIn.

Mexican naming convention actually gives you an advantage here. The two-surname system (paternal + maternal) provides more disambiguation than English naming convention. "Dr. Juan Carlos Fuentes Gutierrez" is far more unique than "Dr. Fuentes." Use it.

The doctor needs a dedicated URL. Not a section on an "About Us" page. Not an anchor link within a team grid. A standalone page with a clean URL structure: `/doctors/dr-juan-carlos-fuentes-plastic-surgeon` or similar. The H1 of that page should be the doctor's full name. This is the entity home. Everything else points back to it.

2. Credentials Patients Can Verify

This is the Mexico-specific section that most articles on doctor profiles skip entirely, and it's the one that matters most for Tijuana clinics.

Mexican medical credentials operate in three layers:

Layer 1: Cedula Profesional. This is the government-issued medical license from SEP (Secretaría de Educación Pública). There are two types: one for general medicine and one for the specialty. Both are verifiable at cedulaprofesional.sep.gob.mx. For patient understanding, this is the closest Mexican analogue to a US medical license, though the systems are not identical.

Layer 2: Board Certification. CONACEM (Consejo Nacional de Certificación en Medicina) is the national oversight body for specialty board certification, verifiable at conacem.org.mx. Under CONACEM, each specialty has its own certifying council. For plastic surgery: CMCPER (Consejo Mexicano de Cirugía Plástica, Estética y Reconstructiva). For bariatric/obesity surgery: CMCOEM (Consejo Mexicano de Cirugía para la Obesidad y Enfermedades Metabólicas). For patient understanding, this is the closest Mexican analogue to US specialty board certification, though the regulatory structures are different.

Layer 3: Hospital Privileges. Hospitals in Mexico are regulated through CSG (Consejo de Salubridad General) certification and COFEPRIS oversight. A doctor with privileges at a CSG-certified or JCI-accredited hospital has an institutional trust signal that transfers to their entity.

CONACEM provides general certification information. For some specialties, the specific council directory (such as CMCPER for plastic surgery) offers a more direct public lookup.

Here's the credential equivalency that should appear on every Tijuana doctor profile, in some form:

AI language models trained primarily on English-language data have much deeper representation of US medical institutions than Mexican ones. When ChatGPT encounters "ABMS board-certified," it has extensive training data about what that means. "CONACEM-certified" has much less representation. The solution isn't to claim US credentials. It's to contextualize: "Board certified by CMCPER (Consejo Mexicano de Cirugía Plástica, Estética y Reconstructiva), included here as a functional comparison point for US patients." That framing helps both machines and humans understand the credential.

3. Specialty and Procedure Focus

Don't just say "Plastic Surgeon." Specify:

• Specialty: Plastic and Reconstructive Surgery
• Primary procedures: Deep plane facelift, neck lift, blepharoplasty
• Procedure volume or experience indicators when available

The "cosmetic surgeon" vs. "plastic surgeon" distinction is a genuine entity disambiguation problem. In both the US and Mexico, "plastic surgeon" is generally associated with formal specialty training and board certification through bodies like ABPS (US) or CMCPER (Mexico). "Cosmetic surgeon" is a broader, less standardized label that does not map to a single certification body. Many AI and search systems appear to reflect the distinction commonly made in US medical publishing between "plastic surgeon" and "cosmetic surgeon." When your profile says "cosmetic surgeon" on one platform and "plastic surgeon" on another, AI may interpret these as different specialties, not synonyms.

Use `medicalSpecialty` to declare specialty and consider `knowsAbout` or service/procedure markup to reinforce procedural focus. Make your Google Business Profile category the most specific option available. Match it to Doctoralia. Match it everywhere.

4. Clinic and Hospital Affiliation

Connect the doctor entity to the clinic entity and the hospital entity. In schema, use `worksFor` for the clinic (MedicalOrganization) and `hospitalAffiliation` for the hospital.

In Tijuana, hospital affiliation carries disproportionate weight because it serves as a safety proxy for cross-border patients. A profile that names the hospital and, where relevant, cites recognized accreditation gives patients and search systems a stronger verification path. The `hospitalAffiliation` schema property helps express that relationship clearly in machine-readable form.

5. Local Proof Across GBP and Directories

Google allows individual practitioner GBP pages at the same address as the practice. Each doctor should have their own listing with the correct primary category ("Plastic Surgeon," not "Plastic Surgery Clinic"). This is technically supported but practically tricky. Google sometimes flags multiple listings at the same address as duplicates. The category must be correct. Ongoing management is required. But the entity value is significant: reviews on the practitioner listing build the doctor's entity separately from the clinic's.

The directories that matter for Tijuana doctors:

• Own website (entity home)
• Google Business Profile (individual practitioner listing)
• LinkedIn
• Doctoralia
• RealSelf (plastic surgery)
• BariatricPal (bariatric surgery)
• CONACEM/CMCPER/CMCOEM directory
• Hospital directory page

NAP (name, address, phone) plus credential consistency across all of them. Same name format. Same specialty label. Same certifying body. Every inconsistency is a confidence leak.

And one thing most people miss: medical tourism facilitators. Companies like MedicalMex, BajaMed Group, and similar intermediaries often have their own doctor profiles on their websites. If a facilitator lists "Dr. Juan Fuentes, Cosmetic Surgeon" while your site says "Dr. Juan Carlos Fuentes Gutierrez, Plastic and Reconstructive Surgeon," you've created an entity conflict on a third-party site you may not even be monitoring.

6. Reviews That Reinforce Doctor Identity

I wrote about this in detail in How Google Reviews Impact AI Recommendations, but it connects directly to doctor profiles.

The timing for medical tourism is different from other industries. At discharge, the patient is tired, maybe still medicated, focused on getting home across the border. They'll leave a "wonderful experience" review if you ask. But the detailed, entity-rich review comes later. At 3-4 weeks, the patient sees real results and is in the optimal emotional state for specific feedback.

A practical two-stage approach is to collect a basic review close to discharge (basic sentiment, gets the star rating), then request a more detailed follow-up at 3-4 weeks via WhatsApp once recovery is underway. Ask for specific details: procedure name, doctor name, where they traveled from, how recovery went. The WhatsApp channel matters because these patients are back in the US and a message from their coordinator feels personal, not transactional.

There's also what I think of as the private-channel visibility problem. Much of the patient communication in Tijuana medical tourism, in our experience, happens on WhatsApp. Testimonials, before/after reactions, recommendations to friends. All of it is invisible to search engines and AI systems. You need to actively convert those WhatsApp signals into public, indexable formats. Google reviews. Website testimonials. Social posts. Otherwise you're sitting on a goldmine of entity-confirming signals that never enters the indexed web.

7. Structured Data and Machine-Readable Page Architecture

This is the technical layer that makes everything above parseable by machines. Schema.org provides the Physician type with properties for `medicalSpecialty`, `hospitalAffiliation`, `hasCredential`, and `availableService`.

A practical approach is multi-typing with `@type: ["Person", "Physician"]`, although implementation should be tested against your CMS and validation tools. Some systems understand the specific Physician type. Others default to Person. Using both is defensive implementation.

I want to be clear about what schema does and doesn't do. Schema helps AI clarify identity and credentials. Schema does not guarantee citation. Schema without consistent content across platforms is useless. Content without schema is harder to parse. Both together create the strongest entity footprint.

`sameAs` is often one of the most useful and most overlooked properties in physician entity markup. It explicitly tells AI systems: this entity on my website is the same person as these profiles on other platforms. Without it, AI must infer that "Dr. Juan Carlos Fuentes" on your site and "Dr. Juan Carlos Fuentes Gutierrez" on Doctoralia are the same person. With it, the connection is explicit.

Here is the JSON-LD template we built for a plastic surgeon in Tijuana, mapped to Mexican credentials. A note on Mexican names: if your physician uses two surnames (paternal + maternal), make sure the `familyName` field reflects exactly how the name appears on all platforms. Inconsistent split-name handling is one of the easiest ways to create entity fragmentation.

A note on the `alumniOf` property: use it for fellowship and training relationships only when the relationship is publicly documented and accurately titled. A fellowship under a specific surgeon is a meaningful signal, but the description should reflect the formal nature of the training accurately.

For training relationships like fellowships under a specific surgeon, document those details in the page content and description fields. Only use alumniOf for formally registered educational programs.

And here is the adapted version for a bariatric surgeon:

You can test syntax with Google's Rich Results Test and broader schema validation tools, keeping in mind that not all physician markup is eligible for Google rich results. Paste the URL. Check for errors. Fix them. This is the minimum verification step before going live, but it doesn't tell you whether the schema is semantically complete for AI entity resolution. That requires the cross-platform audit described below.

Why Tijuana Doctors Need Stronger Profiles Than Most Markets

Tijuana is not just a medical city. It is a comparison market. The patient crosses an international border, and that adds trust barriers that a domestic patient in Dallas or Phoenix never faces.

The doctor profile has to resolve multiple questions simultaneously:

Credentials in an unfamiliar system. US patients understand ABMS. They don't understand CONACEM. The profile must bridge that gap or the patient's verification journey fails. And when it fails, the patient doesn't call to ask questions. They bounce to the next search result.

Direct comparison with US providers. A patient considering a facelift in Tijuana is also considering Beverly Hills. The Tijuana surgeon is often significantly less expensive, which creates a quality question the profile must answer. Strong entity signals, board certification, hospital affiliation, training lineage, don't just build AI visibility. They build the confidence that makes an AI comfortable recommending an affordable option. When pricing is low and provider information is sparse or inconsistent, recommendation systems may default to more conservative answers.

Safety concerns. In our experience, English-language AI systems often answer cross-border medical travel questions cautiously. Unless counter-evidence is strong and structured, the default response leans cautious. The profile is where that counter-evidence lives.

Entity disambiguation in a dense market. The Zona Rio medical corridor in Tijuana has a dense concentration of clinics within a few kilometers. "Dr. Garcia at a Tijuana clinic" matches dozens of potential entities. Full name (both surnames), specialty, clinic, hospital, and credential chain creates a unique, disambiguated entity. The Mexican two-surname convention is an advantage here. Use it consistently.

Training lineage can matter too, especially when the relationship is public, relevant, and consistently documented. In GEO for Plastic Surgeons in Tijuana, I wrote about how the Connell fellowship lineage functions like an academic citation network. "Trained by" a recognized pioneer creates a chain of credibility that AI systems can follow, if the entities are linked. If the training relationship is formal and verifiable, `alumniOf` or related organization/person references may help express it in structured data.

The data points in the same direction: your own website is the primary source AI pulls from. For Tijuana clinics competing across a border, the doctor profile page is where the trust equation gets resolved or where it collapses.

How to Audit Your Doctor Profile in 20 Minutes

Before you build anything new, you need to know what you're working with. This is the audit checklist we run on every doctor profile. It takes about 20 minutes and it will show you exactly where the gaps are.

If you run this audit and find inconsistencies on more than two platforms, you have a cascading confidence problem. Start with the entity home (your website), get it right, then reconcile every other platform against it.

One more platform that matters more than most clinics realize: Reddit. In our internal observations, Reddit is cited often enough in tools like ChatGPT and Perplexity that it is worth monitoring as part of physician reputation and discovery. Unlike review platforms where you can solicit reviews, Reddit mentions are perceived as organic. A thread where a patient says "Dr. Quiroz at VIDA did my deep plane facelift, here are my results" creates entity associations in a source AI appears to value for its authenticity. You can't directly control Reddit. But you can provide outcomes so good that patients share them.

What Happens When AI Cannot Verify Your Doctor

When systems lack confidence in an entity, they may omit the provider, hedge, or rely on safer, better-documented alternatives. They default to the competitor with clearer, more consistent data. Or worse, they actively misrepresent your doctor: wrong specialty, outdated address, confused with another doctor who shares a common surname.

Yext's healthcare predictions framed it this way: if your data is messy, systems may be less willing to surface or strongly endorse a provider. In healthcare specifically, which falls under YMYL (Your Money or Your Life) content standards, AI systems are even more cautious. They will hedge or omit rather than risk recommending an unverified provider.

The upGrowth AI Visibility Benchmark found a pattern that matches what we've observed at VIDA: the clinic that wins AI recommendations is usually not the one with the most content. It's the one with the strongest entity clarity, source consistency, and structured authority signals.

This means a surgeon with five years of experience and a perfectly structured entity presence can outperform a surgeon with twenty years of experience and a brochure bio. We saw this happen with our own doctors. We saw them invisible to AI despite being among the most qualified facelift surgeons in Tijuana. The fix wasn't about adding experience. They had plenty. The fix was about making their experience legible.

Google's Search Quality Evaluator Guidelines place especially high trust expectations on health-related YMYL content. But here's what clinics miss: Google's quality raters evaluate based on what they can find and verify, not what is claimed. A paragraph bio that says "board certified" without specifying the certifying body, without linking to a verification registry, without structured data, fails the evaluability test. Even if the credentials are legitimate.

The gap between how large health systems like Mayo Clinic publish physician profiles, with structured, machine-readable, verified entity information on every doctor, and a typical Tijuana clinic's team page is not incremental. It's architectural. Large health systems tend to publish physician information in highly structured, standardized ways, which likely makes those profiles easier for search systems to interpret. They surface consistently not necessarily because every specialist is the best in every field, but because their entity infrastructure makes every physician findable, verifiable, and parseable.

You don't need Mayo Clinic's budget. You need their approach to information architecture on the doctor page. And in a market where we estimate very few Tijuana clinics have proper physician schema, doing this now creates an early visibility advantage that will be much harder to build later.

What We Changed and What Happened

After implementing entity optimization across the VIDA doctor profiles, we ran the same AI prompts that had produced nothing six months earlier. We saw more frequent and more accurate mentions in our prompt checks over time, though not uniformly across every platform.

I can't draw a clean causal line because there are too many variables. AI models update, retrieval systems change, competitors move. But the correlation between structured entity profiles and increased AI mentions has been consistent enough across every implementation we've done that I'm confident the direction is right, even if attribution remains imperfect.

The infrastructure described in this article is what every other article on this blog builds on. When I write about why your clinic is invisible to AI despite having 500 reviews, the root cause traces to profile structure. When I describe what GEO actually means for medical tourism clinics, the doctor profile is where implementation starts. When I explain the pricing transparency advantage in AI search, the doctor entity is what makes that pricing credible.

Your doctor profile is not a biography. It is infrastructure. And right now, in Tijuana, very few clinics appear to have built it well.

Open ChatGPT. Type your surgeon's name. See what comes back. That's your starting point.

And if what comes back is wrong, incomplete, or nothing at all, now you know exactly what to build.