The VIDA Case Study: How 5 Invisible Surgeons Became AI-Visible in 6 Months

It was late 2024 when I typed "Dr. Alejandro Quiroz" into ChatGPT and got nothing back.

Not a wrong answer. Not a partial match. Nothing. The model had no idea who he was. I tried "Dr. Juan Carlos Fuentes." Nothing. "Dr. Carlos Castaneda." Nothing. "Dr. Gabriela Rodriguez Ruiz." Nothing. Four surgeons. Four blank responses. I sat there looking at the screen trying to reconcile what I knew about these doctors with what one of the most widely adopted AI research tools returned about them.

What I knew: Quiroz and Fuentes are both fellows of Dr. Bruce Connell, the surgeon who pioneered the deep plane facelift technique. Castaneda specializes in post-bariatric body contouring, gynecomastia, and high-BMI surgery. Between them, they perform hundreds of procedures a year at VIDA Wellness & Beauty Center, among the larger medical tourism centers in Tijuana. Dr. Gabriela Rodriguez Ruiz holds an MD, a PhD, is a Fellow of the American College of Surgeons, and has performed more than 7,800 bariatric procedures across her career. By the credentials and case experience visible to us, these are among the more qualified surgeons in the city.

What ChatGPT returned in our tests: no useful information.

Disclosure: Tersefy led this implementation for VIDA Wellness & Beauty Center. VIDA is a client. The observations, methodology, and results described here reflect our direct work and internal tracking.

I ran the same names through Gemini. Through Perplexity. Through Google's AI Overviews. Same result everywhere. These doctors were not surfacing in the AI systems many patients now use during provider research. The problem was never the doctors. It was the page.

Here is exactly what we found when we audited their digital presence, how we built the infrastructure to fix it over six months, and the results we measured. I'll be specific about the implementation and honest about the limitations of what we can claim.

If you want context on why the methodology we used differs structurally from traditional SEO, see GEO and AEO Are Not Just SEO.

What We Found When We Audited the Doctor Profiles

Each doctor had a page on the VIDA website. Each page was a brochure-style bio: professional headshot, a paragraph summarizing their credentials, a list of procedures they perform, and a contact button. Beautiful for a patient scrolling on their phone. A weak format for systems trying to extract and verify entity data.

This wasn't a mistake. It was a product of the era these pages were built in. Between roughly 2008 and 2020, Tijuana medical tourism growth was largely intermediated by facilitator platforms like PlacidWay and Medical Departures. Clinics grew by being excellent at the clinical product and outsourcing digital distribution to intermediaries. The website's job was to reassure patients after a facilitator had already referred them, not to be independently discoverable. These pages weren't built with machine parsing or entity verification in mind.

But that's exactly what started happening. And when we audited each doctor's digital presence, we found seven specific problems.

That last point deserves emphasis. Dr. Bruce Connell is a well-documented surgeon in the literature and in online professional references. He published extensively on the deep plane technique, trained fellows internationally, and is referenced across PubMed and surgical education records. Connecting the VIDA surgeons to Connell through explicit biographical and training data may help systems associate them with a well-documented surgical lineage. Most Tijuana practices can't replicate this advantage. VIDA's surgeons were sitting on it and it was buried in a sentence.

The pattern held across all four doctors. These weren't marketing problems. They were primarily information-architecture and verification problems. Much of the evidence a machine might use to assess these doctors already existed, but it was fragmented and inconsistently presented. It just wasn't in a format machines could reliably extract and verify.

The 6-Part Implementation: What We Actually Built

We spent six months building entity infrastructure. Not content. Not ads. Not social media. Infrastructure. Here is what each part involved, in brief. The individual doctor sections below show how each piece played out in practice.

Part 1: Entity Architecture

This was the foundation everything else was built on. We created individual entity home pages for each doctor with dedicated URLs, structured credential sections, and the full professional name standardized across all platforms. Each page was built as a database record a machine could parse, not a brochure a human would scan. We wrote the detailed guide for building these profiles separately.

Part 2: Physician Schema Markup

This is the part that sounds intimidating but is actually the most mechanical. We implemented multi-typed JSON-LD using Person plus Physician on each doctor page. hasCredential for Mexican credentials, sameAs links to directories, medicalSpecialty, hospitalAffiliation, and availableService properties fully populated. None of this is exotic technology. Almost nobody in Tijuana medical tourism was using it.

