SwiftSchemaGenerate
    Schema stack

    Job Posting Stack

    Job detail pages with employer identity, salary clarity, FAQs, and breadcrumb context for boards or career sites.

    Open generatorValidate in Rich Results Test
    Included schema
    Job Posting
    Organization
    Frequently Asked Questions
    Breadcrumb
    Fit

    When to use this stack

    • Individual job postings that need clear employer, pay, and location signals
    • Roles where applicants expect direct apply, eligibility, and process clarity
    • Job board listings that must stay in sync with on-page content
    Composition

    What is included

    • Job Posting

      Primary job entity with title, description, employer, location, and pay.

    • Organization

      Employer identity for trust, logo, and brand alignment.

    • Frequently Asked Questions

      Answer application process, eligibility, and location questions.

    • Breadcrumb

      Navigation context within careers or a job board.

    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

    • datePosted
    • description
    • employmentType
    • hiringOrganization.@id
    • itemListElement[].name
    • jobLocation.address.addressCountry
    • jobLocation.address.addressLocality
    • jobLocation.address.addressRegion
    • logo
    • mainEntity[].@type=Question
    • mainEntity[].acceptedAnswer.text
    • name
    • title
    • url
    • validThrough

    Recommended properties

    • applicantLocationRequirements.name
    • baseSalary.currency
    • baseSalary.value.unitText
    • baseSalary.value.value
    • contactPoint.contactType
    • contactPoint.telephone
    • directApply
    • educationRequirements
    • estimatedSalary.currency
    • estimatedSalary.percentile50.value
    • experienceRequirements
    • identifier.value
    • industry
    • itemListElement[].item
    • jobLocationType
    • mainEntity[].acceptedAnswer.text
    • mainEntity[].author.name
    • mainEntity[].name
    • occupationalCategory
    • sameAs[]
    • url
    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": "JobPosting",
    "@id": "https://www.example.com/jobs/senior-product-manager#job",
    "title": "Senior Product Manager",
    "description": "Lead the strategy and roadmap for our analytics platform, working with design and engineering to ship high-quality features.",
    "datePosted": "2026-02-21",
    "validThrough": "2026-03-31",
    "employmentType": "FULL_TIME",
    "jobLocationType": "HYBRID",
    "hiringOrganization": {
      "@type": "Organization",
      "@id": "https://www.example.com/#org",
      "name": "Northwind Analytics"
    },
    "jobLocation": {
      "@type": "Place",
      "address": {
        "@type": "PostalAddress",
        "streetAddress": "400 Market St",
        "addressLocality": "San Francisco",
        "addressRegion": "CA",
        "postalCode": "94111",
        "addressCountry": "US"
      }
    },
    "applicantLocationRequirements": {
      "@type": "Country",
      "name": "US"
    },
    "directApply": true,
    "baseSalary": {
      "@type": "MonetaryAmount",
      "currency": "USD",
      "value": {
        "@type": "QuantitativeValue",
        "value": 180000,
        "unitText": "YEAR"
      }
    },
    "estimatedSalary": {
      "@type": "MonetaryAmountDistribution",
      "currency": "USD",
      "unitText": "YEAR",
      "percentile10": { "@type": "MonetaryAmount", "value": 160000, "currency": "USD" },
      "percentile50": { "@type": "MonetaryAmount", "value": 180000, "currency": "USD" },
      "percentile90": { "@type": "MonetaryAmount", "value": 205000, "currency": "USD" }
    },
    "industry": "Software",
    "occupationalCategory": "15-1299.08",
    "educationRequirements": "BA/BS or equivalent experience",
    "experienceRequirements": "5+ years in product management; experience with analytics products",
    "identifier": {
      "@type": "PropertyValue",
      "name": "Job ID",
      "value": "PM-2026-02"
    },
    "url": "https://www.example.com/jobs/senior-product-manager/apply"
  },
  {
    "@context": "https://schema.org",
    "@type": "Organization",
    "@id": "https://www.example.com/#org",
    "name": "Northwind Analytics",
    "url": "https://www.example.com",
    "logo": "https://www.example.com/images/logo-120x60.png",
    "sameAs": [
      "https://www.linkedin.com/company/northwind-analytics",
      "https://twitter.com/northwind"
    ]
  },
  {
    "@context": "https://schema.org",
    "@type": "FAQPage",
    "mainEntity": [
      {
        "@type": "Question",
        "name": "Is this role remote-friendly?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "Yes. We are hybrid with hubs in SF and NYC; candidates anywhere in the US can apply."
        }
      },
      {
        "@type": "Question",
        "name": "What does the interview process look like?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "Intro call, product sense interview, a collaborative case with engineering, and a final panel. No take-home assignment."
        }
      }
    ]
  },
  {
    "@context": "https://schema.org",
    "@type": "BreadcrumbList",
    "itemListElement": [
      { "@type": "ListItem", "position": 1, "name": "Home", "item": "https://www.example.com" },
      { "@type": "ListItem", "position": 2, "name": "Jobs", "item": "https://www.example.com/jobs" },
      { "@type": "ListItem", "position": 3, "name": "Senior Product Manager", "item": "https://www.example.com/jobs/senior-product-manager" }
    ]
  }
]
    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 estimatedSalary?

    Optional. Include it if you have vetted ranges; otherwise stick to baseSalary to avoid mismatches.

    How do I keep JSON-LD in sync with the page?

    Source the JSON-LD from the same backend fields that render the job card. Update dateModified when changing compensation, location, or eligibility.

    Primary sources

    References