JSON-LD Job Posting Schema Generator

How JobPosting Schema Processing Works

This builder generates compliant JSON-LD matching the Schema.org JobPosting definitions. The script dynamically binds your inputs to key-value elements in the schema graph.

For physical locations, it populates a nested PostalAddress object containing street, city, region, postal code, and country variables. If work-from-home policy is enabled, it flags jobLocationType as TELECOMMUTE and generates `applicantLocationRequirements` variables, telling Googlebot the listing represents a remote vacancy. Salary limits are formatted under MonetaryAmount arrays with standard ISO 4217 currencies and time unit variables.

Before & After Implementation Examples

<div class="job-posting">
  <h1>Sales Manager</h1>
  <p>Location: Boston, MA. Salary: $80,000.</p>
  <p>Contact: [email protected]</p>
</div>

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "JobPosting",
  "title": "Sales Manager",
  "hiringOrganization": {
    "@type": "Organization",
    "name": "My Company"
  },
  "jobLocation": {
    "@type": "Place",
    "address": {
      "@type": "PostalAddress",
      "addressLocality": "Boston",
      "addressRegion": "MA"
    }
  }
}
</script>

Industry Use Cases

Common JobPosting Schema Mistakes

Recruitment Schema Best Practices

• Provide Base Salary: Always include salary ranges (min, max, currency, time unit) to qualify for Google Job listings prioritization filters.
• Include Detailed Descriptions: Paste complete job descriptions with full formatting tags rather than brief summaries.
• Set Valid Expirations: Always declare the validThrough tag to let bots know when to retire the listing.
• Enforce HTTPS Logos: Link only SSL-secure company logos to ensure they display correctly inside search widgets.

Frequently Asked Questions