Medical and health content carries a standard of scrutiny that no other content category faces in quite the same way. When a user asks ChatGPT or Perplexity about a drug interaction, a treatment protocol, or a diagnostic criterion, the AI system draws from sources it considers credible and credibility, in both traditional search and generative AI, increasingly depends on whether the people behind the content can be verified as qualified. Author schema for medical content credentials is the mechanism that makes that verification machine-readable.

This guide walks through every step of implementing Person schema for medical writers, clinical reviewers, and contributing healthcare professionals: from defining the author entity to expressing board certifications, institutional affiliations, and knowledge domains in structured data and connecting those entities to the articles they authored or reviewed.

Why Credentialed Author Markup Matters for Healthcare Pages

Google's Quality Rater Guidelines classify health, finance, and legal content as Your Money or Your Life (YMYL) topics – pages where inaccurate information could directly harm a reader. For YMYL pages, Google places exceptional weight on the Experience, Expertise, Authoritativeness, and Trustworthiness (E-E-A-T) signals that determine whether a source is worth surfacing.

Structured data connects those E-E-A-T signals to the machines that evaluate them. Without author schema, a physician's credentials exist only in prose on an "About the Author" section – readable by humans, invisible to search engines and AI retrieval systems. With properly implemented Person schema, those same credentials become structured, crawlable, and citable facts that AI systems can extract and verify against other data sources.

The practical result: pages with credentialed author markup are more likely to be cited by AI systems as authoritative health sources, and more likely to satisfy Google's quality evaluation for YMYL content. The relationship between E-E-A-T signals and structured data is well established – markup that surfaces author qualifications directly reinforces the trust signals that both search engines and AI tools rely on to evaluate medical pages.

Step 1: Define Your Author as a Named Entity

The first task is establishing the author as a distinct, named entity in your structured data. This means creating a Person schema block with properties that uniquely identify the individual – not a generic byline, but a verifiable entity with a stable identifier.

At minimum, every medical author's Person schema should include:

  • @type: always Person
  • name: the author's full legal name, matching how it appears on credentials, publications, and professional profiles
  • url: a stable URL for the author – this can be a profile page on your site, a university faculty page, or a LinkedIn profile
  • sameAs: one or more external URLs that confirm identity across the web (LinkedIn, Google Scholar, ORCID, institutional directory)
{
 "@context": "https://schema.org",
 "@type": "Person",
 "name": "Dr. Sarah Okonkwo",
 "url": "https://www.yourdomain.com/authors/dr-sarah-okonkwo",
 "sameAs": [
 "https://orcid.org/0000-0001-2345-6789",
 "https://www.linkedin.com/in/sarahokonkwo",
 "https://scholar.google.com/citations?user=EXAMPLEID"
 ]
}

The sameAs property is particularly important for medical authors. ORCID iDs – persistent digital identifiers for researchers – are the most authoritative external anchor for academic and clinical contributors. Where an ORCID exists, always include it. Google Scholar profiles and PubMed author pages serve the same corroborating function for AI systems that cross-reference entity identity across sources.

Step 2: Add Professional Credentials Using hasCredential

The hasCredential property expresses formal qualifications – medical degrees, board certifications, and licensed professional designations – as structured objects within the author's Person schema. Each credential is represented as an EducationalOccupationalCredential type.

"hasCredential": [
 {
 "@type": "EducationalOccupationalCredential",
 "credentialCategory": "degree",
 "name": "Doctor of Medicine (MD)",
 "recognizedBy": {
 "@type": "Organization",
 "name": "University of Lagos College of Medicine"
 }
 },
 {
 "@type": "EducationalOccupationalCredential",
 "credentialCategory": "certification",
 "name": "Board Certification in Internal Medicine",
 "recognizedBy": {
 "@type": "Organization",
 "name": "American Board of Internal Medicine"
 }
 }
]

Credential Categories to Use

Schema.org's EducationalOccupationalCredential supports several credentialCategory values relevant to healthcare authors:

  • degree – MD, DO, PhD, PharmD, NP, PA-C, and similar earned academic degrees
  • certification – board certifications from recognized bodies (ABIM, ABFM, ABP, ABMS member boards)
  • license – state or national professional licenses
  • badge – continuing medical education (CME) completions and specialty training badges

