SwiftSchemaGenerate
    Schema stack

    Scholar Profile Stack

    Scholar/researcher profiles with Person + CreativeWork context, FAQs, and breadcrumb navigation.

    Open generatorValidate in Rich Results Test
    Included schema
    Person
    Creative Work
    Frequently Asked Questions
    Breadcrumb
    Fit

    When to use this stack

    • Faculty or researcher profile pages
    • Scholar bios with publications and research focus
    • Pages where FAQs clarify office hours, topics, or collaboration
    Composition

    What is included

    • Person

      Represents the scholar with name, affiliation, and profile URL.

    • Creative Work

      Highlights publications or research outputs linked to the scholar.

    • Frequently Asked Questions

      Answers common questions about research areas and contact.

    • Breadcrumb

      Provides navigation context to the scholar profile.

    Data contract

    Properties across the bundle

    Nested properties keep their parent path, such as offers.priceCurrency. Only publish values that match visible page content.

    Required properties

    • author.name
    • itemListElement[].name
    • mainEntity[].@type=Question
    • mainEntity[].acceptedAnswer.text
    • name
    • url

    Recommended properties

    • affiliation.name
    • datePublished
    • description
    • image
    • itemListElement[].item
    • jobTitle
    • mainEntity[].acceptedAnswer.text
    • mainEntity[].author.name
    • mainEntity[].name
    • publisher.name
    • sameAs[]
    Copy-ready example

    Combined JSON-LD

    Paste this as one script tag, then replace every example value with data from the live page.

    Validate
    [
  {
    "@context": "https://schema.org",
    "@type": "Person",
    "@id": "https://www.example.com/scholars/rivera#person",
    "name": "Dr. Maya Rivera",
    "url": "https://www.example.com/scholars/rivera",
    "jobTitle": "Professor of Computer Science",
    "affiliation": {
      "@type": "Organization",
      "name": "Northwind University"
    },
    "image": "https://www.example.com/images/maya-rivera.webp",
    "sameAs": [
      "https://scholar.google.com/citations?user=rivera",
      "https://orcid.org/0000-0002-1825-0097"
    ]
  },
  {
    "@context": "https://schema.org",
    "@type": "CreativeWork",
    "@id": "https://www.example.com/scholars/rivera#paper-1",
    "name": "Distributed Systems at Scale",
    "author": {
      "@type": "Person",
      "name": "Dr. Maya Rivera"
    },
    "url": "https://www.example.com/publications/distributed-systems",
    "datePublished": "2024-11-20",
    "publisher": {
      "@type": "Organization",
      "name": "ACM"
    }
  },
  {
    "@context": "https://schema.org",
    "@type": "FAQPage",
    "mainEntity": [
      {
        "@type": "Question",
        "name": "What are your research areas?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "Distributed systems, resiliency engineering, and performance optimization."
        }
      },
      {
        "@type": "Question",
        "name": "Do you accept graduate students?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "Yes. Please review the lab page and email a brief research statement."
        }
      },
      {
        "@type": "Question",
        "name": "How can I collaborate?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "Use the contact form and include a summary of your project and timeline."
        }
      }
    ]
  },
  {
    "@context": "https://schema.org",
    "@type": "BreadcrumbList",
    "itemListElement": [
      { "@type": "ListItem", "position": 1, "name": "Home", "item": "https://www.example.com" },
      { "@type": "ListItem", "position": 2, "name": "Scholars", "item": "https://www.example.com/scholars" },
      { "@type": "ListItem", "position": 3, "name": "Dr. Maya Rivera", "item": "https://www.example.com/scholars/rivera" }
    ]
  }
]
    Workflow

    Implement and verify

    1. 01

      Start with the live page

      Confirm titles, prices, availability, policies, and visible FAQ content before generating markup.

    2. 02

      Add one JSON-LD script

      Use the combined example as a template in the document head or before the closing body tag.

    3. 03

      Complete regional details

      Fill shipping destinations and timing for every region the page actually serves.

    4. 04

      Link the return policy

      Use a stable MerchantReturnPolicy URL and keep its terms synchronized with the page.

    5. 05

      Match visible answers

      Add only FAQs that users can read on the same page, with identical answers.

    6. 06

      Validate after changes

      Run Rich Results Test after implementation and whenever price, availability, or policy data changes.

    Quality check

    Common errors and fixes

    • Missing currency or availability

      Use ISO currency codes and complete schema.org availability URLs in Offer data.

    • Incomplete shipping details

      Include shippingDestination.addressCountry and deliveryTime.transitTime with units.

    • Return policy is not connected

      Reference MerchantReturnPolicy from the Offer and provide a stable public policy URL.

    • FAQ answers differ from the page

      Keep structured FAQ answers identical to visible answers.

    Questions

    Stack FAQs

    Can I list multiple publications?

    Yes. Add one CreativeWork per publication with unique @id and URL values.

    Should I include affiliations?

    Include affiliation when it is visible on the page to strengthen entity context.

    Primary sources

    References