Part 3: Credential Verification Infrastructure

This one sounds obvious when you say it out loud. Saying "board certified" is a claim. Linking to the verification source is evidence. We added verification links for each credential layer: Cedula Profesional at cedulaprofesional.sep.gob.mx, CMCPER certification through CONACEM, and hospital affiliation with CSG certification. We also built credential equivalency tables explaining Mexican credentials in US terms.

Part 4: Cross-Platform Entity Consistency

The most tedious part and possibly the most important. We audited every platform where each doctor appeared and standardized name format, specialty description, and credential claims. Cleaning up facilitator sites with outdated information was unglamorous. It was also necessary.

Part 5: Review Intelligence

This is where the project stopped being a technical exercise and started requiring me to change how real people work. Everything above lives in code and dashboards. This part lives in WhatsApp threads and coordinator habits. We implemented a two-touch review system: Touch 1 at discharge for the emotional star rating, Touch 2 at 3 to 4 weeks via WhatsApp for entity-rich details. We wrote the full review playbook separately.

Part 6: Content Architecture

The final piece. We built search- and AI-oriented content around each doctor's specialty to reinforce entity associations. Deep plane facelift technique pages for the facelift surgeons. GLP-1 vs surgery comparison pages for Dra. Gaby. Cost transparency content for all specialties. Each piece internally links to the doctor profiles.

Doctor by Doctor: What We Found, What We Built, What Changed

The implementation framework was the same for all four doctors. But the problems, the solutions, and the results were different for each one. Here is what actually happened, doctor by doctor.

Dr. Alejandro Quiroz: Deep Plane Facelift

LinkedIn said "Dr. A. Quiroz." The website said "Dr. Alejandro Quiroz." A PlacidWay listing from 2019 said "Alejandro Quiroz Gutierrez" with pricing from five years ago. At least three different name entities across platforms. His connection to Dr. Bruce Connell, the pioneer of the deep plane facelift technique, was buried in one sentence of a paragraph bio. No structured data. No alumniOf. No entity connection. This is arguably the strongest credential differentiator of any plastic surgeon in Tijuana and it was invisible to machines. All his reviews went to the VIDA clinic GBP. His name appeared in maybe 15% of them. Zero individual GBP listing.

We built a canonical entity page with full name standardized as "Dr. Alejandro Quiroz" across all platforms. JSON-LD with Person plus Physician, alumniOf linking to Dr. Bruce Connell, hasCredential with CMCPER and Cedula Profesional with verification links. Claimed and built individual GBP practitioner listing. Cleaned the PlacidWay listing. Two-touch review system with coordinators specifically prompting patients to mention "Dr. Quiroz" and "deep plane facelift." Published deep plane facelift content positioning him in the "deep plane facelift Tijuana" query space.

The prompt "best deep plane facelift surgeon in Tijuana" returned zero VIDA mentions in late 2024. By mid-2025, Dr. Quiroz's name appeared on multiple platforms with his Connell training lineage mentioned correctly. The prompt "who trained under Dr. Bruce Connell" started returning his name. His Review Specificity Score went from an estimated 15% to above 45% within 90 days. His monthly surgical volume went from approximately 17 procedures to 24. And the customer acquisition cost for plastic surgery across the practice dropped from approximately $1,200 per surgical patient to $655. I am not going to claim entity optimization alone dropped the CAC. Better ad targeting, coordinator training, and organic referral growth all played a role. But the entity work changed which patients were finding us and how informed they were before first contact. Patients who arrive through AI-mediated research tend to have already vetted the doctor's credentials. They convert faster and require less convincing.

Dr. Juan Carlos Fuentes: Deep Plane Facelift

Fuentes had reviews he did not even know about. His Doctoralia profile had been created by the platform itself, and patients had been leaving feedback there for months. Nobody at VIDA had claimed it. That was free entity data sitting uncollected.

His name inconsistency was similar to Quiroz but with a twist. His full Mexican name "Juan Carlos Fuentes Gutierrez" is nearly unique globally. That is an entity disambiguation advantage most English-name doctors would kill for. But it was not being used consistently. We standardized on "Dr. Juan Carlos Fuentes" for public-facing platforms, with "Juan Carlos Fuentes Gutierrez" as the legal/schema name.