Using the correct category helps AI systems interpret what each credential means, rather than treating all qualifications as equivalent.

Including the Issuing Organization

Always populate recognizedBy with the full, formal name of the credentialing body. For US board certifications, this means using the exact name as listed by the American Board of Medical Specialties (ABMS) – "American Board of Internal Medicine" rather than "ABIM." This specificity is what allows AI systems to cross-verify the credential against known institutional entities.

Step 3: Express Educational Background Using alumniOf

The alumniOf property links an author to the institutions where they completed their training. For medical authors, this typically includes medical school, residency programs, and fellowship training – each of which adds credibility that AI systems recognize.

"alumniOf": [
 {
 "@type": "EducationalOrganization",
 "name": "Johns Hopkins School of Medicine",
 "url": "https://www.hopkinsmedicine.org/som"
 },
 {
 "@type": "EducationalOrganization",
 "name": "Massachusetts General Hospital",
 "description": "Internal Medicine Residency Program"
 }
]

Residency and fellowship programs are hosted by hospitals rather than universities, so use MedicalOrganization or Hospital as the @type for those entries when the host institution is a clinical facility. For fellowship programs with a dual affiliation – hospital plus academic medical center – include both the hospital name and the affiliated university if the program is commonly associated with both.

The physician and doctor schema implementation follows a similar entity-building pattern for practice-based providers, which makes the combination of alumniOf and hasCredential a natural extension of that foundation.

Step 4: Define Institutional Affiliations Using memberOf

Active professional affiliations – medical societies, academic appointments, editorial board memberships, and hospital staff positions – are expressed using the memberOf property. These affiliations signal ongoing professional standing, not just historical credentials.

"memberOf": [
 {
 "@type": "MedicalOrganization",
 "name": "American College of Physicians",
 "url": "https://www.acponline.org"
 },
 {
 "@type": "Organization",
 "name": "Cleveland Clinic",
 "url": "https://my.clevelandclinic.org",
 "description": "Attending Physician, Department of Gastroenterology"
 }
]

Choosing the Right @type for Each Affiliation

Medical society memberships are MedicalOrganization. Hospital staff positions are Hospital or MedicalClinic. Academic appointments are EducationalOrganization. Editorial board memberships at journals are Organization. Using the correct type, rather than defaulting to Organization for everything, gives AI retrieval systems more precise entity signals to work with. The full range of schema types relevant to medical websites covers these distinctions in depth.

Step 5: Declare Subject Matter Expertise Using knowsAbout

The knowsAbout property allows you to declare the specific medical topics an author is qualified to write about. This is one of the most directly useful properties for AI citation purposes: it tells retrieval systems not just who the author is, but which domains of health content they are authoritative in.

"knowsAbout": [
 "Cardiovascular disease prevention",
 "Lipid management and dyslipidemia",
 "Hypertension treatment guidelines",
 "Preventive cardiology"
]

Each value in knowsAbout can be a plain string (as above), but schema.org also accepts a Thing object with a name and optionally a url pointing to a recognized taxonomy. For health content, linking to MedlinePlus, ICD-10 categories, or MeSH terms adds machine-verifiable precision that plain strings cannot.

"knowsAbout": [
 {
 "@type": "MedicalCondition",
 "name": "Hypertension",
 "url": "https://medlineplus.gov/highbloodpressure.html"
 }
]

Limit knowsAbout to topics the author genuinely has credentials or published work in. An overly broad list – covering every system of medicine – weakens the signal rather than strengthening it. Specificity is what makes this property useful to AI systems evaluating whether an author is an appropriate source for a particular health query.

Step 6: Connect the Author to Published Articles Using the author Property

Author schema only earns its value when it is connected to specific published pages. The connection is made through the Article (or MedicalWebPage) schema block that wraps each piece of content, using the author property to reference the Person entity.

{
 "@context": "https://schema.org",
 "@type": "MedicalWebPage",
 "headline": "Managing High LDL Cholesterol: Evidence-Based Approaches",
 "datePublished": "2025-01-15",
 "dateModified": "2025-06-01",
 "author": {
 "@type": "Person",
 "name": "Dr. Sarah Okonkwo",
 "url": "https://www.yourdomain.com/authors/dr-sarah-okonkwo"
 },
 "publisher": {
 "@type": "Organization",
 "name": "YourHealthSite",
 "url": "https://www.yourdomain.com"
 }
}

