Model Context Optimization — Structured Data Audit
https://my.clevelandclinic.org
April 28, 2026
Site Entity Relationship Summary
Step 1 — SITE ENTITY INVENTORY: - URL: https://my.clevelandclinic.org/about/contact/phone-directory Entity Type: ContactPage / Directory Primary Entity: Cleveland Clinic (Parent Organization) Secondary Entities: Cleveland Clinic Children’s, Cleveland Clinic Florida, Cleveland Clinic Canada, Cleveland Clinic Nevada. - URL: https://my.clevelandclinic.org/about/website Entity Type: WebSite / Service Primary Entity: Cleveland Clinic Web Presence Secondary Entities: Non-Discrimination Notice, Patient Rights, Privacy Practices (Policies). - URL: https://my.clevelandclinic.org/patients Entity Type: WebPage / ServiceHub Primary Entity: Patient and Visitor Services Secondary Entities: MyChart (Software), Financial Assistance, Medical Records (Service). - URL: https://my.clevelandclinic.org/patients/information/medical-records Entity Type: MedicalBusiness / Service Primary Entity: Health Information Management (Department) Secondary Entities: MyChart, Epic Systems Corporation, Health Information Exchange (HIE). - URL: https://my.clevelandclinic.org/patients/billing-finance/comprehensive-hospital-charges Entity Type: PriceSpecification / Service Primary Entity: Cleveland Clinic Hospital Charges Secondary Entities: CMS (Organization), Florida Health Finder, Specific Regional Hospitals (Avon, Beachwood, etc.). - URL: https://my.clevelandclinic.org/health Entity Type: Guide / Archive Primary Entity: Cleveland Clinic Health Library Secondary Entities: Body Systems, Diseases & Conditions, Medical Treatments, Procedures, Drugs. - URL: https://my.clevelandclinic.org/health/procedures Entity Type: CollectionPage Primary Entity: Medical Procedures Index Secondary Entities: Cleveland Clinic Specialists. - URL: https://my.clevelandclinic.org/health/symptoms Entity Type: CollectionPage Primary Entity: Medical Symptoms Index Secondary Entities: Health Educators. - URL: https://my.clevelandclinic.org/departments/education Entity Type: EducationalOrganization Primary Entity: Cleveland Clinic Education Institute Secondary Entities: Center for Youth and College Education, Center for Continuing Education. - URL: https://my.clevelandclinic.org/departments/patient-experience/depts/office-patient-experience Entity Type: MedicalOrganization / Department Primary Entity: Office of Patient Experience Secondary Entities: Ombudsman Office, Chief Experience Officer (Role). - URL: https://my.clevelandclinic.org/online-services/mychart Entity Type: SoftwareApplication / Service Primary Entity: MyChart Secondary Entities: MyClevelandClinic App, Epic Systems Corporation. - URL: https://my.clevelandclinic.org/online-services/virtual-visits Entity Type: MedicalWebPage / Service Primary Entity: Virtual Visits (Telehealth) Secondary Entities: Express Care, Virtual Primary Care. - URL: https://my.clevelandclinic.org/online-services/virtual-second-opinions Entity Type: MedicalWebPage / Service Primary Entity: Virtual Second Opinions (VSO) Secondary Entities: Nurse Care Manager, Specialist Providers. - URL: https://my.clevelandclinic.org/locations Entity Type: MedicalOrganization / Place Primary Entity: Cleveland Clinic Global Locations Secondary Entities: Main Campus, Regional Hospitals. - URL: https://my.clevelandclinic.org/locations/ohio-locations Entity Type: CollectionPage / Place Primary Entity: Ohio Medical Facilities Secondary Entities: Northeast Ohio Wellness Centers. - URL: https://my.clevelandclinic.org/locations/nevada Entity Type: MedicalBusiness / Place Primary Entity: Cleveland Clinic Nevada Secondary Entities: Lou Ruvo Center for Brain Health. - URL: https://my.clevelandclinic.org/professionals Entity Type: WebPage / ServiceHub Primary Entity: Professional Resources Secondary Entities: Quality Alliance, Cleveland Clinic Connected. - URL: https://my.clevelandclinic.org/professionals/referring Entity Type: WebPage / Service Primary Entity: Physician Referral Service Secondary Entities: Referring Physician Hotline, Physician Relations Team. - URL: https://my.clevelandclinic.org/help Entity Type: FAQPage Primary Entity: Cleveland Clinic Support Secondary Entities: International Patients, Ombudsman. - URL: https://my.clevelandclinic.org/giving Entity Type: Charity / Service Primary Entity: Cleveland Clinic Philanthropy Secondary Entities: VeloSano, Catalyst Grants. - URL: https://my.clevelandclinic.org/providers & https://my.clevelandclinic.org/staff Entity Type: CollectionPage / SearchAction Primary Entity: Find a Provider Tool Secondary Entities: Staff Physicians. - URL: https://my.clevelandclinic.org/services Entity Type: Service / Archive Primary Entity: Clinical Services Index Secondary Entities: Adult Services, Pediatric Services. - URL: https://my.clevelandclinic.org/webappointment Entity Type: ScheduleAction / Service Primary Entity: Appointment Scheduling Secondary Entities: Global Patient Services. - URL: https://my.clevelandclinic.org/health-essentials-newsletter Entity Type: PublicationEvent Primary Entity: Health Essentials Newsletter Secondary Entities: Cleveland Clinic Wellness. - URL: https://my.clevelandclinic.org/podcasts/health-essentials Entity Type: PodcastSeries Primary Entity: Health Essentials Podcast Secondary Entities: Dr. Jorge Gutierrez-Aceves, Dr. Jared Harp, Dr. Lauren Wichman. - URL: https://my.clevelandclinic.org/research Entity Type: ResearchOrganization Primary Entity: Cleveland Clinic Research Secondary Entities: Lerner Research Institute, Global Center for Pathogen & Human Health Research. - URL: https://my.clevelandclinic.org/clinical-trials Entity Type: CollectionPage / MedicalStudy Primary Entity: Clinical Trials Directory Secondary Entities: Institutional Review Board (IRB). - URL: https://my.clevelandclinic.org/florida/locations Entity Type: CollectionPage / Place Primary Entity: Florida Medical Facilities Secondary Entities: Weston Hospital, Indian River Hospital, Martin Health. - URL: https://my.clevelandclinic.org/canada Entity Type: MedicalBusiness / Place Primary Entity: Cleveland Clinic Canada Secondary Entities: Toronto Clinics (Downtown/Midtown). Step 2 — CROSS-PAGE ENTITY RELATIONSHIPS: - PARENT-CHILD HIERARCHY: The core Cleveland Clinic Organization entity serves as the parent to the Education Institute, Lerner Research Institute, Office of Patient Experience, and individual regional entities (Florida, Canada, Nevada, London, Abu Dhabi). - SHARED SERVICE INFRASTRUCTURE: The "MyChart" entity is a cross-cutting SoftwareApplication that facilitates services on the Medical Records page, Virtual Visits page, and Appointment Scheduling page. - BIDIRECTIONAL PROFESSIONAL/PATIENT LINKS: The "Referring a Patient" page (Professional) and "Find a Provider" (Patient) both reference the same "Specialist" entities. The Professionals hub references "Research" and "Education," which are primary entities on their own dedicated hubs. - ENTITY RECURRENCE: The "Specialist/Doctor" entity type is the connective tissue between the "Health Library" (authors/experts), "Podcasts" (guests), "Clinical Trials" (investigators), and "Find a Provider" (service providers). - REGIONAL ENTITY OVERLAP: "Cleveland Clinic Nevada" and "Cleveland Clinic Canada" are defined as both geographic "Places" and functional "MedicalBusinesses" that host specific "Services" (Brain Health, Executive Health) and "Specialists." Step 3 — ENTITY ARCHITECTURE BLUEPRINT: - ROOT IDENTIFIER: A single persistent @id for the Cleveland Clinic parent organization (e.g., `https://my.clevelandclinic.org/#organization`) should be defined on the Home/About pages and referenced in the `publisher` or `parentOrganization` fields of every other page. - DEPARTMENTAL TOPOLOGY: Institutes (Education, Research, Patient Experience) should be defined as `Organization` with a `subOrganization` relationship to the Root Identifier. - SERVICE-TO-LOCATION MAPPING: Each service (e.g., Virtual Second Opinions, Medical Records) should link to the Root Identifier via `provider` and specify `areaServed` or `availableChannel` (Virtual vs. Physical Locations). - PERSON-ENTITY PERSISTENCE: Each doctor/staff member mentioned in the Podcast or Health Library should have a persistent @id (e.g., `https://my.clevelandclinic.org/staff/[name]#person`) that resolves to their profile in the "Find a Provider" directory. - KNOWLEDGE GRAPH TOPOLOGY: The site functions as a centralized Hub-and-Spoke. The Root Organization (Hub) connects to Clinical Services, Research, Education, and Regional Locations (Spokes). Each Spoke further connects to specific MedicalEntities (Conditions, Procedures) and Persons (Providers). Step 4 — CRITICAL GAPS: - ISOLATED EXPERT ENTITIES: Doctors featured in the "Health Essentials Podcast" and "Health Library" lack direct @id connectivity to their professional profiles in the "Find a Provider" tool, creating a broken chain of authority for AI. - SERVICE-LOCATION DISCONNECT: Regional landing pages (Nevada, Canada) list services as text, but these are not programmatically linked to the primary "Services" or "Virtual Visits" entity definitions via `hasOfferCatalog` or `areaServed`. - MISSING HUB ENTITIES: The "Office of Patient Experience" and "Education Institute" function as entity-defining pages but appear isolated from the clinical services they oversee. There is no machine-readable link between "Patient Experience" and the "Ombudsman" services listed on the Help/FAQ pages. - UNIFIED ACTION GAPS: The "Request an Appointment" action is a critical site-wide capability, yet it is often treated as a link rather than a structured `PotentialAction` belonging to the Organization or specific Services. - TRUST ANCHOR FRAGMENTATION: Policy pages (Non-Discrimination, Privacy) are isolated nodes. They should be linked to the Root Organization via `publishingPrinciples` to establish the "broken chain of trust" compliance required by modern AI trust algorithms.
Page Scores
Per-Page Analysis
https://my.clevelandclinic.org/about/contact/phone-directory10 / 100
Current Structured Data
No JSON-LD structured data found on this page.
Page Analysis
This page is a comprehensive 'ContactPage' acting as a central directory for the Cleveland Clinic's global operations. It provides high-utility communication data for diverse user intents: patient appointments, billing, international services, and department-specific helplines. The content establishes a clear hierarchy: the parent Organization (Cleveland Clinic) provides services through regional sub-organizations (Ohio, Florida, Canada, Nevada) and specialized institutes (Children's, Heart, Cancer). From an AI perspective, this page is the authoritative source for the 'contactPoint' properties of the entire enterprise.
Schema Assessment
The 'Extracted Schema' is empty. There is zero structured data on this page. For a high-authority medical institution, this is a catastrophic failure in semantic visibility. AI systems are forced to rely on error-prone text scraping to extract critical contact information, which leads to lower confidence scores in AI-generated answers and voice search results.
Entity Connectivity Gaps
The most significant gap is the total absence of the 'ContactPage' and 'Organization' types. While the text mentions numerous sub-organizations identified in the Site Context (e.g., Cleveland Clinic Florida, Canada, Nevada), there are no @id links to connect these mentions to their respective entity definitions. The phone numbers are presented as flat strings rather than 'ContactPoint' objects with defined 'contactType' (e.g., 'billing', 'emergency', 'reservations') and 'areaServed'. Furthermore, critical services like 'Virtual Second Opinions' and 'Patient Experience/Ombudsman' exist as text only, failing to link back to the 'Service' and 'Department' entities defined on other pages of the site.
AI Retrieval Impact
Because there is no structured data, AI systems (LLMs, Voice Assistants, Knowledge Graphs) cannot verify the 'Chain of Trust' for these phone numbers. If a user asks a voice assistant for the 'Cleveland Clinic Florida appointment number', the assistant must guess based on proximity in text rather than a programmatic declaration. This reduces the site's E-E-A-T signals, as the authoritative contact information for a global leader in healthcare is not machine-verifiable. This results in missed opportunities for 'Zero-click' results and AI Overviews.
Recommendation
Implement a 'ContactPage' schema as the top-level type. Within it, define the primary 'Organization' using the site-wide @id 'https://my.clevelandclinic.org/#organization'. Use an array of 'contactPoint' objects to define every number listed on the page, utilizing 'contactType' to categorize them (e.g., 'Appointment Services', 'Billing Support'). Crucially, use 'areaServed' to distinguish numbers for Ohio, Florida, Canada, and Nevada. Link the 'Ombudsman' section to the 'Office of Patient Experience' entity using its specific @id to maintain cross-page connectivity. This schema is a recommendation and should be reviewed before implementation.
Score Justification
The score of 10 reflects a total absence of structured data on a page that is fundamentally a database of contact information. Without JSON-LD, the page exists as an island of text that AI cannot reliably process for knowledge graph construction.
Recommended Structured Data
{
    "@context": "https://schema.org",
    "@type": "ContactPage",
    "mainEntity": {
        "@type": "MedicalOrganization",
        "@id": "https://my.clevelandclinic.org/#organization",
        "name": "Cleveland Clinic",
        "url": "https://my.clevelandclinic.org/",
        "contactPoint": [
            {
                "@type": "ContactPoint",
                "telephone": "+1-866-320-4573",
                "contactType": "appointments",
                "areaServed": "US-OH"
            },
            {
                "@type": "ContactPoint",
                "telephone": "+1-877-463-2010",
                "contactType": "appointments",
                "areaServed": "US-FL"
            },
            {
                "@type": "ContactPoint",
                "telephone": "+1-888-507-6885",
                "contactType": "appointments",
                "areaServed": "CA"
            },
            {
                "@type": "ContactPoint",
                "telephone": "+1-702-483-6000",
                "contactType": "appointments",
                "areaServed": "US-NV"
            },
            {
                "@type": "ContactPoint",
                "telephone": "+1-216-444-5437",
                "contactType": "appointments",
                "name": "Cleveland Clinic Children's"
            },
            {
                "@type": "ContactPoint",
                "telephone": "+1-216-445-6249",
                "contactType": "billing support"
            },
            {
                "@type": "ContactPoint",
                "telephone": "+1-216-444-6404",
                "contactType": "international support",
                "name": "Global Patient Services"
            },
            {
                "@type": "ContactPoint",
                "telephone": "+1-216-444-2544",
                "contactType": "customer service",
                "name": "Ombudsman/Patient Experience",
                "serviceOperator": {
                    "@id": "https://my.clevelandclinic.org/departments/patient-experience/depts/office-patient-experience#organization"
                }
            }
        ]
    },
    "breadcrumb": {
        "@type": "BreadcrumbList",
        "itemListElement": [
            {
                "@type": "ListItem",
                "position": 1,
                "name": "About",
                "item": "https://my.clevelandclinic.org/about"
            },
            {
                "@type": "ListItem",
                "position": 2,
                "name": "Contact",
                "item": "https://my.clevelandclinic.org/about/contact"
            },
            {
                "@type": "ListItem",
                "position": 3,
                "name": "Phone Directory"
            }
        ]
    }
}
https://my.clevelandclinic.org/about/website10 / 100
Current Structured Data
No JSON-LD structured data found on this page.
Page Analysis
This page serves as the 'Legal and Operational Hub' for the Cleveland Clinic's digital ecosystem. It is a meta-informational WebPage that defines the rules, rights, and editorial standards governing the entire domain. The content identifies several high-value administrative entities: the Cleveland Clinic organization, the WebSite itself, and a collection of critical policies (Non-Discrimination, Patient Rights, Privacy Practices, Editorial Policy, and Terms of Use). Effectively, this page is the 'Trust Anchor' for the site's E-E-A-T signals.
Schema Assessment
The extracted schema is empty. There is no JSON-LD present to define the WebSite, the Organization, or the vital publishing principles mentioned in the content. For an AI agent or a search engine, the relationships between these policies and the brand are purely inferred from text, which is the weakest form of semantic connectivity.
Entity Connectivity Gaps
The most critical gap is the 'Trust Anchor Fragmentation' identified in the Site Context. While the page lists policies like the 'Editorial Policy' and 'Notice of Privacy Practices' as H3 headings, they are not declared as structured CreativeWork entities. Crucially, these are not linked to the parent organization (@id https://my.clevelandclinic.org/#organization) via the publishingPrinciples property. Furthermore, the 'WebSite' entity itself is not defined here, nor is the relationship between the phone directory and this administrative hub established programmatically.
AI Retrieval Impact
Without structured data, AI systems (including LLMs and RAG engines) cannot verify the 'Chain of Trust' for the site's medical content. They cannot programmatically confirm that the Health Library articles are governed by the 'Editorial Policy' mentioned here. This leads to lower retrieval confidence in medical queries and a failure to pass modern AI trust audits that look for explicit publishingPrinciples and organizational accountability.
Recommendation
Transform this page into the 'Semantic Root' for site-wide trust signals. Implement a WebPage schema that defines the Cleveland Clinic as the publisher using a persistent @id. Use the 'publishingPrinciples' property to link to the individual URLs of the Privacy Policy, Terms of Use, and Editorial Policy. Declare a 'WebSite' entity that references the organization as its provider. This will unify the isolated nodes found in the Site Context and provide a machine-readable foundation for the entire domain's authority. This schema is a recommendation and should be reviewed before implementation.
Score Justification
A score of 10 is assigned because the page contains zero structured data despite being the most important page for establishing organizational trust and publishing standards for the entire knowledge graph.
Recommended Structured Data
{
    "@context": "https://schema.org",
    "@graph": [
        {
            "@type": "WebPage",
            "@id": "https://my.clevelandclinic.org/about/website#webpage",
            "url": "https://my.clevelandclinic.org/about/website",
            "name": "About This Website | Cleveland Clinic",
            "description": "Learn more about the Cleveland Clinic website, including terms of use, privacy practices, and editorial policies.",
            "isPartOf": {
                "@id": "https://my.clevelandclinic.org/#website"
            },
            "publisher": {
                "@id": "https://my.clevelandclinic.org/#organization"
            },
            "mainEntity": {
                "@id": "https://my.clevelandclinic.org/#website"
            }
        },
        {
            "@type": "WebSite",
            "@id": "https://my.clevelandclinic.org/#website",
            "url": "https://my.clevelandclinic.org/",
            "name": "Cleveland Clinic",
            "publisher": {
                "@id": "https://my.clevelandclinic.org/#organization"
            }
        },
        {
            "@type": "Organization",
            "@id": "https://my.clevelandclinic.org/#organization",
            "name": "Cleveland Clinic",
            "url": "https://my.clevelandclinic.org/",
            "logo": "https://my.clevelandclinic.org/assets/img/logo.png",
            "contactPoint": {
                "@type": "ContactPoint",
                "telephone": "+1-216-444-2200",
                "contactType": "customer service"
            },
            "publishingPrinciples": [
                {
                    "@type": "CreativeWork",
                    "name": "Editorial Policy",
                    "url": "https://my.clevelandclinic.org/about/website/editorial-policy"
                },
                {
                    "@type": "CreativeWork",
                    "name": "Privacy & Security",
                    "url": "https://my.clevelandclinic.org/about/website/privacy-security"
                },
                {
                    "@type": "CreativeWork",
                    "name": "Non-Discrimination Notice",
                    "url": "https://my.clevelandclinic.org/about/website/non-discrimination-notice"
                },
                {
                    "@type": "CreativeWork",
                    "name": "Terms of Use",
                    "url": "https://my.clevelandclinic.org/about/website/terms-of-use"
                }
            ]
        },
        {
            "@type": "ContactPage",
            "@id": "https://my.clevelandclinic.org/about/contact/phone-directory#webpage",
            "url": "https://my.clevelandclinic.org/about/contact/phone-directory"
        }
    ]
}
https://my.clevelandclinic.org/patients1 / 100
Current Structured Data
No JSON-LD structured data found on this page.
Page Analysis
This page functions as a critical 'Service Hub' or 'Patient Directory' for the Cleveland Clinic. It is the primary entry point for non-clinical patient interactions including billing, medical records access, travel logistics, and appointment scheduling. Content-wise, it represents a 'Service' entity provided by a 'MedicalOrganization', featuring an 'OfferCatalog' of various administrative and support services. It also includes social proof in the form of 'Patient Stories' (biographical articles) and critical 'PotentialActions' (ScheduleAction, PayAction).
Schema Assessment
The extracted schema is an empty array. There is zero structured data present on this page. This is a total failure of semantic representation for one of the most important navigational hubs on the domain. The page exists only as a visual document for humans, while remaining a 'black box' for AI agents and knowledge graph extractors.
Entity Connectivity Gaps
1. Primary Entity Definition: No 'WebPage' or 'Service' entity is declared. 2. Root Connectivity: There is no reference to the Cleveland Clinic parent organization @id (https://my.clevelandclinic.org/#organization), severing this hub from the site's authority. 3. Service Decomposition: Entities like 'Medical Records' (Service), 'Billing & Insurance' (FinancialService), and 'Parking/Lodging' (Accommodation) are present in text but absent in data. 4. Missing Actions: The 'Request Your Medical Records' and 'Pay Your Bill' links should be structured as 'PotentialAction' types. 5. Social Proof: The 'Patient Stories' section lacks Article or Review markup, making these authority-building narratives invisible to AI E-E-A-T evaluations.
AI Retrieval Impact
AI systems and LLMs cannot programmatically determine what services Cleveland Clinic offers to patients from this page. Retrieval-Augmented Generation (RAG) systems will struggle to verify 'Accepted Insurance' or 'Appointment Checklist' as structured facts, likely resulting in hallucinations or lower confidence scores. The 'Chain of Trust' is broken because there is no machine-readable link between these services and the verified Organization entity.
Recommendation
Implement a high-fidelity WebPage schema that defines the 'Patient and Visitor Services' as a central 'Service' entity. This entity must use the Cleveland Clinic @id as the 'provider'. Use an 'OfferCatalog' to list the specific sub-services (Billing, Records, Travel) and link them to their respective deep-pages identified in the Site Context. Crucially, add 'potentialAction' markup for 'ScheduleAction' (appointments) and 'PayAction' (billing) to enable direct AI agent interaction. Finally, wrap Patient Stories in 'ItemList' of 'Article' entities to signal real-world expertise and outcomes.
Score Justification
A score of 1 is assigned because the page contains no structured data whatsoever. Despite the rich content and high authority of the domain, the lack of any JSON-LD means the page is semantically non-existent to AI crawlers.
Recommended Structured Data
{
    "@context": "https://schema.org",
    "@graph": [
        {
            "@type": "WebPage",
            "@id": "https://my.clevelandclinic.org/patients#webpage",
            "url": "https://my.clevelandclinic.org/patients",
            "name": "Patients and Visitors | Cleveland Clinic",
            "description": "Administrative and support hub for Cleveland Clinic patients, providing access to billing, medical records, and travel assistance.",
            "isPartOf": {
                "@id": "https://my.clevelandclinic.org/#website"
            },
            "publisher": {
                "@id": "https://my.clevelandclinic.org/#organization"
            },
            "mainEntity": {
                "@type": "Service",
                "@id": "https://my.clevelandclinic.org/patients#service",
                "name": "Patient and Visitor Services",
                "provider": {
                    "@id": "https://my.clevelandclinic.org/#organization"
                },
                "hasOfferCatalog": {
                    "@type": "OfferCatalog",
                    "name": "Patient Resources",
                    "itemListElement": [
                        {
                            "@type": "Offer",
                            "itemOffered": {
                                "@type": "Service",
                                "name": "Medical Records Request",
                                "url": "https://my.clevelandclinic.org/patients/information/medical-records"
                            }
                        },
                        {
                            "@type": "Offer",
                            "itemOffered": {
                                "@type": "FinancialService",
                                "name": "Billing and Insurance",
                                "url": "https://my.clevelandclinic.org/patients/billing-finance"
                            }
                        },
                        {
                            "@type": "Offer",
                            "itemOffered": {
                                "@type": "Service",
                                "name": "Travel and Lodging Assistance",
                                "url": "https://my.clevelandclinic.org/patients/travel"
                            }
                        }
                    ]
                }
            },
            "potentialAction": [
                {
                    "@type": "ScheduleAction",
                    "target": "https://my.clevelandclinic.org/webappointment"
                },
                {
                    "@type": "PayAction",
                    "target": "https://my.clevelandclinic.org/patients/billing-finance"
                }
            ]
        },
        {
            "@type": "MedicalOrganization",
            "@id": "https://my.clevelandclinic.org/#organization",
            "name": "Cleveland Clinic",
            "url": "https://my.clevelandclinic.org/",
            "logo": "https://my.clevelandclinic.org/assets/img/logo.png",
            "telephone": "216.444.2200"
        }
    ]
}
https://my.clevelandclinic.org/patients/information/medical-records5 / 100
Current Structured Data
No JSON-LD structured data found on this page.
Page Analysis
This is a Service and Information page centered on 'Medical Records' management. The content defines a critical workflow for patients to access their health data. The primary entity is the Health Information Management (HIM) department of Cleveland Clinic. Secondary entities include MyChart (SoftwareApplication), Epic Systems Corporation (Organization), and various regional medical facilities. The page functions as a functional guide/how-to for requesting records via electronic, fax, or mail channels, and references legal entities like the Health Information Exchange (HIE).
Schema Assessment
The extracted schema is empty ([]). There is a total absence of structured data. Even basic breadcrumb or organization schema is missing. From a machine-readability standpoint, this page is an invisible node in a knowledge graph, relying entirely on unstructured text parsing which is prone to hallucination or low-confidence extraction by AI agents.
Entity Connectivity Gaps
The page content demands several critical entity definitions that are currently absent: 1. A 'Service' entity for Medical Records Requests. 2. A 'MedicalOrganization' or 'Department' entity for 'Health Information Management' with its specific contact point (216.444.5580). 3. A 'SoftwareApplication' entity for 'MyChart' to establish the relationship between the tool and the service. 4. Missing '@id' connectivity to the Cleveland Clinic parent organization defined in the Site Context. 5. No 'HowTo' or 'ContactPoint' schema for the specific instructions on requesting records. 6. The 'Notice of Privacy Practices' is a critical trust signal mentioned in text but not linked as a 'publishingPrinciples' or 'policy' entity.
AI Retrieval Impact
Because there is zero structured data, AI systems and LLMs cannot verify this as the authoritative source for Cleveland Clinic medical records through programmatic means. The relationship between 'MyChart' and 'Medical Records' remains an unverified text association rather than a hard-coded functional link. Retrieval systems (like SGE or Claude) may fail to accurately extract the specific processing times (7-10 days) or fees as 'facts', instead treating them as 'unstructured claims'. The 'Chain of Trust' to the parent organization is completely broken.
Recommendation
Implement a high-fidelity 'MedicalWebPage' schema that contains a 'Service' entity. This service must list 'Cleveland Clinic' as the provider via the site-wide @id 'https://my.clevelandclinic.org/#organization'. Define the 'Health Information Management' department as the 'serviceOperator'. Explicitly link 'MyChart' as a related 'SoftwareApplication'. Use 'ContactPoint' for the phone and fax numbers to ensure AI-driven voice assistants can accurately provide contact info. Add a 'HowTo' property to structure the multi-step request process. [Disclaimer: this schema is a recommendation and should be reviewed before implementation]
Score Justification
A score of 5 is assigned because the page provides zero structured data. It fails to meet even the most basic standards of AI-readiness or semantic connectivity, despite containing high-stakes medical and legal information.
Recommended Structured Data
{
    "@context": "https://schema.org",
    "@type": "MedicalWebPage",
    "@id": "https://my.clevelandclinic.org/patients/information/medical-records#webpage",
    "url": "https://my.clevelandclinic.org/patients/information/medical-records",
    "name": "Medical Records Request and Access",
    "description": "Learn how to request and access your medical records at Cleveland Clinic via MyChart, mail, or fax.",
    "mainEntity": {
        "@type": "Service",
        "@id": "https://my.clevelandclinic.org/patients/information/medical-records#service",
        "name": "Medical Records Request Service",
        "serviceType": "Health Information Management",
        "provider": {
            "@id": "https://my.clevelandclinic.org/#organization"
        },
        "areaServed": "US",
        "hasOfferCatalog": {
            "@type": "OfferCatalog",
            "name": "Medical Record Services",
            "itemListElement": [
                {
                    "@type": "Offer",
                    "itemOffered": {
                        "@type": "Service",
                        "name": "Electronic Health Information Export"
                    }
                },
                {
                    "@type": "Offer",
                    "itemOffered": {
                        "@type": "Service",
                        "name": "Radiology Image Copy Request"
                    }
                }
            ]
        },
        "availableChannel": {
            "@type": "ServiceChannel",
            "name": "MyChart Digital Access",
            "serviceUrl": "https://my.clevelandclinic.org/online-services/mychart",
            "providesService": {
                "@type": "SoftwareApplication",
                "name": "MyChart",
                "operatingSystem": "Web, iOS, Android",
                "publisher": {
                    "@type": "Organization",
                    "name": "Epic Systems Corporation"
                }
            }
        }
    },
    "provider": {
        "@type": "MedicalOrganization",
        "name": "Health Information Management",
        "parentOrganization": {
            "@id": "https://my.clevelandclinic.org/#organization"
        },
        "contactPoint": {
            "@type": "ContactPoint",
            "telephone": "+1-216-444-5580",
            "contactType": "customer service",
            "hoursAvailable": {
                "@type": "OpeningHoursSpecification",
                "dayOfWeek": [
                    "Monday",
                    "Tuesday",
                    "Wednesday",
                    "Thursday",
                    "Friday"
                ],
                "opens": "08:00",
                "closes": "16:30"
            },
            "availableLanguage": "English"
        },
        "address": {
            "@type": "PostalAddress",
            "streetAddress": "9500 Euclid Avenue",
            "addressLocality": "Cleveland",
            "addressRegion": "OH",
            "postalCode": "44195",
            "addressCountry": "US"
        }
    },
    "step": [
        {
            "@type": "HowToStep",
            "text": "Log in to MyChart and navigate to Document Center."
        },
        {
            "@type": "HowToStep",
            "text": "Complete the Release of Information Authorization Form."
        },
        {
            "@type": "HowToStep",
            "text": "Submit the request electronically or via fax to 216.587.8043."
        }
    ]
}
https://my.clevelandclinic.org/patients/billing-finance/comprehensive-hospital-charges15 / 100
Current Structured Data
No JSON-LD structured data found on this page.
Page Analysis
The page serves as a high-stakes regulatory disclosure hub for hospital pricing transparency, compliant with CMS regulations. It functions as a 'Service' and 'Directory' hybrid, providing machine-readable datasets (standard charges) and interactive tools (cost estimator) for multiple regional medical facilities under the Cleveland Clinic umbrella. Primary entities include the parent Organization (Cleveland Clinic), numerous sub-organizations (regional hospitals like Akron General, Avon, and Florida Weston), and the 'PriceSpecification' datasets for each. Secondary entities include CMS (regulatory body) and Florida Health Finder (third-party verification service).
Schema Assessment
The page currently lacks any JSON-LD structured data. Despite containing critical financial and regulatory information that requires high trust (E-E-A-T), the page is a semantic void for AI. There are no @type declarations for the services, no @id links to the regional locations mentioned, and no machine-readable connection to the parent organization identified in the Site Context.
Entity Connectivity Gaps
The most critical gap is the 'Broken Chain of Trust' between the regulatory requirement (CMS) and the clinical providers. 1. The page fails to define itself as a 'Service' or 'WebPage' with a 'mainEntity' of 'FinancialProduct' or 'Service'. 2. There is no @id linking the regional hospitals (e.g., Akron General, Fairview Hospital) to their established entities in the site-wide graph. 3. The charge lists for the 20+ hospitals are provided as flat text links rather than 'DataDownload' or 'PriceSpecification' objects. 4. The 'PotentialAction' for the Cost Estimator Tool and 'Schedule Customer Service Callback' are not programmatically declared, making these utility-heavy features invisible to AI agents.
AI Retrieval Impact
AI retrieval systems (SGE, GPT-4o, Claude) cannot programmatically verify that these are the official CMS-mandated charge lists. Because the entity relationships are not declared, an AI agent cannot confidently answer 'What is the price list for Cleveland Clinic Lodi Hospital?' without manual scraping, which reduces retrieval confidence. Furthermore, the lack of 'reviewedBy' or 'dateModified' schema for pricing data — which is time-sensitive — weakens the content's authority in health-finance-related queries.
Recommendation
Implement a robust Service-to-Location graph. 1. Define the page as a 'WebPage' with a 'Service' mainEntity. 2. Use the Root Identifier (https://my.clevelandclinic.org/#organization) as the 'provider'. 3. For each hospital listed, create a 'subOrganization' or 'provider' entry using its specific @id (e.g., https://my.clevelandclinic.org/locations/ohio-locations#avon) and link it to a 'PriceSpecification' or 'DataDownload' entity. 4. Explicitly define the 'Cost Estimator' as a 'PotentialAction' with an 'EntryPoint' URL. 5. Include 'publishingPrinciples' linking to the Non-Discrimination and Privacy policies identified in the Site Context to establish a formal trust anchor. Disclaimer: this schema is a recommendation and should be reviewed before implementation.
Score Justification
The score of 15 is assigned because the page contains zero JSON-LD. While the content is high-quality and structured for humans, it is entirely invisible to the semantic web. In a 'Your Money Your Life' (YMYL) category like hospital billing, the absence of entity connectivity is a critical failure for AI readiness.
Recommended Structured Data
{
    "@context": "https://schema.org",
    "@type": "WebPage",
    "@id": "https://my.clevelandclinic.org/patients/billing-finance/comprehensive-hospital-charges#webpage",
    "url": "https://my.clevelandclinic.org/patients/billing-finance/comprehensive-hospital-charges",
    "name": "Comprehensive Hospital Charges | Cleveland Clinic",
    "description": "Access comprehensive hospital charges, payer-specific negotiated rates, and cost estimator tools for Cleveland Clinic facilities.",
    "isPartOf": {
        "@id": "https://my.clevelandclinic.org/#website"
    },
    "about": {
        "@id": "https://my.clevelandclinic.org/#organization"
    },
    "mainEntity": {
        "@type": "Service",
        "@id": "https://my.clevelandclinic.org/patients/billing-finance/comprehensive-hospital-charges#billingService",
        "name": "Hospital Price Transparency and Billing Service",
        "provider": {
            "@id": "https://my.clevelandclinic.org/#organization"
        },
        "areaServed": "US",
        "serviceType": "Financial Transparency",
        "potentialAction": [
            {
                "@type": "SearchAction",
                "name": "Cost Estimator Tool",
                "target": "https://my.clevelandclinic.org/patients/billing-finance/cost-estimator"
            },
            {
                "@type": "CommunicateAction",
                "name": "Schedule Customer Service Callback",
                "target": "https://my.clevelandclinic.org/patients/billing-finance/comprehensive-hospital-charges"
            }
        ],
        "hasOfferCatalog": {
            "@type": "OfferCatalog",
            "name": "Hospital Charge Lists",
            "itemListElement": [
                {
                    "@type": "ListItem",
                    "position": 1,
                    "item": {
                        "@type": "MedicalOrganization",
                        "@id": "https://my.clevelandclinic.org/locations#main-campus",
                        "name": "Cleveland Clinic Main Campus",
                        "subjectOf": {
                            "@type": "DataDownload",
                            "name": "Standard Charges CSV",
                            "encodingFormat": "text/csv"
                        }
                    }
                },
                {
                    "@type": "ListItem",
                    "position": 2,
                    "item": {
                        "@type": "MedicalOrganization",
                        "@id": "https://my.clevelandclinic.org/locations/florida#weston-hospital",
                        "name": "Cleveland Clinic Florida Weston Hospital"
                    }
                }
            ]
        }
    },
    "publisher": {
        "@id": "https://my.clevelandclinic.org/#organization"
    },
    "dateModified": "2024-06-28"
}
https://my.clevelandclinic.org/health10 / 100
Current Structured Data
No JSON-LD structured data found on this page.
Page Analysis
This page is the central hub for the Cleveland Clinic 'Health Library.' It functions as a CollectionPage and a navigational entry point (Directory) for medical knowledge. The content establishes several high-value entity relationships: a parent Organization (Cleveland Clinic) hosting a Medical Archive (Health Library) which contains distinct categories like Diseases & Conditions, Procedures, and Symptoms. It also cross-promotes secondary entities identified in the site context, such as the 'Health Essentials Podcast' and the 'Health Essentials Newsletter'.
Schema Assessment
The extracted schema is empty. There is zero structured data present on a page that serves as the gateway to the site's most authoritative content. This creates a total semantic vacuum for AI crawlers.
Entity Connectivity Gaps
The most critical gap is the lack of a 'CollectionPage' or 'MedicalWebPage' declaration. Because the schema is empty, the 'Health Library' does not exist as a machine-readable entity. There is no 'SearchAction' defined for the prominent search bar, meaning AI systems cannot programmatically understand how to query this database. Furthermore, there is no connection to the Root Organization (@id https://my.clevelandclinic.org/#organization), and the relationships to 'Health Essentials' (Podcast/Newsletter) are lost as they are not linked via 'mentions' or 'relatedLink' properties. The categories (Body Systems, Procedures, etc.) are treated as flat text links rather than defined 'ItemList' or 'Taxonomy' entities.
AI Retrieval Impact
For AI retrieval and LLMs, this page is a 'dead end' in the knowledge graph. While a human sees a library, an AI sees an unorganized list of links. The authority (E-E-A-T) of the Cleveland Clinic does not programmatically flow into the Health Library because the 'publisher' relationship is not declared. This results in lower retrieval confidence for 'Cleveland Clinic' as a source when LLMs search for medical information, as the connection between the brand and its educational archive is not explicitly mapped.
Recommendation
Implement a 'CollectionPage' as the primary type, linked to the global Organization @id. Define the Health Library as a 'CreativeWorkSeries' or 'ArchiveComponent'. Add a 'SearchAction' to enable programmatic entry. Explicitly link the 'Health Essentials Podcast' and 'Newsletter' using the persistent @ids identified in the Site Context. Use 'hasPart' to define the major medical categories (Procedures, Symptoms, etc.) to create a hierarchical graph. This schema is a recommendation and should be reviewed before implementation.
Score Justification
A score of 10 is assigned because the page contains zero JSON-LD structured data. On a page that acts as a critical navigational hub for thousands of medical articles, the absence of schema prevents any automated entity connectivity or chain-of-trust verification.
Recommended Structured Data
{
    "@context": "https://schema.org",
    "@type": "CollectionPage",
    "@id": "https://my.clevelandclinic.org/health#webpage",
    "url": "https://my.clevelandclinic.org/health",
    "name": "Cleveland Clinic Health Library",
    "description": "Find answers to your health questions from experts you can trust.",
    "isPartOf": {
        "@id": "https://my.clevelandclinic.org/#website"
    },
    "publisher": {
        "@id": "https://my.clevelandclinic.org/#organization"
    },
    "mainEntity": {
        "@type": "CreativeWorkSeries",
        "@id": "https://my.clevelandclinic.org/health#library",
        "name": "Health Library",
        "about": {
            "@type": "MedicalThing",
            "name": "Health and Wellness"
        },
        "author": {
            "@id": "https://my.clevelandclinic.org/#organization"
        }
    },
    "potentialAction": {
        "@type": "SearchAction",
        "target": {
            "@type": "EntryPoint",
            "urlTemplate": "https://my.clevelandclinic.org/health/search?q={search_term_string}"
        },
        "query-input": "required name=search_term_string"
    },
    "hasPart": [
        {
            "@type": "ItemList",
            "name": "Health Categories",
            "itemListElement": [
                {
                    "@type": "ListItem",
                    "position": 1,
                    "name": "Body Systems & Organs"
                },
                {
                    "@type": "ListItem",
                    "position": 2,
                    "name": "Diseases & Conditions"
                },
                {
                    "@type": "ListItem",
                    "position": 3,
                    "name": "Medical Treatments"
                },
                {
                    "@type": "ListItem",
                    "position": 4,
                    "name": "Procedures"
                },
                {
                    "@type": "ListItem",
                    "position": 5,
                    "name": "Drugs, Devices & Supplements"
                },
                {
                    "@type": "ListItem",
                    "position": 6,
                    "name": "Diagnostics & Testing"
                },
                {
                    "@type": "ListItem",
                    "position": 7,
                    "name": "Symptoms"
                }
            ]
        }
    ],
    "mentions": [
        {
            "@id": "https://my.clevelandclinic.org/podcasts/health-essentials#podcast"
        },
        {
            "@id": "https://my.clevelandclinic.org/health-essentials-newsletter#publication"
        }
    ]
}
https://my.clevelandclinic.org/health/procedures10 / 100
Current Structured Data
No JSON-LD structured data found on this page.
Page Analysis
This page functions as a central directory and navigational hub for the 'Medical Procedures' segment of the Cleveland Clinic Health Library. It is a 'CollectionPage' that serves as an A-Z index for consumers seeking information on specific medical treatments and surgeries. The page includes search and filtering capabilities (by letter, body system, or category) and provides pathways to other Health Library hubs like Symptoms and Diseases & Conditions. The primary entity is the Procedures Index itself, which acts as a gateway to thousands of individual MedicalProcedure entities.
Schema Assessment
The extracted schema is entirely empty ([ ]). There is no JSON-LD providing any semantic context to AI agents. The page fails to identify itself as a CollectionPage, fails to link to the parent Organization, and fails to provide a machine-readable list of the procedures it indexes. From an AI perspective, this page is a 'black box' of unstructured text and scripts rather than a structured node in a knowledge graph.
Entity Connectivity Gaps
1. Missing Page-Level Type: The page should be defined as a 'CollectionPage' and 'MedicalWebPage'. 2. Missing Entity Connection: There is no reference to the Cleveland Clinic Organization @id (https://my.clevelandclinic.org/#organization) defined in the Site Context. 3. Missing ItemList: The A-Z directory and categories (Body Systems, etc.) are not represented as an 'ItemList', preventing LLMs from understanding the scope of the index. 4. Missing SearchAction: The internal search functionality is not declared, missing an opportunity for 'Deep Rank' or SGE interaction. 5. Missing breadcrumbs: No BreadcrumbList exists to show the hierarchy (Home > Health Library > Procedures).
AI Retrieval Impact
Because there is zero structured data, AI systems cannot verify this page as the authoritative index for Cleveland Clinic procedures. It relies entirely on NLP for extraction, which is less reliable than structured entity mapping. The 'chain of trust' identified in the Site Context is completely broken here; there is no programmatic link between these procedures and the medical professionals or the parent organization that validates them. This results in lower retrieval confidence for 'Cleveland Clinic procedures' queries in SGE and AI-powered search engines.
Recommendation
Immediately implement a CollectionPage schema that defines the page's purpose. The most critical fix is establishing the @id link to the parent Organization and the Health Library hub. Use an ItemList to define the main categories of procedures (Diagnostics, Testing, etc.) and include a SearchAction for the 'Search our topics' feature. This will transition the page from a flat UI component to a structured 'hub' node in the site's knowledge graph. Note: this schema is a recommendation and should be reviewed before implementation.
Score Justification
A score of 10 is assigned because the page contains absolutely no structured data. While the content is high-quality and well-organized for humans, it is invisible to semantic crawlers and knowledge graph builders. It fails every metric of Model Context Optimization.
Recommended Structured Data
{
    "@context": "https://schema.org",
    "@graph": [
        {
            "@type": "CollectionPage",
            "@id": "https://my.clevelandclinic.org/health/procedures#webpage",
            "url": "https://my.clevelandclinic.org/health/procedures",
            "name": "Medical Procedures A-Z Index",
            "description": "Browse an A to Z list of medical procedures from Cleveland Clinic's Health Library.",
            "isPartOf": {
                "@id": "https://my.clevelandclinic.org/#website"
            },
            "publisher": {
                "@id": "https://my.clevelandclinic.org/#organization"
            },
            "about": {
                "@type": "MedicalProcedure",
                "name": "Medical Procedures"
            },
            "mainEntity": {
                "@type": "ItemList",
                "name": "Procedure Categories",
                "itemListElement": [
                    {
                        "@type": "ListItem",
                        "position": 1,
                        "name": "Diagnostics & Testing",
                        "url": "https://my.clevelandclinic.org/health/diagnostics"
                    },
                    {
                        "@type": "ListItem",
                        "position": 2,
                        "name": "Medical Treatments",
                        "url": "https://my.clevelandclinic.org/health/treatments"
                    }
                ]
            },
            "potentialAction": {
                "@type": "SearchAction",
                "target": {
                    "@type": "EntryPoint",
                    "urlTemplate": "https://my.clevelandclinic.org/health/procedures?q={search_term_string}"
                },
                "query-input": "required name=search_term_string"
            }
        },
        {
            "@type": "Organization",
            "@id": "https://my.clevelandclinic.org/#organization",
            "name": "Cleveland Clinic",
            "url": "https://my.clevelandclinic.org/"
        },
        {
            "@type": "BreadcrumbList",
            "@id": "https://my.clevelandclinic.org/health/procedures#breadcrumb",
            "itemListElement": [
                {
                    "@type": "ListItem",
                    "position": 1,
                    "name": "Home",
                    "item": "https://my.clevelandclinic.org/"
                },
                {
                    "@type": "ListItem",
                    "position": 2,
                    "name": "Health Library",
                    "item": "https://my.clevelandclinic.org/health"
                },
                {
                    "@type": "ListItem",
                    "position": 3,
                    "name": "Procedures",
                    "item": "https://my.clevelandclinic.org/health/procedures"
                }
            ]
        }
    ]
}
https://my.clevelandclinic.org/health/symptoms15 / 100
Current Structured Data
No JSON-LD structured data found on this page.
Page Analysis
The page is a high-level directory and navigation hub for medical symptoms within the Cleveland Clinic Health Library. Functionally, it is a CollectionPage designed to aggregate and categorize individual MedicalSymptom and MedicalCondition entities. The content includes a complex search and filtering interface (A-Z, Body Systems, etc.) and references 'Health Educators' as a support service. The primary entity is the Symptoms Index itself, which serves as a gateway to thousands of specific medical articles.
Schema Assessment
The extracted schema is empty. This is a critical failure for a major medical institution's directory page. There is no machine-readable declaration of the page's purpose, the organization behind it, or the search capabilities offered. For AI systems, this page appears as a collection of unstructured text and scripts rather than a structured knowledge graph node.
Entity Connectivity Gaps
The most significant gap is the lack of a CollectionPage or MedicalWebPage declaration. Crucially, the 'Search our topics' functionality is not defined as a SearchAction, preventing LLMs from understanding how to query the library directly. There is no @id connectivity to the 'Cleveland Clinic' parent organization identified in the Site Context. Furthermore, the 'Health Educators' mentioned in the content are not defined as a 'provider' or 'contactPoint'. The relationships between 'Symptoms' and related categories like 'Procedures' or 'Drugs' are purely visual and lack semantic linking via hasPart or relatedTopic properties.
AI Retrieval Impact
AI systems and LLMs cannot programmatically identify this page as the authoritative index for symptoms. Without a structured ItemList or SearchAction, the 'A-Z' directory remains opaque to retrieval-augmented generation (RAG) systems that rely on schema to prioritize authoritative sources. The absence of a publisher link to the Cleveland Clinic root @id breaks the chain of trust, meaning the E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness) of the parent organization is not programmatically inherited by this directory or its subsequent links.
Recommendation
Immediately implement a CollectionPage schema that identifies the 'Cleveland Clinic Health Library Symptoms Index' as the primary entity. Use a @graph structure to link this page to the site's root Organization @id (https://my.clevelandclinic.org/#organization). Include a SearchAction property to define the symptom search tool. Declare the 'Health Educator' service as a ContactPoint with a specific serviceType. Finally, ensure 'lastReviewed' and 'reviewedBy' properties are present to provide the necessary medical trust signals for AI verification. This schema is a recommendation and should be reviewed before implementation.
Score Justification
A score of 15 is assigned because the page has zero structured data. Despite being a critical entry point for medical knowledge, it provides no semantic guidance to AI crawlers. It is an isolated node that fails to leverage the authority of the Cleveland Clinic brand or its vast health library ecosystem.
Recommended Structured Data
{
    "@context": "https://schema.org",
    "@graph": [
        {
            "@type": "CollectionPage",
            "@id": "https://my.clevelandclinic.org/health/symptoms",
            "url": "https://my.clevelandclinic.org/health/symptoms",
            "name": "Medical Symptoms Directory",
            "isPartOf": {
                "@id": "https://my.clevelandclinic.org/#website"
            },
            "publisher": {
                "@id": "https://my.clevelandclinic.org/#organization"
            },
            "about": {
                "@type": "MedicalSymptom",
                "name": "Medical Symptoms"
            },
            "description": "An A to Z list of medical symptoms and health information reviewed by Cleveland Clinic experts.",
            "potentialAction": {
                "@type": "SearchAction",
                "target": {
                    "@type": "EntryPoint",
                    "urlTemplate": "https://my.clevelandclinic.org/health/symptoms?q={search_term_string}"
                },
                "query-input": "required name=search_term_string"
            }
        },
        {
            "@type": "MedicalWebPage",
            "@id": "https://my.clevelandclinic.org/health/symptoms#medicalwebpage",
            "mainEntityOfPage": {
                "@id": "https://my.clevelandclinic.org/health/symptoms"
            },
            "lastReviewed": "2024-01-01",
            "reviewedBy": {
                "@id": "https://my.clevelandclinic.org/#organization"
            },
            "provider": {
                "@type": "MedicalOrganization",
                "name": "Cleveland Clinic Health Educators",
                "parentOrganization": {
                    "@id": "https://my.clevelandclinic.org/#organization"
                }
            }
        },
        {
            "@type": "Organization",
            "@id": "https://my.clevelandclinic.org/#organization",
            "name": "Cleveland Clinic",
            "url": "https://my.clevelandclinic.org/",
            "logo": "https://my.clevelandclinic.org/assets/img/logo.png"
        }
    ]
}
https://my.clevelandclinic.org/departments/education10 / 100
Current Structured Data
No JSON-LD structured data found on this page.
Page Analysis
The page serves as the central hub for the 'Education Institute' at Cleveland Clinic. Based on the content, this is an EducationalOrganization and a Department within a larger MedicalOrganization. The primary entity is the Education Institute itself. Secondary entities include the Cleveland Clinic (Parent Organization), the Center for Youth and College Education, and various specific training programs such as CME Certification, Global Executive Education, and Graduate Medical Education (GME). The content implies a hierarchical relationship where the Education Institute oversees three functional units: Student & Faculty Development, Professional Development & Knowledge Resources, and Technical & Education Support.
Schema Assessment
The extracted schema is empty ([ ]). There is no JSON-LD present to define the entity, its parent organization, its physical location, or its specific service offerings. From an AI and Knowledge Graph perspective, this page is a 'dark node'—it exists as crawlable text but lacks the programmatic instructions required for high-confidence entity extraction or relationship mapping.
Entity Connectivity Gaps
1. Primary Entity Missing: No EducationalOrganization or MedicalBusiness type is declared. 2. Parent Relationship Gap: There is no machine-readable link to the Cleveland Clinic root organization (@id: https://my.clevelandclinic.org/#organization), which is identified in the Site Context as the parent. 3. Sub-Organization Gaps: The 'Center for Youth and College Education' and other listed centers are mentioned in text but not defined as subOrganization entities. 4. Service Gaps: Critical services like 'CME Certification' and 'Global Executive Education' are presented as text links rather than structured Service or Course entities. 5. Person Connectivity: While the page mentions training 'physicians' and 'caregivers,' there are no links to the 'Provider' or 'Person' entities identified in the Site Context staff directory. 6. Action Gaps: The 'GME Training Verification' and 'Contact Us' functions are not defined as PotentialAction types.
AI Retrieval Impact
AI systems and LLMs cannot verify the Education Institute's relationship to the Cleveland Clinic brand with 100% confidence, relying instead on probabilistic NLP. The 'broken chain of trust' identified in the Site Context is prevalent here; the expertise of the Educational Institute does not programmatically flow to the clinical departments it supports. This reduces the site's E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness) score in AI retrieval systems, as the educational authority of the institution is not anchored to its organizational identity.
Recommendation
1. Implement an EducationalOrganization schema for the Education Institute. 2. Use a persistent @id (e.g., https://my.clevelandclinic.org/departments/education#organization) to allow other pages to reference this entity. 3. Explicitly link this entity to the parent Cleveland Clinic organization using the 'parentOrganization' property and the root @id. 4. Define the various units (Student & Faculty Development, etc.) as 'subOrganization' nodes. 5. Map 'CME Certification' and 'Executive Education' as 'Service' entities with the Education Institute as the 'provider'. 6. Add a ContactPoint for the Education Institute to facilitate direct AI-driven user inquiries. This schema is a recommendation and should be reviewed before implementation.
Score Justification
The score of 10 reflects a total absence of structured data on a high-value institutional page. While the text is rich, the lack of any JSON-LD means the entity is invisible to structured knowledge graph builders.
Recommended Structured Data
{
    "@context": "https://schema.org",
    "@graph": [
        {
            "@type": "EducationalOrganization",
            "@id": "https://my.clevelandclinic.org/departments/education#organization",
            "name": "Cleveland Clinic Education Institute",
            "url": "https://my.clevelandclinic.org/departments/education",
            "description": "The Education Institute oversees training and education programs offered to a global audience of healthcare professionals, including physicians, medical students, and residents.",
            "parentOrganization": {
                "@id": "https://my.clevelandclinic.org/#organization"
            },
            "subOrganization": [
                {
                    "@type": "EducationalOrganization",
                    "name": "Center for Youth and College Education",
                    "url": "https://my.clevelandclinic.org/departments/education/centers/youth-college-education"
                }
            ],
            "hasOfferCatalog": {
                "@type": "OfferCatalog",
                "name": "Educational Services",
                "itemListElement": [
                    {
                        "@type": "Service",
                        "name": "CME Certification",
                        "description": "Educational design consulting and certification."
                    },
                    {
                        "@type": "Service",
                        "name": "Global Executive Education",
                        "description": "Executive education for healthcare organizations."
                    },
                    {
                        "@type": "Service",
                        "name": "GME Training Verification"
                    }
                ]
            },
            "contactPoint": {
                "@type": "ContactPoint",
                "contactType": "General Information",
                "url": "https://my.clevelandclinic.org/departments/education#contact"
            }
        },
        {
            "@type": "WebPage",
            "@id": "https://my.clevelandclinic.org/departments/education",
            "url": "https://my.clevelandclinic.org/departments/education",
            "name": "Education Institute | Cleveland Clinic",
            "isPartOf": {
                "@id": "https://my.clevelandclinic.org/#website"
            },
            "about": {
                "@id": "https://my.clevelandclinic.org/departments/education#organization"
            }
        }
    ]
}
https://my.clevelandclinic.org/departments/patient-experience/depts/office-patient-experience1 / 100
Current Structured Data
No JSON-LD structured data found on this page.
Page Analysis
This page represents a high-level administrative department within the Cleveland Clinic health system: the Office of Patient Experience. It serves as a strategic hub for patient-centered initiatives, including safety, quality, and satisfaction programs. The content identifies the office as an advisory resource, mentions the Chief Experience Officer role, and introduces critical sub-entities such as the Ombudsman Office and Patient Experience Measurement programs. It also references secondary media assets like the 'Studies in Empathy' podcast and service-oriented tools like the Caregiver Celebrations system.
Schema Assessment
The extracted schema is entirely empty ([ ]). There is no structured data present on this page to define the entities, their relationships, or the organizational hierarchy. The page functions as a 'Black Hole' in the Cleveland Clinic knowledge graph, providing no machine-readable data for AI systems to process.
Entity Connectivity Gaps
The most significant gap is the lack of a MedicalOrganization definition for the 'Office of Patient Experience' itself. According to the Site Context, this should be a 'subOrganization' of the main Cleveland Clinic entity (https://my.clevelandclinic.org/#organization), but no such link exists. Critical missing entities include: 1. The Ombudsman Office (should be a Service or sub-department); 2. The Chief Experience Officer (Person entity with a defined role); 3. The 'Studies in Empathy' Podcast (should link to the PodcastSeries entity identified in the site-wide inventory); 4. Measurement Services (defined as specialized medical services); and 5. ContactPoint data for patient feedback. Because no @id identifiers are used, these entities remain as flat text strings rather than navigable nodes.
AI Retrieval Impact
AI systems and LLMs cannot programmatically identify this page as the authoritative source for Cleveland Clinic's patient advocacy and ombudsman services. The 'broken chain of trust' is severe here: the site claims to be 'Patients First,' but it fails to provide the structured evidence (linking to policies, oversight departments, and leadership) that modern Trust Algorithms require for high-authority E-E-A-T ranking. LLMs will struggle to attribute the 'Studies in Empathy' podcast to this specific department, and the organizational relationship between this office and the global brand remains invisible to knowledge graph builders.
Recommendation
Implement a high-fidelity MedicalOrganization schema for the Office of Patient Experience. Use a persistent @id and declare its parentOrganization as the main Cleveland Clinic entity. Explicitly define the Ombudsman Office as a Service provided by this department. Link the 'Studies in Empathy' podcast mentioned on the page to its corresponding PodcastSeries entity via 'subjectOf'. Add a ContactPoint for the Ombudsman to ensure AI can correctly route 'how do I report a problem' queries. This schema is a recommendation and should be reviewed before implementation.
Score Justification
The score is 1 because the page contains zero structured data. Despite having rich entity-based content that is critical for organizational trust, the site provides no machine-readable entry point for AI retrieval or entity extraction.
Recommended Structured Data
{
    "@context": "https://schema.org",
    "@graph": [
        {
            "@type": "MedicalOrganization",
            "@id": "https://my.clevelandclinic.org/departments/patient-experience/depts/office-patient-experience#organization",
            "name": "Cleveland Clinic Office of Patient Experience",
            "url": "https://my.clevelandclinic.org/departments/patient-experience/depts/office-patient-experience",
            "logo": "https://my.clevelandclinic.org/assets/img/cleveland-clinic-logo.png",
            "parentOrganization": {
                "@id": "https://my.clevelandclinic.org/#organization"
            },
            "description": "The Office of Patient Experience at Cleveland Clinic focuses on putting 'Patients First' by ensuring safe, high-value, and high-quality care that addresses physical, emotional, and spiritual needs.",
            "contactPoint": {
                "@type": "ContactPoint",
                "telephone": "+1-216-444-2200",
                "contactType": "customer service",
                "areaServed": "Global"
            },
            "subOrganization": [
                {
                    "@type": "MedicalOrganization",
                    "@id": "https://my.clevelandclinic.org/departments/patient-experience/depts/office-patient-experience#ombudsman",
                    "name": "Ombudsman Office",
                    "description": "A resource for patients to express concerns and resolve issues regarding their care experience."
                }
            ],
            "hasOfferCatalog": {
                "@type": "OfferCatalog",
                "name": "Patient Experience Programs",
                "itemListElement": [
                    {
                        "@type": "Service",
                        "name": "Patient Experience Measurement"
                    },
                    {
                        "@type": "Service",
                        "name": "Ombudsman Services"
                    },
                    {
                        "@type": "Service",
                        "name": "Caregiver Celebrations"
                    }
                ]
            },
            "subjectOf": {
                "@id": "https://my.clevelandclinic.org/podcasts/health-essentials#podcast"
            }
        },
        {
            "@type": "WebPage",
            "@id": "https://my.clevelandclinic.org/departments/patient-experience/depts/office-patient-experience#webpage",
            "url": "https://my.clevelandclinic.org/departments/patient-experience/depts/office-patient-experience",
            "name": "Patient Experience Office | Cleveland Clinic",
            "isPartOf": {
                "@id": "https://my.clevelandclinic.org/#website"
            },
            "about": {
                "@id": "https://my.clevelandclinic.org/departments/patient-experience/depts/office-patient-experience#organization"
            },
            "description": "Read about why patients come first at Cleveland Clinic. Learn more regarding our commitment to safety, high-quality care and patient satisfaction."
        }
    ]
}
https://my.clevelandclinic.org/online-services/mychart5 / 100
Current Structured Data
No JSON-LD structured data found on this page.
Page Analysis
This page serves as the primary gateway and informational hub for 'MyChart,' a central patient portal. The content identifies it as a 'secure, online health management tool' (SoftwareApplication) and a 'service' (Service) that facilitates medical record access, appointment scheduling, provider messaging, and virtual visits. It is the connective tissue for patient-facing digital operations, referencing secondary entities like the MyClevelandClinic app and Epic Systems Corporation (implied developer).
Schema Assessment
The extracted schema is entirely empty ([ ]). There is no JSON-LD providing machine-readable identity for the application or its relationship to the parent organization. This represents a total semantic vacuum for a page that is critical to the site's digital service infrastructure.
Entity Connectivity Gaps
The most critical gap is the absence of a SoftwareApplication entity and a Service entity. The page content demands a declaration that MyChart is a software product developed by Epic (developer) and published/provided by Cleveland Clinic (publisher/provider). Furthermore, the page lacks PotentialAction schema for 'LoginAction' and 'RegisterAction,' which are the primary user intents. From a Site Context perspective, this page fails to define the #software @id that other pages (like Medical Records or Virtual Visits) need to reference, creating a broken internal knowledge graph.
AI Retrieval Impact
AI agents and LLMs cannot verify the authenticity of this portal or understand the specific capabilities it offers (e.g., billing, scheduling). Without structured 'PotentialAction' data, AI-driven assistants cannot facilitate user journeys like 'Find the Cleveland Clinic login page.' The 'chain of trust' is broken because there is no programmatic link between the software tool and the verified @id of the Cleveland Clinic organization identified in the Site Context.
Recommendation
Deploy a multi-type entity graph using SoftwareApplication and Service. Define a persistent @id for MyChart (e.g., https://my.clevelandclinic.org/online-services/mychart#software) and link it to the Cleveland Clinic root @id (https://my.clevelandclinic.org/#organization) via the 'publisher' and 'provider' properties. Explicitly define 'LoginAction' and 'RegisterAction' to enable AI-driven task completion. This schema is a recommendation and should be reviewed before implementation.
Score Justification
The score of 5 reflects a total absence of structured data on a page that is foundational to the site's utility. Since no entity-defining types exist, the page is invisible to structured knowledge graphs despite its high content value.
Recommended Structured Data
{
    "@context": "https://schema.org",
    "@graph": [
        {
            "@type": "SoftwareApplication",
            "@id": "https://my.clevelandclinic.org/online-services/mychart#software",
            "name": "MyChart",
            "description": "A secure online health management tool that connects Cleveland Clinic patients to their electronic medical records.",
            "applicationCategory": "MedicalApplication",
            "operatingSystem": "Web, iOS, Android",
            "publisher": {
                "@id": "https://my.clevelandclinic.org/#organization"
            },
            "softwareHelp": {
                "@type": "WebPage",
                "url": "https://my.clevelandclinic.org/help"
            },
            "potentialAction": [
                {
                    "@type": "LoginAction",
                    "target": "https://mychart.clevelandclinic.org/MyChart/Authentication/Login"
                },
                {
                    "@type": "RegisterAction",
                    "target": "https://mychart.clevelandclinic.org/MyChart/signup"
                }
            ]
        },
        {
            "@type": "Service",
            "@id": "https://my.clevelandclinic.org/online-services/mychart#service",
            "name": "MyChart Patient Portal Service",
            "serviceType": "Patient Portal",
            "provider": {
                "@id": "https://my.clevelandclinic.org/#organization"
            },
            "areaServed": "US",
            "hasOfferCatalog": {
                "@type": "OfferCatalog",
                "name": "MyChart Capabilities",
                "itemListElement": [
                    {
                        "@type": "Offer",
                        "itemOffered": {
                            "@type": "Service",
                            "name": "Appointment Scheduling"
                        }
                    },
                    {
                        "@type": "Offer",
                        "itemOffered": {
                            "@type": "Service",
                            "name": "Medical Record Access"
                        }
                    },
                    {
                        "@type": "Offer",
                        "itemOffered": {
                            "@type": "Service",
                            "name": "Provider Messaging"
                        }
                    }
                ]
            }
        },
        {
            "@type": "WebPage",
            "@id": "https://my.clevelandclinic.org/online-services/mychart",
            "url": "https://my.clevelandclinic.org/online-services/mychart",
            "name": "MyChart | Cleveland Clinic",
            "isPartOf": {
                "@id": "https://my.clevelandclinic.org/#website"
            },
            "about": {
                "@id": "https://my.clevelandclinic.org/online-services/mychart#software"
            }
        }
    ]
}
https://my.clevelandclinic.org/online-services/virtual-visits5 / 100
Current Structured Data
No JSON-LD structured data found on this page.
Page Analysis
This page functions as a critical Service Hub for Cleveland Clinic's telehealth ecosystem. It defines three distinct service offerings: Express Care Virtual Visits (on-demand), Scheduled Virtual Visits (specialist/follow-up), and Virtual Primary Care. The content specifies geographic availability (Ohio and Florida), operational hours, and treated medical conditions (e.g., Asthma, UTIs). It also introduces a critical SoftwareApplication dependency: the 'MyClevelandClinic' app (powered by MyChart), which serves as the primary 'availableChannel' for these services.
Schema Assessment
The page contains zero JSON-LD structured data. Despite being a high-intent conversion page for a multi-billion dollar healthcare provider, it offers no machine-readable signals. There is no BreadcrumbList, no Service definition, no Organization reference, and no SoftwareApplication entity. It is an 'invisible' page to semantic search engines and LLM knowledge graphs.
Entity Connectivity Gaps
The most significant gap is the total absence of a Service entity. According to the Site Context, the Cleveland Clinic Organization (@id: https://my.clevelandclinic.org/#organization) should be the provider, but this connection is missing. Crucial missing entities include: 1. SoftwareApplication (for the MyClevelandClinic app), 2. MedicalService (for Virtual Visits), 3. AdministrativeArea (for Ohio and Florida service constraints), and 4. FAQPage (to capture the service-related questions at the bottom). Furthermore, the specific 'Commonly treated conditions' are listed as flat text strings rather than links to the MedicalCondition entities defined in the Site Context's Health Library.
AI Retrieval Impact
AI systems and LLMs cannot programmatically verify that Cleveland Clinic is the provider of these virtual services. Retrieval-Augmented Generation (RAG) systems will struggle to accurately extract 'Express Care' hours or geographic restrictions with high confidence. The lack of a connected 'SoftwareApplication' entity means AI assistants (like Siri or Gemini) cannot reliably link the 'Virtual Visit' intent to the 'MyClevelandClinic' app, breaking the user journey from search to action. This represents a total failure in establishing E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness) for the telehealth offering.
Recommendation
Deploy a comprehensive JSON-LD graph. 1. Use 'MedicalWebPage' as the top-level container. 2. Define a 'Service' entity for 'Virtual Visits' and link it to the Cleveland Clinic parent @id. 3. Explicitly declare 'areaServed' for Ohio and Florida. 4. Define 'availableChannel' as a 'ServiceChannel' that references the 'SoftwareApplication' (@id for MyChart/MyClevelandClinic app). 5. Map 'offers' to represent the different visit types (Express vs. Primary Care). 6. Use 'lastReviewed' to provide a trust signal for medical service information. This schema is a recommendation and should be reviewed before implementation.
Score Justification
A score of 5 is assigned because the page provides zero structured data. It lacks even the most basic BreadcrumbList or WebSite schema, rendering it a 'dark node' in the Cleveland Clinic knowledge graph despite its immense business value.
Recommended Structured Data
{
    "@context": "https://schema.org",
    "@graph": [
        {
            "@type": "MedicalWebPage",
            "@id": "https://my.clevelandclinic.org/online-services/virtual-visits#webpage",
            "url": "https://my.clevelandclinic.org/online-services/virtual-visits",
            "name": "Virtual Visits | Cleveland Clinic",
            "description": "See a Cleveland Clinic provider online from the comfort of your home using the MyClevelandClinic app.",
            "isPartOf": {
                "@id": "https://my.clevelandclinic.org/#website"
            },
            "about": {
                "@id": "https://my.clevelandclinic.org/online-services/virtual-visits#service"
            }
        },
        {
            "@type": "MedicalService",
            "@id": "https://my.clevelandclinic.org/online-services/virtual-visits#service",
            "name": "Cleveland Clinic Virtual Visits",
            "serviceType": "Telehealth",
            "provider": {
                "@id": "https://my.clevelandclinic.org/#organization"
            },
            "areaServed": [
                {
                    "@type": "State",
                    "name": "Ohio"
                },
                {
                    "@type": "State",
                    "name": "Florida"
                }
            ],
            "availableChannel": {
                "@type": "ServiceChannel",
                "name": "MyClevelandClinic App",
                "serviceUrl": "https://my.clevelandclinic.org/online-services/mychart",
                "providesService": {
                    "@id": "https://my.clevelandclinic.org/online-services/virtual-visits#service"
                }
            },
            "hasOfferCatalog": {
                "@type": "OfferCatalog",
                "name": "Virtual Visit Types",
                "itemListElement": [
                    {
                        "@type": "Offer",
                        "itemOffered": {
                            "@type": "Service",
                            "name": "Express Care Virtual Visits",
                            "description": "On-demand urgent care for common concerns."
                        }
                    },
                    {
                        "@type": "Offer",
                        "itemOffered": {
                            "@type": "Service",
                            "name": "Virtual Primary Care",
                            "description": "Consistent, continuing care with a primary care team in Ohio."
                        }
                    }
                ]
            },
            "potentialAction": {
                "@type": "UseAction",
                "target": {
                    "@type": "EntryPoint",
                    "urlTemplate": "https://my.clevelandclinic.org/online-services/virtual-visits",
                    "actionPlatform": [
                        "http://schema.org/DesktopWebPlatform",
                        "http://schema.org/IOSPlatform",
                        "http://schema.org/AndroidPlatform"
                    ]
                }
            }
        },
        {
            "@type": "Organization",
            "@id": "https://my.clevelandclinic.org/#organization",
            "name": "Cleveland Clinic",
            "url": "https://my.clevelandclinic.org/"
        },
        {
            "@type": "SoftwareApplication",
            "@id": "https://my.clevelandclinic.org/online-services/mychart#software",
            "name": "MyClevelandClinic",
            "operatingSystem": "iOS, Android",
            "applicationCategory": "MedicalBusiness"
        }
    ]
}
https://my.clevelandclinic.org/online-services/virtual-second-opinions15 / 100
Current Structured Data
No JSON-LD structured data found on this page.
Page Analysis
The page functions as a critical service landing page for Cleveland Clinic's 'Virtual Second Opinions' (VSO). It describes a complex medical service involving multiple stages (Registration, Intake, Records Collection, Matching, Delivery) and two distinct service tiers (Concierge and Concierge Plus). Primary entities include the Virtual Second Opinion service itself, Cleveland Clinic (Provider), Nurse Care Managers, and Specialist Physicians. Secondary entities include medical specialties like Oncology and Heart Care. The content implies a high-trust, professional medical service, but the lack of structured data leaves these entities as flat, unverified text strings.
Schema Assessment
The extracted schema is empty ([ ]). There is no JSON-LD present to define the page type, the service, the provider, or the relationships between the medical experts and the organization. This represents a total failure of semantic connectivity; for an AI or search engine, this page is an unstructured 'black box' of text rather than a verifiable node in a medical knowledge graph.
Entity Connectivity Gaps
The most significant gap is the total absence of a 'Service' or 'MedicalWebPage' entity. Specifically: 1. No link to the parent organization (@id https://my.clevelandclinic.org/#organization). 2. The 'Nurse Care Manager' and 'Specialist' roles mentioned are not structured as 'Person' or 'MedicalSpecialty' entities. 3. The service tiers (Concierge vs. Concierge Plus) are listed in a table but not defined as 'Offer' or 'PriceSpecification' entities. 4. The 'Get Started' call to action is not defined as a 'PotentialAction' (Action/ScheduleAction). 5. The medical specialties (Cancer Care, Heart Care) are not linked to their respective 'MedicalSpecialty' definitions or 'MedicalCondition' schemas.
AI Retrieval Impact
AI retrieval systems (like ChatGPT, Claude, and Google SGE) cannot programmatically verify that this service is an official offering of the Cleveland Clinic. Without @id connectivity, the 'expert advice' mentioned in the meta description cannot be verified against the clinic's staff directory, breaking the chain of trust. This results in lower retrieval confidence for queries related to 'virtual medical opinions' or 'remote specialist consultations,' as the AI cannot distinguish this highly-vetted service from low-quality health blogs.
Recommendation
Deploy a 'MedicalWebPage' schema as the root container, with a 'Service' entity as the 'mainEntity'. Use '@id' to link the service to the parent Cleveland Clinic Organization identifier defined on the homepage. Define 'ServiceChannel' for the virtual delivery method and use 'Offer' to distinguish between 'Concierge' and 'Concierge Plus' tiers. Map the 'Specialties' listed to 'MedicalSpecialty' types. Add a 'ReviewAction' or 'MedicalSpecialty' link to ensure the AI understands the service outputs a professional medical report. Disclaimer: this schema is a recommendation and should be reviewed before implementation.
Score Justification
A score of 15 is assigned because the page contains zero JSON-LD schema, failing to represent the complex medical service described in the content. While the page is human-readable, it is invisible to structured AI knowledge graphs.
Recommended Structured Data
{
    "@context": "https://schema.org",
    "@type": "MedicalWebPage",
    "@id": "https://my.clevelandclinic.org/online-services/virtual-second-opinions#webpage",
    "url": "https://my.clevelandclinic.org/online-services/virtual-second-opinions",
    "name": "Virtual Second Opinions | Cleveland Clinic",
    "description": "Cleveland Clinic\u2019s virtual second opinions offer expert advice about a wide range of conditions, treatments and procedures from top specialists.",
    "mainEntity": {
        "@type": "Service",
        "@id": "https://my.clevelandclinic.org/online-services/virtual-second-opinions#service",
        "name": "Virtual Second Opinion",
        "serviceType": "Medical Second Opinion",
        "provider": {
            "@id": "https://my.clevelandclinic.org/#organization"
        },
        "areaServed": "International",
        "offers": [
            {
                "@type": "Offer",
                "name": "Concierge",
                "description": "Written report only from a Cleveland Clinic Physician"
            },
            {
                "@type": "Offer",
                "name": "Concierge Plus",
                "description": "Written report plus virtual visit with a Cleveland Clinic Physician"
            }
        ],
        "hasOfferCatalog": {
            "@type": "OfferCatalog",
            "name": "VSO Specialties",
            "itemListElement": [
                {
                    "@type": "ListItem",
                    "position": 1,
                    "item": {
                        "@type": "MedicalSpecialty",
                        "name": "Oncology"
                    }
                },
                {
                    "@type": "ListItem",
                    "position": 2,
                    "item": {
                        "@type": "MedicalSpecialty",
                        "name": "Cardiology"
                    }
                }
            ]
        },
        "potentialAction": {
            "@type": "RegisterAction",
            "target": "https://my.clevelandclinic.org/online-services/virtual-second-opinions",
            "name": "Get Started"
        }
    },
    "publisher": {
        "@id": "https://my.clevelandclinic.org/#organization"
    },
    "about": [
        {
            "@type": "MedicalSpecialty",
            "name": "Oncology"
        },
        {
            "@type": "MedicalSpecialty",
            "name": "Cardiology"
        }
    ]
}
https://my.clevelandclinic.org/locations5 / 100
Current Structured Data
No JSON-LD structured data found on this page.
Page Analysis
The page functions as a primary geographic directory (Hub) for the Cleveland Clinic's global network of medical facilities. Based on the content, it is a Search/Collection page designed to help users find specific Hospitals, MedicalClinics, and Wellness Centers. It implies a 'Parent-to-Child' relationship between the main Cleveland Clinic Organization and its numerous physical sub-organizations. The page includes dynamic elements like a location filter/search tool and references critical contact information and appointment-related actions.
Schema Assessment
The extracted schema is completely empty ([]). This is a critical failure for a page that serves as the entry point to the organization's entire physical infrastructure. There is no structured data to define the page as a CollectionPage, no ItemList to index the regional hubs, and no SearchAction to define the 'Find a Location' functionality for AI agents or search engines.
Entity Connectivity Gaps
The most glaring gap is the total lack of entity declaration. The page content demands a 'CollectionPage' or 'MedicalWebPage' type. From an entity perspective: 1. The relationship to the Root Organization (@id 'https://my.clevelandclinic.org/#organization') is missing. 2. There is no 'ItemList' schema to programmatically list the major regional hubs (Ohio, Florida, Nevada, Canada, Abu Dhabi, London) identified in the Site Context. 3. The 'Find a Location' tool is not declared as a 'SearchAction', making the search capability invisible to AI. 4. Strategic links to 'Hospital' and 'MedicalBusiness' entities defined on sub-pages are absent, preventing the formation of a hub-and-spoke knowledge graph.
AI Retrieval Impact
AI systems and LLMs cannot programmatically identify this page as the authoritative directory for Cleveland Clinic locations. Without structured data, the 'chain of trust' from the brand to its physical facilities is broken. Search engines cannot easily parse the regional hierarchy, leading to poor visibility in localized AI Overviews or 'near me' search queries. The dynamic 'Loading' state of the location list further complicates things; without schema, the content inside those loaders is a 'black box' to many crawlers, meaning the actual locations may never be associated with the parent organization in a knowledge graph.
Recommendation
Immediately implement a 'CollectionPage' schema that anchors to the site-wide Cleveland Clinic Organization @id. Define an 'ItemList' containing the primary regional hubs as 'ListItem' entities, each pointing to its respective landing page URL (Ohio, Florida, Nevada, etc.). Add a 'SearchAction' targeting the location search functionality to allow AI-driven discovery. Use 'subOrganization' or 'hasOfferCatalog' logic to link the main brand to these geographic entities. [This schema is a recommendation and should be reviewed before implementation]
Score Justification
A score of 5 is assigned because the page provides zero structured data. Despite being a critical directory page for a global medical leader, it offers no machine-readable hints to AI regarding the organization's physical structure, locations, or search capabilities.
Recommended Structured Data
{
    "@context": "https://schema.org",
    "@type": "CollectionPage",
    "@id": "https://my.clevelandclinic.org/locations#webpage",
    "url": "https://my.clevelandclinic.org/locations",
    "name": "Cleveland Clinic Locations & Directions",
    "isPartOf": {
        "@id": "https://my.clevelandclinic.org/#website"
    },
    "about": {
        "@id": "https://my.clevelandclinic.org/#organization"
    },
    "mainEntity": {
        "@type": "ItemList",
        "name": "Cleveland Clinic Global Regional Hubs",
        "itemListElement": [
            {
                "@type": "ListItem",
                "position": 1,
                "item": {
                    "@type": "MedicalOrganization",
                    "name": "Cleveland Clinic Ohio Locations",
                    "url": "https://my.clevelandclinic.org/locations/ohio-locations"
                }
            },
            {
                "@type": "ListItem",
                "position": 2,
                "item": {
                    "@type": "MedicalBusiness",
                    "name": "Cleveland Clinic Florida",
                    "url": "https://my.clevelandclinic.org/florida/locations"
                }
            },
            {
                "@type": "ListItem",
                "position": 3,
                "item": {
                    "@type": "MedicalBusiness",
                    "name": "Cleveland Clinic Nevada",
                    "url": "https://my.clevelandclinic.org/locations/nevada"
                }
            },
            {
                "@type": "ListItem",
                "position": 4,
                "item": {
                    "@type": "MedicalBusiness",
                    "name": "Cleveland Clinic Canada",
                    "url": "https://my.clevelandclinic.org/canada"
                }
            },
            {
                "@type": "ListItem",
                "position": 5,
                "item": {
                    "@type": "Hospital",
                    "name": "Cleveland Clinic London",
                    "url": "https://clevelandcliniclondon.uk/"
                }
            },
            {
                "@type": "ListItem",
                "position": 6,
                "item": {
                    "@type": "Hospital",
                    "name": "Cleveland Clinic Abu Dhabi",
                    "url": "https://www.clevelandclinicabudhabi.ae/en/"
                }
            }
        ]
    },
    "potentialAction": {
        "@type": "SearchAction",
        "target": {
            "@type": "EntryPoint",
            "urlTemplate": "https://my.clevelandclinic.org/locations?q={search_term_string}"
        },
        "query-input": "required name=search_term_string"
    }
}
https://my.clevelandclinic.org/locations/ohio-locations5 / 100
Current Structured Data
No JSON-LD structured data found on this page.
Page Analysis
The page functions as a regional directory and search hub for Cleveland Clinic's Ohio-based medical facilities. It is a classic 'CollectionPage' or 'Directory' intended to help users navigate a complex physical infrastructure. Key entities include the parent Organization (Cleveland Clinic), specific regional facilities (Fairview Hospital, Main Campus), and a 'SearchAction' utility for location discovery based on user proximity.
Schema Assessment
The extracted schema is entirely empty. There is zero structured data present, which means from an AI retrieval perspective, this page is a 'dark node.' It provides no machine-readable information about the entities it lists, their relationships, or the services available at these locations.
Entity Connectivity Gaps
This page lacks every critical semantic anchor required for a medical directory. Specifically: 1. It lacks a 'CollectionPage' or 'MedicalWebPage' declaration. 2. It fails to link to the site-wide Organization identifier ('https://my.clevelandclinic.org/#organization') identified in the Site Context. 3. The search tool is not defined as a 'SearchAction'. 4. The specific locations (Fairview Hospital, Main Campus) are treated as flat text rather than 'Hospital' or 'MedicalBusiness' entities with their own '@id' identifiers. 5. The appointment and question phone numbers are not marked up as 'ContactPoint' entities.
AI Retrieval Impact
Because there is no schema, AI systems and LLMs cannot programmatically verify which facilities belong to the Cleveland Clinic network in Ohio. This breaks the 'chain of trust' between the parent organization and its physical satellites. Knowledge graph builders will fail to associate regional search intent with this hub, and the site misses out on 'Local Business' and 'Hospital' rich results that drive patient acquisition. Search engines are forced to rely on visual scraping, which is less reliable than structured data for high-stakes medical entity extraction.
Recommendation
Implement a high-fidelity 'CollectionPage' that defines the primary entity as an 'ItemList' of Ohio medical facilities. Each facility in the list should be a 'Hospital' or 'MedicalBusiness' entity with a unique '@id' (e.g., '.../locations/fairview-hospital#hospital') to allow cross-referencing. Explicitly link the 'publisher' to the root organization '@id' and add a 'SearchAction' targeting the location filter tool. This schema is a recommendation and should be reviewed before implementation.
Score Justification
The score is near-zero because the page contains no JSON-LD whatsoever. Even basic breadcrumbs or organization identifiers are missing, leaving the page completely disconnected from the site's broader knowledge graph structure.
Recommended Structured Data
{
    "@context": "https://schema.org",
    "@type": "CollectionPage",
    "@id": "https://my.clevelandclinic.org/locations/ohio-locations#webpage",
    "name": "Find an Ohio Location Near Me | Cleveland Clinic",
    "description": "Find Cleveland Clinic locations across Ohio, including hospitals, family health centers, and specialty centers.",
    "publisher": {
        "@id": "https://my.clevelandclinic.org/#organization"
    },
    "breadcrumb": {
        "@type": "BreadcrumbList",
        "itemListElement": [
            {
                "@type": "ListItem",
                "position": 1,
                "name": "Home",
                "item": "https://my.clevelandclinic.org/"
            },
            {
                "@type": "ListItem",
                "position": 2,
                "name": "Locations",
                "item": "https://my.clevelandclinic.org/locations"
            },
            {
                "@type": "ListItem",
                "position": 3,
                "name": "Ohio Locations",
                "item": "https://my.clevelandclinic.org/locations/ohio-locations"
            }
        ]
    },
    "mainEntity": {
        "@type": "ItemList",
        "name": "Cleveland Clinic Ohio Locations",
        "itemListElement": [
            {
                "@type": "ListItem",
                "position": 1,
                "item": {
                    "@type": "Hospital",
                    "@id": "https://my.clevelandclinic.org/locations/main-campus#hospital",
                    "name": "Cleveland Clinic Main Campus",
                    "address": {
                        "@type": "PostalAddress",
                        "addressLocality": "Cleveland",
                        "addressRegion": "OH"
                    }
                }
            },
            {
                "@type": "ListItem",
                "position": 2,
                "item": {
                    "@type": "Hospital",
                    "@id": "https://my.clevelandclinic.org/locations/fairview-hospital#hospital",
                    "name": "Fairview Hospital",
                    "address": {
                        "@type": "PostalAddress",
                        "addressLocality": "Cleveland",
                        "addressRegion": "OH"
                    }
                }
            }
        ]
    },
    "potentialAction": {
        "@type": "SearchAction",
        "target": {
            "@type": "EntryPoint",
            "urlTemplate": "https://my.clevelandclinic.org/locations/ohio-locations?q={search_term_string}"
        },
        "query-input": "required name=search_term_string"
    },
    "mainEntityOfPage": {
        "@id": "https://my.clevelandclinic.org/locations/ohio-locations"
    }
}
https://my.clevelandclinic.org/locations/nevada5 / 100
Current Structured Data
No JSON-LD structured data found on this page.
Page Analysis
The page serves as the primary regional landing page for Cleveland Clinic's Nevada operations. The content defines a high-stakes medical entity: the Lou Ruvo Center for Brain Health. It identifies specific physical location data (888 West Bonneville Ave, Las Vegas), contact information, and specialized medical services including Neurology, Imaging (PET/CT, MRI), and Clinical Research. It also establishes a clear organizational hierarchy (Cleveland Clinic Nevada as a regional arm of the global organization) and includes functional calls-to-action for physician referrals, appointments, and philanthropy.
Schema Assessment
Total failure. The extracted schema is completely empty. Despite the page being rich in verifiable entities (LocalBusiness, MedicalOrganization, PostalAddress, Services, and PotentialActions), it provides zero structured data to AI crawlers. This makes the location 'invisible' to structured knowledge graphs and prevents AI agents from programmatically associating this facility with the parent Cleveland Clinic organization.
Entity Connectivity Gaps
The most critical gap is the absence of a MedicalBusiness or Hospital entity to anchor the physical location in Las Vegas. Specifically: 1. No @id association with the parent Cleveland Clinic entity defined in the Site Context (https://my.clevelandclinic.org/#organization). 2. Missing PostalAddress and GeoCoordinates for the Las Vegas facility. 3. Missing MedicalSpecialty declarations for Neurology and Imaging. 4. Missing relationships between the location and the 'Find a Doctor' or 'Clinical Trials' services mentioned in the text. 5. Failure to define the 'Lou Ruvo Center for Brain Health' as a subOrganization or department, which is a significant brand entity identified in the Site Context.
AI Retrieval Impact
AI systems and LLMs cannot verify this location's authenticity or its relationship to the Cleveland Clinic brand via the 'chain of trust.' In 'near me' queries or specialized neurological service searches (e.g., 'Alzheimer's treatment Las Vegas'), this page lacks the structured signals required for inclusion in AI Overviews (SGE) or Rich Results. The lack of connectivity means that the authority (E-E-A-T) of the parent organization is not programmatically flowing to this regional site, and the site's unique regional data is not being aggregated back into the parent knowledge graph.
Recommendation
Immediately implement a MedicalBusiness schema using the @id 'https://my.clevelandclinic.org/locations/nevada#medicalbusiness'. This entity must include the physical address, phone number, and geo-coordinates. Use the 'parentOrganization' property to link to the site-wide organization @id identified in the context. Declare the Lou Ruvo Center as a 'subOrganization'. Use 'hasOfferCatalog' to list services like Imaging and Cognitive Care as discrete Service entities rather than flat text. Add a 'DonateAction' to link the philanthropy section to the site-wide 'Giving' entity. DISCLAIMER: this schema is a recommendation and should be reviewed before implementation.
Score Justification
A score of 5 is assigned because the page has zero structured data. It fails to utilize even basic schema for a high-value medical location, resulting in a complete lack of AI-readiness and semantic connectivity.
Recommended Structured Data
{
    "@context": "https://schema.org",
    "@type": "MedicalBusiness",
    "@id": "https://my.clevelandclinic.org/locations/nevada#medicalbusiness",
    "name": "Cleveland Clinic Nevada",
    "url": "https://my.clevelandclinic.org/locations/nevada",
    "logo": "https://my.clevelandclinic.org/assets/img/logo.png",
    "image": "https://my.clevelandclinic.org/assets/img/nevada-events.jpg",
    "description": "Cleveland Clinic Nevada specializes in collaborative neurological and imaging care for individuals with cognitive disorders, movement disorders and multiple sclerosis.",
    "telephone": "+1-702-483-6000",
    "address": {
        "@type": "PostalAddress",
        "streetAddress": "888 West Bonneville Ave.",
        "addressLocality": "Las Vegas",
        "addressRegion": "NV",
        "postalCode": "89106",
        "addressCountry": "US"
    },
    "parentOrganization": {
        "@id": "https://my.clevelandclinic.org/#organization"
    },
    "subOrganization": {
        "@type": "MedicalOrganization",
        "@id": "https://my.clevelandclinic.org/locations/nevada#lou-ruvo-center",
        "name": "Cleveland Clinic Lou Ruvo Center for Brain Health"
    },
    "medicalSpecialty": [
        "Neurology",
        "MedicalImaging"
    ],
    "hasOfferCatalog": {
        "@type": "OfferCatalog",
        "name": "Neurological Services",
        "itemListElement": [
            {
                "@type": "Offer",
                "itemOffered": {
                    "@type": "Service",
                    "name": "Alzheimer's Disease Treatment"
                }
            },
            {
                "@type": "Offer",
                "itemOffered": {
                    "@type": "Service",
                    "name": "Multiple Sclerosis Care"
                }
            },
            {
                "@type": "Offer",
                "itemOffered": {
                    "@type": "Service",
                    "name": "PET/CT Imaging"
                }
            }
        ]
    },
    "potentialAction": [
        {
            "@type": "ScheduleAction",
            "target": "https://my.clevelandclinic.org/webappointment"
        },
        {
            "@type": "DonateAction",
            "target": "https://my.clevelandclinic.org/giving"
        }
    ]
}
https://my.clevelandclinic.org/professionals10 / 100
Current Structured Data
No JSON-LD structured data found on this page.
Page Analysis
This is a Service Hub / Directory page specifically designed for healthcare professionals. The page functions as a gateway to high-value B2B and B2P (Business-to-Professional) offerings including patient referral services, clinical integration networks (Quality Alliance), international collaboration programs (Cleveland Clinic Connected), and academic resources (CME, Research, and Consult QD). The primary entity is the Cleveland Clinic Professional Services division, which mediates relationships between the parent organization and external medical practitioners.
Schema Assessment
The page contains zero JSON-LD structured data. Despite the page content identifying critical entities like the 'Referring Physician Hotline' and specific programs like 'Quality Alliance,' none of these are programmatically defined. The AI only sees raw text, failing to recognize this page as a functional service interface for medical professionals.
Entity Connectivity Gaps
There is a total collapse of entity connectivity. First, the page fails to reference the root organization @id identified in the Site Context (https://my.clevelandclinic.org/#organization). Second, the 'Referring Physician Hotline' is not marked as a ContactPoint, making it invisible to automated systems and voice assistants. Third, high-level programs like 'Cleveland Clinic Connected' and 'Quality Alliance' are missing as Organization or Service sub-entities. Fourth, the 'Consult QD' and 'Research' sections are mentioned as text links but should be structured as 'mentions' or 'hasPart' relationships to the publication and ResearchOrganization entities defined elsewhere in the site architecture.
AI Retrieval Impact
For AI agents and LLMs, this page is an 'authority dead-end.' Because there is no schema, the 'Referring Physician Hotline' cannot be reliably extracted as a trusted contact for providers. The relationship between the Cleveland Clinic and the 'Quality Alliance' network remains an unverified text claim rather than a structured organizational link. In AI-powered search (SGE/AI Overviews), this page is less likely to be surfaced for queries like 'Cleveland Clinic physician referral' or 'Cleveland Clinic professional education' because the machine-readable intent (Service) is missing.
Recommendation
Implement a WebPage schema that declares the Cleveland Clinic as the publisher using the site-wide @id. The mainEntity should be defined as a 'Service' representing the Professional Resource Hub. Explicitly include a 'ContactPoint' for the Referring Physician Hotline. Use 'hasPart' to link to 'Quality Alliance' and 'Cleveland Clinic Connected' as nested Service entities. Crucially, the 'Consult QD' section should link via @id to the Publication entity to maintain the chain of authority. This schema is a recommendation and should be reviewed before implementation.
Score Justification
The score is 10 because the page provides no structured data whatsoever. It relies entirely on natural language processing for entity extraction, which is less reliable than structured data for high-stakes medical and professional service relationships.
Recommended Structured Data
{
    "@context": "https://schema.org",
    "@type": "WebPage",
    "@id": "https://my.clevelandclinic.org/professionals#webpage",
    "url": "https://my.clevelandclinic.org/professionals",
    "name": "Resources for Medical Professionals | Cleveland Clinic",
    "description": "Browse the resources available for medical professionals at Cleveland Clinic including referring patients, education, and clinical networks.",
    "publisher": {
        "@id": "https://my.clevelandclinic.org/#organization"
    },
    "mainEntity": {
        "@type": "Service",
        "name": "Cleveland Clinic Professional Resources",
        "provider": {
            "@id": "https://my.clevelandclinic.org/#organization"
        },
        "contactPoint": {
            "@type": "ContactPoint",
            "telephone": "+1-855-733-3712",
            "contactType": "Referring Physician Hotline",
            "areaServed": "US",
            "availableLanguage": "en"
        },
        "hasOfferCatalog": {
            "@type": "OfferCatalog",
            "name": "Professional Programs",
            "itemListElement": [
                {
                    "@type": "ListItem",
                    "position": 1,
                    "item": {
                        "@type": "Service",
                        "name": "Referring a Patient",
                        "url": "https://my.clevelandclinic.org/professionals/referring"
                    }
                },
                {
                    "@type": "ListItem",
                    "position": 2,
                    "item": {
                        "@type": "Organization",
                        "name": "Quality Alliance",
                        "description": "A clinically integrated network spanning more than 21 counties in Northeast Ohio."
                    }
                },
                {
                    "@type": "ListItem",
                    "position": 3,
                    "item": {
                        "@type": "Service",
                        "name": "Cleveland Clinic Connected",
                        "description": "A global program for knowledge sharing and clinical excellence."
                    }
                }
            ]
        }
    },
    "mentions": [
        {
            "@type": "EducationalOrganization",
            "@id": "https://my.clevelandclinic.org/departments/education#organization",
            "name": "Cleveland Clinic Center for Continuing Education"
        },
        {
            "@type": "ResearchOrganization",
            "@id": "https://my.clevelandclinic.org/research#organization",
            "name": "Cleveland Clinic Research"
        }
    ]
}
https://my.clevelandclinic.org/professionals/referring10 / 100
Current Structured Data
No JSON-LD structured data found on this page.
Page Analysis
The page functions as a critical b2b service portal for healthcare providers. Its primary entity is the 'Physician Referral Service,' which facilitates the transfer of care from external physicians to Cleveland Clinic specialists. Key sub-entities identified include the 'Referring Physician Hotline' (a ContactPoint), the 'Physician Relations Team' (a Departmental Entity), and various regional referral services for Ohio, Florida, and Nevada. The page implies a 'ScheduleAction' for patient referral and a 'Service' provided by the parent Organization.
Schema Assessment
The extracted schema is empty. There is zero JSON-LD on this page. For a high-stakes institutional page, this is a total failure in AI-readiness. AI systems are forced to rely on unstructured text parsing, which is prone to error regarding phone numbers and specific regional referral protocols.
Entity Connectivity Gaps
1. Primary Entity Missing: No 'Service' or 'MedicalBusiness' schema defining the referral program. 2. Broken Trust Chain: No connection to the site-wide Cleveland Clinic @id (https://my.clevelandclinic.org/#organization). 3. Missing Actionability: No 'PotentialAction' (ScheduleAction or TransferAction) to programmatically define how to refer a patient. 4. Isolated Contacts: The hotline (855.733.3712) and email are text-only, preventing automated contact extraction by AI assistants. 5. Geographic Disconnect: Regional referral paths (Florida, Nevada) are not linked to the 'areaServed' or 'location' entities defined elsewhere in the site context.
AI Retrieval Impact
LLMs and search engines cannot verify this as an official service of Cleveland Clinic via knowledge graph traversal. The 'Referring Physician Hotline' remains an unverified string rather than a high-confidence 'ContactPoint.' AI-driven search (SGE/Perplexity) may fail to accurately summarize referral steps or misattribute regional contact info because the relationships between the parent org and the specific regional referral services are not declared.
Recommendation
Implement a 'Service' schema as the mainEntity of the WebPage. This service must list Cleveland Clinic (via the root @id) as the 'provider.' Explicitly define 'ContactPoint' for the hotline and 'PotentialAction' for the referral process. Use 'hasOfferCatalog' to link to specialized referral guides and 'areaServed' to bridge the gap to Florida and Nevada regional entities identified in the site-wide context. Prioritize the inclusion of the 'ContactPoint' with 'contactType': 'physician referral'.
Score Justification
A score of 10 is assigned because the page has zero structured data. Despite being a major entry point for a critical professional service, it provides no machine-readable identifiers or entity links, making it invisible to formal knowledge graph construction.
Recommended Structured Data
{
    "@context": "https://schema.org",
    "@graph": [
        {
            "@type": "WebPage",
            "@id": "https://my.clevelandclinic.org/professionals/referring#webpage",
            "url": "https://my.clevelandclinic.org/professionals/referring",
            "name": "Referring a Patient to Cleveland Clinic",
            "isPartOf": {
                "@id": "https://my.clevelandclinic.org/#website"
            },
            "about": {
                "@id": "https://my.clevelandclinic.org/professionals/referring#service"
            },
            "mainEntity": {
                "@id": "https://my.clevelandclinic.org/professionals/referring#service"
            }
        },
        {
            "@type": "Service",
            "@id": "https://my.clevelandclinic.org/professionals/referring#service",
            "name": "Cleveland Clinic Physician Referral Service",
            "provider": {
                "@id": "https://my.clevelandclinic.org/#organization"
            },
            "serviceType": "Medical Referral Service",
            "areaServed": [
                {
                    "@type": "AdministrativeArea",
                    "name": "Ohio"
                },
                {
                    "@type": "AdministrativeArea",
                    "name": "Florida"
                },
                {
                    "@type": "AdministrativeArea",
                    "name": "Nevada"
                }
            ],
            "availableChannel": {
                "@type": "ServiceChannel",
                "name": "Referring Physician Hotline",
                "serviceNumber": "855.733.3712",
                "availableLanguage": "English"
            },
            "potentialAction": {
                "@type": "ScheduleAction",
                "target": {
                    "@type": "EntryPoint",
                    "urlTemplate": "https://my.clevelandclinic.org/professionals/referring",
                    "actionPlatform": [
                        "http://schema.org/DesktopWebPlatform",
                        "http://schema.org/MobileWebPlatform"
                    ]
                },
                "name": "Refer a Patient"
            },
            "hasPart": [
                {
                    "@type": "ContactPoint",
                    "contactType": "physician relations",
                    "telephone": "855.733.3712",
                    "email": "refer123@ccf.org"
                }
            ]
        },
        {
            "@type": "Organization",
            "@id": "https://my.clevelandclinic.org/#organization",
            "name": "Cleveland Clinic",
            "url": "https://my.clevelandclinic.org/"
        }
    ]
}
https://my.clevelandclinic.org/help5 / 100
Current Structured Data
No JSON-LD structured data found on this page.
Page Analysis
The page functions as a central Support and Contact Hub for the Cleveland Clinic health system. It serves as a directory for diverse user needs, including finding doctors, accessing billing information, regional contact details (Ohio, Florida, Nevada, Canada), and specialized services like the 'Ombudsman Office' and 'Nurse on Call'. Content-wise, it is a hybrid of a ContactPage and a portal for several Service and MedicalOrganization entities.
Schema Assessment
Critical failure. The extracted schema is entirely empty ([ ]). There is no JSON-LD present to define the page's purpose, the contact methods, or the relationships between the support categories and the parent organization. AI systems must rely on unstructured scraping, which is prone to error regarding specific phone numbers and regional service availability.
Entity Connectivity Gaps
1. Missing Page Type: No FAQPage or ContactPage declaration. 2. Missing Contact Points: Regional phone numbers for Ohio, Florida, Nevada, and Canada are flat text rather than structured 'ContactPoint' entities with 'areaServed' properties. 3. Broken Entity Graph: The 'Ombudsman Office' and 'MyChart' are mentioned but not linked to their existing @id definitions found in the Site Context. 4. Service Isolation: The 'Nurse on Call' service is not defined as a 'Service' entity, making it invisible to voice-search queries for triage support. 5. Missing Actions: There is no 'ContactAction' or 'SearchAction' structured data for the email forms or search tools.
AI Retrieval Impact
AI retrieval systems (like ChatGPT/Claude) and search engines (SGE) cannot verify which phone number belongs to which region with 100% confidence. Voice assistants cannot distinguish the 'Nurse on Call' service as a functional utility. The lack of @id connectivity means this page does not pass authority from the parent 'Cleveland Clinic' entity to these support resources, weakening E-E-A-T signals for user-support queries.
Recommendation
Implement a high-fidelity ContactPage schema that also incorporates FAQPage for the category navigation. Use the established parent organization @id 'https://my.clevelandclinic.org/#organization' as the provider. Define separate 'contactPoint' objects for each region with specific 'areaServed' (ISO 3166-2) and 'hoursAvailable'. Explicitly link the 'MyChart' mention to its SoftwareApplication @id and the 'Ombudsman' to its MedicalOrganization @id as identified in the Site Context. This schema is a recommendation and should be reviewed before implementation.
Score Justification
A score of 5 is assigned because the page provides no structured data. Despite being a critical navigational hub for a major hospital system, it offers zero machine-readable entity markers or contact points, representing a total disconnect from modern AI-retrieval standards.
Recommended Structured Data
{
    "@context": "https://schema.org",
    "@type": [
        "ContactPage",
        "FAQPage"
    ],
    "@id": "https://my.clevelandclinic.org/help#webpage",
    "mainEntityOfPage": "https://my.clevelandclinic.org/help",
    "name": "Cleveland Clinic Help and Frequently Asked Questions",
    "description": "Contact information and frequently asked questions for Cleveland Clinic locations and services.",
    "publisher": {
        "@id": "https://my.clevelandclinic.org/#organization"
    },
    "about": {
        "@id": "https://my.clevelandclinic.org/#organization"
    },
    "contactPoint": [
        {
            "@type": "ContactPoint",
            "telephone": "800.223.2273",
            "contactType": "customer service",
            "areaServed": "US-OH",
            "hoursAvailable": {
                "@type": "OpeningHoursSpecification",
                "dayOfWeek": [
                    "Monday",
                    "Tuesday",
                    "Wednesday",
                    "Thursday",
                    "Friday",
                    "Saturday",
                    "Sunday"
                ],
                "opens": "07:00",
                "closes": "19:00"
            }
        },
        {
            "@type": "ContactPoint",
            "telephone": "866.293.7866",
            "contactType": "customer service",
            "areaServed": "US-FL"
        },
        {
            "@type": "ContactPoint",
            "telephone": "702.483.6000",
            "contactType": "customer service",
            "areaServed": "US-NV"
        },
        {
            "@type": "ContactPoint",
            "telephone": "416.507.6600",
            "contactType": "customer service",
            "areaServed": "CA"
        }
    ],
    "mainEntity": [
        {
            "@type": "Question",
            "name": "How do I contact the Ombudsman Office?",
            "acceptedAnswer": {
                "@type": "Answer",
                "text": "You can reach the Ombudsman Office for patient experience concerns by visiting their dedicated department page.",
                "url": "https://my.clevelandclinic.org/departments/patient-experience/depts/office-patient-experience"
            }
        },
        {
            "@type": "Question",
            "name": "Where do I find my medical records?",
            "acceptedAnswer": {
                "@type": "Answer",
                "text": "Medical records can be requested via MyChart or through the Health Information Management department.",
                "url": "https://my.clevelandclinic.org/patients/information/medical-records"
            }
        }
    ],
    "hasPart": [
        {
            "@type": "Service",
            "name": "Nurse on Call",
            "provider": {
                "@id": "https://my.clevelandclinic.org/#organization"
            },
            "description": "Talk to a nurse by reaching out to your primary care provider's office."
        },
        {
            "@type": "SoftwareApplication",
            "name": "MyChart",
            "@id": "https://my.clevelandclinic.org/online-services/mychart#software"
        }
    ]
}
https://my.clevelandclinic.org/giving5 / 100
Current Structured Data
No JSON-LD structured data found on this page.
Page Analysis
This page serves as the central hub for Cleveland Clinic's philanthropic activities. It is a 'Giving' landing page that functions as both a Service (fundraising/philanthropy) and a gateway to various sub-entities. Primary entities include the Cleveland Clinic Philanthropy department, while secondary entities include specific programs like VeloSano (an event/fundraiser), Catalyst Grants, and the SENSE program. The content implies a 'DonateAction' and a direct relationship between donor contributions and medical breakthroughs (MedicalCondition/Research).
Schema Assessment
The current schema is non-existent (empty array). There is zero structured data provided to define the organization, the donation actions, the philanthropic services, or the relationships to the parent Cleveland Clinic entity. For AI systems, this page is a 'blind spot' where intent (donating) and authority (official charity status) cannot be programmatically verified.
Entity Connectivity Gaps
1. Root Identity: No link to the parent Organization (@id: https://my.clevelandclinic.org/#organization). 2. Missing Entity Types: The page should be defined as a 'WebPage' about an 'Organization' (Philanthropy Dept) or 'Service'. 3. Action Gaps: The primary 'Donate Now' call-to-action is not defined as a 'DonateAction'. 4. Sub-Entity Isolation: High-value programs mentioned (VeloSano, Global Women's Health Forum, Catalyst Grants) are treated as flat text rather than linked entities or events. 5. Trust Signals: Missing 'publishingPrinciples' and 'funder' relationships that establish the legal and ethical framework of the giving department.
AI Retrieval Impact
AI retrieval systems and LLMs cannot verify the authenticity of this donation page through structured trust signals, which is critical for 'Your Money or Your Life' (YMYL) content. Knowledge engines cannot connect 'VeloSano' to 'Cleveland Clinic' via a machine-readable graph, and conversational AI cannot accurately answer 'how do I donate to Cleveland Clinic research?' with high confidence because the 'DonateAction' is not declared. This results in a total breakdown of the chain of trust.
Recommendation
Implement a high-fidelity graph starting with a WebPage entity that has the primary subject as an Organization (the Philanthropy department). Explicitly link this to the site-wide Cleveland Clinic @id. Define VeloSano and other programs as 'subOrganization' or 'event' entities. Crucially, add a 'potentialAction' of type 'DonateAction' to the organization to allow AI agents to understand the transaction path. Note: this schema is a recommendation and should be reviewed before implementation.
Score Justification
The score of 5 reflects the complete absence of structured data. While the page content is rich and authoritative for human readers, it is invisible to semantic crawlers and AI agents that rely on structured connectivity to build knowledge graphs.
Recommended Structured Data
{
    "@context": "https://schema.org",
    "@graph": [
        {
            "@type": "WebPage",
            "@id": "https://my.clevelandclinic.org/giving#webpage",
            "url": "https://my.clevelandclinic.org/giving",
            "name": "Give to Cleveland Clinic",
            "isPartOf": {
                "@id": "https://my.clevelandclinic.org/#website"
            },
            "about": {
                "@id": "https://my.clevelandclinic.org/giving#philanthropy"
            },
            "description": "Your gift to Cleveland Clinic will help transform healthcare for our patients, our communities and our world."
        },
        {
            "@type": "Organization",
            "@id": "https://my.clevelandclinic.org/giving#philanthropy",
            "name": "Cleveland Clinic Philanthropy",
            "parentOrganization": {
                "@id": "https://my.clevelandclinic.org/#organization"
            },
            "url": "https://my.clevelandclinic.org/giving",
            "logo": "https://my.clevelandclinic.org/assets/img/cleveland-clinic-logo.png",
            "contactPoint": {
                "@type": "ContactPoint",
                "telephone": "+1-216-444-1243",
                "contactType": "Philanthropy Office"
            },
            "potentialAction": {
                "@type": "DonateAction",
                "target": {
                    "@type": "EntryPoint",
                    "urlTemplate": "https://my.clevelandclinic.org/giving",
                    "actionPlatform": [
                        "http://schema.org/DesktopWebPlatform",
                        "http://schema.org/MobileWebPlatform"
                    ]
                },
                "recipient": {
                    "@id": "https://my.clevelandclinic.org/#organization"
                }
            }
        },
        {
            "@type": "Event",
            "@id": "https://my.clevelandclinic.org/giving#velosano",
            "name": "VeloSano Bike to Cure",
            "description": "VeloSano turns collective action against cancer into lifesaving research at Cleveland Clinic.",
            "organizer": {
                "@id": "https://my.clevelandclinic.org/giving#philanthropy"
            }
        },
        {
            "@type": "MedicalOrganization",
            "@id": "https://my.clevelandclinic.org/#organization",
            "name": "Cleveland Clinic",
            "url": "https://my.clevelandclinic.org/"
        }
    ]
}
https://my.clevelandclinic.org/providers35 / 100
Current Structured Data
[
    {
        "@context": "http://schema.org",
        "@type": "MedicalOrganization",
        "alternateName": "Cleveland Clinic",
        "areaServed": "http://www.wikidata.org/entity/Q13780930",
        "description": "Cleveland Clinic, a non-profit academic medical center, provides clinical and hospital care and is a leader in research, education and health information, and regarded as the best and highest-performing hospital in the world.",
        "foundingDate": "1921-02-28",
        "legalName": "Cleveland Clinic",
        "name": "Cleveland Clinic",
        "numberOfEmployees": {
            "@type": "QuantitativeValue",
            "value": "65000"
        },
        "image": "https://assets.clevelandclinic.org/transform/1bc1ff31-3cbc-4976-9ddf-9bc85e0877eb/Cleveland-Clinic-Logo-Web",
        "sameAs": [
            "https://en.wikipedia.org/wiki/Cleveland_Clinic",
            "https://www.linkedin.com/company/cleveland-clinic",
            "https://www.instagram.com/clevelandclinic",
            "https://twitter.com/ClevelandClinic",
            "https://www.youtube.com/user/ClevelandClinic",
            "https://www.facebook.com/ClevelandClinic"
        ],
        "url": "https://clevelandclinic.org"
    }
]
Page Analysis
This is a functional Directory and Search interface page, acting as the entry point for Cleveland Clinic's 'Find a Provider' service. The primary entity is the Search Tool (a SearchAction) and the directory itself (a CollectionPage). The page content emphasizes filtering by specialty and location, and highlights the 'Physician Ratings' system as a trust anchor. Secondary entities include the network of Providers and the parent Organization.
Schema Assessment
The current schema is a generic 'MedicalOrganization' boilerplate. While technically valid, it is semantically incorrect for this page. It describes the Cleveland Clinic as a whole (using a home-page style about snippet) but completely ignores the functional nature of the 'Find a Provider' tool. It lacks a SearchAction, does not define the page as a CollectionPage, and contains no connectivity to the specific provider entities or rating systems mentioned in the text.
Entity Connectivity Gaps
1. Functional Gap: Missing 'SearchAction' which is the primary utility of this page. AI cannot identify this as a queryable endpoint. 2. Type Mismatch: The page is a directory/tool, but schema claims it is an organization description. 3. Missing AggregateRating: The content explicitly mentions 'Physician Ratings at Cleveland Clinic' as a key trust signal, but no schema supports this claim. 4. Broken @id Persistence: The extracted schema uses 'https://clevelandclinic.org' for the URL but doesn't reference the established 'https://my.clevelandclinic.org/#organization' identifier mentioned in the Site Context. 5. Service Linkage: The 'Find a Provider' capability is not linked to the 'Appointment Scheduling' (ScheduleAction) service identified in the site-wide audit.
AI Retrieval Impact
AI retrieval systems (like ChatGPT or Google SGE) will treat this as a general 'About' page for Cleveland Clinic rather than a functional tool to find doctors. Because the search functionality is not programmatically declared, LLMs cannot reliably guide users to 'Search for heart pain specialists at Cleveland Clinic' through a structured action. Furthermore, the 'trust' signal of physician ratings is invisible to the knowledge graph, reducing the E-E-A-T score of the provider network.
Recommendation
Transform the schema from a static Organization block into a 'CollectionPage' that hosts a 'SearchAction'. Explicitly link this page to the parent Organization using the site-wide @id 'https://my.clevelandclinic.org/#organization'. Define the 'Find a Provider' tool as a Service provided by the organization. Include a 'potentialAction' of 'SearchAction' with a URL template for the search query. This schema is a recommendation and should be reviewed before implementation.
Score Justification
The score of 35 is assigned because while the schema is technically valid and provides basic organization data, it is a 'mismatched intent' implementation. It fails to describe the actual entity (the Search Tool/Directory) and misses all opportunities for cross-page connectivity identified in the site context.
Recommended Structured Data
{
    "@context": "https://schema.org",
    "@type": "CollectionPage",
    "@id": "https://my.clevelandclinic.org/providers#webpage",
    "name": "Find a Provider | Cleveland Clinic",
    "description": "Discover the find a provider tool available at Cleveland Clinic. Browse all Cleveland Clinic providers in one place and find the right one for you.",
    "url": "https://my.clevelandclinic.org/providers",
    "isPartOf": {
        "@id": "https://my.clevelandclinic.org/#website"
    },
    "publisher": {
        "@id": "https://my.clevelandclinic.org/#organization"
    },
    "mainEntity": {
        "@type": "MedicalWebPage",
        "@id": "https://my.clevelandclinic.org/providers#maintool",
        "name": "Cleveland Clinic Provider Directory",
        "potentialAction": {
            "@type": "SearchAction",
            "target": {
                "@type": "EntryPoint",
                "urlTemplate": "https://my.clevelandclinic.org/providers?q={search_term_string}"
            },
            "query-input": "required name=search_term_string"
        }
    },
    "about": {
        "@id": "https://my.clevelandclinic.org/#organization"
    },
    "mentions": [
        {
            "@type": "Service",
            "name": "Physician Ratings and Reviews",
            "description": "Cleveland Clinic's verified rating system for health care providers."
        },
        {
            "@type": "MedicalAudience",
            "audienceType": "Patients"
        }
    ]
}
https://my.clevelandclinic.org/services15 / 100
Current Structured Data
No JSON-LD structured data found on this page.
Page Analysis
This page is a 'Service Index' or 'Service Hub' for the entire Cleveland Clinic health system. It acts as a central directory for Adult and Pediatric clinical services, Telehealth (Virtual Care), Second Opinions, and Administrative Services (Billing/Insurance). The primary entity is the Cleveland Clinic Service Catalog, which serves as a gateway to dozens of specialized medical departments and regional healthcare offerings.
Schema Assessment
The extracted schema is empty. There is zero structured data on a page that defines the core business offerings of one of the world's largest healthcare providers. The page exists only as a visual 'document' for humans, offering no machine-readable signals for AI to index the clinic's capabilities.
Entity Connectivity Gaps
The gap is total. 1. The page lists 50+ medical services (e.g., 'Heart Care', 'Neurology') as flat text strings rather than 'MedicalService' entities linked to their respective departments. 2. There is no connection to the Root Organization (@id: https://my.clevelandclinic.org/#organization). 3. Virtual Care and Second Opinions are described but not linked to the 'MedicalWebPage' or 'Service' entities identified in the Site Context. 4. Regional availability (Ohio, Florida, Nevada, etc.) is listed as text but lacks 'areaServed' or 'location' relationships to the regional entities defined elsewhere in the site architecture. 5. The 'Request an Appointment' call-to-action is not defined as a 'ScheduleAction' or 'PotentialAction'.
AI Retrieval Impact
AI systems and LLMs cannot programmatically extract the relationship between Cleveland Clinic and its clinical offerings from this page. Without a structured 'OfferCatalog', search engines cannot confidently map specific medical conditions or treatments to this provider. The 'chain of trust' is broken because the services are not attributed to the verified parent organization. This results in reduced visibility in AI Overviews and SGE when users search for 'Cleveland Clinic adult services' or 'pediatric care at Cleveland Clinic'.
Recommendation
Implement a 'CollectionPage' schema that contains a 'Service' hub linked to a comprehensive 'hasOfferCatalog'. Each service listed (e.g., Heart Care) should be a 'MedicalService' entity with an '@id' reflecting its specific service page. Explicitly link the 'provider' property to the site-wide organization '@id'. Declare 'areaServed' for each regional contact listed to connect this page to the Florida, Nevada, and International entities defined in the site context. This schema is a recommendation and should be reviewed before implementation.
Score Justification
A score of 15 is assigned because the page contains no structured data whatsoever. Despite being a critical 'hub' page that should define the entity relationships for the entire organization's service line, it offers zero machine-readability, representing a massive missed opportunity for Model Context Optimization.
Recommended Structured Data
{"@context":"https://schema.org","@graph":[{"@type":"CollectionPage","@id":"https://my.clevelandclinic.org/services#webpage","url":"https://my.clevelandclinic.org/services","name":"Our Services | Cleveland Clinic","description":"Discover more about the different institutes and departments that make up Cleveland Clinic, as well as all of the services they provide.","publisher":{"@id":"https://my.clevelandclinic.org/#organization"},"mainEntity":{"@type":"Service","@id":"https://my.clevelandclinic.org/services#mainService","name":"Cleveland Clinic Medical Services","provider":{"@id":"https://my.clevelandclinic.org/#organization"},"hasOfferCatalog":{"@type":"OfferCatalog","name":"Clinical Service Catalog","itemListElement":[{"@type":"OfferCatalog","name":"Adult Services","itemListElement":[{"@type":"MedicalService","name":"Heart Care","url":"https://my.clevelandclinic.org/departments/heart"},{"@type":"MedicalService","name":"Cancer Care","url":"https://my.clevelandclinic.org/departments/cancer"}]},{"@type":"OfferCatalog","name":"Pediatric Services","itemListElement":[{"@type":"MedicalService","name":"Pediatric Primary Care","url":"https://my.clevelandclinic.org/departments/pediatrics"}]}]}},{"@type":"MedicalWebPage","@id":"https://my.clevelandclinic.org/online-services/virtual-visits#service","name":"Virtual Care","description":"Virtual visits allow you to see a provider without heading into one of our physical locations.","isPartOf":{"@id":"https://my.clevelandclinic.org/services#webpage"}},{"@type":"ScheduleAction","target":{"@type":"EntryPoint","urlTemplate":"https://my.clevelandclinic.org/webappointment","actionPlatform":["http://schema.org/DesktopWebPlatform","http://schema.org/MobileWebPlatform"]},"object":{"@id":"https://my.clevelandclinic.org/services#mainService"},"agent":{"@id":"https://my.clevelandclinic.org/#organization"}}]}
https://my.clevelandclinic.org/webappointment10 / 100
Current Structured Data
No JSON-LD structured data found on this page.
Page Analysis
The page is a high-intent transactional hub identified as a 'Request an Appointment' or 'Appointment Scheduling' page. Its primary function is to facilitate a conversion (ScheduleAction). Based on the content, the primary entity is the Cleveland Clinic appointment service, and secondary entities include the parent organization (Cleveland Clinic), global and local facilities, and the patients (audience). It serves as the bridge between clinical services (found on other pages) and the actual medical consultation.
Schema Assessment
CRITICAL FAILURE: The extracted schema is empty. There is zero JSON-LD structured data present. For a page that functions as the primary intake point for one of the world's largest health systems, this represents a total vacuum of machine-readable data. AI systems cannot programmatically identify this as the official scheduling endpoint; they must rely on fragile text-scraping rather than verified entity-action signals.
Entity Connectivity Gaps
The absence of schema creates several severe gaps: 1. Action Identification: There is no 'ScheduleAction' or 'PotentialAction' defined, meaning AI agents cannot reliably trigger a booking process. 2. Entity Disconnect: The page does not reference the site-wide organization @id (https://my.clevelandclinic.org/#organization), making it an 'isolated node' that isn't programmatically connected to the Cleveland Clinic brand. 3. Service Mapping: The page mentions 'expert care in person or online' but lacks structured links to the 'Virtual Visits' or 'Global Patient Services' entities defined elsewhere in the site architecture. 4. Trust Signals: No metadata regarding the organization's contact points or operating hours for scheduling is provided in a structured format.
AI Retrieval Impact
This page is invisible to the 'Action Layer' of modern AI. While an LLM might find the URL via search, it cannot 'understand' the page as a functional tool. This prevents the site from being utilized by voice assistants or AI agents that perform task-oriented actions (e.g., 'Book an appointment at Cleveland Clinic'). It also weakens the site's overall E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness) because the critical 'chain of trust' from informational content (Health Library) to action (Booking) is broken at the machine level.
Recommendation
1. Implement a 'ContactPage' type as the primary container. 2. Define a 'ScheduleAction' as a 'potentialAction' of the Cleveland Clinic organization entity. 3. Explicitly link this page to the root organization using the @id identified in the Site Context (https://my.clevelandclinic.org/#organization). 4. Use 'EntryPoint' schema to describe how an AI agent should interact with the scheduling form. 5. Include 'ContactPoint' data for different regions (Ohio, Florida, International) to provide structured alternatives to the web form. *This schema is a recommendation and should be reviewed before implementation.*
Score Justification
A score of 10 is assigned because the page contains no structured data whatsoever. Despite its high importance to the business and user journey, it offers zero machine-readable connectivity, which is a significant optimization failure.
Recommended Structured Data
{
    "@context": "https://schema.org",
    "@graph": [
        {
            "@type": "ContactPage",
            "@id": "https://my.clevelandclinic.org/webappointment#webpage",
            "url": "https://my.clevelandclinic.org/webappointment",
            "name": "Request an Appointment | Cleveland Clinic",
            "description": "Official appointment request portal for Cleveland Clinic. Schedule in-person or virtual visits with expert providers.",
            "isPartOf": {
                "@id": "https://my.clevelandclinic.org/#website"
            },
            "about": {
                "@id": "https://my.clevelandclinic.org/#organization"
            },
            "mainEntity": {
                "@type": "MedicalOrganization",
                "@id": "https://my.clevelandclinic.org/#organization",
                "name": "Cleveland Clinic",
                "potentialAction": {
                    "@type": "ScheduleAction",
                    "target": {
                        "@type": "EntryPoint",
                        "urlTemplate": "https://my.clevelandclinic.org/webappointment",
                        "actionPlatform": [
                            "http://schema.org/DesktopWebPlatform",
                            "http://schema.org/MobileWebPlatform"
                        ]
                    },
                    "name": "Request an Appointment",
                    "result": {
                        "@type": "MedicalReservation"
                    }
                }
            },
            "breadcrumb": {
                "@id": "https://my.clevelandclinic.org/webappointment#breadcrumb"
            }
        },
        {
            "@type": "WebSite",
            "@id": "https://my.clevelandclinic.org/#website",
            "url": "https://my.clevelandclinic.org/",
            "publisher": {
                "@id": "https://my.clevelandclinic.org/#organization"
            }
        }
    ]
}
https://my.clevelandclinic.org/health-essentials-newsletter10 / 100
Current Structured Data
No JSON-LD structured data found on this page.
Page Analysis
The page is a dedicated subscription landing page for the 'Health Essentials' newsletter. From a content perspective, it serves as an entry point for users to join an audience for Cleveland Clinic's health and wellness content. The primary entity is the 'Health Essentials' newsletter (a Periodical/Publication), and the parent entity is the Cleveland Clinic organization. Secondary entities include specific health topics (fitness, wellness) and related media like the Health Essentials podcast mentioned in the site context.
Schema Assessment
The extracted schema is an empty array. There is zero structured data present on the page. AI systems see only a collection of text strings and an image without any programmatic way to identify that this is an official subscription channel, who the publisher is, or what the 'Health Essentials' brand represents in the broader Cleveland Clinic ecosystem.
Entity Connectivity Gaps
The most critical gap is the total absence of a 'Periodical' or 'Newsletter' entity definition. Content-wise, this page requires a 'WebPage' type that identifies its 'about' subject as the Health Essentials newsletter. Per the Site Context, it fails to reference the root organization @id (https://my.clevelandclinic.org/#organization), creating a broken chain of trust. There is no 'SubscribeAction' defined, meaning LLMs cannot identify the primary intent of the page (subscription) through structured data. Furthermore, there is no cross-linkage to the 'Health Essentials Podcast' or 'Health Library' entities identified in the site-wide analysis, leaving this page as an isolated node.
AI Retrieval Impact
AI retrieval systems (SGE, LLMs, Knowledge Graphs) cannot verify the authenticity of this newsletter or link it to the Cleveland Clinic's authority. Without a 'publisher' property linking back to the parent organization @id, the content lacks the E-E-A-T signals required for high-confidence health recommendations. In AI-driven search, the newsletter cannot be programmatically associated with health topics it covers, leading to reduced visibility in 'stay informed' or 'health tips' discovery queries.
Recommendation
Implement a connected JSON-LD graph. Define the page as a 'WebPage' with the primary entity being a 'Periodical' named 'Health Essentials'. Crucially, link this Periodical to the Cleveland Clinic parent organization using the global @id 'https://my.clevelandclinic.org/#organization' as the 'publisher'. Add a 'potentialAction' of type 'SubscribeAction' to define the page's purpose. Finally, use 'relatedLink' or 'sameAs' to connect this newsletter to the Health Essentials Podcast and the Health Library to solidify the knowledge graph spoke. This schema is a recommendation and should be reviewed before implementation.
Score Justification
The page receives a score of 10 because it lacks any structured data whatsoever. Despite being a critical conversion point for the brand's digital presence, it provides no machine-readable context, falling well below the requirement for AI-readiness.
Recommended Structured Data
{
    "@context": "https://schema.org",
    "@graph": [
        {
            "@type": "WebPage",
            "@id": "https://my.clevelandclinic.org/health-essentials-newsletter#webpage",
            "url": "https://my.clevelandclinic.org/health-essentials-newsletter",
            "name": "Sign Up for Health Essentials | Cleveland Clinic",
            "isPartOf": {
                "@id": "https://my.clevelandclinic.org/#website"
            },
            "publisher": {
                "@id": "https://my.clevelandclinic.org/#organization"
            },
            "about": {
                "@id": "https://my.clevelandclinic.org/health-essentials-newsletter#periodical"
            },
            "description": "Sign up for our Health Essentials newsletter to get fitness, health and wellness tips sent to you weekly."
        },
        {
            "@type": "Periodical",
            "@id": "https://my.clevelandclinic.org/health-essentials-newsletter#periodical",
            "name": "Health Essentials",
            "publisher": {
                "@id": "https://my.clevelandclinic.org/#organization"
            },
            "audience": {
                "@type": "Audience",
                "audienceType": "Health-conscious individuals"
            },
            "sameAs": [
                "https://my.clevelandclinic.org/podcasts/health-essentials"
            ],
            "potentialAction": {
                "@type": "SubscribeAction",
                "target": {
                    "@type": "EntryPoint",
                    "urlTemplate": "https://my.clevelandclinic.org/health-essentials-newsletter"
                }
            }
        },
        {
            "@type": "Organization",
            "@id": "https://my.clevelandclinic.org/#organization",
            "name": "Cleveland Clinic",
            "url": "https://my.clevelandclinic.org/"
        }
    ]
}
https://my.clevelandclinic.org/podcasts/health-essentials5 / 100
Current Structured Data
No JSON-LD structured data found on this page.
Page Analysis
The page functions as a PodcastSeries landing page and a content hub for the 'Health Essentials' podcast. The primary entity is the podcast series itself, published by Cleveland Clinic. Secondary entities include specific medical experts (Dr. Jorge Gutierrez-Aceves, Dr. Jared Harp, Dr. Lauren Wichman, Dr. Ronan Factora) and medical conditions/topics (Chronic Kidney Disease, Cannabis Use Disorder, Sports Medicine, Nutrition). The content implies a 'Host/Guest' relationship between the medical experts and the episodes, and a 'Publisher' relationship between the Organization and the Series.
Schema Assessment
The extracted schema is entirely empty ([ ]). There is no JSON-LD present to define the PodcastSeries, the individual episodes, the hosts, or the connection to the parent organization. This is a total architectural void for AI systems seeking to verify health-related expertise and authorship.
Entity Connectivity Gaps
The most significant gap is the lack of a PodcastSeries entity linked to the Cleveland Clinic via @id. Crucially, the medical experts listed (e.g., Dr. Jorge Gutierrez-Aceves) are mentioned as flat text strings rather than Person entities. This breaks the link to their professional profiles identified in the Site Context. There are no PodcastEpisode entities, meaning the individual recordings, their subjects (MedicalCondition), and their dates (datePublished) are invisible to knowledge graphs. The 'More Podcasts' section identifies further series (Butts & Guts, Love Your Heart) which should be linked as related creative works.
AI Retrieval Impact
AI retrieval systems (including Google SGE and LLMs) cannot programmatically verify that this health advice is authored by credentialed medical professionals. The 'Expertise' and 'Authoritativeness' (E-E-A-T) signals are severely weakened because the chain of trust between the doctor's provider profile and their podcast advice is broken. This content is unlikely to appear in 'Listen Now' rich results or be cited as a structured authoritative source for health queries in AI-driven search.
Recommendation
Implement a high-fidelity PodcastSeries schema. Define the Cleveland Clinic as the 'publisher' using the site-wide @id 'https://my.clevelandclinic.org/#organization'. For each episode, create a PodcastEpisode entity featuring the 'actor' (the doctor) with a persistent @id linking to their professional staff page (e.g., https://my.clevelandclinic.org/staff/jorge-gutierrez-aceves#person). Use the 'about' property to link episodes to specific MedicalCondition or MedicalSpecialty entities. Disclaimer: this schema is a recommendation and should be reviewed before implementation.
Score Justification
A score of 5 is assigned because there is a total absence of structured data on a page that is critical for establishing E-E-A-T. While the content is rich in expert entities, none are machine-readable, rendering the semantic connectivity non-existent.
Recommended Structured Data
{
    "@context": "https://schema.org",
    "@type": "PodcastSeries",
    "@id": "https://my.clevelandclinic.org/podcasts/health-essentials#podcast",
    "name": "Health Essentials Podcast",
    "description": "Tune in for trusted advice on health, wellness and nutrition for the whole family from Cleveland Clinic experts.",
    "url": "https://my.clevelandclinic.org/podcasts/health-essentials",
    "publisher": {
        "@id": "https://my.clevelandclinic.org/#organization"
    },
    "hasPart": [
        {
            "@type": "PodcastEpisode",
            "name": "Are You Taking Care of Your Kidneys?",
            "description": "Urologist Dr. Jorge Gutierrez-Aceves discusses chronic kidney disease and essential organ health.",
            "datePublished": "2026-04-16",
            "actor": {
                "@type": "Person",
                "@id": "https://my.clevelandclinic.org/staff/jorge-gutierrez-aceves#person",
                "name": "Jorge Gutierrez-Aceves, MD",
                "jobTitle": "Urologist"
            },
            "about": {
                "@type": "MedicalCondition",
                "name": "Chronic Kidney Disease",
                "@id": "https://my.clevelandclinic.org/health/diseases/15096-kidney-disease-chronic"
            }
        },
        {
            "@type": "PodcastEpisode",
            "name": "What Is Cannabis Use Disorder?",
            "description": "Addiction psychiatrist Jared Harp explains cannabis use disorder (CUD) and treatment options.",
            "datePublished": "2026-04-15",
            "actor": {
                "@type": "Person",
                "@id": "https://my.clevelandclinic.org/staff/jared-harp#person",
                "name": "Jared Harp, DO",
                "jobTitle": "Addiction Psychiatrist"
            },
            "about": {
                "@type": "MedicalCondition",
                "name": "Cannabis Use Disorder"
            }
        },
        {
            "@type": "PodcastEpisode",
            "name": "Sports Essentials | Lift Your Performance",
            "description": "Meet co-host Dr. Lauren Wichman, a sports medicine specialist.",
            "datePublished": "2026-04-13",
            "actor": {
                "@type": "Person",
                "@id": "https://my.clevelandclinic.org/staff/lauren-wichman#person",
                "name": "Lauren Wichman, MD",
                "jobTitle": "Sports Medicine Specialist"
            }
        }
    ]
}
https://my.clevelandclinic.org/staff25 / 100
Current Structured Data
[
    {
        "@context": "http://schema.org",
        "@type": "MedicalOrganization",
        "alternateName": "Cleveland Clinic",
        "areaServed": "http://www.wikidata.org/entity/Q13780930",
        "description": "Cleveland Clinic, a non-profit academic medical center, provides clinical and hospital care and is a leader in research, education and health information, and regarded as the best and highest-performing hospital in the world.",
        "foundingDate": "1921-02-28",
        "legalName": "Cleveland Clinic",
        "name": "Cleveland Clinic",
        "numberOfEmployees": {
            "@type": "QuantitativeValue",
            "value": "65000"
        },
        "image": "https://assets.clevelandclinic.org/transform/1bc1ff31-3cbc-4976-9ddf-9bc85e0877eb/Cleveland-Clinic-Logo-Web",
        "sameAs": [
            "https://en.wikipedia.org/wiki/Cleveland_Clinic",
            "https://www.linkedin.com/company/cleveland-clinic",
            "https://www.instagram.com/clevelandclinic",
            "https://twitter.com/ClevelandClinic",
            "https://www.youtube.com/user/ClevelandClinic",
            "https://www.facebook.com/ClevelandClinic"
        ],
        "url": "https://clevelandclinic.org"
    }
]
Page Analysis
This page functions as the primary search portal and directory for the Cleveland Clinic provider network ('Find a Provider'). Its purpose is to facilitate user discovery of medical specialists via name, specialty, or location. From an entity perspective, this is a MedicalWebPage containing a SearchAction, representing a Directory Service provided by the Cleveland Clinic Organization.
Schema Assessment
The current JSON-LD is a static, boilerplate 'MedicalOrganization' block. While accurate at a high level, it describes the entire institution rather than the specific entity of this page. It lacks the 'SearchAction' required for AI to recognize this as a functional tool and fails to provide a persistent @id for the organization that matches the 'Hub' architecture described in the Site Context. It is an isolated node that describes who the company is, but not what this page does.
Entity Connectivity Gaps
1. Page Type Mismatch: The page is a directory/tool, but the schema only defines a business. 2. Missing Action: There is no 'SearchAction' defined, making the search functionality invisible to AI agents. 3. Missing Specialist Linkage: The content mentions 'specialists' and 'physicians' as the objects of the search, but these are not declared as expected results or related entities. 4. Fragmented Identity: It does not use the recommended root identifier (https://my.clevelandclinic.org/#organization) found in the site context, preventing cross-page entity merging. 5. Service-Location Disconnect: The page mentions searching by location, but the schema does not link to the 'Global Locations' or 'Ohio Locations' entities identified in the site audit.
AI Retrieval Impact
AI systems and LLMs will treat this page as a generic 'About Us' or 'Contact' variant rather than a functional medical directory. This reduces the likelihood of the site being used as a source for 'Find a doctor at...' or 'Who are the cardiologists at...' queries. Knowledge graph builders will fail to connect the 'Find a Provider' tool to the actual Physician profiles (Person entities) on the site, creating a dead-end in the authority chain.
Recommendation
Transform the schema from a static organization block to a functional MedicalWebPage. 1. Use @id: 'https://my.clevelandclinic.org/#organization' to link this page to the site-wide parent entity. 2. Add a 'potentialAction' of type 'SearchAction' with a target URL template for the provider search. 3. Define the mainEntity as a 'Service' representing the 'Provider Directory'. 4. Explicitly link to the 'Specialist' and 'MedicalSpecialty' types to define the scope of the search. 5. Include 'publishingPrinciples' linking to policy pages to address the 'broken chain of trust' identified in the site audit. Disclaimer: this schema is a recommendation and should be reviewed before implementation.
Score Justification
The score is low (25) because the schema provides no information about the page's actual content or functionality. It is valid JSON-LD but fails as a semantic descriptor for a directory/search tool, ignoring all site-wide context and entity relationships.
Recommended Structured Data
{
    "@context": "https://schema.org",
    "@type": "MedicalWebPage",
    "@id": "https://my.clevelandclinic.org/staff#webpage",
    "url": "https://my.clevelandclinic.org/staff",
    "name": "Find a Provider | Cleveland Clinic",
    "description": "Search Cleveland Clinic\u2019s trusted network of primary care doctors and specialists.",
    "breadcrumb": {
        "@id": "https://my.clevelandclinic.org/staff#breadcrumb"
    },
    "about": {
        "@type": "Service",
        "@id": "https://my.clevelandclinic.org/staff#directoryService",
        "name": "Cleveland Clinic Physician Directory",
        "serviceType": "Medical Provider Search",
        "provider": {
            "@id": "https://my.clevelandclinic.org/#organization"
        }
    },
    "potentialAction": {
        "@type": "SearchAction",
        "target": {
            "@type": "EntryPoint",
            "urlTemplate": "https://my.clevelandclinic.org/staff?q={search_term_string}"
        },
        "query-input": "required name=search_term_string"
    },
    "publisher": {
        "@id": "https://my.clevelandclinic.org/#organization"
    },
    "mainEntity": {
        "@type": "MedicalOrganization",
        "@id": "https://my.clevelandclinic.org/#organization",
        "name": "Cleveland Clinic",
        "url": "https://my.clevelandclinic.org",
        "logo": "https://assets.clevelandclinic.org/transform/1bc1ff31-3cbc-4976-9ddf-9bc85e0877eb/Cleveland-Clinic-Logo-Web",
        "sameAs": [
            "https://en.wikipedia.org/wiki/Cleveland_Clinic",
            "https://www.linkedin.com/company/cleveland-clinic",
            "https://twitter.com/ClevelandClinic"
        ]
    }
}
https://my.clevelandclinic.org/research10 / 100
Current Structured Data
No JSON-LD structured data found on this page.
Page Analysis
This is a high-level Research Hub page representing Cleveland Clinic's scientific and clinical research enterprise. The page identifies as the central repository for 'Cleveland Clinic Research', which encompasses the Lerner Research Institute and the Global Center for Pathogen & Human Health Research. Primary entities include the research organization itself, while secondary entities include the State of Ohio (partner), Otto Glasser (historical figure), and various research disciplines (genomics, immuno-oncology, quantum computing). The content implies a hierarchical relationship where Cleveland Clinic is the parent organization to a network of specialized research institutes.
Schema Assessment
The extracted schema is empty. There is zero structured data present on a critical pillar page of the Cleveland Clinic domain. From an AI-readiness perspective, this is a 'dark node' in the knowledge graph. There are no @type declarations to define this as a ResearchOrganization, no @id to facilitate connectivity, and no machine-readable relationships to the parent Cleveland Clinic entity or the sub-institutes it describes.
Entity Connectivity Gaps
The most significant gap is the total absence of a ResearchOrganization entity. Based on site context, this page should serve as the authoritative definition for 'Cleveland Clinic Research' and 'Lerner Research Institute'. Missing relationships include: 1. parentOrganization link to the Cleveland Clinic root @id. 2. subOrganization links to Lerner Research Institute and the Global Center for Pathogen & Human Health Research. 3. memberOf relationships to the Cleveland Innovation District. 4. mentions/knowsAbout properties for clinical areas like 'Immuno-oncology' or 'Quantum Computing'. 5. Historical attribution for Dr. Otto Glasser as an influential person associated with the organization's history.
AI Retrieval Impact
Because there is no structured data, AI systems (LLMs, Knowledge Graph builders, SGE) cannot programmatically verify the relationship between Cleveland Clinic and its research arms. This page fails to contribute to the site's E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness) at a machine level. Retrieval systems cannot confidently identify this as the 'official' research hub, leading to lower retrieval confidence when users query for 'Cleveland Clinic clinical trials' or 'Lerner Research Institute leadership'. The 'chain of trust' identified in the Site Context is broken at this hub.
Recommendation
Implement a ResearchOrganization schema as the primary entity for this page, with a persistent @id (e.g., https://my.clevelandclinic.org/research/#research). Explicitly define the parentOrganization as the main Cleveland Clinic entity using its site-wide @id. Use subOrganization properties to link to the specific institutes mentioned (Lerner, Global Center). Include a 'funder' property for the Ohio/JobsOhio relationship to ground the entity in a regional economic context. Finally, ensure this page is referenced as the 'publisher' or 'creator' on all health library and podcast pages to establish the research-backed authority of that content. [Disclaimer: this schema is a recommendation and should be reviewed before implementation]
Score Justification
The score is 10 because there is no schema present. While the content is rich and high-quality, it is invisible to semantic crawlers. A page of this importance acting as a 'hub' in the site architecture must have high-fidelity connectivity to anchor the rest of the site's expert content.
Recommended Structured Data
{
    "@context": "https://schema.org",
    "@graph": [
        {
            "@type": "ResearchOrganization",
            "@id": "https://my.clevelandclinic.org/research/#research",
            "name": "Cleveland Clinic Research",
            "description": "Home to basic, translational and clinical research at Cleveland Clinic, focused on challenging the status quo for patient care.",
            "url": "https://my.clevelandclinic.org/research",
            "parentOrganization": {
                "@type": "Organization",
                "@id": "https://my.clevelandclinic.org/#organization"
            },
            "subOrganization": [
                {
                    "@type": "ResearchOrganization",
                    "@id": "https://my.clevelandclinic.org/research/#lerner",
                    "name": "Lerner Research Institute"
                },
                {
                    "@type": "ResearchOrganization",
                    "@id": "https://my.clevelandclinic.org/research/#pathogen-center",
                    "name": "Global Center for Pathogen & Human Health Research"
                }
            ],
            "knowsAbout": [
                "Precision Medicine",
                "Genomic Medicine",
                "Population Health",
                "Immuno-oncology",
                "Quantum Computing"
            ],
            "location": {
                "@type": "Place",
                "name": "Cleveland, Ohio"
            },
            "funder": [
                {
                    "@type": "GovernmentOrganization",
                    "name": "State of Ohio"
                },
                {
                    "@type": "Organization",
                    "name": "JobsOhio"
                }
            ]
        },
        {
            "@type": "WebPage",
            "@id": "https://my.clevelandclinic.org/research",
            "url": "https://my.clevelandclinic.org/research",
            "name": "Research & Innovations | Cleveland Clinic",
            "isPartOf": {
                "@id": "https://my.clevelandclinic.org/#website"
            },
            "about": {
                "@id": "https://my.clevelandclinic.org/research/#research"
            }
        }
    ]
}
https://my.clevelandclinic.org/clinical-trials10 / 100
Current Structured Data
No JSON-LD structured data found on this page.
Page Analysis
This page serves as a high-level hub and directory for Cleveland Clinic's Clinical Trials. It is a 'CollectionPage' and 'MedicalWebPage' that functions as the gateway to over 8,000 research studies. The primary entity is the Cleveland Clinic Clinical Trial program, which is intrinsically linked to the Lerner Research Institute and the parent Cleveland Clinic organization. The page content highlights medical specialties (Cancer, Heart, etc.), regulatory oversight (Institutional Review Board), and a 'SearchAction' capability for prospective participants.
Schema Assessment
The extracted schema is empty ([]). There is a complete absence of structured data. From an AI-readiness perspective, this is a total blackout; the page relies entirely on unstructured text parsing, which fails to establish the high-stakes 'chain of trust' required for medical research entities.
Entity Connectivity Gaps
The most critical gap is the lack of a 'MedicalStudy' collection or 'SearchAction' declaration. Specifically: 1. No connection to the parent organization (@id: https://my.clevelandclinic.org/#organization) or the Lerner Research Institute. 2. The Institutional Review Board (IRB) is mentioned as a safety anchor but is not defined as an 'Organization' providing oversight. 3. The search tool is a critical user action but lacks a 'SearchAction' schema, making the discovery of specific trials invisible to AI agents. 4. Medical specialties (Dermatology, Oncology, etc.) are listed as flat text rather than 'MedicalSpecialty' entities linked to the study offerings.
AI Retrieval Impact
AI systems and Large Language Models (LLMs) cannot programmatically verify Cleveland Clinic's authority in clinical research via this page. The lack of structured E-E-A-T signals (like IRB oversight and institutional affiliation) reduces retrieval confidence for 'clinical trials near me' or 'experimental treatments for [condition]' queries. Without @id connectivity, AI agents cannot bridge the gap between a patient's medical condition and the research opportunities available at this institution.
Recommendation
Implement a 'CollectionPage' as the primary type, explicitly defining the Cleveland Clinic parent organization as the 'publisher' and 'provider'. Use '@id' to link to the 'ResearchOrganization' (Lerner Research Institute) identified in the site context. Add a 'SearchAction' targeting the clinical trials search engine to signal programmatic accessibility. Declare the 'InstitutionalReviewBoard' as a 'member' or 'funder' entity to establish regulatory trust. This schema is a recommendation and should be reviewed before implementation.
Score Justification
The score is 10 because the page provides zero structured data. While the content is rich and authoritative, it is invisible to knowledge graphs. The single-digit/low-teen score reflects a 'broken chain of trust' where the institution's expertise is not machine-readable.
Recommended Structured Data
{
    "@context": "https://schema.org",
    "@graph": [
        {
            "@type": "CollectionPage",
            "@id": "https://my.clevelandclinic.org/clinical-trials#webpage",
            "url": "https://my.clevelandclinic.org/clinical-trials",
            "name": "Clinical Trials at Cleveland Clinic",
            "isPartOf": {
                "@id": "https://my.clevelandclinic.org/#website"
            },
            "about": {
                "@type": "MedicalStudy",
                "name": "Cleveland Clinic Clinical Research Program",
                "description": "Over 8,000 clinical trials focused on developing new treatments and understanding medical conditions."
            },
            "mainEntity": {
                "@type": "MedicalOrganization",
                "@id": "https://my.clevelandclinic.org/#organization",
                "name": "Cleveland Clinic",
                "parentOrganization": {
                    "@type": "ResearchOrganization",
                    "name": "Lerner Research Institute",
                    "@id": "https://my.clevelandclinic.org/research#organization"
                }
            },
            "potentialAction": {
                "@type": "SearchAction",
                "target": {
                    "@type": "EntryPoint",
                    "urlTemplate": "https://my.clevelandclinic.org/clinical-trials?q={search_term_string}"
                },
                "query-input": "required name=search_term_string"
            },
            "mentions": [
                {
                    "@type": "Organization",
                    "name": "Institutional Review Board",
                    "description": "Panel of patient safety advocates that reviews clinical trials to ensure safety and rights are protected."
                },
                {
                    "@type": "MedicalSpecialty",
                    "name": "Oncology"
                },
                {
                    "@type": "MedicalSpecialty",
                    "name": "Cardiology"
                },
                {
                    "@type": "MedicalSpecialty",
                    "name": "Neurology"
                }
            ]
        }
    ]
}
https://my.clevelandclinic.org/florida/locations15 / 100
Current Structured Data
No JSON-LD structured data found on this page.
Page Analysis
This page serves as a high-level regional directory (CollectionPage) for Cleveland Clinic Florida. It functions as a navigational hub for several major medical facilities, including Weston Hospital, Indian River Hospital, Martin North, Martin South, and Tradition Hospital. The content includes interactive filters for location discovery and calls-to-action for appointment scheduling and phone contact. From an entity perspective, this is a critical 'Regional Hub' node that connects the global parent organization to specific physical clinical service points.
Schema Assessment
The extracted schema is entirely empty. There is no JSON-LD present to define the page type, the regional organization, or the individual hospitals listed in the directory. This represents a total failure of structured data implementation for a high-traffic regional landing page.
Entity Connectivity Gaps
The most significant gap is the lack of a 'MedicalOrganization' entity for Cleveland Clinic Florida, which should be defined with a persistent @id and linked to the parent organization identified in the Site Context. Furthermore, the hospitals mentioned (Weston, Indian River, Martin Health) are treated as flat text rather than distinct 'Hospital' or 'MedicalBusiness' entities. There is no 'ItemList' or 'hasOfferCatalog' to programmatically define the collection of locations. The 'Request an Appointment' action is missing a 'ScheduleAction' definition, and the 'Call' feature lacks 'ContactPoint' markup.
AI Retrieval Impact
Because there is no schema, AI systems and LLMs cannot verify the hierarchical relationship between Cleveland Clinic (Main) and its Florida branch. This page remains an 'isolated node' in the knowledge graph. When users ask AI 'What hospitals are part of Cleveland Clinic in Florida?', the AI must rely on error-prone scraping rather than an authoritative graph. This reduces the retrieval confidence for Florida-specific medical queries and weakens the site's E-E-A-T (Experience, Expertise, Authoritativeness, and Trustworthiness) signals at a regional level.
Recommendation
Implement a 'CollectionPage' as the primary type. Within it, define 'Cleveland Clinic Florida' as a 'MedicalOrganization' with an @id of 'https://my.clevelandclinic.org/florida#organization' and link it via 'parentOrganization' to the root identifier 'https://my.clevelandclinic.org/#organization'. Use an 'ItemList' to enumerate the hospitals, defining each as a 'Hospital' entity with its own @id. Add 'ContactPoint' for the 877 number and a 'potentialAction' of type 'ScheduleAction' for the appointment request. This schema is a recommendation and should be reviewed before implementation.
Score Justification
A score of 15 is assigned because the page contains zero structured data despite being a vital directory for multiple major medical facilities. It fails to provide any machine-readable context for AI systems.
Recommended Structured Data
{
    "@context": "https://schema.org",
    "@type": "CollectionPage",
    "@id": "https://my.clevelandclinic.org/florida/locations#webpage",
    "name": "Locations & Directions | Cleveland Clinic Florida",
    "description": "Directory of Cleveland Clinic medical campuses and facilities in Florida, including Weston, Indian River, and Martin Health.",
    "publisher": {
        "@id": "https://my.clevelandclinic.org/#organization"
    },
    "mainEntity": {
        "@type": "MedicalOrganization",
        "@id": "https://my.clevelandclinic.org/florida#organization",
        "name": "Cleveland Clinic Florida",
        "parentOrganization": {
            "@id": "https://my.clevelandclinic.org/#organization"
        },
        "contactPoint": {
            "@type": "ContactPoint",
            "telephone": "+1-877-463-2010",
            "contactType": "customer service"
        },
        "hasPart": [
            {
                "@type": "Hospital",
                "@id": "https://my.clevelandclinic.org/florida/locations/weston-hospital#hospital",
                "name": "Weston Hospital"
            },
            {
                "@type": "Hospital",
                "@id": "https://my.clevelandclinic.org/florida/locations/indian-river-hospital#hospital",
                "name": "Indian River Hospital"
            },
            {
                "@type": "Hospital",
                "@id": "https://my.clevelandclinic.org/florida/locations/martin-north-hospital#hospital",
                "name": "Martin North Hospital"
            },
            {
                "@type": "Hospital",
                "@id": "https://my.clevelandclinic.org/florida/locations/martin-south-hospital#hospital",
                "name": "Martin South Hospital"
            },
            {
                "@type": "Hospital",
                "@id": "https://my.clevelandclinic.org/florida/locations/tradition-hospital#hospital",
                "name": "Tradition Hospital"
            }
        ]
    },
    "potentialAction": {
        "@type": "ScheduleAction",
        "target": "https://my.clevelandclinic.org/webappointment",
        "name": "Request an Appointment"
    }
}
https://my.clevelandclinic.org/canada38 / 100
Current Structured Data
[
    {
        "@context": "http://schema.org",
        "@type": "MedicalOrganization",
        "name": "Cleveland Clinic",
        "numberOfEmployees": {
            "@type": "QuantitativeValue",
            "value": "65000"
        },
        "url": "https://my.clevelandclinic.org/canada",
        "alternateName": "Cleveland Clinic",
        "sameAs": [
            "https://en.wikipedia.org/wiki/Cleveland_Clinic",
            "https://www.linkedin.com/company/cleveland-clinic",
            "https://www.instagram.com/clevelandclinic",
            "https://twitter.com/ClevelandClinic",
            "https://www.youtube.com/user/ClevelandClinic",
            "https://www.facebook.com/ClevelandClinic"
        ],
        "areaServed": "http://www.wikidata.org/entity/Q13780930",
        "legalName": "Cleveland Clinic",
        "foundingDate": "1921-02-28",
        "logo": "https://my.clevelandclinic.org/-/scassets/images/org/logo/logo-ccf.svg?h=48&la=en&w=300&hash=F5231F16526C9ED33D180771275ED4B7E42C2018",
        "description": "Cleveland Clinic, a non-profit academic medical center, provides clinical and hospital care and is a leader in research, education and health information, and regarded as the best and highest-performing hospital in the world."
    },
    {
        "@context": "https://schema.org",
        "@type": "WebPage",
        "name": "Cleveland Clinic Homepage",
        "description": "Cleveland Clinic, a non-profit academic medical center, provides clinical and hospital care.",
        "publisher": {
            "@type": "Organization",
            "name": "Cleveland Clinic"
        },
        "image": "https://my.clevelandclinic.org/-/scassets/images/org/hero/home-hero-nov-22.jpg",
        "url": "https://my.clevelandclinic.org/canada"
    }
]
Page Analysis
The page is a regional hub for 'Cleveland Clinic Canada,' acting as a secondary homepage for its Toronto-based operations. It serves as a directory for local clinics (Downtown and Midtown), a service portal (Patient and Employer services), and a recruitment tool for staff. It establishes the branch's identity within the global Cleveland Clinic network, emphasizing virtual care and sports rehabilitation.
Schema Assessment
The current JSON-LD is generic and misleading. It declares a 'MedicalOrganization' named 'Cleveland Clinic' (the parent entity) rather than the specific Canadian subsidiary. It lacks @id identifiers, meaning it exists as an isolated node. The 'WebPage' schema is titled 'Cleveland Clinic Homepage,' which conflicts with the actual page content. It uses a Wikidata entity for 'areaServed' which is helpful, but the lack of internal connectivity to the global CC entity or local Toronto locations makes it low-fidelity.
Entity Connectivity Gaps
1. ID Persistence: No @id for the Canadian entity to distinguish it from the parent organization. 2. Hierarchical Connection: Missing 'parentOrganization' relationship linking this branch to the main Cleveland Clinic identifier defined in site context. 3. Physical Entity Gaps: The page mentions 'Downtown' and 'Midtown' clinics, but these are not defined as 'LocalBusiness' or 'Place' entities with addresses. 4. Service-to-Provider Mapping: Services like 'Sports Medicine' and 'Virtual Care' are text-only and not structured as 'Service' or 'MedicalSpecialty' entities. 5. Action Gaps: The 'Request An Appointment' and 'Email Our Team' features are not represented as 'PotentialAction' or 'ContactPoint'.
AI Retrieval Impact
AI systems (SGE, LLMs) will struggle to differentiate between the global brand and this specific regional entity. Without @id linking, search engines cannot confidently attribute the Toronto phone number or services to the correct branch. The 'chain of trust' is broken because the schema claims to be the global organization but is located on a regional sub-folder, creating a semantic mismatch that lowers E-E-A-T signals.
Recommendation
Transition from 'MedicalOrganization' to a more specific 'MedicalBusiness' for Cleveland Clinic Canada. Implement a persistent @id (e.g., https://my.clevelandclinic.org/canada#organization). Use 'parentOrganization' to link to the global CC entity. Define 'location' properties for the Downtown and Midtown clinics with actual PostalAddress data. Map the 'Patient Services' as an 'OfferCatalog' and include a 'ContactPoint' for the Toronto-specific phone number. Disclaimer: this schema is a recommendation and should be reviewed before implementation.
Score Justification
The score is 38 because while valid schema exists, it is functionally anonymous. It fails to identify the specific entity the page is about (the Canada branch), lacks @id connectivity to the parent organization, and omits the critical local business data (Toronto addresses) that AI needs for local service retrieval.
Recommended Structured Data
{
    "@context": "https://schema.org",
    "@graph": [
        {
            "@type": "MedicalBusiness",
            "@id": "https://my.clevelandclinic.org/canada#organization",
            "name": "Cleveland Clinic Canada",
            "description": "A leading healthcare facility in Toronto providing patient-centered care, virtual consultations, and sports health services.",
            "url": "https://my.clevelandclinic.org/canada",
            "telephone": "+1-416-507-6600",
            "logo": "https://my.clevelandclinic.org/-/scassets/images/org/logo/logo-ccf.svg",
            "parentOrganization": {
                "@type": "Organization",
                "@id": "https://my.clevelandclinic.org/#organization",
                "name": "Cleveland Clinic"
            },
            "areaServed": {
                "@type": "City",
                "name": "Toronto",
                "@id": "http://www.wikidata.org/entity/Q172"
            },
            "address": {
                "@type": "PostalAddress",
                "addressLocality": "Toronto",
                "addressRegion": "ON",
                "addressCountry": "CA"
            },
            "hasOfferCatalog": {
                "@type": "OfferCatalog",
                "name": "Canada Patient Services",
                "itemListElement": [
                    {
                        "@type": "Offer",
                        "itemOffered": {
                            "@type": "Service",
                            "name": "Sports Health"
                        }
                    },
                    {
                        "@type": "Offer",
                        "itemOffered": {
                            "@type": "Service",
                            "name": "Virtual Care"
                        }
                    },
                    {
                        "@type": "Offer",
                        "itemOffered": {
                            "@type": "Service",
                            "name": "Employer Services"
                        }
                    }
                ]
            },
            "contactPoint": {
                "@type": "ContactPoint",
                "telephone": "+1-416-507-6600",
                "contactType": "customer service",
                "email": "mailto:Canada@ccf.org"
            },
            "potentialAction": {
                "@type": "ScheduleAction",
                "target": {
                    "@type": "EntryPoint",
                    "urlTemplate": "https://my.clevelandclinic.org/canada#appointments"
                },
                "name": "Request An Appointment"
            }
        },
        {
            "@type": "WebPage",
            "@id": "https://my.clevelandclinic.org/canada#webpage",
            "url": "https://my.clevelandclinic.org/canada",
            "name": "Cleveland Clinic Canada | Toronto Health Care Facility",
            "isPartOf": {
                "@id": "https://my.clevelandclinic.org/#website"
            },
            "about": {
                "@id": "https://my.clevelandclinic.org/canada#organization"
            }
        }
    ]
}
Implementation Roadmap
Critical
Root Trust Anchor Implementation
Medium
Action
Transform this page into the 'Semantic Root' for site-wide trust signals. Implement a WebPage schema that defines the Cleveland Clinic as the publisher using a persistent @id. Use the 'publishingPrinciples' property to link to the individual URLs of the Privacy Policy, Terms of Use, and Editorial Policy. Declare a 'WebSite' entity that references the organization as its provider.
Impact
Without structured data, AI systems (including LLMs and RAG engines) cannot verify the 'Chain of Trust' for the site's medical content. They cannot programmatically confirm that the Health Library articles are governed by the 'Editorial Policy' mentioned here.
Expected Outcome
Machine-readable foundation for the entire domain's authority and verification of medical content publishing principles.
Source
https://my.clevelandclinic.org/about/website
Appointment Transaction Layer Actionability
Medium
Action
Implement a 'ContactPage' type as the primary container. Define a 'ScheduleAction' as a 'potentialAction' of the Cleveland Clinic organization entity. Explicitly link this page to the root organization using the @id identified in the Site Context (https://my.clevelandclinic.org/#organization). Use 'EntryPoint' schema to describe how an AI agent should interact with the scheduling form.
Impact
This page is invisible to the 'Action Layer' of modern AI. This prevents the site from being utilized by voice assistants or AI agents that perform task-oriented actions (e.g., 'Book an appointment at Cleveland Clinic').
Expected Outcome
Programmatic enablement of AI-driven appointment scheduling and direct interaction for voice assistants.
Source
https://my.clevelandclinic.org/webappointment
Global Communication Directory Authentication
Medium
Action
Implement a 'ContactPage' schema as the top-level type. Within it, define the primary 'Organization' using the site-wide @id 'https://my.clevelandclinic.org/#organization'. Use an array of 'contactPoint' objects to define every number listed on the page, utilizing 'contactType' to categorize them (e.g., 'Appointment Services', 'Billing Support'). Crucially, use 'areaServed' to distinguish numbers for Ohio, Florida, Canada, and Nevada.
Impact
Because there is no structured data, AI systems (LLMs, Voice Assistants, Knowledge Graphs) cannot verify the 'Chain of Trust' for these phone numbers. If a user asks a voice assistant for a specific appointment number, the assistant must guess based on proximity in text rather than a programmatic declaration.
Expected Outcome
Machine-verifiable communication database for global operations, enabling accurate 'Zero-click' results.
Source
https://my.clevelandclinic.org/about/contact/phone-directory
Patient Service Hub Semantic Mapping
High
Action
Implement a high-fidelity WebPage schema that defines the 'Patient and Visitor Services' as a central 'Service' entity. This entity must use the Cleveland Clinic @id as the 'provider'. Use an 'OfferCatalog' to list the specific sub-services (Billing, Records, Travel) and link them to their respective deep-pages identified in the Site Context. Crucially, add 'potentialAction' markup for 'ScheduleAction' and 'PayAction'.
Impact
Retrieval-Augmented Generation (RAG) systems will struggle to verify 'Accepted Insurance' or 'Appointment Checklist' as structured facts, likely resulting in hallucinations or lower confidence scores. The 'Chain of Trust' is broken because there is no machine-readable link between these services and the verified Organization entity.
Expected Outcome
Verification of service offerings for RAG systems and enablement of direct AI agent interactions for billing and scheduling.
Source
https://my.clevelandclinic.org/patients
Health Information Management & Records Authorization
Medium
Action
Implement a high-fidelity 'MedicalWebPage' schema that contains a 'Service' entity. This service must list 'Cleveland Clinic' as the provider via the site-wide @id 'https://my.clevelandclinic.org/#organization'. Define the 'Health Information Management' department as the 'serviceOperator'. Explicitly link 'MyChart' as a related 'SoftwareApplication'. Use 'ContactPoint' for the phone and fax numbers.
Impact
AI systems and LLMs cannot verify this as the authoritative source for Cleveland Clinic medical records through programmatic means. Retrieval systems may fail to accurately extract the specific processing times (7-10 days) or fees as 'facts', instead treating them as 'unstructured claims'.
Expected Outcome
Authoritative factual verification for health data access requests and multi-channel support contact accuracy.
Source
https://my.clevelandclinic.org/patients/information/medical-records
Clinical Research Enterprise Entity Definition
High
Action
Implement a ResearchOrganization schema as the primary entity for this page, with a persistent @id (e.g., https://my.clevelandclinic.org/research/#research). Explicitly define the parentOrganization as the main Cleveland Clinic entity using its site-wide @id. Use subOrganization properties to link to the specific institutes mentioned (Lerner, Global Center). Include a 'funder' property for the Ohio/JobsOhio relationship.
Impact
Because there is no structured data, AI systems cannot programmatically verify the relationship between Cleveland Clinic and its research arms. This page fails to contribute to the site's E-E-A-T at a machine level. Retrieval systems cannot confidently identify this as the 'official' research hub.
Expected Outcome
Consolidation of research-backed authority into the knowledge graph, anchoring medical content to institutional expertise.
Source
https://my.clevelandclinic.org/research
Clinical Trial Discovery & Regulatory Oversight
High
Action
Implement a 'CollectionPage' as the primary type, explicitly defining the Cleveland Clinic parent organization as the 'publisher' and 'provider'. Use '@id' to link to the 'ResearchOrganization' (Lerner Research Institute). Add a 'SearchAction' targeting the clinical trials search engine to signal programmatic accessibility. Declare the 'InstitutionalReviewBoard' as a 'member' or 'funder' entity.
Impact
AI systems and LLMs cannot programmatically verify Cleveland Clinic's authority in clinical research via this page. The lack of structured E-E-A-T signals (like IRB oversight) reduces retrieval confidence for 'experimental treatments' queries.
Expected Outcome
Machine-readable clinical study catalog with verified regulatory oversight signals for high-stakes medical queries.
Source
https://my.clevelandclinic.org/clinical-trials
Global Location Infrastructure Hub
High
Action
Immediately implement a 'CollectionPage' schema that anchors to the site-wide Cleveland Clinic Organization @id. Define an 'ItemList' containing the primary regional hubs as 'ListItem' entities, each pointing to its respective landing page URL (Ohio, Florida, Nevada, etc.). Add a 'SearchAction' targeting the location search functionality to allow AI-driven discovery.
Impact
AI systems and LLMs cannot programmatically identify this page as the authoritative directory for Cleveland Clinic locations. Without structured data, the 'chain of trust' from the brand to its physical facilities is broken. Search engines cannot easily parse the regional hierarchy.
Expected Outcome
Programmatic mapping of global physical infrastructure, improving visibility in localized AI Overviews and 'near me' queries.
Source
https://my.clevelandclinic.org/locations
Administrative Trust & Patient Advocacy Anchor
Medium
Action
Implement a high-fidelity MedicalOrganization schema for the Office of Patient Experience. Use a persistent @id and declare its parentOrganization as the main Cleveland Clinic entity. Explicitly define the Ombudsman Office as a Service provided by this department. Link the 'Studies in Empathy' podcast mentioned on the page to its corresponding PodcastSeries entity via 'subjectOf'.
Impact
AI systems and LLMs cannot programmatically identify this page as the authoritative source for Cleveland Clinic's patient advocacy and ombudsman services. The 'broken chain of trust' is severe here: the site claims to be 'Patients First,' but it fails to provide the structured evidence required for high-authority E-E-A-T ranking.
Expected Outcome
Structured verification of patient-centered organizational initiatives and leadership accountability.
Source
https://my.clevelandclinic.org/departments/patient-experience/depts/office-patient-experience
Digital Portal Authentication & Action Schema
Medium
Action
Deploy a multi-type entity graph using SoftwareApplication and Service. Define a persistent @id for MyChart and link it to the Cleveland Clinic root @id via the 'publisher' and 'provider' properties. Explicitly define 'LoginAction' and 'RegisterAction' to enable AI-driven task completion.
Impact
AI agents and LLMs cannot verify the authenticity of this portal. Without structured 'PotentialAction' data, AI-driven assistants cannot facilitate user journeys like 'Find the Cleveland Clinic login page.' The 'chain of trust' is broken.
Expected Outcome
Enables AI assistants to correctly route users to secure portal actions and identifies software capabilities programmatically.
Source
https://my.clevelandclinic.org/online-services/mychart
Telehealth Service Geographic & App Mapping
High
Action
Define a 'Service' entity for 'Virtual Visits' and link it to the Cleveland Clinic parent @id. Explicitly declare 'areaServed' for Ohio and Florida. Define 'availableChannel' as a 'ServiceChannel' that references the 'SoftwareApplication' (@id for MyChart/MyClevelandClinic app). Map 'offers' to represent the different visit types (Express vs. Primary Care).
Impact
AI systems and LLMs cannot programmatically verify that Cleveland Clinic is the provider of these virtual services. Retrieval-Augmented Generation (RAG) systems will struggle to accurately extract 'Express Care' hours or geographic restrictions. AI assistants cannot reliably link the 'Virtual Visit' intent to the 'MyClevelandClinic' app.
Expected Outcome
Accurate AI retrieval of telehealth availability, treated conditions, and direct linkage to the delivery application.
Source
https://my.clevelandclinic.org/online-services/virtual-visits
Global Support & Contact Directory Hub
Medium
Action
Implement a high-fidelity ContactPage schema that also incorporates FAQPage for category navigation. Use the established parent organization @id as the provider. Define separate 'contactPoint' objects for each region with specific 'areaServed' (ISO 3166-2) and 'hoursAvailable'. Explicitly link 'MyChart' and 'Ombudsman' to their existing @id definitions.
Impact
AI retrieval systems cannot verify which phone number belongs to which region with 100% confidence. Voice assistants cannot distinguish the 'Nurse on Call' service as a functional utility. The lack of @id connectivity weakens E-E-A-T signals for user-support queries.
Expected Outcome
High-confidence extraction of regional contact points and automated routing for voice search triage support.
Source
https://my.clevelandclinic.org/help
Professional B2B Referral Connectivity
Medium
Action
Implement a 'Service' schema as the mainEntity. This service must list Cleveland Clinic (via root @id) as the 'provider.' Explicitly define 'ContactPoint' for the hotline and 'PotentialAction' (ScheduleAction) for the referral process. Use 'areaServed' to bridge the gap to Florida and Nevada regional entities.
Impact
LLMs and search engines cannot verify this as an official service of Cleveland Clinic via knowledge graph traversal. AI-driven search may fail to accurately summarize referral steps or misattribute regional contact info.
Expected Outcome
Programmatic identification of official B2B referral channels for external physicians, ensuring accurate cross-regional data.
Source
https://my.clevelandclinic.org/professionals/referring
Nevada Regional Entity & Location Anchor
Medium
Action
Implement a MedicalBusiness schema including physical address, phone, and geo-coordinates. Use 'parentOrganization' to link to the site-wide organization @id. Declare the Lou Ruvo Center as a 'subOrganization'. Use 'hasOfferCatalog' to list services like Imaging and Cognitive Care as discrete Service entities.
Impact
AI systems and LLMs cannot verify this location's authenticity or its relationship to the Cleveland Clinic brand. In 'near me' queries or specialized neurological service searches, this page lacks the structured signals required for inclusion in AI Overviews (SGE).
Expected Outcome
Verification of Nevada operations in local AI search and programmatic association of brain health specialty services to the main brand.
Source
https://my.clevelandclinic.org/locations/nevada
Ohio Physical Infrastructure Mapping
Medium
Action
Implement a high-fidelity 'CollectionPage' that defines an 'ItemList' of Ohio medical facilities. Each facility should be a 'Hospital' or 'MedicalBusiness' entity with a unique '@id'. Explicitly link the 'publisher' to the root organization '@id' and add a 'SearchAction' for the location filter tool.
Impact
AI systems and LLMs cannot programmatically verify which facilities belong to the Cleveland Clinic network in Ohio. This breaks the 'chain of trust' between the parent organization and its physical satellites. Knowledge graph builders will fail to associate regional search intent with this hub.
Expected Outcome
Formalization of the hub-and-spoke relationship between the Cleveland brand and its Ohio hospitals in the knowledge graph.
Source
https://my.clevelandclinic.org/locations/ohio-locations
Expert Verification & Audio E-E-A-T Architecture
High
Action
Implement a high-fidelity PodcastSeries schema. Define Cleveland Clinic as the 'publisher' using the site-wide @id. For each episode, create a PodcastEpisode entity featuring the 'actor' (the doctor) with a persistent @id linking to their professional staff page. Use 'about' to link episodes to specific MedicalCondition or MedicalSpecialty entities.
Impact
AI retrieval systems cannot programmatically verify that this health advice is authored by credentialed medical professionals. E-E-A-T signals are severely weakened because the chain of trust between the doctor's profile and their podcast advice is broken.
Expected Outcome
Connection of credentialed staff expertise to published health advice, enabling 'Listen Now' rich results and authoritative AI citation.
Source
https://my.clevelandclinic.org/podcasts/health-essentials
Important
Health Library Hub & Taxonomy Structure
High
Action
Implement a 'CollectionPage' linked to the global Organization @id. Define the Health Library as a 'CreativeWorkSeries'. Add a 'SearchAction' to enable programmatic entry. Explicitly link 'Health Essentials Podcast' and 'Newsletter' using persistent @ids. Use 'hasPart' to define medical categories.
Impact
For AI retrieval and LLMs, this page is a 'dead end'. Authority (E-E-A-T) does not programmatically flow into the Health Library because the 'publisher' relationship is not declared. This results in lower retrieval confidence for 'Cleveland Clinic' as a source.
Expected Outcome
Verification of Cleveland Clinic as the authoritative source for thousands of medical articles and navigational categories.
Source
https://my.clevelandclinic.org/health
Medical Procedures Directory Verification
Medium
Action
Implement a CollectionPage schema that establishes the @id link to the parent Organization and Health Library hub. Use an ItemList to define the main categories of procedures and include a SearchAction for the 'Search our topics' feature.
Impact
AI systems cannot verify this page as the authoritative index for Cleveland Clinic procedures. The 'chain of trust' is completely broken; there is no programmatic link between these procedures and the medical professionals that validate them.
Expected Outcome
Structured procedural index that passes authority from the organization to thousands of individual treatment pages.
Source
https://my.clevelandclinic.org/health/procedures
Symptoms Index Hub Connectivity
Medium
Action
Implement a CollectionPage schema. Use a @graph structure to link this page to the site's root Organization @id. Include a SearchAction property to define the symptom search tool. Declare the 'Health Educator' service as a ContactPoint with a specific serviceType.
Impact
Without a structured ItemList or SearchAction, the 'A-Z' directory remains opaque to retrieval-augmented generation (RAG) systems. The absence of a publisher link breaks the chain of trust, meaning organizational E-E-A-T is not programmatically inherited.
Expected Outcome
Discovery of authoritative symptom data and support services via structured AI search and RAG extraction.
Source
https://my.clevelandclinic.org/health/symptoms
Regulatory Pricing & Dataset Verification
High
Action
Define the page as a 'WebPage' with a 'Service' mainEntity. Use the Root Identifier as the 'provider'. For each hospital listed, create a 'subOrganization' entry using its specific @id and link it to a 'PriceSpecification' or 'DataDownload' entity. Include 'publishingPrinciples' to establish a formal trust anchor.
Impact
AI retrieval systems cannot programmatically verify that these are the official CMS-mandated charge lists. An AI agent cannot confidently answer 'What is the price list for Cleveland Clinic Lodi Hospital?' without manual scraping, reducing retrieval confidence.
Expected Outcome
High-trust regulatory compliance and machine-verifiable price specification for YMYL financial queries.
Source
https://my.clevelandclinic.org/patients/billing-finance/comprehensive-hospital-charges
Virtual Second Opinion Service Tiering
Medium
Action
Deploy a 'MedicalWebPage' schema with a 'Service' entity as the 'mainEntity'. Link to the parent Organization @id. Use 'Offer' to distinguish between 'Concierge' and 'Concierge Plus' tiers. Map the 'Specialties' listed to 'MedicalSpecialty' types.
Impact
Without @id connectivity, the 'expert advice' cannot be verified against the clinic's staff directory, breaking the chain of trust. AI cannot distinguish this highly-vetted service from low-quality health blogs.
Expected Outcome
Clear programmatic distinction of premium medical service tiers and verified institutional expertise.
Source
https://my.clevelandclinic.org/online-services/virtual-second-opinions
Florida Regional Subsidiary Identification
Medium
Action
Define 'Cleveland Clinic Florida' as a 'MedicalOrganization' with a persistent @id and link it via 'parentOrganization' to the root identifier. Use an 'ItemList' to enumerate the hospitals, defining each as a 'Hospital' entity with its own @id. Add 'ScheduleAction' and 'ContactPoint' markup.
Impact
AI systems and LLMs cannot verify the hierarchical relationship between Cleveland Clinic (Main) and its Florida branch. This page remains an 'isolated node'. AI must rely on error-prone scraping rather than an authoritative graph.
Expected Outcome
Elimination of regional hierarchy ambiguity and structured indexing of Florida-specific hospital entities.
Source
https://my.clevelandclinic.org/florida/locations
Education Institute Institutional Authority
High
Action
Implement an EducationalOrganization schema. Explicitly link this entity to the parent Cleveland Clinic organization using 'parentOrganization' and the root @id. Define the various units (Student & Faculty Development, etc.) as 'subOrganization' nodes. Map 'CME Certification' as a 'Service'.
Impact
AI systems and LLMs cannot verify the Education Institute's relationship to the Cleveland Clinic brand with 100% confidence. The expertise of the Educational Institute does not programmatically flow to the clinical departments it supports.
Expected Outcome
Integrated educational authority within the knowledge graph, linking professional training to clinical excellence.
Source
https://my.clevelandclinic.org/departments/education
Professional Hub Authority Dead-End Resolution
Medium
Action
Implement a WebPage schema declaring the Cleveland Clinic as the publisher using the site-wide @id. The mainEntity should be a 'Service' representing the Professional Resource Hub. Include a 'ContactPoint' for the Referring Physician Hotline. Link 'Consult QD' via @id to the Publication entity.
Impact
For AI agents and LLMs, this page is an 'authority dead-end.' Because there is no schema, the 'Referring Physician Hotline' cannot be reliably extracted as a trusted contact for providers.
Expected Outcome
Verification of B2B service relationships and machine-readable access to professional hotspots for healthcare providers.
Source
https://my.clevelandclinic.org/professionals
Main Service Catalog Graph Integration
High
Action
Implement a 'CollectionPage' schema with a 'Service' hub linked to a comprehensive 'hasOfferCatalog'. Each service listed should be a 'MedicalService' entity with an '@id' reflecting its specific service page. Explicitly link the 'provider' property to the site-wide organization '@id'.
Impact
AI systems and LLMs cannot programmatically extract the relationship between Cleveland Clinic and its clinical offerings. Without a structured 'OfferCatalog', search engines cannot confidently map treatments to this provider.
Expected Outcome
Comprehensive programmatic index of all adult and pediatric services linked to the parent organization.
Source
https://my.clevelandclinic.org/services
Canada Subsidiary Entity Specification
Medium
Action
Transition to 'MedicalBusiness' for Cleveland Clinic Canada. Implement a persistent @id and use 'parentOrganization' to link to the global CC entity. Define 'location' properties for Toronto clinics with actual PostalAddress data. Map 'Patient Services' as an 'OfferCatalog'.
Impact
AI systems will struggle to differentiate between the global brand and this specific regional entity. The 'chain of trust' is broken because the schema claims to be the global organization but is located on a regional sub-folder, lowering E-E-A-T signals.
Expected Outcome
Regional entity disambiguation and programmatic mapping of Toronto-specific clinical services and locations.
Source
https://my.clevelandclinic.org/canada
Provider Directory Intent Correction
Medium
Action
Transform schema from a static organization block into a 'CollectionPage' that hosts a 'SearchAction'. Explicitly link this page to the parent Organization using the site-wide @id. Define the 'Find a Provider' tool as a Service provided by the organization.
Impact
AI retrieval systems will treat this as a general 'About' page rather than a functional tool. Because the search functionality is not programmatically declared, LLMs cannot reliably guide users through a structured search action.
Expected Outcome
Correct intent mapping for provider search, enabling AI agents to facilitate doctor discovery queries.
Source
https://my.clevelandclinic.org/providers
Staff Directory Search Utility Normalization
Medium
Action
Use @id: 'https://my.clevelandclinic.org/#organization' to link this page to the site-wide parent entity. Add a 'potentialAction' of type 'SearchAction'. Define the mainEntity as a 'Service' representing the 'Provider Directory'. Link to 'Specialist' and 'MedicalSpecialty' types.
Impact
Knowledge graph builders will fail to connect the 'Find a Provider' tool to the actual Physician profiles (Person entities) on the site, creating a dead-end in the authority chain.
Expected Outcome
Functional search connectivity that bridges the gap between the directory tool and individual physician profile authority.
Source
https://my.clevelandclinic.org/staff
Strategic
Philanthropic Authority & Transactional Trust
Medium
Action
Implement a graph starting with a WebPage entity subject to the Philanthropy department. Explicitly link this to the site-wide Cleveland Clinic @id. Define VeloSano as a 'subOrganization' or 'event'. Add a 'potentialAction' of type 'DonateAction' to allow AI agents to understand the transaction path.
Impact
AI retrieval systems cannot verify the authenticity of this donation page through structured trust signals, critical for YMYL content. Conversational AI cannot accurately answer 'how do I donate?' because the 'DonateAction' is not declared.
Expected Outcome
Verification of official charity status and enablement of AI-driven donation paths and event discovery.
Source
https://my.clevelandclinic.org/giving
Newsletter Subscription Entity & Intent Verification
Low
Action
Define the page as a 'WebPage' with the primary entity being a 'Periodical' named 'Health Essentials'. Link this to the parent organization using the global @id. Add a 'potentialAction' of type 'SubscribeAction'. Use 'relatedLink' to connect to the Health Essentials Podcast.
Impact
AI systems cannot verify the authenticity of this newsletter or link it to the Cleveland Clinic's authority. Without a 'publisher' property linking back to the parent organization @id, the content lacks the E-E-A-T signals required for high-confidence health recommendations.
Expected Outcome
Programmatic association of health tips and wellness content with the brand's verified publishing authority.
Source
https://my.clevelandclinic.org/health-essentials-newsletter