Same Connell lineage invisibility as Quiroz. He is also a fellow of Dr. Bruce Connell but this was not reflected in any structured data. We implemented the same schema, the same alumniOf connection, the same credential verification links.

He started appearing in facelift-related prompts, though less consistently than Quiroz initially. Lower review volume. But as his entity profile strengthened and his Doctoralia reviews were claimed and incorporated, his visibility caught up. His monthly surgical volume went from approximately 9 procedures to 20. More than doubling. His Review Specificity Score improved from approximately 12% to above 38% within 90 days.

The two-surname convention insight came from his case specifically. In a market where name disambiguation is a real problem, Mexican naming convention is a structural advantage. Use it.

Dr. Carlos Castaneda: Post-Bariatric Body Contouring, Gynecomastia, High-BMI Surgery

Before we repositioned him, Castaneda was doing about 5 surgeries a month.

His case is completely different from Quiroz and Fuentes. He is NOT a Connell fellow. His specialty is not deep plane facelifts. He specializes in body contouring for patients after massive weight loss (post-bariatric body lifts, tummy tucks, arm lifts), gynecomastia surgery for men, and he is one of the few surgeons in Tijuana who operates on high-BMI patients that other surgeons turn away.

This niche is actually a massive opportunity for AI visibility because the query space is underserved. Prompts like "body contouring after gastric sleeve Tijuana" or "gynecomastia surgery Tijuana" or "plastic surgeon for high BMI patients Mexico" have very few authoritative answers in AI systems. The competition is thin.

But his digital presence did not reflect any of this specialization. His page on the VIDA site listed him generically as a "plastic surgeon" alongside Quiroz and Fuentes, with no distinction of his actual expertise. AI had no way to know he specializes in post-bariatric body work or high-BMI cases. Same structural problems as the others: name inconsistency, zero schema, credentials in paragraph form, no individual GBP, reviews going to the VIDA clinic listing.

An additional problem unique to him: there is a natural patient pipeline between Dra. Gaby (bariatric surgery) and Castaneda (post-bariatric body contouring) that was completely invisible. A patient who gets a gastric sleeve from Dra. Gaby, loses 100 lbs, and then comes back for a body lift with Castaneda represents a cross-specialty entity relationship that neither doctor's page reflected.

We built him an entity page specifically positioning him in post-bariatric body contouring, gynecomastia, and high-BMI surgery. Not "plastic surgeon." Those are his actual specialties. JSON-LD with medicalSpecialty explicitly listing body contouring, post-bariatric reconstruction, and gynecomastia. availableService listing specific procedures: body lift, brachioplasty, thigh lift, tummy tuck after weight loss, male breast reduction.

Content linking the bariatric-to-body-contouring patient journey. Published content answering prompts like "what happens to loose skin after gastric sleeve" and "when can I get body contouring after bariatric surgery" that position Castaneda as the next step after Dra. Gaby's procedures. Entity connection between Castaneda and Dra. Gaby through internal linking and hospitalAffiliation. Positioned his high-BMI expertise as a differentiator. Most plastic surgeons in Tijuana have BMI limits. Castaneda operates on patients other surgeons will not.

This is the most dramatic operational result of the four doctors.

After positioning him in his actual niche instead of as a generic "plastic surgeon," his surgical volume went from approximately 5 procedures per month to 25 to 27. A 5x increase. We cannot attribute this entirely to AI visibility. The repositioning also affected traditional search, internal referral patterns from Dra. Gaby's patients, and how coordinators pitched his services. But the entity-niche alignment was the catalyst.

Started appearing in niche-specific prompts like "body contouring after gastric sleeve Tijuana" and "plastic surgeon for high BMI patients Mexico" where almost no Tijuana surgeons were showing up before. The bariatric-to-body-contouring pipeline content created a unique entity relationship that AI started reflecting. His gynecomastia content started appearing in prompts about male plastic surgery in Tijuana, a query space with very few AI answers.

His case illustrates the most important lesson of the entire project: niche specialization can be a bigger visibility advantage than prestigious credentials. A generic "plastic surgeon" listing competes with everyone. A "post-bariatric body contouring specialist who operates on high-BMI patients" listing competes with almost no one.

Dra. Gabriela Rodriguez Ruiz: Bariatric Surgery

Her competition was not just other surgeons. It was a pill.

Dra. Gaby operates in a completely different world from the plastic surgeons. MD, PhD, Fellow of the American College of Surgeons (FACS), more than 7,800 bariatric procedures.