The author object here does not need to repeat every credential property from the full Person schema block. Referencing the author by name and URL is sufficient – search engines and AI systems follow the URL to retrieve the full entity definition. This keeps individual article schema blocks concise while maintaining the full richness of the author's credentials at the entity level.

For healthcare publishers using HealthTopicContent schema, the author property connects in the same way, with MedicalWebPage as the article type rather than a generic Article.

Step 7: Add Clinical Reviewers Using reviewedBy

Many medical publishers separate authorship from clinical review – a health writer drafts the content, a physician reviews it for clinical accuracy. Both roles carry distinct authority signals, and schema.org supports both through separate properties.

The reviewedBy property attaches to the page-level schema, not the author entity:

{
 "@context": "https://schema.org",
 "@type": "MedicalWebPage",
 "headline": "Managing High LDL Cholesterol: Evidence-Based Approaches",
 "author": {
 "@type": "Person",
 "name": "James Whitfield",
 "url": "https://www.yourdomain.com/authors/james-whitfield"
 },
 "reviewedBy": {
 "@type": "Person",
 "name": "Dr. Sarah Okonkwo",
 "url": "https://www.yourdomain.com/authors/dr-sarah-okonkwo"
 }
}

The reviewer referenced in reviewedBy should have their own full Person schema block – with hasCredential, alumniOf, memberOf, and knowsAbout – on their author profile page. The reviewedBy property on the article page creates the connection; the author profile page holds the credential detail.

This separation matters for AI search. A system evaluating whether to cite a health page considers both who wrote it and who verified it. A clinical review by a board-certified specialist in the relevant field meaningfully raises the credibility signal of pages written by non-physician health writers.

Step 8: Assemble the Complete JSON-LD Block

The complete implementation combines the author's Person schema (typically placed on the author's profile page or in a sitewide <script> block) with the article-level schema (placed in the <head> of each article page). Here is a complete, production-ready example:

Author Profile Page Schema

<script type="application/ld+json">
{
 "@context": "https://schema.org",
 "@type": "Person",
 "name": "Dr. Sarah Okonkwo",
 "jobTitle": "Cardiologist",
 "url": "https://www.yourdomain.com/authors/dr-sarah-okonkwo",
 "image": "https://www.yourdomain.com/images/authors/sarah-okonkwo.jpg",
 "sameAs": [
 "https://orcid.org/0000-0001-2345-6789",
 "https://www.linkedin.com/in/sarahokonkwo",
 "https://scholar.google.com/citations?user=EXAMPLEID"
 ],
 "hasCredential": [
 {
 "@type": "EducationalOccupationalCredential",
 "credentialCategory": "degree",
 "name": "Doctor of Medicine (MD)",
 "recognizedBy": {
 "@type": "Organization",
 "name": "University of Lagos College of Medicine"
 }
 },
 {
 "@type": "EducationalOccupationalCredential",
 "credentialCategory": "certification",
 "name": "Board Certification in Cardiovascular Disease",
 "recognizedBy": {
 "@type": "Organization",
 "name": "American Board of Internal Medicine"
 }
 }
 ],
 "alumniOf": [
 {
 "@type": "EducationalOrganization",
 "name": "Johns Hopkins School of Medicine"
 },
 {
 "@type": "MedicalOrganization",
 "name": "Cleveland Clinic",
 "description": "Cardiovascular Medicine Fellowship"
 }
 ],
 "memberOf": [
 {
 "@type": "MedicalOrganization",
 "name": "American College of Cardiology",
 "url": "https://www.acc.org"
 }
 ],
 "knowsAbout": [
 "Cardiovascular disease prevention",
 "Lipid management and dyslipidemia",
 "Hypertension",
 "Heart failure management"
 ]
}
</script>

Article Page Schema

