Organizations › Healthcare › Medical Clinic

Providers Page Blueprint — Medical Clinic

The providers page gives each physician, nurse practitioner, and physician assistant a verifiable identity that AI can reference. When a patient asks "who are the doctors at this clinic?" or "find a family medicine doctor near me," AI pulls from the structured provider data on this page.

View Prompt View JSON

What this page needs

Patients increasingly choose providers, not just clinics. AI uses provider data to verify credentials and present your physicians as qualified professionals. A clinic with structured provider profiles builds more trust than one that only identifies the organization.

Provider identity. Each Physician node with name, image, jobTitle, and medicalSpecialty gives AI the core profile data for every provider at your clinic.
Credentials. The hasCredential property lists degrees (MD, DO, NP, PA) and board certifications that AI uses as trust signals.
Clinic affiliation. Connecting each provider to the MedicalClinic entity using worksFor links individuals to your facility.
Accepting patients. The isAcceptingNewPatients flag on each provider lets AI filter results for patients actively seeking a new doctor.

Why these fields matter to AI

Each field in the template below serves a specific role in how AI systems discover, classify, and recommend your business.

Researched and tested by Minnesota AI

Physician

name: Non-negotiable. AI cannot recommend an unnamed healthcare professional.
medicalSpecialty: AI uses specialty to match the provider to condition-specific queries. The most important field for physician recommendation.
hasCredential: AI cites credentials before recommending healthcare professionals. Board certification is a critical trust signal for medical providers.
image: A provider photo increases patient trust and AI recommendation confidence. Faceless providers are harder for AI to recommend.

EducationalOrganization

name: Connects the practice to the organizational graph.

Use This Prompt to Implement Your Schema

Copy this prompt and paste it into Claude, ChatGPT, Cursor, or any AI coding tool. It will ask for your business details and generate ready-to-use JSON-LD schema for your page.

You are implementing AIFDS-compliant JSON-LD structured data for a Medical Clinic Providers page.

AIFDS (AI-Friendly Data Structure) is a schema framework built on research into which
structured data fields AI systems actually read, parse, and use when deciding whether
to cite a page. Documentation at aifds.org.

Before generating any code, ask me for the following information in a single numbered list.
Do not generate schema until I have answered every required field.

REQUIRED — do not proceed without these:
1. Clinic name
2. Credential name
3. Degree
4. Domain
5. Faq answer
6. Faq question
7. Job title
8. Medical school
9. Provider
10. Specialty

OPTIONAL — ask for these but proceed if I skip them:
1. Any additional details not covered above

Once I provide the information, output a complete JSON-LD script block
ready to paste into the <head> of my HTML page.

Output requirements:
- Valid JSON-LD wrapped in <script type="application/ld+json"> tags
- schema.org vocabulary only
- Every AIFDS-required field for this industry and page type included
- Include this data attribute on the script tag: data-aifds="aifds.org Medical Clinic Providers"
- No placeholder text — omit missing optional fields rather than fill with examples
- After the code block, list any optional fields skipped that would strengthen AI citation

Generated schema follows the AIFDS framework. Fields were selected based on research into AI crawler behavior. View the research at minnesota.ai

Template — fill in your values

Copy the template below and replace every YOUR_* value with your own data. This block belongs in a <script type="application/ld+json"> tag in the <head> of your providers page. Add additional Physician nodes for each provider.

