JobPosting schema markup: example, required fields and WordPress setup

JSON-LD example

Copy this into a <script type="application/ld+json"> tag and replace the values with your own.

{
  "@context": "https://schema.org",
  "@type": "JobPosting",
  "title": "Senior Line Cook",
  "description": "<p>Harbor Lane Kitchen is hiring a senior line cook to run the grill station during dinner service.</p><ul><li>3+ years of line experience</li><li>Evenings and weekends</li></ul>",
  "identifier": {
    "@type": "PropertyValue",
    "name": "Harbor Lane Kitchen",
    "value": "HLK-0412"
  },
  "datePosted": "2026-09-22",
  "validThrough": "2026-10-31T23:59:00-04:00",
  "employmentType": "FULL_TIME",
  "directApply": true,
  "hiringOrganization": {
    "@type": "Organization",
    "name": "Harbor Lane Kitchen",
    "sameAs": "https://example.com",
    "logo": "https://example.com/images/logo.png"
  },
  "jobLocation": {
    "@type": "Place",
    "address": {
      "@type": "PostalAddress",
      "streetAddress": "14 Harbor Lane",
      "addressLocality": "Portland",
      "addressRegion": "ME",
      "postalCode": "04101",
      "addressCountry": "US"
    }
  },
  "baseSalary": {
    "@type": "MonetaryAmount",
    "currency": "USD",
    "value": {
      "@type": "QuantitativeValue",
      "minValue": 24,
      "maxValue": 29,
      "unitText": "HOUR"
    }
  }
}

Properties

When to use it

Use JobPosting on a page that describes one job and lets people apply for it: a careers page entry, a job board detail page, an ATS-hosted listing on your domain.

Don't use it on:

• Job listing or search result pages that show many jobs. Only the detail page gets markup.
• Evergreen "we're always hiring" pages with no specific open role.
• Training courses, franchise offers or anything that charges the applicant. These are not job postings under Google's guidelines.

For remote roles, set jobLocationType to TELECOMMUTE and add applicantLocationRequirements. If the job is hybrid or has an office people can work from, include jobLocation too.

validThrough and the Indexing API

Expired jobs with live markup are the biggest problem on job sites. When a role closes, do one of these:

• Remove the JobPosting markup from the page.
• Remove the page, returning a 404 or 410.
• Make sure validThrough is in the past.

Then tell Google. The Indexing API lets you notify Google directly when a job page is published or removed, so it crawls the change quickly instead of waiting for normal recrawling. Google supports the Indexing API only for pages with JobPosting or livestream (BroadcastEvent inside VideoObject) markup, and it requires a Google Cloud project and a service account verified as an owner in Search Console. A sitemap with accurate lastmod dates is the fallback.

Add it in WordPress

By hand. If each job is its own post or custom post type, print the JSON-LD from wp_head using the job's fields. Many job board plugins already output JobPosting, so check the page source first to avoid duplicates.

With Hydrogen SEO. JobPosting is not among the schema types Hydrogen SEO's docs list for the Schema screen or SEO Settings sheet. Developers can append a JobPosting block with the hydrogen_seo_schemas filter, which receives the full list of schema objects before they print.

One-off markup. The free schema generator in the Hydrogen SEO app at /seo/schema-generator builds JobPosting JSON-LD with employer, location, salary and validThrough from a short form.

Common mistakes

• Salary or location in the title. Keep title to the job title.
• A description that differs from the page. The markup must match the visible posting.
• Leaving expired jobs marked up. This can lead Google to ignore your job markup.
• Remote jobs with no applicant location. Pair TELECOMMUTE with applicantLocationRequirements.
• Salary as free text. Use MonetaryAmount with a QuantitativeValue and a unitText.

See invalid structured data for help reading errors.

Test it

Paste your draft JobPosting markup into the JSON-LD validator to catch missing properties early; the published page still needs a pass through Google's Rich Results Test. Search Console has a job posting report that lists errors and warnings across all job pages. Check it after any template change, because one bad field in a template breaks every listing at once.