Schema stack

    Occupational Guide Stack

    Occupation guide pages with role details, FAQs, and breadcrumb navigation.

    Included schema
    Occupation
    Frequently Asked Questions
    Breadcrumb
    Fit

    When to use this stack

    • Career path guide pages for specific roles
    • Occupation overview pages describing duties and skills
    • Pages where FAQs clarify education and salary expectations
    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

    • description
    • itemListElement[].name
    • mainEntity[].@type=Question
    • mainEntity[].acceptedAnswer.text
    • name
    • occupationLocation.name
    • skills

    Recommended properties

    • educationRequirements
    • estimatedSalary.median
    • experienceRequirements
    • itemListElement[].item
    • mainEntity[].acceptedAnswer.text
    • mainEntity[].author.name
    • mainEntity[].name
    • responsibilities
    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": "Occupation",
        "@id": "https://www.example.com/careers/data-analyst#occupation",
        "name": "Data Analyst",
        "description": "Analyze and interpret data to support business decisions and performance tracking.",
        "occupationLocation": {
          "@type": "AdministrativeArea",
          "name": "United States"
        },
        "skills": [
          "SQL",
          "Data visualization",
          "Statistics"
        ],
        "responsibilities": "Build dashboards, analyze trends, and deliver insights to stakeholders.",
        "educationRequirements": "Bachelor's degree in analytics, business, or a related field.",
        "experienceRequirements": "1-3 years of analytics or reporting experience.",
        "estimatedSalary": {
          "@type": "MonetaryAmountDistribution",
          "currency": "USD",
          "duration": "P1Y",
          "median": 75000,
          "percentile10": 55000,
          "percentile90": 105000
        }
      },
      {
        "@context": "https://schema.org",
        "@type": "FAQPage",
        "mainEntity": [
          {
            "@type": "Question",
            "name": "What tools do data analysts use?",
            "acceptedAnswer": {
              "@type": "Answer",
              "text": "Common tools include SQL, Excel, Python, Tableau, and Power BI."
            }
          },
          {
            "@type": "Question",
            "name": "Is a degree required?",
            "acceptedAnswer": {
              "@type": "Answer",
              "text": "Many roles prefer a bachelor's degree, but strong portfolios and certifications can qualify candidates."
            }
          },
          {
            "@type": "Question",
            "name": "What is the typical salary range?",
            "acceptedAnswer": {
              "@type": "Answer",
              "text": "Entry-level roles often range from $55k-$75k, with higher ranges for specialized analysts."
            }
          }
        ]
      },
      {
        "@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": "Data Analyst", "item": "https://www.example.com/careers/data-analyst" }
        ]
      }
    ]
    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

    Should I include salary data?

    Include estimatedSalary if your guide mentions ranges. Keep values aligned with on-page content.

    How do I handle different regions?

    Use occupationLocation for the region the guide targets. Create separate pages for other regions.

    Primary sources

    References