The bariatric market has a unique challenge: GLP-1 medications (Ozempic, Wegovy) are now the first answer many AI systems give when patients ask about weight loss. Her competition is not just other surgeons. It is a medication category. Her review profile was dominated by the VIDA clinic listing. Patients rarely mentioned "Dr. Rodriguez Ruiz" or "Dra. Gaby" by name. RealSelf and BariatricPal are major platforms for bariatric reviews. She had minimal presence on either.

We built her entity page with FACS prominently structured in hasCredential schema, with explicit sameAs linking to ACS Fellow verification. PhD credential in schema as a differentiator. Published GLP-1 vs surgery comparison content positioning her directly in the "Ozempic or gastric sleeve?" debate. Cost transparency content linking surgery costs with recovery timelines. Two-touch review system specifically trained coordinators to ask bariatric patients to mention "Dra. Gaby" and "gastric sleeve."

She started appearing in bariatric-specific prompts like "best gastric sleeve surgeon in Tijuana" and "FACS certified bariatric surgeon Mexico." The FACS credential started being mentioned correctly in AI answers. Before, AI systems had no way to verify or surface this credential. The GLP-1 comparison content positioned her in a query space that did not exist two years ago. Her Review Specificity Score improvement was the most dramatic of the four doctors because the baseline was so low (patients almost never mentioned her by name before the two-touch system), going from approximately 8% to above 42% within 90 days.

Four Doctors, Four Different Problems, One Framework

The Before and After: What Changed in AI Visibility

Before the implementation, in late 2024, we ran a set of test prompts across ChatGPT, Gemini, Perplexity, and Google AI Overviews. We used 40+ unique prompts, run across four platforms and multiple sessions, totaling over 500 prompt executions. Prompts like "best facelift surgeon in Tijuana," "best bariatric surgeon in Tijuana," "deep plane facelift Tijuana," "gastric sleeve Tijuana reviews." None of the four VIDA doctors appeared in any AI answer. Zero citation share.

After the implementation, approximately six months later, running the same prompt set, we observed meaningful change. Doctor names began appearing with correct credentials and specialty descriptions. AI answers that previously cited only facilitator sites began citing VIDA directly. Some AI answers began reflecting the surgeons' training relationship to Dr. Connell more accurately. Review content with specific doctor names and procedures began being referenced in AI summaries.

To give one concrete example: the prompt "best deep plane facelift surgeon in Tijuana" returned no mention of any VIDA surgeon across any platform in late 2024. By mid-2025, the same prompt returned Dr. Quiroz's name with correct credential context on multiple platforms, including references to his training lineage under Dr. Connell.

The mentions weren't uniform. Some prompts surfaced the doctors consistently. Others sporadically. Some platforms cited them more reliably than others. But compared with our earlier tests, the doctors appeared more often and with more accurate context.

Here's the part that matters most for credibility.

There is no clean causal line here. We changed the entity profiles, the schema, the reviews, and the content all within the same six months. AI models updated their training data during that period. Competitors made their own changes. I cannot tell you which single lever moved the needle most. I could tell you entity optimization produced a 40% increase in AI citations. That would be a made-up number. The real answer is messier. Multiple things changed at the same time. I cannot hand you a clean attribution model. What I can hand you is the before state, the after state, and six months of implementation notes.

What we can say: across our implementations so far, we've repeatedly observed that stronger entity structure tends to coincide with improved AI visibility. The pattern appears positive even though precise attribution remains difficult. This is what we saw. Take it for what it is: one implementation, one clinic, six months of data.

The Numbers We Can Share

I promised honesty about what we can and can't claim. Here are the numbers I'm comfortable defending.

Citation visibility: From no appearances in our initial prompt set to recurring appearances in later tests. We don't publish the exact percentage because AI outputs vary by session, by user, by geography, and the number would be misleadingly precise. The meaningful metric is the shift from complete absence to consistent presence. That shift is real.

Review Specificity Score: We track the percentage of reviews that mention the doctor by name and the specific procedure, with patient origin city counted as an additional enrichment field. We scored reviews across Google, RealSelf, Doctoralia, and internal follow-up captures. A review counted as "specific" if it named the doctor and the procedure. Before implementing the two-touch system, across a sample of approximately 200 recent reviews, we estimated sub-20% contained this entity-rich information. Within 90 days, our internal tracking across a comparable sample put that number above 40%.

