Executive Playbook
Days 1-10: Entity Foundation
- Audit entity consistency across GBP, Healthgrades, Zocdoc, Doximity, insurance directories
- Verify NPPES/NPI records match current practice information
- Standardize physician name format and credentials everywhere
- Implement MedicalOrganization and Physician schema
Days 11-20: Content Authority 5. Identify 3 core specialty topics for pillar content 6. Create FAQ content targeting top 20 patient questions 7. Add author credentials and dateModified to all medical content 8. Verify clinical accuracy against current guidelines
Days 21-30: Platform Optimization 9. Complete GBP with all attributes, services, photos 10. Configure AI crawler access based on risk assessment 11. Claim Bing Places and Apple Business Connect 12. Establish baseline AI visibility through query testing
KPIs:
| Metric | Definition | Target |
|---|---|---|
| AI Mention Rate | % of target queries with practice appearing | +20% in 6 months |
| Entity Accuracy | % of AI responses with correct info | 95%+ |
| Grounding Citations | Times cited as source in Perplexity/AI Overviews | Monthly growth |
| Conversion Assist | Patients reporting AI-influenced discovery | Track and grow |
The Shift to AI-Mediated Healthcare Discovery
Patients increasingly begin healthcare journeys through AI interfaces. Google’s Search Generative Experience documentation confirms AI Overviews appear for informational queries across categories, with health topics receiving enhanced source quality requirements. OpenAI’s 2024 announcements reported ChatGPT surpassing 100 million weekly active users globally. Perplexity’s published metrics indicate millions of daily queries with health among top categories.
This creates a visibility problem distinct from traditional SEO. When AI synthesizes answers from multiple sources, practices without strong entity signals and content authority are excluded from responses entirely, regardless of organic ranking position.
Medical AI SEO addresses this through entity optimization, topical authority building, and platform-specific strategies that position practices as sources AI systems confidently reference.
How AI Systems Select Sources
Training vs. Retrieval: Large language models have fixed training data plus optional real-time retrieval. Base knowledge comes from training snapshots; retrieval-augmented generation (RAG) accesses current web content. Both channels require optimization.
Entity Recognition: AI systems identify entities through consistent signals across authoritative sources. Conflicting information (different addresses, credential formats, specialty terms) reduces confidence and can cause exclusion or inaccurate representation.
Authority Hierarchy: Analysis of AI-generated medical responses shows consistent patterns. Major medical institutions, government health sources (NIH, CDC), and established health publishers receive disproportionate citation. Individual practices appear when backed by strong entity signals, media presence, or topical authority in specific areas.
Why Competitors Lose AI Visibility
Understanding failure patterns clarifies winning strategy:
Entity Fragmentation: Practices with inconsistent NAP across directories, multiple name variations, or conflicting credential formats create entity confusion. AI systems cannot confidently identify fragmented entities, defaulting to competitors with cleaner signals.
Thin Content Dependence: Practices relying on service pages with minimal content lose to competitors with comprehensive condition and treatment coverage. AI systems need extractable, authoritative content to cite.
Platform Neglect: Competitors ignoring Bing Places lose Copilot visibility. Those blocking AI crawlers forfeit ChatGPT and Perplexity presence. Single-platform optimization creates gaps competitors exploit.
Stale Information: Practices with outdated content, old addresses in directories, or former physician listings confuse AI systems. Competitors with current, maintained information win by default.
Missing Credentials: AI systems weight E-E-A-T signals heavily for medical content. Practices without visible author credentials, board certification mentions, or institutional affiliations lose to competitors who display expertise signals prominently.
Review Neglect: Practices with few reviews, poor ratings, or no response patterns signal lower authority. Competitors actively managing reputation capture local AI visibility.
The common thread: competitors lose through neglect and inconsistency. Winning requires systematic attention to signals competitors ignore.
Entity Optimization
Core Requirements
Standardize across all platforms:
- Business name (exact match everywhere)
- Physician names with credentials (consistent format)
- Specialty terminology (match NUCC taxonomy)
- Address format (identical representation)
- Phone number (same format)
Credentialing Databases
Verify accuracy in authoritative sources AI systems may reference:
- NPPES/NPI Registry: Current location, specialty codes
- CAQH ProView: Complete profile for payer directory accuracy
- State Medical Board: Active license status
Knowledge Graph Presence
Google Knowledge Graph: Driven by GBP completeness, structured data, and authoritative mentions. Focus on GBP optimization and schema markup.
Wikipedia/Wikidata: Significant impact for physicians meeting notability criteria (substantial coverage in independent reliable sources). However, Wikipedia’s conflict of interest policies prohibit self-promotional editing. Violations result in article deletion and editor sanctions. For most practices, other entity-building methods are lower-risk and more practical.
Schema Implementation
Required types:
- MedicalOrganization/MedicalClinic (practice entity)
- Physician (individual provider entities)
- FAQPage (patient question content)
Validate with Google Rich Results Test. Monitor Search Console for errors.
AI Crawler Access Decision Framework
| Crawler | Allow | Disallow | Decision Factors |
|---|---|---|---|
| GPTBot | ChatGPT visibility | Excluded from ChatGPT | Allow unless content licensing or competitive concerns |
| PerplexityBot | Perplexity citations | No Perplexity presence | Generally allow; high-value citations |
| ClaudeBot | Claude visibility | Excluded | Similar to GPTBot considerations |
| Google-Extended | Google AI training | Search unaffected | Block if concerned about AI training specifically |
No universal correct answer. Evaluate based on practice risk tolerance and strategic priorities.
Content Authority
Architecture
Pillar pages: Comprehensive coverage of core specialty topics (3,000-5,000 words). Condition overview, symptoms, diagnosis, treatment options, outcomes, patient considerations.
Cluster content: Supporting articles on subtopics and patient questions (1,000-2,000 words). Link to pillar and related clusters.
Quality Signals
- Clinical accuracy aligned with current guidelines (cite ACC/AHA, USPSTF, specialty society guidelines where relevant)
- Named author with verifiable credentials
- Visible publication and update dates
- dateModified schema markup
Freshness
Annual minimum review. Immediate update when guidelines change. Maintain XML sitemap lastmod accuracy.
Platform-Specific Strategy
Google AI Overviews: Featured snippet formatting, passage-level quality, content freshness, strong entity signals.
ChatGPT: Entity consistency across web, Wikipedia/Wikidata for eligible physicians, traditional SEO for browsing queries.
Perplexity: Direct-answer format, visible authorship, recent dates, citations within content.
Copilot: Bing Places completeness, Bing-indexed content quality.
Local Optimization
Google Business Profile:
- Precise primary category (Cardiologist, not Doctor)
- All attributes completed
- Service descriptions with detail
- Photos of facility, staff, equipment
- Regular posts
- All reviews answered
- Q&A populated
Multi-Location: Individual listings per location, unique content per location page, location-specific review strategy.
AI Agents: Preparing for the Next Phase
AI systems are evolving from answer engines to action-capable agents. Google, OpenAI, and other providers are building systems that complete tasks, not just provide information. Healthcare implications are significant.
Near-Term Agent Capabilities
Appointment Booking: AI agents will check availability and book appointments directly. Practices with:
- Real-time scheduling API integration
- Structured availability data
- Clear booking parameters (new vs. existing patient, visit types, insurance requirements)
will be actionable by agents. Practices requiring phone calls become friction points agents route around.
Insurance Verification: Agents will verify coverage before recommending providers. Practices with:
- Machine-readable insurance acceptance lists
- Network status clearly indicated
- Pre-authorization requirement information
will be matchable to patient coverage. Incomplete insurance information causes agent exclusion.
Provider Matching: Agents will match patients to providers based on structured criteria:
- Specialty and subspecialty classifications
- Condition-specific experience
- Languages spoken
- Accessibility features
- Telehealth availability
- Geographic coverage
Practices with rich, structured attribute data become more precisely matchable.
Preparation Strategy
Structured Data Depth: Expand schema beyond basic entity information. Include:
- Detailed service descriptions with schema markup
- Physician-condition associations
- Procedure offerings with preparation requirements
- Insurance and payment structured data
API Readiness: Evaluate scheduling system API capabilities. Systems with open APIs or integration partnerships with health platforms position practices for agent interoperability.
Attribute Completeness: Every filterable attribute an agent might use should be documented: telehealth availability, weekend hours, languages, accessibility, parking, new patient acceptance, age ranges served.
Conversational Content: Agents will pull from content to answer follow-up questions. FAQ coverage of practical concerns (what to bring, how to prepare, what to expect, parking, check-in process) supports agent conversations.
Competitive Advantage Window
Agent capabilities are emerging now but adoption is early. Practices building structured data depth and API readiness today will be agent-compatible when these systems reach mainstream use. Competitors who wait will face integration costs under time pressure.
Compliance
HIPAA: No patient identifiers without documented consent. Proper consent for testimonials.
FTC: No unsubstantiated claims. Required disclosures for testimonials.
FDA: Claims aligned with approved indications.
State Medical Boards: Review state-specific advertising restrictions before publishing.
Measurement
Monthly Protocol:
- Test 50+ target queries across Google AI Overviews, ChatGPT, Perplexity, Copilot
- Document: appearance, accuracy, competitor presence
- Track trends against baseline
- Correlate with optimization activities
Tools: Manual testing essential. Semrush, Ahrefs, and dedicated platforms offer emerging AI tracking features.
Operational Appendix
A. Schema Markup Templates
MedicalOrganization
{
"@context": "https://schema.org",
"@type": "MedicalClinic",
"name": "[Practice Name]",
"@id": "[URL]/#organization",
"url": "[URL]",
"logo": "[Logo URL]",
"description": "[Practice description with specialty focus]",
"medicalSpecialty": "[Primary Specialty]",
"telephone": "[Phone]",
"address": {
"@type": "PostalAddress",
"streetAddress": "[Street]",
"addressLocality": "[City]",
"addressRegion": "[State]",
"postalCode": "[ZIP]",
"addressCountry": "US"
},
"geo": {
"@type": "GeoCoordinates",
"latitude": [LAT],
"longitude": [LONG]
},
"openingHoursSpecification": [
{
"@type": "OpeningHoursSpecification",
"dayOfWeek": ["Monday", "Tuesday", "Wednesday", "Thursday", "Friday"],
"opens": "08:00",
"closes": "17:00"
}
]
}
Physician
{
"@context": "https://schema.org",
"@type": "Physician",
"name": "[Dr. Name, Credentials]",
"givenName": "[First]",
"familyName": "[Last]",
"honorificSuffix": "[MD/DO, Board Certifications]",
"jobTitle": "[Specialty Title]",
"medicalSpecialty": "[Specialty]",
"description": "[Bio with expertise areas]",
"image": "[Photo URL]",
"worksFor": {
"@type": "MedicalClinic",
"@id": "[Practice URL]/#organization"
},
"hasCredential": [
{
"@type": "EducationalOccupationalCredential",
"credentialCategory": "Board Certification",
"name": "[Certification Name]",
"recognizedBy": {
"@type": "Organization",
"name": "[Certifying Board]"
}
}
]
}
FAQPage
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [
{
"@type": "Question",
"name": "[Question text]",
"acceptedAnswer": {
"@type": "Answer",
"text": "[Answer text - concise, clinically accurate]"
}
}
]
}
B. Entity Audit Checklist
| Platform | Check | Status |
|---|---|---|
| Google Business Profile | Name, address, phone, categories, attributes, photos, services | |
| Bing Places | Complete profile matching GBP | |
| Apple Business Connect | Claimed and accurate | |
| Healthgrades | Profile claimed, credentials current | |
| Zocdoc | If applicable, profile complete | |
| Doximity | Physician profiles verified | |
| WebMD | Directory listing accurate | |
| Vitals | Profile current | |
| Insurance Directories | Spot-check major payers | |
| Hospital Directories | Affiliated hospital listings accurate | |
| NPPES/NPI | Current information | |
| State Medical Board | License status current | |
| Practice Website | NAP matches all directories |
C. AI Crawler Robots.txt Examples
Maximum AI Access:
User-agent: GPTBot
Allow: /
User-agent: ClaudeBot
Allow: /
User-agent: PerplexityBot
Allow: /
User-agent: Google-Extended
Allow: /
Retrieval Only (Block Training):
User-agent: GPTBot
Disallow: /
User-agent: ClaudeBot
Disallow: /
User-agent: PerplexityBot
Allow: /
User-agent: Google-Extended
Disallow: /
Selective Access:
User-agent: GPTBot
Allow: /blog/
Allow: /conditions/
Disallow: /
User-agent: PerplexityBot
Allow: /
D. Query Testing Template
| Query | Platform | Appears | Accurate | Competitors | Notes | Date |
|---|---|---|---|---|---|---|
| [Query 1] | Google AIO | Y/N | Y/N | [List] | ||
| [Query 1] | ChatGPT | Y/N | Y/N | [List] | ||
| [Query 1] | Perplexity | Y/N | Y/N | [List] | ||
| [Query 1] | Copilot | Y/N | Y/N | [List] |
Query Categories to Test:
- Condition + location (“cardiologist chicago”)
- Symptom queries (“chest pain specialist near me”)
- Treatment queries (“[procedure] + [city]”)
- Provider comparison (“best [specialty] [location]”)
- Insurance queries (“[specialty] accepts [insurance] [location]”)
E. Content Freshness Protocol
| Content Type | Review Frequency | Update Triggers |
|---|---|---|
| Condition pages | Annual minimum | Guideline changes, new treatments |
| Treatment pages | Annual minimum | FDA approvals, protocol changes |
| Physician bios | Semi-annual | Credential changes, new publications |
| FAQ content | Annual | New common questions, accuracy issues |
| Service descriptions | Annual | Service changes, pricing updates |
Update Process:
- Review against current clinical guidelines
- Update dateModified schema
- Update visible “last reviewed” date
- Update XML sitemap lastmod
- Log update in content tracking system
F. Implementation Timeline Detail
Phase 1: Foundation (Weeks 1-4)
- Week 1: Entity audit, document inconsistencies
- Week 2: NPPES/CAQH verification, begin corrections
- Week 3: Schema markup implementation
- Week 4: GBP optimization, crawler configuration
Phase 2: Content (Weeks 5-12)
- Weeks 5-6: Topical authority strategy, content gap analysis
- Weeks 7-10: Pillar content development (1 per 2 weeks)
- Weeks 11-12: FAQ content, author credential pages
Phase 3: Authority (Months 3-6)
- Month 3: Review generation program launch
- Month 4: Digital PR outreach begins
- Month 5: Professional association engagement
- Month 6: Baseline measurement, strategy refinement
Phase 4: Expansion (Months 6-12)
- Secondary topic clusters
- Video content development
- Competitive monitoring system
- Agent-readiness preparation
Phase 5: Maintenance (Ongoing)
- Monthly AI visibility testing
- Annual content review cycle
- Quarterly strategy assessment
- Continuous entity monitoring
G. Compliance Quick Reference
| Regulation | Key Requirements | Risk Areas |
|---|---|---|
| HIPAA | No PHI without consent | Testimonials, case studies, photos |
| FTC | Substantiated claims, disclosures | Outcome claims, testimonials, endorsements |
| FDA | Approved indications only | Drug/device claims, off-label mentions |
| State Medical Board | Varies by state | Comparative claims, guarantees, specialties |
Pre-Publication Checklist:
- [ ] No patient identifiers without documented consent
- [ ] Claims substantiated with evidence
- [ ] Testimonial disclosures included
- [ ] Credentials accurately represented
- [ ] No prohibited comparative claims
- [ ] Content reviewed by qualified clinician