SwiftSchemaGenerate
    Schema stack

    Profile / Portfolio Stack

    Personal profile/portfolio pages with Person + ProfilePage + WebPage, FAQs, and breadcrumb context.

    Open generatorValidate in Rich Results Test
    Included schema
    Profile Page
    Person
    Web Page
    Frequently Asked Questions
    Breadcrumb
    Fit

    When to use this stack

    • Personal sites or portfolio pages showcasing work and contact
    • Author/creator profiles needing clear identity and navigation
    • Pages where FAQs clarify services, availability, and contact
    Composition

    What is included

    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

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

    Recommended properties

    • description
    • image
    • itemListElement[].item
    • mainEntity[].acceptedAnswer.text
    • mainEntity[].author.name
    • mainEntity[].name
    • sameAs[]
    • worksFor.name
    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": "ProfilePage",
    "@id": "https://www.example.com/about#profile",
    "name": "Alex Doe — Designer",
    "url": "https://www.example.com/about",
    "description": "Portfolio and contact for Alex Doe, product designer."
  },
  {
    "@context": "https://schema.org",
    "@type": "Person",
    "@id": "https://www.example.com/about#person",
    "name": "Alex Doe",
    "jobTitle": "Product Designer",
    "url": "https://www.example.com/about",
    "image": "https://www.example.com/images/alex.jpg",
    "worksFor": { "@type": "Organization", "name": "Northwind" },
    "sameAs": [
      "https://www.linkedin.com/in/alexdoe",
      "https://dribbble.com/alexdoe"
    ]
  },
  {
    "@context": "https://schema.org",
    "@type": "WebPage",
    "@id": "https://www.example.com/about#page",
    "name": "About Alex Doe",
    "url": "https://www.example.com/about",
    "description": "Portfolio, case studies, and contact for Alex Doe."
  },
  {
    "@context": "https://schema.org",
    "@type": "FAQPage",
    "mainEntity": [
      { "@type": "Question", "name": "Are you available for freelance?", "acceptedAnswer": { "@type": "Answer", "text": "Yes. Availability opens in April; email for details." } },
      { "@type": "Question", "name": "Do you take speaking engagements?", "acceptedAnswer": { "@type": "Answer", "text": "Yes. Topics include product design systems and UX research." } }
    ]
  },
  {
    "@context": "https://schema.org",
    "@type": "BreadcrumbList",
    "itemListElement": [
      { "@type": "ListItem", "position": 1, "name": "Home", "item": "https://www.example.com" },
      { "@type": "ListItem", "position": 2, "name": "About", "item": "https://www.example.com/about" }
    ]
  }
]
    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

    Do I need both ProfilePage and WebPage?

    ProfilePage is a subtype of WebPage; including both is optional but adds clarity. Keep names/URLs consistent.

    What if I have multiple people?

    Use one Person per profile page. For team pages, see the About / Team stack.

    Primary sources

    References