Entity Consistency: This one was embarrassing once we saw it. Before implementation, each doctor had an average of 3 to 4 inconsistencies across the platforms we audited. Name format differences. Specialty descriptions that didn't match. Credential claims from outdated facilitator pages. After standardization, we removed most major inconsistencies across the main platforms we could update.

Content Architecture: Published search- and AI-oriented articles for each specialty vertical. Each article internally links to the doctor profiles, reinforcing entity associations. The content is built to answer the specific prompts patients actually ask AI systems.

These numbers aren't a marketing dashboard with lead attribution. They're entity-level measurements of discoverability. The kind of metrics that matter when the question isn't "how many clicks did we get" but "does the machine know we exist."

How We Measured This

Before I share what changed, here is exactly how we measured it. These definitions stayed consistent throughout the project.

A prompt execution was one query typed into one platform. We used 40+ unique prompts like "best deep plane facelift surgeon in Tijuana" and "FACS certified bariatric surgeon Mexico." Each prompt was run across ChatGPT, Gemini, Perplexity, and Google AI Overviews. Some prompts were run multiple times across sessions to check for variability. Total: over 500 individual prompt executions.

A mention counted when the AI response included the doctor's name with at least one correct contextual detail (specialty, practice name, or credential). A response that said "VIDA offers plastic surgery" without naming a specific doctor did not count. A response that named "Dr. Quiroz" with "facelift" or "VIDA" counted. We did not count partial brand mentions without doctor names.

Review Specificity Score: we pulled a sample of recent Google reviews (approximately 200 in the baseline, comparable sample in the follow-up). A review counted as "specific" if it mentioned the doctor by name AND the procedure. Patient origin city was tracked as a bonus field but was not required for the count. We scored reviews across Google, RealSelf, Doctoralia, and internal WhatsApp follow-up captures.

Platforms audited for entity consistency: Google Business Profile, the VIDA website, LinkedIn, Doctoralia, RealSelf, PlacidWay, Medical Departures, and BariatricPal (for Dra. Gaby specifically).

Date ranges: baseline measurements were taken in October to November 2024. Follow-up measurements were taken in April to May 2025, approximately six months after the first implementation changes went live. Review Specificity Score was tracked monthly starting January 2025.

We did not use any third-party AI monitoring tool. All prompt testing was manual. We recorded results in a spreadsheet. This is not a peer-reviewed study. It is an operational log from a real implementation.

The "Invisible Surgeon, Visible Practice" Paradox

This is something we didn't expect to find. We noticed something early in the project: VIDA as a practice entity probably had some AI visibility before we started. The practice has years of review history, media mentions, and facilitator listings. AI systems were more likely to recognize the organization than the individual surgeons. A prompt might return something about "VIDA Wellness & Beauty Center in Tijuana offers plastic surgery and bariatric surgery." The brand had some presence in the machine's understanding.

But the surgeons didn't.

This is a problem because patients choosing a surgeon for a deep plane facelift or a gastric sleeve aren't choosing a brand. They're choosing a specific pair of hands. AI prompts reflect this. People ask "who is the best facelift surgeon in Tijuana," not "what is the best clinic in Tijuana." BrightLocal's 2024 research suggests business websites are a major source in ChatGPT local search outputs. If your website treats doctors as supporting characters in the practice's story rather than as distinct entities, the machine will do the same.

The implementation essentially unbundled the practice entity into individual surgeon entities while keeping the practice as the institutional anchor. Each surgeon's entity page links back to VIDA through hospitalAffiliation. VIDA's pages link to the surgeons. The result is a bidirectional entity relationship that strengthens both. The practice gives institutional credibility to the surgeon. The surgeon gives procedural specificity to the practice.

What We Learned That We Didn't Expect

Six months of building this surfaced insights I didn't anticipate. Some of these challenged assumptions we started with.

In this implementation, schema alone didn't appear to change outcomes visibly. We expected structured data to be the primary lever. In isolation, it appeared to have minimal visible effect. Schema without consistent cross-platform entity data produced limited change. The combination of schema plus directory consistency plus review specificity is what appeared to compound. None of the individual pieces seemed to do much alone. Together, the effect was clear. This aligns with what we've come to think of as a confidence threshold. AI systems appear to respond better when multiple authoritative sources corroborate the same doctor-level facts before surfacing a recommendation.

