Job Posting Schema Generator - JSON-LD for Google for Jobs
Import existing JSON-LD
Paste JSON-LD or a full <script> tag. Matching fields fill the form; properties the form doesn't cover are kept in the output as they are.
Job Details
HTML is allowed. Include responsibilities, qualifications, and benefits.
When the posting expires. Omit if the job stays open indefinitely.
Employer
Location
Set to TELECOMMUTE for fully remote jobs.
Compensation
Whether candidates can apply directly on your site without redirecting elsewhere.
JSON-LD Output
What is JobPosting schema?
JobPosting schema is structured data that describes a single open job: the title, full description, employer, location, pay, and when the posting was published. It uses the schema.org JobPosting type in JSON-LD on the job's own page. Google reads it to include the listing in its job search experience.
Each job needs its own page and its own JobPosting block. Listing pages that show many jobs should not carry the markup; the individual job pages they link to should.
JobPosting schema example (JSON-LD)
A complete example you can adapt. Paste it into the page's HTML, or build your own with the generator above.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "JobPosting",
"title": "Senior Backend Engineer (Go)",
"description": "<p>Harbour Freight Tech is hiring a senior backend engineer to build the routing services behind our shipping platform. This role is fully remote for candidates in the United States or Canada.</p><ul><li>5+ years writing production Go</li><li>Experience with PostgreSQL and Kafka</li></ul>",
"identifier": {
"@type": "PropertyValue",
"name": "Harbour Freight Tech",
"value": "ENG-2291"
},
"datePosted": "2026-10-28",
"validThrough": "2026-12-31T23:59:59-05:00",
"employmentType": "FULL_TIME",
"hiringOrganization": {
"@type": "Organization",
"name": "Harbour Freight Tech",
"sameAs": "https://harbourfreight.tech/",
"logo": "https://harbourfreight.tech/logo.png"
},
"jobLocationType": "TELECOMMUTE",
"applicantLocationRequirements": [
{
"@type": "Country",
"name": "USA"
},
{
"@type": "Country",
"name": "Canada"
}
],
"baseSalary": {
"@type": "MonetaryAmount",
"currency": "USD",
"value": {
"@type": "QuantitativeValue",
"minValue": 150000,
"maxValue": 185000,
"unitText": "YEAR"
}
},
"directApply": true
}
</script> Which Google rich result does it enable?
JobPosting markup makes a page eligible for Google's job search experience: the expandable jobs panel that appears for searches like backend engineer jobs, with filters for location, date posted, employment type, and pay. Your listing can show your logo, salary, and a direct apply button next to postings from job boards.
Google also applies content policies on top of the markup. The job must be real and currently open, the full description must be visible without logging in, and expired jobs must have the markup removed or validThrough set in the past.
Required and recommended properties
| Property | Status | Notes |
|---|---|---|
title | Required | The job title only. No codes, salaries, or exclamation marks. |
description | Required | The full description in HTML: duties, qualifications, hours. For fully remote jobs it must say the job is fully remote. |
datePosted | Required | ISO 8601 date the job was first posted. |
hiringOrganization | Required | The employer as an Organization with a name, plus sameAs and logo if you can. |
jobLocation | Required | A Place with a PostalAddress including addressCountry. Optional for fully remote jobs that set applicantLocationRequirements. |
applicantLocationRequirements | Recommended | Where remote applicants may live, e.g. {"@type": "Country", "name": "USA"}. For states use {"@type": "State", "name": "Michigan, USA"}. |
jobLocationType | Recommended | Set to TELECOMMUTE only for 100% remote jobs. |
baseSalary | Recommended | MonetaryAmount with currency and a QuantitativeValue (single value or min/max) plus unitText like YEAR or HOUR. |
employmentType | Recommended | FULL_TIME, PART_TIME, CONTRACTOR, TEMPORARY, INTERN, VOLUNTEER, PER_DIEM, or OTHER. |
validThrough | Recommended | When the posting expires. Required in practice if the job has a closing date. |
directApply, identifier | Recommended | Whether users can apply on your page, and your internal job ID. |
Common JobPosting schema mistakes
- Marking hybrid or occasionally remote jobs as
TELECOMMUTE. Use it only when the job is fully remote, and include the office address instead for hybrid roles. - Leaving a remote job with no country at all. Add
applicantLocationRequirements, or Google falls back to the country injobLocation. - Keeping the markup live after the role is filled. Remove it or set
validThroughin the past so the listing drops out. - Putting the salary, location, or company name in the
title. - Adding JobPosting markup to a search results or category page that lists many jobs.
- Hiding the description behind a login or an application form that has to be started first.
Remote and hybrid roles
For a fully remote job, set the Remote Work field to TELECOMMUTE and add each country (or state) applicants can live in. The generator then treats Job Location as optional, which matches Google's rules. If the role is remote but tied to an office for payroll or occasional visits, you can include both the applicant countries and the office address. For hybrid roles, skip TELECOMMUTE and give the office address only, so the listing shows up for searches near that office.
Why salary is worth adding
baseSalary is only recommended, but job seekers filter
by pay, and listings without it can miss those searches. Give a range
with minValue and maxValue when you have one,
and pick the pay period that matches how the role is advertised.
California, Colorado, New York and Washington already require pay
ranges in job ads, and the EU Pay Transparency Directive requires
employers to state pay before the interview, so the markup often just
repeats what the ad already says.
Related Tools
Local Business Schema Generator
Generate LocalBusiness JSON-LD for Google Maps and local search results.
Product Schema Generator
Generate Product JSON-LD with price, availability, and review stars.
Article Schema Generator
Generate Article JSON-LD for rich results with headline and thumbnail.
FAQ Schema Generator
Generate FAQPage JSON-LD. Rich results limited to government and health sites since August 2023.