What properties are required for a JobPosting to appear in Google Jobs?

title, description, datePosted, validThrough, hiringOrganization and jobLocation (or jobLocationType for remote roles) are all required. Missing any one of these means Google won't consider the listing for Google Jobs, even if the rest of the markup is technically valid.

What happens if I leave an expired job posting live on my site?

Google automatically removes listings from Google Jobs once validThrough has passed, regardless of whether the page itself still returns a 200 status. Leaving expired postings unfixed for too long can also affect Google's trust in future postings from the same domain.

Do I need to include salary in JobPosting schema?

baseSalary isn't strictly required in every region, but Google strongly recommends it and some markets increasingly expect it for full eligibility in richer job result features. Where you do include it, it must be a valid MonetaryAmount with a currency and either a fixed value or a min/max range.

Where should JobPosting JSON-LD be placed?

In a tag on the actual job listing page, one block per posting. Bulk job boards should generate a unique JobPosting object per URL rather than one shared script across multiple listings.

Free tool · No signup

Job Posting Schema Generator

Build JobPosting JSON-LD with every property Google Jobs requires, so listings are eligible to appear.

Job title *

Description (HTML allowed) *

Date posted *

Valid through

Employment type

Hiring organisation *

Organisation URL

Street address

City *

Region / state

Postcode

Country code

Salary minimum

Salary maximum

Salary currency

Salary unit

JobPosting JSON-LD

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "JobPosting",
  "title": "Senior Technical SEO Manager",
  "description": "<p>Own crawl, indexation and structured data across a 40,000-URL marketplace. Work alongside engineering on rendering and site speed.</p>",
  "datePosted": "2026-06-01",
  "validThrough": "2026-08-31",
  "employmentType": "FULL_TIME",
  "hiringOrganization": {
    "@type": "Organization",
    "name": "Example Marketplace Ltd",
    "sameAs": "https://example.com"
  },
  "jobLocation": {
    "@type": "Place",
    "address": {
      "@type": "PostalAddress",
      "streetAddress": "18 Finsbury Square",
      "addressLocality": "London",
      "addressRegion": "Greater London",
      "postalCode": "EC2A 1AH",
      "addressCountry": "GB"
    }
  },
  "baseSalary": {
    "@type": "MonetaryAmount",
    "currency": "GBP",
    "value": {
      "@type": "QuantitativeValue",
      "minValue": 62000,
      "maxValue": 78000,
      "unitText": "YEAR"
    }
  }
}
</script>

Paste this block into the <head> or anywhere in the <body> of the page it describes, then confirm it parses with the JSON-LD schema validator.

In short

A job posting schema generator produces JobPosting JSON-LD with the properties Google for Jobs requires: title, description, datePosted, validThrough, hiringOrganization and jobLocation, plus employmentType and baseSalary where applicable. Missing any required property disqualifies the listing from Google Jobs entirely, and an expired validThrough date causes it to be dropped from results even if everything else is correct. Fill in the fields below to generate a complete, valid listing.

Worked example

What the output looks like

Input: Senior Backend Engineer, Acme Logistics, posted 2024-05-01, expires 2024-07-01, remote, $120,000-$150,000/year
Output: { "@context": "https://schema.org", "@type": "JobPosting", "title": "Senior Backend Engineer", "description": "Design and maintain distributed systems powering our logistics platform.", "datePosted": "2024-05-01", "validThrough": "2024-07-01T00:00:00Z", "employmentType": "FULL_TIME", "hiringOrganization": { "@type": "Organization", "name": "Acme Logistics", "sameAs": "https://acmelogistics.com" }, "jobLocationType": "TELECOMMUTE", "baseSalary": { "@type": "MonetaryAmount", "currency": "USD", "value": { "@type": "QuantitativeValue", "minValue": 120000, "maxValue": 150000, "unitText": "YEAR" } } }
How to read it: For a remote role, jobLocationType is set to TELECOMMUTE and jobLocation can be omitted or replaced with applicantLocationRequirements — check that validThrough is a full ISO 8601 datetime, since a date-only string is sometimes rejected.

How it works

Enter the core job details

Provide the job title, a full description, the date posted, and an expiry date in validThrough. Google removes listings automatically once validThrough passes, so this date must be kept current.

Add the organization and location

Fill in hiringOrganization with the company name and logo, and jobLocation with a structured street address. Remote roles use jobLocationType instead of a physical address.

Specify salary and employment type

Add baseSalary as a value or range with a currency code and pay period, and select employmentType such as FULL_TIME or CONTRACTOR. The tool nests these correctly as required by Google's job posting schema.

What this tool does

Generates JobPosting markup with title, description, datePosted and validThrough
Structures hiringOrganization and jobLocation to Google Jobs' exact format
Builds baseSalary as a nested MonetaryAmount with currency and pay period
Flags missing required fields before you publish the listing

Questions

Frequently asked

More free SEO tools

Learn the concept

What is Schema Markup?

Track visibility for your career and job listing pages

LemRank tracks rankings, backlinks, and AI-search visibility in one dashboard. 14-day free Pro trial. No credit card.