Cookies & analytics

    We use cookies for analytics and to serve ads. Accept to enable Google Analytics and AdSense. You can decline to stay opt-out.

    SwiftSchema Logo

    SwiftSchema

    Intuitive Schema Generation at Your Fingertips

    AboutLearnContact
      Stack

      Profile / Portfolio Stack

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

      Open generatorValidate in Rich Results Test

      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

      What's included

      Required properties (stack union)

      Ensure every applicable required property is present in your implementation. Nested props reference their parent objects (for example, `offers.priceCurrency`).

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

      Recommended properties (stack union)

      description
      image
      itemListElement[].item
      mainEntity[].acceptedAnswer.text
      mainEntity[].author.name
      mainEntity[].name
      sameAs[]
      worksFor.name

      Combined JSON-LD

      Paste as a single script tag. Keep product details, offer data, shipping/returns, and FAQ answers in sync with the 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" }
    ]
  }
]

      Implementation steps

      1. Start from your live product detail page content; ensure titles, prices, and availability match the page.
      2. Embed one JSON-LD script in the head or just before the closing body tag using the combined example as a template.
      3. Fill shipping details for each region you serve and keep them aligned with on-page shipping tables.
      4. Attach your canonical MerchantReturnPolicy URL and keep the policy text in sync with Merchant Center.
      5. Add 3–6 FAQs that address purchase blockers (shipping, returns, compatibility) and keep answers consistent with visible content.
      6. Validate in the Rich Results Test and revalidate after price/availability/policy changes.

      Common errors and fixes

      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.

      References