The Connell lineage mattered more than we expected. The training relationship with a recognized pioneer created an entity association that AI seemed to follow. Dr. Bruce Connell exists as a well-documented surgeon in medical literature and AI training data. Explicitly documenting the training relationship may have helped systems connect these surgeons to a recognized figure in their specialty. You could think of this as borrowing context from a better-documented professional lineage. It's also something most Tijuana practices can't replicate, which makes it a genuine early visibility advantage.

The two-surname convention is a real advantage. Mexican naming convention provides better entity disambiguation than English naming. "Dr. Juan Carlos Fuentes Gutierrez" is nearly unique globally. "Dr. John Smith" is essentially unresolvable without extensive additional context. The four-part Mexican name structure functions almost like a natural identifier. Longer, more distinctive full names likely reduce ambiguity across platforms and search systems. This may be a structural advantage when names are kept consistent across platforms.

In our case, Bing indexing appeared to be a meaningful unlock for ChatGPT visibility. We were focused on Google. When we set up Bing Webmaster Tools and submitted the sitemap, ChatGPT mentions appeared to increase within weeks. This makes directional sense. ChatGPT's web browsing features have used Bing's search index for retrieval in certain modes, though not all ChatGPT responses depend on live Bing retrieval in the same way. Bing has negligible market share as a standalone search engine, which is why almost no practice thinks about it. But for ChatGPT experiences that use web retrieval, Bing indexing quality may directly affect what ChatGPT can find and surface. This is a simple, low-cost step worth taking, especially if your pages aren't well indexed outside Google. Takes 15 minutes.

The coordinator is the bottleneck and the solution. Review quality improved dramatically once coordinators had specific scripts and understood why entity-rich reviews mattered. The operational change was small. One extra WhatsApp message at 3 to 4 weeks post-op. The impact was disproportionate. But without coordinator buy-in, the two-touch system produces nothing. The coordinator who doesn't understand what AI does with reviews will send a generic request and get a generic review.

Facilitator sites were actively working against us. Outdated information on PlacidWay and similar platforms created entity conflicts that we believe degraded AI confidence. Cleaning these up was the least exciting part of the entire project. It was also one of the most necessary.

Niche positioning beat prestigious credentials for speed of results. Castaneda had no Connell lineage and no FACS. But by positioning him in his actual niche (post-bariatric body contouring, high-BMI surgery, gynecomastia) instead of as a generic plastic surgeon, he went from approximately 5 surgeries per month to 25 to 27. Quiroz had Connell. Dra. Gaby had FACS. Castaneda had specificity. In a thin query space with almost no competition, specificity won. This matters because most doctors reading this do not have a Connell or a FACS. They have a niche. And that niche, properly structured, may be their strongest visibility lever.

Better-informed patients cost less to acquire. The CAC for plastic surgery dropped from approximately $1,200 to $655 per surgical patient during the implementation period. I am not claiming entity optimization alone caused this, but we observed a pattern: patients arriving through AI-mediated research had already vetted the doctor's credentials before first contact. They asked fewer basic questions. They needed less convincing. They converted faster. The entity work did not just make the doctors more visible. It changed the quality of the visibility. Being found by a patient who already knows your training lineage, your board certification, and your review specificity score is fundamentally different from being found by a patient who clicked a generic ad.

What This Means for Your Practice

I realize not every practice is VIDA. Not every surgeon trained under a pioneer of their specialty. But the structural problems we found are universal across Tijuana's medical tourism market. In fact, based on what we've seen, entity optimization still appears uncommon across Tijuana's medical tourism market.

If you're a single-surgeon practice, the implementation is actually simpler. One entity to optimize. One set of platforms to align. One review strategy to implement. You don't need the multi-doctor complexity we navigated at VIDA.

If you're a multi-specialty practice, the complexity multiplies but the framework is the same. Each doctor needs an entity home, consistent cross-platform presence, and a review collection system that captures entity-rich feedback. The key operational challenge is routing reviews to individual surgeon entities rather than letting everything pool under the practice brand.

If you're a dental practice, the credential system is different (CONACEM doesn't certify dentists the same way) but the entity optimization principles are identical. Name consistency, structured data, verification links, review specificity. The mechanics don't change by specialty.