<script type="application/ld+json">
{
 "@context": "https://schema.org",
 "@type": "MedicalWebPage",
 "headline": "Managing High LDL Cholesterol: Evidence-Based Approaches",
 "description": "A clinician-reviewed guide to lowering LDL cholesterol through lifestyle modification and pharmacological treatment.",
 "datePublished": "2025-01-15",
 "dateModified": "2025-06-01",
 "url": "https://www.yourdomain.com/articles/managing-high-ldl-cholesterol",
 "author": {
 "@type": "Person",
 "name": "Dr. Sarah Okonkwo",
 "url": "https://www.yourdomain.com/authors/dr-sarah-okonkwo"
 },
 "publisher": {
 "@type": "Organization",
 "name": "YourHealthSite",
 "url": "https://www.yourdomain.com",
 "logo": {
 "@type": "ImageObject",
 "url": "https://www.yourdomain.com/images/logo.png"
 }
 },
 "medicalAudience": {
 "@type": "MedicalAudience",
 "audienceType": "Patient"
 }
}
</script>

Placing the Person schema on a dedicated author profile page – rather than repeating the full block on every article – keeps implementation manageable and allows the entity definition to scale independently of individual articles. Schema generators that scan page content can accelerate this process considerably; the AI-powered schema markup generator reads the full content of a page and populates the correct properties for healthcare schema types, including the complete Person and MedicalWebPage suite, rather than pattern-matching on keywords.

Step 9: Validate the Markup and Confirm Indexing

Before schema goes live, it must pass validation. Two tools cover the necessary checks:

  1. Google's Rich Results Test (search.google.com/test/rich-results): Paste your page URL or code snippet to confirm there are no syntax errors and that the schema renders correctly.
  2. Schema.org Validator (validator.schema.org): Tests conformance with the schema.org specification, independent of Google's specific rich results requirements.

After validation, submit the updated URLs through Google Search Console's URL Inspection tool to accelerate indexing of the new structured data. Monitor the Coverage and Enhancements reports in Search Console over the following two to four weeks to confirm Google has processed the schema without errors.

Common errors to watch for at this stage:

  • Missing required properties on EducationalOccupationalCredential (name and recognizedBy are both expected)
  • Mismatched URLs between the author.url reference in article schema and the actual URL of the author's profile page
  • JSON syntax errors from unclosed brackets or missing commas – a linter like JSONLint catches these before validation
  • Using Article instead of MedicalWebPage for health content, which signals a weaker health-specific authority claim

Detailed guidance on validating structured data and fixing errors covers the full remediation workflow for each error type that search engines commonly flag.

Step 10: Build Author Profile Pages That Reinforce the Schema

Structured data functions as a machine-readable layer on top of human-readable content. For author schema to carry full weight, the author profile page it points to must contain the same credential information in visible, indexable prose – not just in the JSON-LD block.

An effective medical author profile page includes:

  • Full name and professional title (matching the schema exactly)
  • Credentials listed in visible text (MD, PhD, board certification with specialty and issuing board)
  • Educational history (medical school, residency, fellowship)
  • Current institutional affiliation and role
  • Publication history or links to authored articles on the site
  • External professional profile links (ORCID, Google Scholar, medical society directory)

The schema and the page content should tell exactly the same story. AI systems that evaluate source credibility cross-reference what structured data claims against what the page actually says. Discrepancies – a credential in the schema that appears nowhere on the page – reduce the reliability signal rather than strengthening it.

For healthcare publishers managing multiple contributing authors, this principle extends to every contributor page: each one needs both the visible credential content and the corresponding structured data. Healthcare schema markup for broader clinical contexts covers how these author entities fit within the wider schema architecture of a health-focused site.

FAQ

What Is hasCredential in Person Schema and Why Does It Matter for Medical Content?

hasCredential is a schema.org property that attaches formal qualifications – medical degrees, board certifications, and professional licenses – to a Person entity as structured EducationalOccupationalCredential objects. For medical content, this property matters because it converts prose credential claims into machine-readable facts that search engines and AI systems can evaluate when assessing whether a source is qualified to publish on a health topic. Pages with credentialed author markup are more likely to satisfy Google's E-E-A-T requirements for YMYL content and more likely to be cited by AI tools as authoritative health sources.

How Is reviewedBy Different From author in Healthcare Schema?

author identifies who wrote the content. reviewedBy identifies who evaluated the content for clinical accuracy – typically a licensed physician or specialist. Both properties attach to the article-level schema, and both reference Person entities with their own credential markup. The distinction matters because AI systems and search quality evaluators treat independent clinical review as a separate, additive trust signal: a health article written by a non-physician but reviewed by a board-certified specialist carries stronger authority signals than one that lacks a review attribution entirely.

Should the Full Person Schema Block Appear on Every Article Page?

