reviewedBy

reviewedBy · Not mentioned by Google

Appears in

• MedicalWebPage

What is it?

The person or organization that reviewed the web page content for accuracy and completeness. For medical web pages, reviewedBy identifies the qualified healthcare professional or medical board that verified the health information is correct. This is one of the strongest E-E-A-T signals available in structured data for health content.

Why this matters for AEO

AI answer engines prioritize medically reviewed content for health queries. When a user asks "is metformin safe during pregnancy?", the AI evaluates source credibility before generating an answer. A page with reviewedBy pointing to "Dr. James Chen, MD, FASAM" with verifiable credentials carries more weight than an anonymous health article. Structured reviewer data lets AI engines trace the credentialing chain programmatically.

What the specs say

Schema.org: Organization or Person. People or organizations that have reviewed the content on this web page for accuracy and/or completeness. schema.org/reviewedBy

Google: Not mentioned. No dedicated Google structured data page exists for MedicalWebPage.

How to find your value

• Byline area — "Medically reviewed by Dr. [Name]" text near the author
• Footer disclosure — Editorial review policy section
• About/team page — Medical advisory board listing
• Credentials database — NPI registry, state medical board, specialty board certifications

Format and code

Use a Person object with credentials for individual reviewers, or an Organization for board/committee reviews.

Person reviewer with credentials:

{
  "@context": "https://schema.org",
  "@type": "MedicalWebPage",
  "name": "Understanding Addiction Treatment Options",
  "reviewedBy": {
    "@type": "Person",
    "name": "Dr. James Chen, MD, FASAM",
    "jobTitle": "Medical Director, Addiction Medicine",
    "hasCredential": {
      "@type": "EducationalOccupationalCredential",
      "credentialCategory": "American Board of Addiction Medicine"
    },
    "worksFor": {
      "@type": "Organization",
      "name": "Recovery Medical Center"
    }
  },
  "lastReviewed": "2024-12-01"
}

Organization reviewer:

{
  "@context": "https://schema.org",
  "@type": "MedicalWebPage",
  "name": "Heart Disease Prevention Guide",
  "reviewedBy": {
    "@type": "Organization",
    "name": "American Heart Association Medical Advisory Board"
  }
}

Webflow implementation

Static pages

Add the reviewer in the JSON-LD block in Page Settings > Custom Code:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "MedicalWebPage",
  "name": "Health Topic",
  "reviewedBy": {
    "@type": "Person",
    "name": "Dr. Name, MD",
    "jobTitle": "Specialty"
  },
  "lastReviewed": "2024-09-15"
}
</script>

CMS template pages

Create a reference field in your articles CMS collection linking to a "Reviewers" collection that stores name, credentials, job title, and organization. Pull these values dynamically into the JSON-LD embed.

In Schema HQ

The reviewedBy Person or Organization object from CMS fields, including credential and affiliation data when available. is built automatically

Related fields

• lastReviewed
• medicalAudience
• specialty
• author
• publisher

FAQ

How is reviewedBy different from author?

author identifies who wrote the content. reviewedBy identifies who checked it for accuracy. In health content, the author might be a health writer while the reviewer is a board-certified physician. Both can (and should) be included.

Should reviewedBy link to a verifiable profile?

Yes. Adding sameAs with URLs to verifiable profiles (NPI registry, Healthgrades, LinkedIn, hospital staff page) strengthens the credentialing signal. AI engines and Google's E-E-A-T evaluation benefit from traceable, verifiable reviewer identities.

Can a page have multiple reviewers?

Yes. Use an array of Person or Organization objects. This is common for pages reviewed by both a subject-matter specialist and a general medical editor.