The broader context makes this a priority. BrightEdge reported significant growth in AI-referred traffic to healthcare sites during 2024, though definitions and measurement methods vary across studies. Concurrently, Google AI Overviews rapidly expanded its global footprint across hundreds of countries during 2024 and 2025. This shift is already underway. The practices that build entity infrastructure now may have an outsized advantage as these systems become the primary way patients research and choose providers.

The four VIDA doctors aren't more qualified today than they were in late 2024. Their credentials haven't changed. Their experience hasn't changed. Their surgical skills haven't changed.

What changed is how their credentials, experience, and skills are represented in the systems patients are increasingly using to choose a doctor.

The problem was never the doctors. It was the page. For the full methodology behind what we built at VIDA, see our complete GEO playbook.

Related articles

• Why Your Clinic Has 500 Five-Star Reviews and ChatGPT Still Doesn't Know You Exist
• How to Structure a Doctor Profile So AI Can Trust It: A Tijuana Clinic's Guide to Physician Entity Optimization
• GEO for Plastic Surgeons in Tijuana: Why Highly Qualified Facelift Surgeons Stay Invisible to AI
• How to Get Patient Reviews That AI Can Actually Use: The Medical Tourism Coordinator's Playbook
• GEO for Bariatric Surgeons in Tijuana: Staying Visible When Your Competition Is Ozempic

Quick answers

How long does it take for AI visibility changes to show results?

In our experience at VIDA, we began observing AI mentions approximately 4 to 6 months after the initial entity optimization. But this isn't a clean timeline. Some changes, like Bing Webmaster Tools setup, appeared to have a faster effect than others. Schema implementation alone didn't produce visible change for weeks. AI visibility builds gradually as multiple signals compound, and there's no guaranteed timeline.

Can a single-doctor practice benefit from entity optimization, or is this only for large practices?

A single-doctor practice may actually benefit more. You have one entity to optimize, one set of platforms to audit, and one review strategy to implement. The VIDA project was complex precisely because we had to build distinct entity profiles for five surgeons within one practice brand. A solo practitioner can execute the same framework with less coordination overhead.

What is the most important first step for a practice that wants to improve AI visibility?

Open ChatGPT, Gemini, and Perplexity. Type your surgeon's full name. Type "best [specialty] in [city]." See what comes back. That diagnostic takes five minutes and tells you exactly where you stand. If the answer is nothing, you know the scope of the problem. If the answer is wrong or outdated, you know the nature of the problem. The audit always comes first.

Does physician schema markup alone improve AI recommendations?

In our observation, no. Schema without consistent cross-platform entity data produced minimal visible change. Schema is one layer of a multi-layer system. It makes your credentials machine-readable, but if those credentials are contradicted by outdated facilitator listings or diluted by vague reviews, the schema alone doesn't appear to be enough. The combination is what matters.

How do you measure AI citation share for a doctor?

We run a set of specialty-specific and location-specific prompts across ChatGPT, Gemini, Perplexity, and Google AI Overviews. We record whether the doctor appears, with what credentials, and whether the source is the practice website, a directory, or a facilitator site. We repeat this monthly. It's manual, it varies by session, and it isn't as clean as Google Analytics. But it's the best measurement available right now.

Why were experienced surgeons invisible to AI despite having strong credentials?

Because AI systems don't read resumes. They extract structured entity data from web pages, directories, and reviews. A surgeon with strong real-world credentials but weak web representation is far less legible to machines than they should be. Digital legibility isn't the same as clinical qualification. It's a formatting problem, not a quality problem.

Is entity optimization a one-time project or an ongoing process?

The initial build (entity pages, schema, cross-platform consistency) is a project with a clear endpoint. The ongoing work is review collection, content creation, and monitoring for entity drift: platforms updating your information, new directories appearing, facilitator sites publishing outdated data. Think of it as building the house and then maintaining it. The foundation is a one-time investment. The upkeep is continuous but lighter.

What is the role of patient reviews in AI visibility for doctors?

Reviews serve as independent corroboration of the claims on your website. When your website says "Dr. Quiroz specializes in deep plane facelifts" and multiple reviews mention "Dr. Quiroz" and "deep plane facelift" in natural language, that consistency across sources builds entity confidence. Generic reviews ("great experience!") provide star ratings but zero entity data. Specific reviews (doctor name, procedure, origin city, outcome) function as independent entity verification that AI systems can extract and cross-reference.