No. The best practice is to place the complete Person schema block – with hasCredential, alumniOf, memberOf, and knowsAbout – on the author's dedicated profile page. Article pages reference the author by name and URL using a concise author object. Search engines and AI retrieval systems follow the URL to retrieve the full entity definition. Repeating the full block on every article is unnecessary and increases the risk of inconsistencies if credentials need to be updated.

How Many Credentials Should Be Included in hasCredential?

Include all credentials that are directly relevant to the subject matter of the health content the author publishes. A cardiologist writing about cardiovascular disease should list their MD, cardiology board certification, and any subspecialty certifications. Credentials unrelated to the content category – a culinary certification held by the same physician – add no authority signal and should be omitted. The goal is relevance and verifiability, not an exhaustive credential inventory.

Does knowsAbout Improve AI Citation Rates for Health Content?

Yes, when used accurately. knowsAbout tells AI retrieval systems which specific medical domains an author is qualified to address. A health AI query about hypertension management is more likely to surface a page whose author's schema explicitly declares hypertension as a domain of expertise, compared to a page whose author schema contains only a generic MD credential. The property functions as a topical authority signal at the entity level, complementing the topical depth signals built through content clusters and related articles.

What External Identifiers Work Best for Medical Authors?

ORCID iDs are the strongest external identifier for researchers and clinical authors because ORCID (Open Researcher and Contributor ID) maintains a globally recognized, persistent identifier system specifically designed for academic and healthcare contributors. PubMed author profiles, Google Scholar pages, and institutional faculty directories serve as strong secondary identifiers. LinkedIn profiles are acceptable supporting references but carry less authority than academic or clinical identifiers. All external URLs included in sameAs should be stable, publicly accessible, and maintained by the author or their institution.

Can Author Schema Help a Health Site Rank Better in Google AI Overviews?

Credentialed author schema strengthens the E-E-A-T signals that Google's quality evaluation systems use to assess YMYL content, and Google AI Overviews draw heavily from pages that pass that quality threshold. While no single schema property guarantees inclusion in AI Overviews, pages with verified, credentialed author entities consistently outperform anonymously authored health content in both traditional rankings and AI-generated answer citations. Author schema is one component of a broader structured data strategy; MedicalCondition and MedicalProcedure schema on the same pages further reinforces the topical authority signals that drive AI citation.

What Happens If the Author Schema and the Visible Profile Page Content Do Not Match?

Discrepancies between structured data claims and visible page content reduce the reliability of both signals. If an author's schema lists a board certification that does not appear anywhere on the profile page, AI systems evaluating source credibility may treat the claim as unverified. Google's quality guidelines explicitly value consistency between on-page content and structured data. The author profile page and its corresponding JSON-LD block should contain identical credential information – any update to one should be applied to the other simultaneously.

What to Do Now

  1. Audit your existing author pages. Identify every medical writer, clinical contributor, and reviewer who publishes on your site. For each, note which credentials, affiliations, and educational backgrounds are already documented in visible prose and which still need to be added.

  2. Create or update author profile pages. Each contributing author needs a dedicated URL containing their full credential information in readable text – this is the foundation that the structured data references and that AI systems verify against.

  3. Build the Person schema blocks. Starting with your highest-credentialed authors, write complete JSON-LD blocks including hasCredential, alumniOf, memberOf, knowsAbout, and sameAs with ORCID or equivalent identifiers. Place these in the <head> of each author profile page.

  4. Update article-level schema. On each published health article, add or update the author property to reference the author's profile URL, and add reviewedBy for any articles with a named clinical reviewer.

  5. Validate and monitor. Run each page through Google's Rich Results Test and the schema.org validator before publishing. Submit updated URLs through Search Console and monitor the Enhancements report for errors over the following month.

  6. Extend the schema to your full content library. Author markup on a handful of articles does not build the entity authority that comes from consistent implementation across your entire site. Prioritize your highest-traffic health pages first, then work systematically through the rest.

For teams managing large volumes of health content across multiple authors, generating JSON-LD at scale reduces the manual overhead of applying this process page by page without sacrificing accuracy.

Generate JSON-LD Schema for your medical author pages using AuthorityStack.ai's AI-powered schema generator – paste a URL, and it produces accurate Person and MedicalWebPage markup populated from your actual page content.