Schema stack

    Job Board Stack

    Job board/listing pages with an ItemList of JobPostings, FAQs, and breadcrumb navigation.

    Included schema
    Item List
    Job Posting
    Frequently Asked Questions
    Breadcrumb
    Fit

    When to use this stack

    • Job board/category pages listing multiple openings
    • Career hubs that need structured listings plus FAQs
    • Pages where breadcrumb context and FAQ coverage reduce user friction
    Composition

    What is included

    • Represents the list of job postings on the page.

    • Captures each individual job with title, location, and hiring org.

    • Answers application process, timeline, and remote eligibility questions.

    • Provides navigation context from the careers hub.

    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[].@type=ListItem
    • itemListElement[].item.@type=JobPosting
    • itemListElement[].item.datePosted
    • itemListElement[].item.description
    • itemListElement[].item.employmentType
    • itemListElement[].item.hiringOrganization.name
    • itemListElement[].item.jobLocation.address.addressCountry
    • itemListElement[].item.title
    • itemListElement[].name
    • mainEntity[].@type=Question
    • mainEntity[].acceptedAnswer.text

    Recommended properties

    • itemListElement[].item
    • itemListElement[].item.applicantLocationRequirements.name
    • itemListElement[].item.baseSalary.currency
    • itemListElement[].item.baseSalary.value
    • itemListElement[].item.directApply
    • itemListElement[].item.jobLocation.address.addressLocality
    • itemListElement[].item.jobLocation.address.addressRegion
    • itemListElement[].item.jobLocation.address.postalCode
    • itemListElement[].item.title
    • itemListElement[].item.url
    • itemListElement[].item.validThrough
    • itemListElement[].position
    • mainEntity[].acceptedAnswer.text
    • mainEntity[].author.name
    • mainEntity[].name
    Copy-ready example

    Combined JSON-LD

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

    [
      {
        "@context": "https://schema.org",
        "@type": "ItemList",
        "@id": "https://www.example.com/careers/engineering#list",
        "name": "Engineering Jobs",
        "itemListElement": [
          {
            "@type": "ListItem",
            "position": 1,
            "item": {
              "@type": "JobPosting",
              "@id": "https://www.example.com/careers/senior-frontend#job",
              "title": "Senior Frontend Engineer",
              "description": "Lead frontend initiatives using React/TypeScript. Improve performance and DX.",
              "datePosted": "2025-02-10",
              "validThrough": "2025-04-30",
              "employmentType": "FULL_TIME",
              "jobLocation": {
                "@type": "Place",
                "address": {
                  "@type": "PostalAddress",
                  "addressCountry": "US",
                  "addressLocality": "Remote"
                }
              },
              "hiringOrganization": {
                "@type": "Organization",
                "name": "Example Corp",
                "sameAs": "https://www.example.com"
              },
              "baseSalary": {
                "@type": "MonetaryAmount",
                "currency": "USD",
                "value": {
                  "@type": "QuantitativeValue",
                  "minValue": 150000,
                  "maxValue": 190000,
                  "unitText": "YEAR"
                }
              },
              "applicantLocationRequirements": {
                "@type": "Country",
                "name": "United States"
              },
              "directApply": true
            }
          },
          {
            "@type": "ListItem",
            "position": 2,
            "item": {
              "@type": "JobPosting",
              "@id": "https://www.example.com/careers/data-engineer#job",
              "title": "Data Engineer",
              "description": "Build and optimize our analytics pipelines and data platform.",
              "datePosted": "2025-01-28",
              "employmentType": "FULL_TIME",
              "jobLocation": {
                "@type": "Place",
                "address": {
                  "@type": "PostalAddress",
                  "addressCountry": "US",
                  "addressLocality": "Austin",
                  "addressRegion": "TX",
                  "postalCode": "73301"
                }
              },
              "hiringOrganization": {
                "@type": "Organization",
                "name": "Example Corp",
                "sameAs": "https://www.example.com"
              },
              "baseSalary": {
                "@type": "MonetaryAmount",
                "currency": "USD",
                "value": {
                  "@type": "QuantitativeValue",
                  "minValue": 140000,
                  "maxValue": 180000,
                  "unitText": "YEAR"
                }
              },
              "directApply": true
            }
          }
        ]
      },
      {
        "@context": "https://schema.org",
        "@type": "FAQPage",
        "mainEntity": [
          {
            "@type": "Question",
            "name": "Do you hire remotely?",
            "acceptedAnswer": {
              "@type": "Answer",
              "text": "Yes. Roles marked Remote accept applicants in the listed countries. Check applicantLocationRequirements for any restrictions."
            }
          },
          {
            "@type": "Question",
            "name": "How long does the process take?",
            "acceptedAnswer": {
              "@type": "Answer",
              "text": "Our typical process is 2-3 weeks: recruiter screen, hiring manager interview, panel, then offer."
            }
          },
          {
            "@type": "Question",
            "name": "How do I apply?",
            "acceptedAnswer": {
              "@type": "Answer",
              "text": "Use the Apply link on each job. We do not accept applications via email. DirectApply is supported from the job page."
            }
          }
        ]
      },
      {
        "@context": "https://schema.org",
        "@type": "BreadcrumbList",
        "itemListElement": [
          { "@type": "ListItem", "position": 1, "name": "Home", "item": "https://www.example.com" },
          { "@type": "ListItem", "position": 2, "name": "Careers", "item": "https://www.example.com/careers" },
          { "@type": "ListItem", "position": 3, "name": "Engineering", "item": "https://www.example.com/careers/engineering" }
        ]
      }
    ]
    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

    How many JobPosting objects should I include?

    Include one JobPosting per listing visible on the page. Keep titles, locations, and salaries aligned with the UI.

    Do I need directApply?

    Set directApply to true only if candidates can apply directly on the page without intermediate redirects.

    Primary sources

    References