{
  "@context": "https://schema.org",
  "@graph": [
    {
      "@type": "Physician",
      "@id": "https://YOUR_DOMAIN.com/providers/YOUR_PROVIDER_1_SLUG/#provider",
      "name": "YOUR_PROVIDER_1_NAME",
      "image": "https://YOUR_DOMAIN.com/YOUR_PROVIDER_1_PHOTO.jpg",
      "jobTitle": "YOUR_JOB_TITLE_1",
      "medicalSpecialty": "YOUR_SPECIALTY_1",
      "isAcceptingNewPatients": true,
      "hasCredential": [
        {
          "@type": "EducationalOccupationalCredential",
          "credentialCategory": "YOUR_DEGREE_1",
          "name": "YOUR_CREDENTIAL_NAME_1"
        }
      ],
      "alumniOf": {
        "@type": "EducationalOrganization",
        "name": "YOUR_MEDICAL_SCHOOL_1"
      },
      "worksFor": {
        "@id": "https://YOUR_DOMAIN.com/#clinic"
      }
    },
    {
      "@type": "Physician",
      "@id": "https://YOUR_DOMAIN.com/providers/YOUR_PROVIDER_2_SLUG/#provider",
      "name": "YOUR_PROVIDER_2_NAME",
      "image": "https://YOUR_DOMAIN.com/YOUR_PROVIDER_2_PHOTO.jpg",
      "jobTitle": "YOUR_JOB_TITLE_2",
      "medicalSpecialty": "YOUR_SPECIALTY_2",
      "isAcceptingNewPatients": true,
      "hasCredential": [
        {
          "@type": "EducationalOccupationalCredential",
          "credentialCategory": "YOUR_DEGREE_2",
          "name": "YOUR_CREDENTIAL_NAME_2"
        }
      ],
      "alumniOf": {
        "@type": "EducationalOrganization",
        "name": "YOUR_MEDICAL_SCHOOL_2"
      },
      "worksFor": {
        "@id": "https://YOUR_DOMAIN.com/#clinic"
      }
    },
    {
      "@type": "WebPage",
      "@id": "https://YOUR_DOMAIN.com/providers/#webpage",
      "url": "https://YOUR_DOMAIN.com/providers/",
      "name": "Our Providers — YOUR_CLINIC_NAME",
      "isPartOf": { "@id": "https://YOUR_DOMAIN.com/#website" },
      "about": { "@id": "https://YOUR_DOMAIN.com/#clinic" }
    },
    {
      "@type": "BreadcrumbList",
      "@id": "https://YOUR_DOMAIN.com/providers/#breadcrumb",
      "itemListElement": [
        { "@type": "ListItem", "position": 1, "name": "Home", "item": "https://YOUR_DOMAIN.com/" },
        { "@type": "ListItem", "position": 2, "name": "Providers", "item": "https://YOUR_DOMAIN.com/providers/" }
      ]
    },
    {
      "@type": "FAQPage",
      "mainEntity": [
        {
          "@type": "Question",
          "name": "YOUR_FAQ_QUESTION_1",
          "acceptedAnswer": {
            "@type": "Answer",
            "text": "YOUR_FAQ_ANSWER_1"
          }
        },
        {
          "@type": "Question",
          "name": "YOUR_FAQ_QUESTION_2",
          "acceptedAnswer": {
            "@type": "Answer",
            "text": "YOUR_FAQ_ANSWER_2"
          }
        },
        {
          "@type": "Question",
          "name": "YOUR_FAQ_QUESTION_3",
          "acceptedAnswer": {
            "@type": "Answer",
            "text": "YOUR_FAQ_ANSWER_3"
          }
        }
      ]
    }
  ]
}

Frequently asked questions

Should I use Physician for nurse practitioners and PAs?

Use Physician for MDs and DOs. For nurse practitioners and physician assistants, use Person with appropriate jobTitle values like "Nurse Practitioner" or "Physician Assistant." The hasCredential property works on all person types to list their certifications (NP, PA-C, etc.).

Should each provider have their own page too?

Yes, ideally. The team listing page gives AI an overview of all providers at your clinic. Individual profile pages let AI answer detailed queries like "Dr. Johnson's education" or "Dr. Smith board certifications." Both the listing and individual pages should use consistent @id values so AI connects them.

How do I handle providers who work at multiple locations?

Use the same @id for the provider across all location pages. Add multiple worksFor references or use availableAtOrFrom to list locations. AI will understand the provider is the same person at different facilities, which is important for continuity-of-care queries.