Job Posting Structured Data: Complete Implementation Guide

Why Use JobPosting Schema?

• Surface your job listings in the Google Jobs search experience, reaching candidates directly from Google Search.
• Provide structured salary, location, and employment type details that help candidates quickly assess whether a role is relevant.
• Reduce dependency on paid job board placements by driving organic traffic to your own careers pages.
• Improve application quality by presenting clear, detailed role information before the candidate clicks through to your site.
• Support remote and hybrid role filters, ensuring your listings appear when candidates search for flexible work arrangements.

Required Properties

These properties are required by Google for JobPosting structured data to be eligible for rich results.

Recommended Properties

Adding these properties improves your chances of appearing in rich results and provides more context to search engines.

JSON-LD Example

Here is a complete JobPosting structured data example you can use as a starting point. Or use our JobPosting generator to create one automatically.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "JobPosting",
  "title": "Senior Front-End Developer",
  "description": "<p>We are looking for a Senior Front-End Developer to join our engineering team in Manchester. You will lead the development of our customer-facing web applications using React and TypeScript.</p><p><strong>Requirements:</strong></p><ul><li>5+ years of professional front-end development experience</li><li>Strong proficiency in React, TypeScript, and modern CSS</li><li>Experience with automated testing frameworks</li></ul>",
  "datePosted": "2025-09-01",
  "validThrough": "2025-10-31",
  "hiringOrganization": {
    "@type": "Organization",
    "name": "Northwind Technologies",
    "sameAs": "https://www.northwindtech.co.uk",
    "logo": "https://www.northwindtech.co.uk/logo.png"
  },
  "jobLocation": {
    "@type": "Place",
    "address": {
      "@type": "PostalAddress",
      "streetAddress": "100 Deansgate",
      "addressLocality": "Manchester",
      "addressRegion": "Greater Manchester",
      "postalCode": "M3 2GP",
      "addressCountry": "GB"
    }
  },
  "baseSalary": {
    "@type": "MonetaryAmount",
    "currency": "GBP",
    "value": {
      "@type": "QuantitativeValue",
      "minValue": 65000,
      "maxValue": 85000,
      "unitText": "YEAR"
    }
  },
  "employmentType": "FULL_TIME",
  "directApply": true
}
</script>

How to Implement JobPosting Schema

1. 1Add a JSON-LD script block to each individual job listing page. Do not place multiple JobPosting objects on a single index or category page.
2. 2Set the title to the exact role name candidates would search for. Avoid prefixing it with the company name or location — those are separate properties.
3. 3Provide a comprehensive HTML description covering responsibilities, qualifications, benefits, and application instructions.
4. 4Include the hiringOrganization with the company name, website URL, and logo to ensure proper branding in search results.
5. 5Specify jobLocation with a complete postal address. For remote positions, add jobLocationType set to TELECOMMUTE and omit the physical address.
6. 6Validate each listing with Google's Rich Results Test and monitor indexing status through the Job Postings report in Google Search Console.

Common Mistakes to Avoid

• Using internal job codes or abbreviations in the title field (e.g. 'SR FE DEV - MCR') instead of a human-readable title that matches candidate search queries.
• Placing multiple JobPosting objects on a single listing page or on category pages — Google requires one JobPosting per dedicated URL.
• Omitting the validThrough date, which can cause expired roles to continue appearing in Google Jobs and frustrate candidates.
• Providing salary information that does not match what is stated on the page, violating Google's structured data guidelines.
• Forgetting to remove or update structured data when a position is filled, leading to stale listings in search results.

Testing & Validation

Before deploying your JobPosting structured data, validate it using these tools:

1. 1Google Rich Results Test — Paste your page URL or code snippet to check if your structured data is eligible for rich results.
2. 2Schema Markup Validator — Validates your JSON-LD syntax against the schema.org specification.
3. 3Google Search Console — After deployment, monitor the Enhancements report for any errors or warnings.

Frequently Asked Questions