What is JobPosting structured data for?

It makes a job listing eligible for the Google Jobs experience, where roles appear in a dedicated search widget with filters for salary, location and type. This dramatically increases qualified applicant reach for free.

Is datePosted required?

Yes, Google requires datePosted in ISO 8601 date format, and validThrough is strongly recommended. Expired postings without a validThrough can linger in results, so always set an expiry.

How do I mark a job as remote?

Set jobLocationType to TELECOMMUTE and add an applicantLocationRequirements country. This builder toggles those fields when you check the remote box, while still allowing an optional base location.

How is salary structured?

Salary uses a MonetaryAmount with a nested QuantitativeValue holding minValue, maxValue, and a unitText such as HOUR, YEAR or MONTH. The tool builds this object so the format always validates.

Why does my job not appear in Google Jobs?

Common causes are a missing validThrough, an expired posting, blocked crawling, or the page not being indexed. Valid markup is required but the page must also be crawlable and the job must be current.

What is the JSON-LD JobPosting Schema Builder?

Build a valid JobPosting JSON-LD with title, description, employment type, salary range, job location, remote flag, hiring organization and validThrough date for eligibility in Google Jobs. It runs free in your browser on Gera Tools, with nothing uploaded.

JSON-LD JobPosting Schema Builder

Name: JSON-LD JobPosting Schema Builder
Creator: Gera Tools
License: https://creativecommons.org/licenses/by/4.0/

JobPosting markup for Google for Jobs

The JSON-LD JobPosting Schema Builder assembles the structured data Google needs to surface a role in its Jobs experience. Accurate markup puts your opening into a filterable widget at the top of search results — one of the highest-leverage free recruiting channels available to any employer, regardless of size.

When a job seeker searches for a role on Google, the Jobs carousel often appears above organic listings. That widget pulls entirely from structured data embedded on the source page, not from the page text itself. Without a valid JobPosting schema block, your listing is invisible to that experience no matter how well-written the page is.

How it works

The tool emits a JobPosting object at the root of a <script type="application/ld+json"> block. The key fields:

title / description / employmentType — the role name, the full job description text, and a value from Google’s allowed list such as FULL_TIME, PART_TIME, CONTRACTOR, or TEMPORARY.
datePosted / validThrough — both in ISO 8601 date format (YYYY-MM-DD). datePosted is required; validThrough is strongly recommended.
hiringOrganization — an Organization object with name, optional sameAs (your company website), and optionally a logo URL (square PNG, 112 px or larger, crawlable).
baseSalary — a MonetaryAmount wrapping a QuantitativeValue with minValue, maxValue, and a unitText of HOUR, DAY, WEEK, MONTH, or YEAR.
jobLocation — a Place with a nested PostalAddress containing streetAddress, addressLocality, addressRegion, and addressCountry.
Remote jobs — adding jobLocationType: "TELECOMMUTE" plus an applicantLocationRequirements object lets Google show the role in remote-filtered searches. The builder toggles both fields together when you check the remote box.

Example salary block

"baseSalary": {
  "@type": "MonetaryAmount",
  "currency": "USD",
  "value": {
    "@type": "QuantitativeValue",
    "minValue": 80000,
    "maxValue": 110000,
    "unitText": "YEAR"
  }
}

Practical guidance

Always set validThrough to the application deadline. Stale postings without an expiry date can linger in Google Jobs results long after the role is filled, which frustrates applicants and creates a poor brand impression. Google may also demote or remove postings it detects as stale.

Match unitText to the actual figure. If you pay £20/hour, use HOUR not YEAR. Mismatched units produce confusing salary displays in the rich result and may cause a manual review failure.

Validate before publishing. Copy the generated script tag and paste it into Google’s Rich Results Test (search.google.com/test/rich-results). It will flag any missing required fields and show a preview of how the listing will appear. The most common failure is a missing datePosted or an invalid employmentType value.

For hybrid or partially remote roles, list the physical office address in jobLocation and still add TELECOMMUTE to jobLocationType — Google supports both in the same posting, which surfaces the role in both location-filtered and remote-filtered searches.

After publishing, allow a few days for Google to crawl and index the page. Verify eligibility in Google Search Console under the Enhancements section, where job posting errors are reported per URL.